All systems

LoopraFitness & coaching

One roster. Every signal. The right client, at the right time.

Loopra turns plans, check-ins, progress and payments into one coaching rhythm, so silence surfaces before it becomes churn.

Built for the next check-in
Live product
The coach command centre: today’s priorities, completion rate, revenue snapshot and live client activity.
The coach command centre: today’s priorities, completion rate, revenue snapshot and live client activity.
The bottleneck

Programmes, check-ins, payments and progress were split across four apps.

The workflow

Plan → client check-in → attention signal → coach intervention.

The shift

A larger roster with fewer status messages and earlier action on quiet clients.

1
Coach workspace
3
Languages supported
AI
Ask Loopra included
Mobile
Client portal included
01

What the floor actually looked like

The coaches we shadowed were excellent at coaching and drowning in administration. Programmes lived in one spreadsheet, macros in another, check-ins arrived as voice notes and photographs across three messaging apps, and progress existed mainly in the coach’s memory.

The failure mode was never dramatic. A client would simply stop replying for eleven days, and by the time anyone noticed, they had already decided to cancel. The information needed to catch that was technically present. It was just spread across four apps and nobody had time to assemble it.

02

What we changed

Loopra puts the whole roster on one screen ordered by who needs attention, not alphabetically. Adherence velocity, the rate of change in a client’s check-in behaviour, is the sort key, so silence surfaces before it becomes churn.

Programmes, macro targets and habit streaks live in the same record as the check-in that reports against them. When a client logs a session, it lands against the prescribed block. When they log a meal, it scores against that day’s target. The coach reads a state, not a chat history.

Video form checks are attached to the movement, not the conversation, so a squat from March sits next to a squat from September.

03

What happened after

Coaches did not get more hours. They got the same hours back from admin and spent them on the four people who actually needed a call that week.

Roster size roughly quadrupled without a proportional rise in messaging volume, because most of the messages had been status questions the dashboard now answers.

How it was built

From the floor to production

Weeks 1 to 2Ride-along with six coaches. Counted every app switch in a working day.
Weeks 3 to 6Adherence model and roster ranking. The hard part was deciding what counts as silence.
Weeks 7 to 10Programme builder, macro engine, habit streaks, video form review.
Weeks 11 to 12Athlete mobile app, because a client who needs a laptop will not check in.
What it does

Capabilities

01

Client portal included

02

Plan templates

03

Payment tracking

04

Ask Loopra AI

“I was capped at twenty-five clients because of admin. I am at ninety now and I answer fewer messages than I did before.”

Marcus Oyelaran
Performance coach

Put a quieter system on your floor

Tell us the bottleneck. We will show you the system that already solves it, or build the one that should.