Plan
The week decided up front from your macro targets and training schedule. Logging-after-the-fact isn’t the workflow.
Planning-first · For athletes
Plan the week. Don’t log it. Mero is a planning-first alternative for athletes who already know their macros — a weekly meal plan, grocery list, prep workflow, and daily checklist generated around your training calendar. Decided up front, not reconstructed after dinner.
Why a diary stops being enough
“MyFitnessPal tells me what I ate.
I don’t need a record — I need a plan.”
Diary-style apps were built for retrospective tracking: a barcode database, a long search field, a calorie burn-down for the day. That’s the right tool when you want to react and log. It’s the wrong tool when the actual job is deciding what to eat in the first place — which meal, in what order, around which training day, with what bought and prepped on Sunday.
Logging vs planning
A logger reconstructs the day after the day happened. A planner decides it in advance. Mero is built for the second question: what should this week look like, what should you buy, what should you prep, and what should you tap as you go.
A food diary (e.g. MyFitnessPal)
A planner (Mero)
DECIDED UP FRONT · TAPPED AS YOU GO
How Mero works
The week decided up front from your macro targets and training schedule. Logging-after-the-fact isn’t the workflow.
Generated from the plan. Aisle-grouped. Reconciled across recipes. Not assembled by hand on Saturday morning.
Sunday output that turns the plan into food. Batch-friendly meals grouped; single-serves stay daily.
Tap planned meals as you eat. Daily macros add up as a side-effect — not as the goal of opening the app.
Next week reflects what you actually ate, not what you logged. The plan gets better as the data does.
Built for
What Mero focuses on instead
The starting library covers the patterns most macro-aware athletes default to, with portion math handled per meal — instead of a 600,000-food database optimized for after-the-fact search. Tracking happens as a side-effect of executing the plan, not as the main job of opening the app.
FAQ
Barcode scanning isn’t in the first release. The default workflow is tapping planned meals, not searching a food database mid-meal. The week is decided up front.
Yes. The today view shows where you stand against the day’s targets in real time as you tap meals. The math adds up as a side-effect of executing the plan.
Importing custom foods isn’t in the first release. The starting library covers the patterns most macro-aware athletes default to, with portion math handled per meal.
Off-plan meals can be logged against the day’s remaining targets. The plan stays intact; the today view shows the deviation so you can decide whether the rest of the day needs to adjust.
If tracking is working for you, you don’t need to switch. The planner is built for athletes whose week is structured — training, prep, groceries — and who want that structure decided before the week starts instead of reconstructed after dinner.
Yes, within scope. The plan is shaped by your goal, training, default eating pattern, and any allergies you flag at onboarding. Specialized medical or therapeutic diets aren’t covered in the first release.
Both are planned. Mero is being built for iOS and Android. Early-access members hear platform timing first.
More general questions? See the main FAQ on the Mero homepage — or the training meal plan app page for training-specific questions.
Join the waitlist
One email gets you first-batch access the day Mero opens, plus the first word on pricing and launch timing. No drip. No noise.