Almost every wellness business starts on a spreadsheet, and for a long time the spreadsheet is exactly right. One location, a known set of clients, a calendar you can hold in your head — a shared sheet and a couple of point tools genuinely do the job. The trouble is that the spreadsheet does not announce the day it stops being enough. It just gets quietly heavier, until one morning you are running a real operation on scaffolding meant for a much smaller thing.
The inflection point looks like friction, not failure
The moment a wellness business outgrows its spreadsheet rarely arrives as a single breakage. It arrives as accumulating friction. A second location opens and now there are two sheets that disagree about a client who visits both. Memberships have to be tracked separately from bookings, which are tracked separately from payments, and reconciling them at month end eats an afternoon. A new front-desk hire needs access — but access is all-or-nothing, because a spreadsheet has no real notion of roles. Clients ask for a phone app and there is simply nowhere to put one. None of these is a catastrophe on its own. Collectively, they are the sound of a business that has crossed from a single practice into a small enterprise while its tools stayed behind.
What a real platform has to do
When a wellness business goes multi-location, the requirements change in kind, not just in degree. A genuine platform — as opposed to a stack of point tools taped together — has to do a handful of things that a spreadsheet fundamentally cannot.
- Central data. One authoritative record of each client, booking, membership and payment, shared across locations, so nobody has to ask which copy is correct.
- Roles and permissions. The ability to give a front-desk hire, a practitioner and a regional manager appropriately different access — not the blunt all-or-nothing of a shared file.
- Memberships and recurring billing. Subscriptions and packages handled as first-class objects, not reconstructed by hand each month from three disconnected tools.
- Mobile. A way to meet clients on the web and on their phones without commissioning three unrelated builds.
This is the shape VBWD is built around: one self-hosted Python backend serving a web front end plus native iOS and Android SDKs, with booking, payments, memberships, catalogue and content as capabilities over an agnostic core that toggle on without a restart. Because the infrastructure does the heavy lifting, a small studio can run technology sized for a large multi-location business — a VBWD internal benchmark imports a one-million-item catalogue in roughly forty minutes, which hedges toward “the platform will not be your bottleneck as you scale,” though real figures vary by setup. VBWD’s own write-up on this, how a small studio runs an enterprise commerce stack, is worth reading if that gap between your size and your ambitions feels familiar.
The honest cost of waiting too long
The expensive part is rarely the move itself. It is the delay. Every extra month on the spreadsheet adds more data in an unstructured shape, more manual habits your staff will have to unlearn, and more client history tangled across tools that were never meant to talk. A migration you could have done cleanly at two locations becomes a genuine project at five. Waiting also carries a compliance edge that grows sharper as you hold more client records: GDPR treats health data as a special category under Article 9, and NIS2 reached full effect across the EU in 2026, bringing audits, 24-hour incident reporting, and fines up to EUR 10M or 2% of turnover — with management potentially personally liable. Germany’s BSI has already issued an early EUR 850,000 fine for weak incident detection, per Reed Smith and Freshfields. A spreadsheet is not a defensible way to steward that kind of data at scale.
The honest caveat
Moving to a platform is not automatically the right call today. If you genuinely have one location and a stable client base, the spreadsheet may still be the correct, cheapest tool — moving early can be its own form of over-engineering. And VBWD is younger than the twenty-year-old incumbents; it trades some accumulated edge-case maturity for modern architecture, speed, auditability and data sovereignty. For a business at or approaching the multi-location inflection that is often the better trade, but it is a trade, and the timing is yours to judge against your own growth. Self-hosting also means you own the operational responsibility along with the control. You can weigh the pieces on the architecture overview.
If your practice has quietly become bigger than the tools running it — two locations that disagree, memberships reconciled by hand, an app you have nowhere to put — the useful next step is concrete: see a real platform running for your own business. Request an enterprise installation and bring the operations you most want to consolidate.
Sources: GDPR Article 9 (health data special category); NIS2 Directive and BSI fine (Reed Smith, Freshfields).
