title: "Why I Built Juvelle" date: "2026-03-01" excerpt: "Every night I was making three different dinners for four people in the same household. That's when I knew something had to change." category: "Behind the Scenes" coverColor: "terracotta"
I want to tell you about a Tuesday night in October that broke me.
It was 6:47 PM. My husband Marcus was in the kitchen with a measuring scale, weighing out 250 grams of ground turkey for his bulk. My daughter Lily, who's eleven and plays competitive soccer, was asking for "more pasta because coach said carbs." My son Theo, who's eight and has recently decided that basically all vegetables are "disgusting," was refusing the broccoli I'd served him. And I was standing there holding a spatula, wondering when exactly dinner became a logistics operation that required three separate meal plans.
That was the moment I started thinking about building Juvelle.
The Problem Nobody Talks About
Here's the thing about family nutrition advice: most of it assumes your family has identical needs. "Make healthy meals for your family!" Sure. Great. But which family? The one where dad is actively trying to put on muscle, where your daughter burns 800 calories at soccer practice three times a week, where your younger kid is going through a phase where he'll only eat beige foods?
That Tuesday night I had made what I thought was a perfectly reasonable dinner — a sheet pan situation with salmon, roasted vegetables, and quinoa. Except:
- Marcus needed more protein and wanted to track his macros precisely
- Lily needed double the carbs because she had practice at 7 PM
- Theo needed... not the vegetables, apparently, or the salmon, or the quinoa
- And I honestly just wanted to eat something without doing math
I ended up making four slightly different versions of the same meal. It took an hour. Nobody was particularly happy. I was exhausted.
This was not a one-time thing. This was every night.
The Spreadsheet Era
Being the person I am, I tried to solve this with a spreadsheet.
I built a Google Sheet with each family member's nutritional targets — Marcus's macros from his coach, Lily's increased caloric needs on practice days versus rest days, general pediatric guidelines for Theo, and my own goals. I color-coded it. I made formulas. I was genuinely proud of this spreadsheet.
It lasted about three weeks before I abandoned it entirely. The problem wasn't the data — the problem was that translating that data into actual meals, with actual grocery lists, for actual humans who have preferences and moods and the occasional "I don't want that tonight," was still entirely manual work. The spreadsheet told me that Lily needed 180 grams of carbohydrates on a training day. It did not tell me how to turn that into dinner.
I tried meal planning apps. I tried nutrition tracking apps. I tried family recipe sites. Nothing was built for a household where multiple people had different, simultaneous nutritional goals that needed to be met with the same base ingredients, roughly at the same time, without requiring me to have a culinary degree.
What I Actually Wanted
I wanted an app that understood that my family is not a monolith.
I wanted something that could say: here's a dinner that works for all four of you — same base meal, but Marcus gets this portion, Lily gets this portion on Tuesdays and Thursdays, and Theo's version has the vegetables on the side so he can decide. And here's your grocery list, already organized, and it accounts for the fact that you already have half a bag of quinoa in the pantry.
I wanted the app to know that "family dinner" doesn't mean everyone eats the exact same thing in the exact same amount. It means everyone gets what they need, ideally from the same pot.
And I wanted the grocery ordering to just... happen. Because by the time I've figured out five nights of meals for four people with different needs, I have absolutely zero energy left to also navigate a grocery app.
Building It
I'm a software engineer by training. My background is in data systems. When I couldn't find the app I wanted, I started building a prototype.
Marcus thought I was procrastinating on dinner when he first saw me sketching out the data model on a whiteboard in our kitchen. (Fair.) But he was also the first real user, and his feedback — "it needs to actually understand that I'm in a bulking phase, not just that I want protein" — shaped a lot of the early decisions.
The hardest part wasn't the technology. The hardest part was the personalization model. People's nutritional needs aren't just about a static calorie target. They change based on activity, based on goals that evolve, based on whether it's a rest day or a training day, based on age and growth stages for kids. Building something that could hold all of that complexity and still produce a coherent meal plan — that was the real challenge.
The grocery integration came later, and honestly it transformed the whole experience. Knowing that the meal plan would automatically generate a grocery order meant I could plan for the week in about ten minutes on Sunday morning and not think about it again.
Why I'm Sharing This
I'm not sharing this because Juvelle is finished. It's not. We're still building.
I'm sharing it because if you've stood in your kitchen at 6:47 PM on a Tuesday wondering why dinner became this complicated, I want you to know you're not alone in that feeling. The standard nutrition and meal planning tools were built for individuals, or for identical families, not for the actual households most of us live in — messy, multi-goal, full of people with different needs who somehow still want to eat together.
That's what we're building Juvelle for. The household that doesn't fit neatly into any one meal plan.
If that's you, welcome. We're glad you're here.
— Amanda