Work · 003 · Live Health & consumer
Case study · Peri Happy

A week of meals for your household, in thirty seconds.

Peri Happy is a nutrition platform for perimenopause and beyond, with more than 550 evidence-based recipes organised by symptom and a weekly email read by 15,000 women. Labs turned the recipe library into the Peri Planner: a weekly food plan that respects your diet, your family and your symptoms, with a shopping list, and that you can change by typing what you actually want.

Speed
30sto plan a week for a whole household
Library
550+recipes indexed by symptom, diet and ingredient
Delivery
1 mofrom concept to live, September 2026
01
Context

Great recipes, and the same question every Sunday

Peri Happy's readers trusted the recipes. What they didn't have was time: a week of meals that suits a woman managing symptoms, a partner who eats differently, two children and a budget is a planning problem, not a browsing problem. Every recipe site has a search box. Almost none of them will tell you what to cook on Thursday.

perihappy.com homepage: Food that works with youperihappy.com
02
What we built

The Peri Planner

Every recipe indexed and made available to a weekly planner that takes diet, family size and current symptoms and produces a week: seven days of meals, a shopping list, and a breakdown of each meal. Then the part that makes it feel like a person rather than a filter: you tailor it by typing. “I want fish tonight but no one else eats it” swaps one plate and leaves the rest alone. Community tooling sits alongside, so the plan is something to talk about, not just download.

The Peri Planner: a vegetarian week for two, with the plan, shopping list and a recipe openPeri Planner · your week
03
How

Constraints first, then language

Planning is a constraint problem before it's a language problem, so the planner solves diet, symptom and household constraints deterministically over the indexed library, and uses models for the parts that need them: understanding a typed request, explaining a swap, writing the breakdown. Multi-model, chosen per task. The whole thing runs on Edge Compute behind Peri Happy's site, which their team deploys and manages through Edge's agentic tooling.

Every recipe, your way: the recipe collection with the Peri Planner promptRecipes · filter by symptom
04
What changed

The library became a service

Live in September 2026, one month after the concept was agreed. Planning a week that used to take an evening of browsing and a notepad takes thirty seconds, and gets better the more precisely a reader says what they want. For Peri Happy, a content site gained a product: something to build membership around, and a reason for 15,000 weekly readers to come back midweek.

05
What's next

Plans that learn, and a planner that shops

Handed to Edge Expert Services to run. The next concepts on the table: plans that remember what a household actually cooked and liked, symptom tracking that feeds the planner, and a shopping list that fills a basket at the reader's supermarket rather than describing one. Labs stays alongside the team as their R&D partner.

In their words

“We describe what we want and it's live minutes later. We spend our time on recipes and research, not infrastructure.”

Founding team · Peri Happy
Client
Peri Happy, perihappy.com
Sector
Health & consumer · Nutrition and community
Status
Live, launched September 2026
Build
One month, concept to live
Labs' role
Report → concept and spec → build → handover
Now run by
Edge Expert Services, deployed through Edge's agentic tooling
Stack
Multi-model planner · Constraint solving over an indexed library · Edge Compute, CDN, DNS and Shield

Turn content into a product.

If you publish something people trust, there's probably a service hiding inside it. A month is often enough to find out.

Talk to Edge Labs