01
Snap
The plate is the log.
Snap is TrainedBy's photo-first meal logging surface. The client photographs the meal. TrainedBy reads the ingredients and macros and writes the day. The coach gets a cleaner read on what was actually eaten — not what the client remembered to type.
01 · Snap
Uploaded 12:40pm
02 · Analysing
Reading ingredients
03 · Logged
Chicken thigh, rice, tenderstem
+44g protein on the day
02
The input
One photo. That's the log.
The client opens the app, snaps the plate, confirms. That's the whole entry. No food search, no manual macro input, no four-step diet-app interaction for every meal. The friction that kills logging on day three is gone by design.
- Snap a meal photo from the client app.
- TrainedBy detects the ingredients and returns macros — protein, carbs, fat, calories.
- Quantities adjustable in a tap if a portion looks off.
03
The output
The day, written from what was actually eaten.
Snap returns a structured read of the meal — ingredients identified, macros estimated, timestamped, attached to the day. The coach doesn't open a separate nutrition tab to see what's happening. The day writes itself, meal by meal, from the photos the client already took.
- Ingredients detected per meal.
- Macros estimated per meal — protein, carbs, fat, calories.
- The day's running totals visible to both coach and client.
- Confidence flagged on each detection, so a low-confidence meal gets reviewed instead of trusted blindly.
- Stored alongside the rest of the client's nutrition record, not in a separate tracker.
04
Why it matters
A camera is harder to lie to than a food search bar.
Manual logging dies the same death every time. The client logs three perfect days, then forgets the cookies on day four, then “rounds down” the rice on day five, then stops opening the app by week two. Snap removes most of that gap. There's no honest way to leave the cookies out when you're already pointing a camera at the plate.
- Less omission. The photo records what the manual entry would have skipped.
- Less drift. A two-second snap beats a two-minute search-and-type.
- Less performance. The log starts looking like the eating, not like what the client thinks the coach wants to see.
05
In the workflow
Wired into nutrition coaching, not bolted onto it.
Snap doesn't sit in a separate logging app. It feeds the same nutrition surface the plan was built on — meal templates, macro targets, day-and-week totals, the trend. The coach reviews adherence in the same place they wrote the plan, against the same numbers.
- Logged meals roll up into the day, the week, and the trend.
- Adherence visible in the Weekly Cockpit alongside the rest of the client's signal.
- Coach approvals, swaps, and adjustments live in the same surface.
06
Honest framing
Not a calorie counter. Not a diet app.
Snap is built for coaching, not consumer weight loss. It isn't a streak-driven habit tracker, isn't a marketplace for meal plans, isn't a wellness brand wrapped around a macro counter. The estimates are estimates — directional, useful for tracking adherence over time, not clinical figures. The point isn't perfect numbers. It's a more honest signal a coach can actually coach against.
- Not a consumer diet app. No leaderboard, no streak, no “complete day” badge.
- Macros are estimated. The value is consistency over time, not laboratory accuracy.
- Best read alongside scale weight, training output, and check-in answers — not as a standalone score.
07
What it unlocks
Less friction for the client. Better signal for the coach.
For the client, Snap is the difference between a log they keep and a log they abandon by week three. For the coach, it's the difference between coaching from what was actually eaten and coaching from what the client remembered to write down. Same input, both jobs, every meal. The clients who actually log are the clients who actually adhere.
08
Common questions on Snap.
What does the client actually do?
Open the app, snap the plate, confirm. That's the entry. No food search, no manual macro input.
How accurate are the macros?
Estimated. Useful for tracking adherence and trends over time. The point is consistency, not clinical precision.
What if a detection is wrong?
Confidence is flagged on each meal. The client can adjust portions or correct an ingredient in a tap, and low-confidence meals are easy for the coach to review.
Does the client still need a food database?
Snap is photo-first. Direct food search is there for things a photo can't capture — a protein shake, a supplement, a meal eaten away from the camera.
Where does the data live?
In the client's nutrition record inside TrainedBy, alongside the plan, the macro targets, and the trend. Visible to both coach and client.
Is this a calorie-counting app?
No. Snap is a coaching input. Macro estimates are directional. The value is the realistic picture of what was eaten — not a number for the client to chase.
09
Built for coaches who'd rather see the meal than read about it.
Snap gives you that picture, every meal, every client.