Who this is for

Triathletes, from sprint to long course, who track sessions with a wearable or Strava.

Three common problems

  1. Double days and uneven loads

    A brick day and a swim-only day need different amounts of food; averages hide that.

  2. Fuelling a long race

    Race-week carbohydrate and race-morning eating are easy to get wrong when nerves are high.

  3. Losing fat without losing the season

    A deficit across a build phase can cost training quality if it does not move with the load.

How Sweatmeal handles them

  1. Each day on its own load

    Targets follow the burn your wearable measured, so a brick day and a recovery swim get different numbers.

  2. Race calendar

    Put the race in the calendar and the carbohydrate floor lifts before it.

  3. Recovery in the loop

    On Whoop, Oura or Ultrahuman, low recovery eases the deficit for that day.

The method is on the methodology page. Targets, wearable sync, trends and the race calendar are free; logging and the AI coach are Pro.