Once a month, Consolación Sánchez opens a dashboard at BELSA Estétic and reads six numbers. She used to spend an entire afternoon building them first — pulling a WhatsApp thread here, a spreadsheet tab there, a memory of a conversation nowhere written down at all. The reading didn't get shorter when the system arrived. The assembly disappeared.
The report that was never actually a report
Before the install, BELSA didn't lack information. It drowned in it, scattered. Patient conversations lived in WhatsApp. The schedule lived in a spreadsheet one person could safely edit. A lead from Instagram became a patient only if somebody remembered to copy it across by hand. Revenue was steady — but it was steady because the founder held every thread of it together, every day, in her own head.
So when Consolación wanted to know how the month had actually gone, there was no dashboard to open. There was a reconstruction project. Count the WhatsApp replies that turned into bookings. Guess at how many first-time callers never rebooked. Estimate the split between Instagram and referrals, because nothing recorded the source. The "report" wasn't a report. It was detective work performed by the one person too busy to do it.
This is the pattern we see in almost every clinic that walks into a Strategy Lab with an analog stack: the data exists. It's just never in one place, never in one format, and never attached to anything that can be trusted without a cross-check. A business can run this way for years. It cannot be read this way.
Six numbers, not sixty
When RIVEL OS went live at BELSA in Clinic OS mode, the instinct from most teams would be to build a dashboard that shows everything — every metric a clinic could theoretically track, arranged in a wall of charts nobody has time to interpret. That's not what got built, and it's not an accident.
BELSA's KPI read comes down to six numbers:
- Booking pace — how fast the calendar is filling, this week against the trend.
- Attendance — who actually shows up against who was booked.
- Conversion to treatment — how many consultations become paying treatments.
- Average ticket — what a visit is actually worth, not what the price list says it should be worth.
- Retention — who comes back, and on what rhythm.
- Open pipeline — enquiries sitting in a stage, waiting on someone or something.
Six is not an arbitrary limit. It's the number of questions a founder actually needs answered to know whether the business is healthy, and no more. Every one of them traces back to a single source of truth instead of a guess assembled under deadline. Patient record, source, stage and treatment history all sit in the same place — which is also why BELSA's own case study can publish a figure like +40% in online bookings with a window and a method attached, instead of a number that reads like marketing because nobody can show their work.
What the old monthly ritual actually cost
It's worth sitting with what that reconstruction project really meant in practice, because "the founder spent an afternoon pulling numbers together" undersells it. The afternoon itself was the cheap part.
The expensive part was everything that happened because the numbers weren't trustworthy in the first place. A founder who isn't sure whether conversion actually dropped or whether she's just misremembering a slow week will hesitate on a decision that should have taken five minutes. A founder who can't say with confidence how many enquiries are sitting untouched in the pipeline will either chase all of them personally — which doesn't scale — or chase none of them, which quietly costs revenue nobody can point to.
And there's a second cost that's easy to miss: every time Consolación had to reconstruct a number from memory, she was the only person in the building who could do it. That's not a reporting problem. That's a single point of failure wearing a spreadsheet as a disguise. If she were sick for a week, or traveling, or simply wanted a weekend without her phone, the business didn't just lose her — it lost its only working model of itself.
This is the same bottleneck we see across almost every aesthetic and medical clinic we meet before a Strategy Lab install, regardless of how good the founder is at her craft. The clinical skill was never the constraint. The constraint was that understanding the business required being the business.
Why "more data" was never the problem
It's tempting to think the fix for a founder who can't see her own business clearly is more tracking — another spreadsheet column, another form field, another report nobody reads past the first page. That instinct is almost always wrong, and it's worth saying plainly why.
A clinic that adds tracking without adding structure just moves the chaos one layer deeper. Now there's more to reconcile, not less. The actual fix isn't volume. It's a single place where every number already means the same thing to everyone who looks at it — where "conversion" isn't defined three different ways across three different files, and "booking pace" isn't a feeling someone has about how busy the week looks.
That's the quiet function the Marketing Hub and KPIs layer performs inside RIVEL OS: it doesn't ask a clinic to track more. It asks every enquiry, every booking and every treatment to report into the same six boxes, automatically, the moment it happens — not at month-end, not from memory, not reconstructed under deadline pressure.
"The team finally trusts the data. That's what changed everything." — Consolación Sánchez, founder of BELSA Estétic
That sentence is the real headline, more than any single percentage. A number nobody trusts doesn't change behavior. A number everybody can check does.
What changed when the founder stopped building the report
The practical shift at BELSA wasn't that the founder started seeing more. It's that she stopped being the one who had to produce what she saw. Reception opens the same dashboard. The team moves patients through stages without asking Consolación what stage means. The monthly read — the six numbers — takes the time it takes to read six numbers, not the time it takes to reconstruct a month from fragments.
That distinction matters more than it sounds like it should. A founder who has to build her own report before she can read it is never actually off duty, even during the twenty minutes she spends reviewing it. She's still the system. The dashboard just becomes one more artifact she personally assembles, dressed up to look automated.
What a real system does instead is separate two jobs that used to be stuck together: running the clinic day to day, and knowing how the clinic is doing. BELSA's reception runs the first job now — opening the agenda, answering on WhatsApp from inside the system, moving enquiries through their stages. The founder does the second job, once a month, from the same screen, without touching the first.
The number that actually moves the needle
Of BELSA's six, retention is the one most clinics underweight — not because it doesn't matter, but because without a system, it's nearly impossible to even measure cleanly. "Who comes back" sounds simple until you try to answer it from a WhatsApp thread and a shared spreadsheet. Nobody is deliberately hiding the answer. It's just never been attached to anything that could produce it on demand.
Once retention has a real number instead of a feeling, it stops being background noise and starts being a lever. A clinic that can see its retention rate monthly can ask why it moved, test a change, and check the next month's number against the last one — the same discipline that, applied across BELSA's six metrics together, is what turned a +25% shift in conversion rate from a hopeful guess into a documented, repeatable fact.
None of this requires a bigger team or a bigger budget. It requires the six numbers to live in one place, update themselves, and mean the same thing every time someone looks at them.
Picture the alternative version of a retention conversation, the one that happens without a system behind it. A founder senses, vaguely, that fewer regulars are rebooking than a few months ago. She can't say by how much, or since when, or whether it's concentrated in one treatment line or spread evenly. Every fix she considers — a loyalty offer, a follow-up call, a reminder sequence — is a guess layered on top of another guess, and she won't know if it worked for months, if ever, because the number it's supposed to move was never reliable to begin with.
Now picture it with a real retention figure sitting in the same six-number read every month. The founder sees the drift the month it starts, not the quarter it becomes a problem. She can isolate which service line is losing repeat visits. She can test one change, hold everything else steady, and read next month's number against this month's with actual confidence that the comparison means something. That's not a bigger business. It's the same business, with a working instrument panel instead of a dashboard light that's been taped over.
The compliance context nobody puts in the pitch deck
There's a detail specific to a clinic like BELSA that's easy to skip over: aesthetic medicine in Barcelona runs inside a compliance context that a shared spreadsheet was never built to respect. A treatment history isn't just operational nicety — it's part of the patient record, and a patient record scattered across WhatsApp screenshots and a spreadsheet nobody owns is a liability as much as it is an inconvenience.
This isn't a substitute for legal or regulatory advice specific to your jurisdiction and specialty — that's a conversation for a qualified professional who knows your local requirements. What a system like RIVEL OS does is more modest and more structural: it gives every patient one record instead of three, so the treatment history, the consent context and the communication trail live in a place that can actually be audited instead of reconstructed after the fact. For a clinic operating under real regulatory scrutiny, that structural difference is not a nice-to-have.
It's also, not coincidentally, the same property that makes the six KPI numbers trustworthy. A record that can be audited for compliance is the same record that can be audited for "did conversion really go up." Clarity and accountability turn out to be the same underlying property, applied to two different questions.
What this looks like for your own clinic
You don't need BELSA's exact six metrics to benefit from the principle behind them. You need to be honest about which handful of numbers would actually change a decision if you trusted them completely — and then build toward a system where those numbers exist without anyone having to assemble them under deadline.
Most clinics, studios and consultorios we meet already know, roughly, which numbers those are. What they don't have is a record that can produce them on demand, attached to patients, sources and stages that already live in the same place. That's the gap a real operating system closes — not by adding more dashboards, but by making the ones that matter trustworthy enough to actually use.
If your own monthly read still starts with "let me pull some numbers together," see what it takes to install a system that already has them, or talk to us directly about which six numbers would matter most for your business.
Whichever handful of numbers ends up mattering to you, the test is the same one that changed how BELSA runs: can someone other than the founder open the dashboard, trust what it says, and act on it without a phone call to check? If the honest answer today is no, that's not a tooling gap you patch with another spreadsheet column. It's the one gap worth closing first — before the next busy month makes the guessing more expensive than it already is.