Hey IH đź‘‹
I’ve just launched Grubl — an AI-powered cooking assistant designed to solve one very real problem:
The daily “what’s for dinner?” decision.
I realised dinner isn’t really a recipe problem — it’s a decision fatigue problem.
Most cooking apps are just static recipe libraries. They don’t think about:
What’s already in your fridge
Your budget this week
Busy nights vs relaxed weekends
Hitting macro targets
Reducing food waste
Or the fact that you’re tired at 6pm
So I built something different.
Grubl can:
Generate recipes from your mood or ingredients
Turn fridge chaos into meal ideas
Plan your entire week in minutes
Auto-generate shopping lists
Adjust recipes to hit nutrition goals
Help live while you cook
Learn your taste over time
Under the hood it’s structured AI + ingredient logic + personalisation layers. On the surface, it’s playful and conversational.
A few things surprised me while building it:
Meal planning is way more complex than recipe generation. Optimising for ingredient reuse and budget is tricky.
Users care more about reducing stress than discovering new recipes.
What I’m currently unsure about:
Should I niche down to busy families first?
Or keep it broad and let the use cases sort themselves out?
Is the positioning clear enough on the landing page?
What would make you actually pay for this?
Would genuinely love feedback from builders here.
Site: https://grubl.app