Who hurts
People on a nutrition plan with a real grocery budget — students, families, anyone cutting.
The problem
Meal planners generate recipes without prices. The plan costs 40% more than the user's budget, they abandon it in week two, and blame themselves.
What you build
Plan against live prices from the user's chosen store, optimise for cost per gram of protein, reuse ingredients across meals to kill waste, and output one ordered shopping list.
Why now
Several grocery chains expose price and availability APIs, and delivery services have made basket-level pricing routine.
Validate it this week
One city, one chain, one dietary goal. If people don't re-run it in week two, the plan didn't survive contact with their kitchen.
Why you'd keep winning
Price data coverage per region, which is genuinely annoying to assemble and maintain.
The honest risk
Grocery data access is fragile and often unofficial. Have a manual-price fallback or the product dies with an API change.
The prompt is written to make an AI argue with you before it writes code — that first round of pushback is worth more than the scaffold.