Why I built Mealhive

For a long time, our household had the same conversation twice a week. Usually on the way to the supermarket, sometimes in the car park before we walked in.

“What should we cook?” “I don’t know. What did we have last time?”

The answer was always the meal we’d eaten on Tuesday. Never the one we’d loved on a Thursday three weeks before, the one we’d kept meaning to make again and somehow never did. The repertoire we actually had was much bigger than the one we could remember at 5pm on a Saturday standing in the dairy aisle.

So we’d cook the Tuesday thing again. Or we’d improvise around what was on offer. Or we’d give up and order takeout when we got home because nobody felt like deciding anymore.

That’s the problem Mealhive is built around.

What we actually wanted

Two things, really.

The forgotten amazing meals to come back. Not “more recipes”. Not a content library of 10,000 dishes I’ll never make. The fifteen or twenty I actually rotate, plus the new ones I want to try this week, all in one place, where I can browse them when it’s time to plan.

One shop a week instead of two. We do food shopping two times a week right now, partly because we plan on the fly and run out of things, partly because the plan changes mid-week and the second shop fills the gap. If we can plan the whole week confidently on Sunday and walk in to the supermarket once with a list that covers everything, that’s an hour and a half a week back, plus a chunk of cognitive load.

The grocery list that writes itself, scaled to the number of people we’re cooking for, with anything already in the pantry subtracted out. That’s the bit that turns two trips into one.

The smaller bet underneath

The bet I keep coming back to is this: most weeks don’t need a brilliant meal plan. They need a few dishes we already like, in an order that’s easy to shop for. The wins are small and weekly, not big and one-off.

Most meal-planning apps are built around the opposite assumption: that the problem is “what should we cook?” and the solution is more recipes. The problem for us was never more recipes. It was less friction between the dishes we already loved and the dinner that actually landed on the table.

I like cooking. Marinades that sit overnight, the grill on the patio on a Saturday, slow-baking something on a Sunday afternoon, working through a new technique on a Tuesday. The cooking part of cooking is the part I want to spend more time on. The deciding-what-to-cook-and-realising-we-don’t-have-half-of-it part is the part I want gone.

That’s most of what Mealhive is. A way to keep the recipes we love in one place. A way to plan a week with them in five minutes. A grocery list that builds itself. A pantry that knows what’s in it. A cook mode that walks through the steps with the screen on and the timers running, so we can stay on the pan.

Nothing in there is novel on its own. The bet is that wiring them into one loop (capture, plan, cook, pantry) makes the whole thing feel different. So far, for us, it has.

What you can do today

We’re in closed beta while we tune the experience with a small group. If you want in, get on the waitlist and we’ll send an invite when we open the next round.

If you’re already in, the things I’d love feedback on right now: how the capture flow feels for the kinds of recipes you save, how the grocery list reads when you’re actually shopping, and whether the household sync gets the right thing onto your partner’s phone at the right time.

Write to hello@mealhive.app. I read every message.