Instead of Pabau
Stop renting Pabau. Own your clinic system.
We build your version around how your clinic consults, consents, treats and follows up, bring your Pabau clients and treatment history across with every rebook date intact, load your menu, your injectors and your stock by batch, and run it for you. The records sit in a database you own.
Pabau does not publish a price for any plan. Every tier from Solo to Enterprise is quoted on a demo call, priced per user and per location, and its four add-ons are quoted on top.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What you are paying for
Most of a Pabau bill is rent on the screens
The client files, the consents and the treatment notes are your clinic's. What you pay for is the front end around them, priced on how many people log in and how many clinics you run, at a figure you only learn on a sales call.
A price that grows with every injector
Pabau prices by user in bands: one, two to three, four to five, six to fifteen. Take on a second nurse injector or a receptionist and the whole plan moves up a band.
The price again for every clinic
Plans apply per location, except the top tier. Open a second room across town and you are quoted again for it.
A demo call before you see a number
No plan shows a price. You book a demo, then you are quoted, and the quote depends on where you are and how many people you have.
Four add-ons on top
Marketing Plus, Care Plus, Insights Plus and Engage Plus are each quoted separately, and messages and call minutes on Engage Plus use credits billed as you go.
Rules you still have to remember
The software stores the consent form. It does not stop a 17-year-old being booked for filler, a treatment going ahead on a used script, or a deposit taken inside the cooling-off.
Your medical forms locked in
Client lists come out as reports, but medical and consent forms have no bulk export: they download one by one from each client card. That is why most clinics stay and keep paying.
What you get instead
The clinic record you own, with the cosmetic rules built in
Prescribing
No injectable without a current script
Every script is recorded against the one client it was written for, with the prescriber, the date and whether they saw the client in person or by video.
- check A script by text, email or online questionnaire cannot be recorded at all, because the guidelines do not allow one
- check A toxin or filler treatment will not complete without a current script, and the dose given cannot exceed it
- check The day sheet flags tomorrow's clients whose script has been used or has run out, before they are in the chair
- check Clients whose script or consent runs out before their next booking are listed weeks ahead
Consent
Consent that is complete, or the treatment waits
Written consent per kind of treatment, with the financial consent and the copy the client takes home recorded.
- check Toxin and filler are refused for anyone under 18, at booking, at prescribing and at treatment
- check A client under 18 waits seven days after consenting, and a deposit taken inside that week is refused
- check A consent with no copy given, or no financial consent, holds the treatment until it is fixed
- check The client's consent record prints in your clinic's name with the cooling-off date stated
The record
Every syringe traced to its batch
The treatment record carries the areas, the notes, the aftercare given and the product and batch used, and once finalised it never changes.
- check Ask for every client who received a batch and get one list with phone numbers, ready for a recall
- check An expired batch cannot be used, and stock is received by batch number with its expiry date
- check Treatments with no record, or a record still in draft, top the morning list by practitioner
- check The client gets a printed aftercare sheet naming what was used, so any practitioner can look after them
Aftercare and return visits
The clients who need a call, and the ones who should be back
Complications, two-week reviews and rebooks run from the same record every morning.
- check An open complication with nobody booked to see the client is the first line of the day, with what was done so far
- check Retention by injector: of the clients due back this year, how many came back, which no standard dashboard shows
- check Rebook messages only go to clients who said yes; the never-asked get a call and a no is respected
- check Before and after photos come out of advertising the day a client withdraws consent, and packages are refused on cosmetic procedures
Make it yours
Design your own Pabau replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Pabau. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Pabau data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Skin Clinic for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Skin Clinic for Claude Code
Connected to your own database
What needs a decision this morning?
Needs a decision, worst first
[1] complication_open Mia Kowalski CMP-801 Mia Kowalski reported "Firm, tender lump in the left cheek, no change in skin colour" 3 day(s) ago after Dermal filler, cheeks (2 ml) by Dr Mei Chen (moderate). Nothing is booked to see them. Call 0412 555 108 today and book them in with the treating practitioner; follow the complications protocol.
[1] no_script Zara Ahmed APT-1030 Zara Ahmed is booked 2026-09-30 10:00 (APT-1030) for Toxin, upper face (three areas), and the treatment cannot go ahead: there is no current toxin script for Zara Ahmed on 2026-09-30: the last one, SCR-301, has been used and ran out 2026-09-27.
[1] inside_cooling_off Emily Ross APT-1032 Emily Ross is booked 2026-10-02 14:00 (APT-1032) for Fractional laser resurfacing. Emily Ross signed CON-202 on 2026-09-28 while under 18; the cooling-off runs until 2026-10-05 (s4.5). Move the treatment to 2026-10-05 or later.
[1] under_18_injectable Chloe Bennett APT-1031 Chloe Bennett is booked 2026-10-04 11:00 (APT-1031) for Dermal filler, lips (1 ml). Chloe Bennett is 17. Dermal filler, lips (1 ml) is never given to anyone under 18 (Ahpra non-surgical cosmetic guidelines s4.2).
[1] record_draft Hannah Price TRX-502 Hannah Price's Dermal filler, lips (1 ml) with Jess Taylor on 2026-09-25 has a record still in draft (TRX-502), 4 days on. Another practitioner could not take over their care from this.
[1] record_missing Olivia Grant APT-1021 Olivia Grant's Toxin, upper face (three areas) with Jess Taylor on 2026-09-27 has no treatment record at all, 2 days on. Another practitioner could not take over their care from this. --qty=..., then record final APT-1021
Ask it anything
Questions Pabau cannot answer
Every one of these is a real question the demo answers today. Yours will be different, and that is the point.
Switching
How to switch from Pabau
Moving off Pabau means exporting your client and appointment records, loading them with a dry run first, and giving every client a fresh written consent at their first visit, since consent and medical forms do not export in bulk.
- 1
Export your clients and appointments
In Pabau, run a Clients report and an Appointments report from Analytics and Reports, then export each as CSV from the three dots menu. This gives you the client list and appointment history to bring across. Consent forms and medical records do not export in bulk from Pabau, so plan on collecting a fresh written consent from each client at their first visit in the new system.
- 2
Load the export, dry run first
Ask Claude Code to import the two files, and start with a dry run before anything is written. It matches common column names on its own and does not create anything twice, so you can run it again safely if you need to. Once the dry run looks right, run the real import.
- 3
Check what the import flagged
The import names every row it could not read, whether from a missing field or a format it did not recognise. Go through that list before you trust the numbers, and fix or hand enter anything that matters, such as a client whose history did not carry across cleanly.
- 4
Run both systems side by side
Keep booking in Pabau and the new system together for a short stretch before you commit. This is where you catch anything the export missed, gaps in your rebook dates or a client card that came across thin. Use the time to get comfortable asking for what you need in plain language.
- 5
Switch off Pabau
Once the day sheet, the client cards and the rebook dates check out and the team is booking confidently in the new system, cancel Pabau. Keep the CSV exports as your retention copy of the old clinical record, since consent and medical forms do not travel across and stay behind in that export.
Where the real effort goes
The real work is in your own detail: matching your treatment menu, team roles and rebook intervals to your rules, and deciding how much history to bring across since consent and medical forms stay behind in the Pabau export. The technical move itself is quick. If you have Enterprise DNA install and run it for you, this part is handled as part of that setup.
Not ready for a call?
Get your Pabau switch plan by email
We will send you the step-by-step plan for moving your business off Pabau, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Pabau switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to run it
Run it yourself, or have it run for you
Open source
Run it yourself
Free
- 1 Clone the repo
- 2 npm run demo, then open the folder in Claude Code
- 3 Type /attention, then /day and /compliance
- 4 Import your Pabau client and appointment reports and point it at your own database
Omni by Enterprise DNA
Have Enterprise DNA install it
One setup fee, then a monthly retainer
- check We bring your Pabau clients and treatment history across, so every rebook date is right from the first day, and gather each client's medical form files into their record
- check We load your menu, your injectors with their prescribing and indemnity details, and a stock take by batch, so the first treatment traces to a batch
- check A booking page for clients, consent forms they sign on a tablet at the desk, and card payments, if you want them
- check It runs inside Omni, our managed Command Center, with the rest of your business
Questions
Instead of Pabau, answered
Is it really free? expand_more
Yes. MIT licence. Run it anywhere, change anything, no account with us.
Can clients book online and sign consent forms themselves? expand_more
Not in the free version: bookings and consents are entered by the clinic. Pabau gives clients a booking page and forms on its own screens. A client booking page and consent forms signed on a tablet are part of what Enterprise DNA builds into your version, writing into the same database.
Does it take payments and send text messages? expand_more
The free version records invoices, deposits and payments, and writes reminder and rebook messages for a person to send. It does not process cards or send texts. Enterprise DNA connects the payment terminal and the message service you choose when we build your version.
What happens to our Pabau history? expand_more
Your client list and appointment history come across, with each client's past treatments, so rebook dates are right from day one. Consent and medical forms do not export from Pabau in bulk, so every client gives a fresh written consent at their first visit, which the new system needs anyway. The old forms stay in Pabau's export as your retention copy, and Enterprise DNA gathers them into each client's record when we do the move.
Is client data and their photos safe in this? expand_more
The records live in a database you own, on your own infrastructure or on ours if we run it for you, rather than in a vendor's cloud on the vendor's terms. Photos stay on the clinic's secure storage and the record points to them. Health privacy obligations travel with the data either way; owning the database means you can say exactly where it is and who can see it.
Stop paying per injector to see your own clinic
You pay per user and per clinic, at a price you only hear on a sales call, for a booking screen, a forms screen and reports that stop at the invoice. 30 minutes with Sam. We look at what your clinic pays Pabau for, what your injectors and front desk actually use, and what the installed version would look like for your clinic. If it is a fit, we install it. If it is not, take the free version and run it yourself.
Skin Clinic for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Pabau?
Get your version built