A yoga studio, a spa or an aesthetics practice almost never fails for lack of clients. It fails because money leaks out in places nobody is watching, and all those places share one cause: the information lives split across a notebook, a spreadsheet and several WhatsApp threads.
Where the money leaks
Before talking about software, it is worth naming the leaks. They are always the same ones:
Prepaid sessions nobody deducts properly. You sold a ten-class pack. How many has that client used? If the answer lives in someone’s memory, sooner or later you will give sessions away — or worse, overcharge and lose the client.
Clients who stopped coming and nobody noticed. Without a database there is no way to ask “who has not been here in two months?” And winning back someone who already knows you costs far less than finding someone new.
Appointments that fall through with no warning. An automatic reminder the day before cuts no-shows immediately. It is one of the cheapest things to implement and one of the fastest to pay for itself.
A month-end close assembled from memory. If the books are reconstructed at the end of the month by piecing together transfers and recollections, you are not making decisions with data: you are guessing, late.
What you do need
In order of urgency, not of what looks best in a demo:
- Scheduling tied to real clients. Not a calendar: appointments attached to a client record with their history.
- Prepaid pack tracking, session by session. Every session consumed, with its date and time. It is the heart of the business and where the largest leak is.
- Books that feed themselves. Every sale should generate its entry without anyone recording it separately. If it has to be entered twice, one day it will not be entered at all.
- A client record with their history. What they bought, what they came for, what worked for them. It is what lets you serve people well once you no longer remember everyone.
- Automatic reminders. They should go out on their own, with nobody having to remember.
What you do not need yet
This is where budgets disappear without anything improving:
- Your own mobile app. Your clients are not going to install an app to book once a month. A site that works well on a phone does the same job without the cost of maintaining two applications.
- WhatsApp API integration. It sounds good and costs a lot. At the volume of a small center, prepared messages sent with one click solve the same problem.
- An e-invoicing module, unless your tax regime requires it. If it does, it comes first; if it does not, it is a distraction.
- Elaborate reporting before the data is clean. A dashboard built on incomplete data gives false confidence, which is worse than having no dashboard.
The eternal question: buy or build?
Subscription software works if your operation resembles the one the product assumes. You start fast and you pay every month, forever. The problem shows up when your business has its own logic — freezing packs, negotiated rates, a ritual that books differently — and the system does not account for it. That is when you go back to the parallel spreadsheet, and now you are paying for two things.
A custom system adapts to how you actually work. It costs more up front and makes sense once the operation has real volume and real quirks.
The honest way to decide is not to compare feature tables: it is to measure what the leak is costing you today. If mis-deducted sessions, lost clients and no-shows add up to several hundred thousand pesos a month, the answer becomes obvious on its own.
What it looks like when it works
A wellness center in Medellín I work with went from a paper appointment book to a system with twelve modules — scheduling, prepaid packs, accounting, clinical records, store, marketing — where selling a pack creates its own accounting entry and attendance deducts the session. In four months it multiplied its monthly sales by 3.6.
The system did not sell more on its own: it stopped losing what had already been sold, and it freed up hours that went into serving clients instead of reconciling accounts. The full story, with the numbers, is in the Marce Anahata case study.