Training meal plan app · For athletes

A training meal plan app built around your week

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.

One email. We’ll only write when there’s something real to say.

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

The plan responds to the week. It doesn’t paste the same one over it.

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.

  • Hard intervals or strength. Higher-carb meals bracket the session. Total calories rise on hard days when the goal calls for it.
  • Recovery days. Protein steady. Carbs settle and shift toward vegetables and slower-burning starches.
  • AM vs PM training. A morning session gets a different pre/post structure than a 6 PM one. Same total, different timing.
  • Two-a-days and long days. Combined output is calculated; fueling blocks land around each session, not just at the end of the day.
  • Deload weeks. Carbs and calories proportionally drop. Protein holds. Same shape, lower volume.

INTERVALS · STRENGTH · LONG · RECOVERY · REST

What the app builds

Plan, grocery, prep, today — tied to your training week.

1

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.

2

Grocery

One aisle-grouped list, quantities reconciled across recipes, ready Sunday. The list reflects the training shape of the week.

3

Prep

A Sunday prep workflow that fuels the next week’s hard days first, ordered by oven cycle and active time.

4

Today

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.

Mero Today screen showing meals, macro progress, and checklist status
Today · macros · meal checklist

Tracker vs planner

A tracker tells you what happened.
A planner tells you what to do.

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

  • Tells you what you ate, after the meal.
  • Treats every day as the same daily total.
  • Resets to zero each Monday.
  • Leaves planning and prep to you.

A training meal plan app (Mero)

  • Tells you what to eat, before the week starts.
  • Shapes carbs and calories around your training calendar.
  • Carries last week’s learning into next week.
  • Generates the grocery list and Sunday prep workflow.

Built for

Athletes with a real training schedule and a week that isn’t flat.

  • Endurance with structure. Intervals, threshold, long, recovery, rest. The food layer matches the training layer.
  • Strength athletes with periodized cycles. Volume phases, intensity blocks, deloads. The plan moves with the cycle.
  • Hybrid athletes. A run AM, a lift PM, a long day Saturday. Two-a-days and combined-output days handled.
  • Macro-aware athletes. You know your target. You want a planner that takes the training shape into account.

FAQ

Questions about training-aware planning.

How does carb placement work across a training day?

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.

What counts as a hard day versus a recovery day?

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.

What if I have two sessions in one day?

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.

Does the plan adjust if a session moves during the week?

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.

Can I sync from Strava, TrainingPeaks, or a coach’s calendar?

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.

Does the plan change for a deload week?

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.

Will it work on iOS and Android?

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

Plan around the week you actually train.

One email gets you first-batch access the day Mero opens, plus the first word on pricing and launch timing. No drip. No noise.

No spam. No drip campaign theater. Unsubscribe in one click.