Stories

Operational proof, not customer testimonials.

What TrainedBy actually does inside a coach's week — Monday triage, failed-card recovery, weekly check-ins, Snap days, body- scan reads, week-1 lock-in, public Coach Page → pre-onboarding, and what 30+ clients on one cockpit looks like.

How to read this page

What this page is — and what it is deliberately not.

Most software stories pages lead with customer quotes. This one does not. Customer story assets that meet TrainedBy's editorial bar — real coaches, attributable, accurate — will live here when they're ready to publish. Until then, this page shows what the product does inside a real coaching week, in the same plain-language register the rest of the site uses. Each vignette below is product proof: what the surface looks like, what the coach sees, what the workflow actually produces.

No quotes, no fabricated names, no transformation-photo composites staged for marketing. When real customer stories are published here, they will be attributable, accurate, and clearly framed as customer stories — not as the operational proof below.

Monday triage

What a Monday inside the Weekly Cockpit looks like.

Every active client lands as a row in the cockpit. The week is already triaged before the coach reads a single message. At-risk clients sit at the top with the reason flagged next to them; quiet clients sit at the bottom because no news is good news.

Top of the list
At-risk clients first — adherence drift, missed check-in, payment failure, plateau detection. Each row carries the specific signal that flagged it.
Middle of the list
Plateaued or attention-needed rows — clients whose data this week isn't bad but isn't moving either. The decision queue, not the panic queue.
Bottom of the list
On-track clients — pushed down deliberately. The cockpit treats no news as good news so the coach's energy goes where it earns retention.

The coach starts the week knowing whose week is theirs to fix, not whose week is theirs to remember.

See Weekly Cockpit →

Failed-card recovery

What a failed Stripe charge actually looks like, end to end.

A renewal card declines on a Tuesday. On a manual stack the coach finds out two weeks later, sometimes after the client has already drifted. Inside TrainedBy, the failure is a flagged cockpit row by lunchtime.

Day 0 — the cockpit flags it
Stripe's first attempt fails. The subscription enters Stripe's recovery state. The cockpit surfaces the row immediately with the client name and amount — no manual reconciliation.
Day 0–7 — Stripe's retry cadence runs
Stripe retries on its standard recovery schedule. The client gets a branded automated prompt to update the card in-app. The coach does not chase money; the system does.
Day 2–3 — optional coach nudge
If the row is still flagged after Stripe's first prompt, the coach sends one short coaching-register message — "Stripe couldn't charge your card on Monday — quick update needed in the app." Not collections. Coaching.
Recovery — the row clears
Card updated, Stripe re-charges automatically, cockpit row clears. The coaching relationship never had to be the awkward one.

The recovery flow is built on Stripe Connect with a 0% TrainedBy platform fee. The coach finds out on day one, not week three.

See payments →

Reading a check-in

What 90 seconds of weekly check-in review actually looks like.

Eight short answers — weight and photos, adherence rating, energy/sleep/hunger/mood, steps, training quality, what got hard, what worked, question for me. The coach reads them as one signal block, not eight separate questions.

First read — 30 seconds
Numbers and trends. Weight average, adherence rating, step count, sleep score. Is this a clean week or a complicated one?
Second read — 30 seconds
The two written paragraphs — what got hard, what worked. This is where retention saves usually live. The hardest answer of the week is almost always the most useful for next week's plan.
Reply — 30 seconds
Two parts: one observation about progress, one specific change for the week ahead. Voice note for flagged clients, written for on-track ones. "Strong week, keep the plan" is a real reply when it's true.

Eight questions, ninety seconds, one structured reply. That is what a serious weekly cadence runs on.

Read the check-in playbook →

Snap day

What a Snap nutrition day shows the coach.

The client photographs each meal. TrainedBy reads the ingredients and returns estimated macros. The day writes itself, meal by meal, and the coach sees the reality, not the reported version.

Plan meals logged
Breakfast, lunch, pre-training snack, dinner. Each entry has a photo, the detected ingredients, and macros estimated per meal.
Extras logged
Two digestive biscuits at 4pm. A flat white with full-fat milk at 11am. Off-plan dinner Saturday. Each one captured because the photo log makes it cheap, not because the client confessed.
Day total vs target
Target was 1,900 kcal. Actual day was 2,150 kcal — within range, but the extras were the difference. The coach sees the gap that explains a stalled scale.

Macros are estimates, not clinical figures. The point is the realistic picture of what was eaten, not a number for the client to chase.

See Snap →

Weekly body-scan read

What an AI Body Scan read looks like on a scale-flat week.

Three weekly photos — front, side, back. The scan reads them as a per-region picture, not as a single number. On a week where the scale didn't move, the read is what tells the client they are progressing anyway.

Per-region muscle definition
Definition scored across the major groups — upper back, shoulders, arms, abs, legs. The coach can name which region came up and which held flat.
Symmetry and posture
Side-by-side comparison surfaces posture changes and symmetry shifts the scale cannot see. Useful especially in fat-loss plateaus and recomp phases.
Body-composition signal
A directional body-fat estimate. Useful as a trend, not as a clinical figure — coaching signal, not DEXA.

A clearer mirror for the client when the scale is doing nothing this week. A coaching signal layer, never a clinic.

See AI Body Scan →

First weekly review

What a Day 7 first weekly review looks like.

End of week one. The client has logged six days of training and nutrition, sent three photos, and submitted their first short check-in. The coach replies with the first review that feels like real coaching, not onboarding admin.

Observation
One specific note from the data. "Strong first week — your bench warm-ups looked tentative on Tuesday, and your protein landed under target on Thursday."
Change
One specific direction for next week. "Next week we lift bench working sets from 65% to 70%, and we move your Thursday afternoon snack 30 minutes earlier so the protein anchor lands."
Why
One sentence on the reasoning. "This is how we get past the first plateau — small, deliberate moves once the data tells us where to push."

By Day 7, the client has crossed from "trying coaching" to "doing coaching." That is what locks in retention through month 2.

Read the lock-in sequence →

Pre-onboarding handoff

What public Coach Page → pre-onboarding looks like end-to-end.

The coach has a public page at trainedby.fit/@yourname (or their own domain). The page sells the offer. The CTA hands the prospect into the structured pre-onboarding flow inside TrainedBy. The page sells; pre-onboarding closes.

Public Coach Page
Hero, positioning, who the coaching is for, what's included, optional transformations, optional testimonials, application copy, footer credibility row. The page structure is fixed so every Coach Page stays consistent and credible.
CTA → pre-onboarding
One clear CTA into the pre-onboarding flow. Application or open signup — coach's choice. The prospect sees pricing, completes intake, pays through Stripe Connect, and lands in the app.
Saved lead data
Lead data captured along the way is saved for follow-up. The coach can re-engage prospects who didn't convert without rebuilding the conversation from scratch.

One link, from public page to onboarded client, with no third-party form embed and no Stripe link being pasted into a DM.

See Coach Page →

30+ clients, one cockpit

What a 30-client roster looks like inside the operating surface.

On a manual stack at 30+ clients the coach is the integration layer between WhatsApp, Sheets, Stripe links, and a Notion roster. Inside TrainedBy, every active client is a row, every signal lands in the cockpit, and the week triages itself.

One ranked list
Every active client, ranked by what needs the coach's attention. At-risk first, plateaued second, on-track last.
Signals consolidated
Adherence drift, missed check-ins, anomaly detection on the latest check-in, payment failures, plateau detection. All of them surface as cockpit rows, not as separate inboxes.
Memory replaced by surface
Replaces "I'll remember" with "the cockpit remembered." Roster size stops being a memory test.

That is what makes the difference between a 30-client roster that feels heavy and one that runs cleanly.

Read the migration playbook →

Where to keep reading.

Stories show what the surface does in practice. The pages below are where the system, the category, and the pricing live.

See the system the stories are about.

Coach Page, Weekly Cockpit, Snap, AI Body Scan, Stripe Connect direct, 0% TrainedBy platform fee — all on one account.

See pricing