Ask most studio and clinic owners what keeps them up at night and the answer is rarely a single bad month. It’s the lumpiness — the not knowing. A great January followed by a hollow February, a class that fills one week and empties the next, cash flow that lurches instead of flowing. The membership model exists to smooth that curve. Done well, it turns a wellness business from a series of transactions into a relationship with predictable rhythm. Done casually, it just adds admin. The difference lives almost entirely in the machinery underneath.
Why recurring revenue changes the business, not just the invoice
A membership is not merely a discount wrapped around a punch card. When a meaningful share of your revenue arrives on a schedule, three things shift at once. You can plan hiring and space against a floor you can actually see. Retention becomes the metric that matters, which nudges the whole team toward the client’s ongoing experience rather than the next sale. And the relationship itself lengthens — members show up more, refer more, and forgive the occasional off day. None of that is exotic. What’s hard is the plumbing required to run it without the plumbing running you.
The billing and entitlement machinery it actually requires
The membership model looks simple from the client’s side — pay monthly, walk in, train. Behind the counter it is a small system of moving parts, and every one of them is a place where a naive setup leaks money or goodwill:
- Trials. A free or reduced first period that converts cleanly into a paid plan, without a human having to remember to flip a switch.
- Renewals. Charges that recur on time, prorate correctly when someone upgrades mid-cycle, and pause or resume when life happens.
- Dunning. The unglamorous, decisive one: when a card fails, the system retries intelligently and nudges the member to update payment — instead of silently dropping revenue you already earned.
- Access control (entitlement). The membership has to actually gate something — the door, the booking window, the members-only class, the app content. Entitlement is the link between “is paid up” and “may enter,” and it must update the instant status changes.
Most owners discover these requirements one painful gap at a time, usually after a member is either charged for something they cancelled or let into something they didn’t pay for. A platform built for this treats billing and entitlement as first-class parts of the same system rather than two apps you hope agree with each other.
Owning the machinery instead of renting it
There are two ways to acquire this machinery: rent it as a tenant on someone else’s platform, or run it on infrastructure you control. The rental path is faster to start and, for some, entirely fine. But it means your member records, your billing relationship and your recurring revenue live inside a system you don’t govern — and it usually means a fee that grows as you do.
The self-hosted path keeps those assets yours. VBWD, for example, is a full-stack, self-hosted SDK with an intentionally agnostic core: subscriptions and memberships, booking and scheduling, payments and catalogue each arrive as plugins that toggle on or off without a restart. One backend serves web, iPhone and Android, so members get the same experience across devices without three separate builds. Because the platform is self-hosted, the client data, the customer relationship and the billing are yours, inside your own jurisdiction. And because the infrastructure does the heavy lifting, a small studio can run the same technology a large multi-location operator would — a point explored in VBWD’s piece on how a small studio runs an enterprise commerce stack. It’s source-available under BSL 1.1, which is free for commercial use while annual VBWD-attributable sales stay below the value of 6.7 BTC per year.
The honest caveat
Recurring revenue is a genuinely good business model, but it is not a magic trick — and the platform under it involves a real trade-off. A self-hosted option like VBWD is younger and less “mature” than the long-established subscription suites that have spent two decades polishing every billing edge case. It trades some of that accumulated maturity for modern architecture, speed, auditability and data sovereignty. For an operator who wants to own the customer relationship and the numbers, that’s frequently the better deal. For a team that would rather pay a per-seat fee and never touch infrastructure, a hosted incumbent may fit better. Weigh it honestly; the model rewards the fit, not the hype.
If your practice is wrestling with any of this — lumpy cash flow, cards that fail silently, a membership scheme held together by spreadsheets and reminders — the useful next step is concrete: see it running for your own business. Request an enterprise installation and bring the numbers you want to improve.
