Four areas. One set of definitions.
Owner numbers, retention, the member app and studio operations. Not modules you buy separately and not integrations bolted together — one system, which is the only reason the numbers agree with each other.
The report you would have built, already built.
Weekly revenue and ARM. Active members, snapshotted every Sunday so the number belongs to a week rather than to whenever you happened to look. Churn month to date. One health score per studio out of 100, banded, high is good.
Four definitions decide everything.
Active member, churn, ARM, new member. Ours are written down and applied identically at network, studio and member level — and at least one of them is almost certainly not what your current reports mean by it.
That is a twenty-minute conversation with your own numbers open, not a table on a marketing page.
If two screens disagree, one is a bug.
And we will tell you which. There is no reconciliation step in this product, because there is only one place each number is defined.
Every client re-scored each evening.
Every client at the studio, not only the ones who installed the app. One queue comes out, sorted worst first, with the reason attached as a sentence a coach can act on without decoding it.
Diagram, not a screenshot. Proportions are illustrative; the behaviour is not.
Reach out. Never send.
Touches logged, saves counted.
Fullroom has no send button. A coach reads the draft, changes what they want, and sends it from their own phone.
Where the leading signal comes from.
Members open it because it is useful to them, which is the only reason a data source like this survives. It carries your studio's brand, never ours, and there is no “powered by Fullroom” anywhere a member can see.
Diagram, not a screenshot. It shows the shape of the two signals, not one member's actual numbers.
Every optional feature ships off. A new brand never inherits another brand's promotions, challenge or copy.
The half nobody puts in a retention product.
It is here because a coach will not open a second app to save a member, and a manager will not trust a leave balance that disagrees with payroll.
Diagram, not a screenshot. The figures are the demo studio's week.
Wage cost while you drag the shift.
Breaks, open shifts coaches can claim, and self-serve swaps that need a manager's approval.
A ledger, not a number in a box.
Accruing weekly at the real rates. Casuals and contractors accrue nothing, and the screen says so.
Invite through to onboarded.
Tax and bank details encrypted at rest, documents in a private bucket, and multi-factor authentication for managers and above.
Plus programming authored once and delivered to every site, and role-scoped access enforced in the database rather than hidden in the interface.
It drafts. A human decides.
A language model writes the first version of the outreach message, the plain-English reason on a queue row, and the weekly member insight. That is the whole of its job.
It does not decide who is at risk — the score does that, from rules you can read. It does not message anybody. Switch it off tomorrow and the queue is still right; your coaches would just be typing more.
See the real screens.
Everything above is drawn as a diagram on purpose — we would rather show you the actual product on a call than ship a mock-up of it here. Twenty minutes, on your own numbers.