Plan
Meals shaped by the training week, not a flat daily total. Higher carbs land on the high-output days. Recovery foods sit next to the harder sessions.
Training meal plan app · For athletes
Hard days, recovery days, rest days — fueled separately. Mero plans the meals, groceries, prep workflow, and daily checklist around your training calendar, not a flat daily target. Carbs land where they’re needed. Recovery sits next to the hard sessions. The plan tunes itself each Sunday.
Why a flat target stops working
“Wednesday is a rest day.
Why is my app still asking for the same 350g of carbs?”
Most macro apps treat every day the same. One total, applied flat. That works when training is steady — and stops working the second your week is actually shaped: hard intervals Monday, strength Tuesday, recovery Wednesday, AM session Thursday, long run Saturday. The food layer has to match the training layer.
The training calendar is the input
Mero asks for your training week at onboarding. Hard days run higher carbs and more total calories (if the goal calls for it). Recovery days hold protein, redistribute the carbs, and tilt toward vegetables. Rest days settle. AM sessions get a different pre/post structure than PM sessions. The plan rebuilds when the week changes.
INTERVALS · STRENGTH · LONG · RECOVERY · REST
What the app builds
Meals shaped by the training week, not a flat daily total. Higher carbs land on the high-output days. Recovery foods sit next to the harder sessions.
One aisle-grouped list, quantities reconciled across recipes, ready Sunday. The list reflects the training shape of the week.
A Sunday prep workflow that fuels the next week’s hard days first, ordered by oven cycle and active time.
A daily view with the day’s training context built in. Tap meals as you eat. See where you stand against the day’s targets without a barcode hunt.
Tracker vs planner
Both have a place. A tracker is the right tool for retrospective logging. A training-aware planner is the right tool when the week is shaped and you want it designed up front.
A macro tracker
A training meal plan app (Mero)
Built for
FAQ
The day is split around the session. A pre-training block sets up the work; a post-training block covers recovery; the rest is distributed across remaining meals. AM and PM training get different shapes — same daily total, different timing.
You tag each session at onboarding — intervals, threshold, long, strength, recovery, rest. Each tag carries default carb and calorie modifiers; you can override per session if you want finer control.
Two-a-days are supported. Mero treats them as a single high-output day for total carbs and calories, then places fueling blocks around each session so neither one starves the other.
Yes. Drop the session into a different slot and the plan reshapes the day. The grocery list flags any ingredient swaps you need to pick up; the prep workflow stays intact.
Sync integrations aren’t in the first release. Manual training entry is the default. Calendar sync is on the post-launch roadmap; early-access members hear timing first.
Yes. Deload weeks redistribute carbs and calories proportionally — protein holds steady, total volume drops with the training. Set the week’s training type and the plan responds.
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.
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.