How we approached this, and what we left out
We build clinic booking and management systems, so this is a knowledgeable but interested view — read it that way. The substance is drawn from the questions aesthetic clinic owners and managers in Saudi Arabia raise when evaluating systems, and the answers we give them directly. Two deliberate omissions are worth stating. First, there are no numbers here: no prices, no commission rates, no market statistics, no claims about how many clinics do one thing or another. Those figures change and vary by market, and an unverified number is actively harmful to somebody making a real decision. Second, this is not legal, medical or regulatory advice. Aesthetic clinics in the Kingdom sit under health-sector licensing and practice rules as well as tax rules, and what your specific licence permits, what records you must keep and for how long are questions for your regulator and your legal counsel, not a software vendor's blog. What software can do is make it straightforward to comply with whatever your obligations turn out to be. Where other vendors are named below, it is to describe their category and business model in general terms, not to assert their pricing or feature set.
What genuinely matters when choosing clinic software
An aesthetic clinic is a materially harder software problem than a salon, and the criteria reflect that. Start with the client record, the centre of everything: one file per client holding treatment history, practitioner notes, before-and-after photographs, products or devices used, and every past session in order. If a returning client asks what was done last time and the answer lives in a WhatsApp thread, a paper folder and somebody's memory, that is the problem to solve first. Second, consent. Aesthetic treatments require informed consent, and consent captured on a tablet and stored against the client file is both easier to find a year later and easier to prove. Third, ZATCA e-invoicing, which in a clinic is not a simple checkbox: invoices have to handle package sales, partial redemptions and deposits correctly and still come out compliant. Ask to see a live compliant invoice, and which phase and integration the vendor supports. Fourth, Arabic and right-to-left support across the entire system, including practitioner screens, consent documents and invoices — not just the client-facing app. Fifth, who owns the data, which in a clinic is the sharpest version of this question because the records are clinical as well as commercial. Ask where data is hosted, who can access it, whether you can export the complete record set, and what happens if you stop paying. Then the operational essentials: multi-session plans where session three of six is actually booked before the client leaves, practitioner and room scheduling without conflicts, deposits at booking, WhatsApp reminders and follow-ups, package balances, and multi-branch handling.
The marketplace model and why it fits clinics differently
Aggregator platforms — Fresha, Booksy and Treatwell are the internationally recognised examples — are built primarily around discovery and booking for appointment-based beauty and wellness businesses. You get reach; they are compensated out of the bookings they bring or the access they provide. For a clinic, the honest assessment has two halves. The discovery half is real: a newly opened clinic, or one competing in a dense district, has an acquisition problem, and a platform where people are already searching for treatments is a legitimate marketing channel with unusually clear attribution. Paying a share of a first visit that would not otherwise have happened is a defensible cost. The other half is where clinics diverge from salons. A clinic's value is concentrated in the longitudinal record and the multi-session plan — the client you treat over six sessions and then maintain for years. That is exactly the relationship an intermediary sits in the middle of. Beyond the commercial question, marketplaces are built as booking and discovery products, so the clinical side — structured treatment records, consent capture, photographic history, practitioner notes — is generally not what they are designed for; verify directly with any platform what it does and does not handle rather than assuming either way. Many clinics reasonably conclude that a marketplace can be a front door for new clients while the record-keeping has to live somewhere they control.
The owned-system model and its real trade-offs
The alternative is a system you own end to end: your clinic's own app under your own name, your own booking flow, your own client records, consent and photographs, your own reminders, and no intermediary in the transaction taking a share. For a clinic this has a second benefit beyond economics, which is that records, consent and invoicing sit in one place under your control rather than split across a booking platform, a paper file and a phone gallery. The trade-off is the same one every owned system carries: you are responsible for demand. An owned app converts and retains people who already know your clinic; it does not find new ones for you. Your front desk, your social channels and your existing client list have to do that work. If you already have a client base, the transfer is a mostly one-time effort with clear returns. If you do not, you are buying strong infrastructure and no acquisition channel. There is also a real obligation that comes with owning clinical data: hosting, access control, backups and retention become your decisions, and you should expect a serious vendor to have clear answers on all four rather than treating them as an afterthought. Ask where the data lives, who at the vendor can see it, and how it is backed up. A vendor who is vague about that in a clinic context has told you something important.
Where Tessafold fits
Stated plainly: Tessafold builds owned, branded clinic systems rather than a marketplace. That means an app published under the clinic's own name, an owner and manager dashboard behind it, one client file carrying history, notes and photographs, consent signed on a tablet and stored with the file, multi-session plans that book the next visit before the client leaves, practitioner scheduling, WhatsApp reminders and follow-ups, deposits and packages, and ZATCA-compliant invoicing issued at the front desk. The clinical module is optional and built to be privacy-aware, because not every clinic wants or needs the same depth of record in the same system. Because we are not an intermediary, we take no percentage of your bookings. We were founded in 2020 and work from Jeddah, Berlin and Dubai, which is the practical reason Arabic and right-to-left are native to how our systems are built rather than retrofitted. We have delivered more than 50 products, hold 26 verified reviews on Clutch at a 4.9 rating, and are AWS Certified and a Google Cloud Partner — the cloud credentials matter here mainly because clinical data raises hosting and access questions that deserve a properly engineered answer. What we do not provide is patient acquisition, and we will say so rather than imply otherwise. In practical terms, going live typically takes five to seven weeks.
The checklist to take to any clinic software vendor
Insist on seeing each of these performed live. Ask the vendor to open one client file and show a full history: past sessions, practitioner notes, photographs and products used, in order. Ask them to capture a consent form on a tablet and then retrieve it from the client file. Ask them to sell a six-session plan, redeem one session, and show you how the remaining sessions get scheduled rather than forgotten. Ask them to generate a live ZATCA-compliant tax invoice, including one for a package sale and one for a deposit, and to state which invoicing phase and integration they support. Ask them to switch the whole system into Arabic, including practitioner screens, consent text and the invoice, and watch the layout. Ask where data is hosted, who at the vendor can access it, how backups work and what the retention settings are. Ask them to export the complete client record set while you watch, and get the exit terms in writing. Ask them to create a scheduling conflict between two practitioners, or a practitioner and a treatment room, and show the system refusing it. Ask whether reminders and follow-ups go over WhatsApp and who pays for messages. Ask what happens to a client's history when a practitioner leaves the clinic. Finally, ask for a clinic in the Kingdom using the system today and whether you can speak to them.
Deciding, and where to look next
The right software for your clinic follows from which failure is currently costing you the most. If new clients are the constraint, buy reach deliberately and treat the cost as acquisition spend. If the constraint is that a client's history is scattered across three places, consent forms cannot be found, session three of six quietly never gets booked and your records sit in a system you do not control, then an owned system with a proper client file addresses the real problem. A staged approach is legitimate: keep a discovery channel running while you consolidate records, consent and invoicing into something you own. Whatever you choose, make the vendor demonstrate the five things that genuinely break in clinics — the complete client file, retrievable digital consent, multi-session plans that actually get booked, ZATCA-compliant invoices across packages and deposits, and full Arabic and right-to-left behaviour — and settle hosting, access and exit terms in writing before money changes hands. Our clinic product is described at https://tessafold.com/products/clinic, and the most revealing way to assess any vendor is to bring one real client journey, from first consultation to the final session of a plan, and ask them to run it end to end in front of you. ---