MILabs
Integrations

Custom development for Pabau salons and clinics

Custom development for Pabau businesses that need a tailored application or integration beyond standard booking, forms and reminders.

Updated 2025-11-21

Custom development with Pabau

A Pabau account often grows past its first setup. A salon with two sites may need one view of rebooking across both diaries, while a medical clinic may need intake answers passed to a specific team before a first visit. Physiotherapy services sometimes want a program of exercise prompts that follows each treatment plan, a task that a standard reminder may not handle. When a need like this arrives, custom development is the route that fits: MILabs first works out what the requirement is and where Pabau's data should flow. A fixed-price scope then covers a purpose-built application or internal tool, connected to the existing Pabau records. Your team owns the result. Maintenance is included in the retainer, so changes to forms or rules can be handled without rebuilding from scratch. Each build is tested with staff before handover, and anything that touches clinical notes or consent stays under a named owner.

How it works

  1. Discovery starts with a plain description of the gap, such as a booking rule that may sit outside the standard diary settings, and a list of the Pabau records involved.

  2. Scoping sets out inputs, outputs and permissions in writing, with a fixed price agreed before any build starts.

  3. The build connects a custom application or internal tool to the existing Pabau records, using only the access your staff logins already have.

  4. Staff test the flow with de-identified examples, and the clinician or therapist confirms any output that touches clinical content.

  5. Handover covers how the tool works, who owns each rule, and how changes are requested under the retainer that covers upkeep.

good questions, straight answers

Frequently asked questions

How does custom development work with Pabau?
MILabs starts by identifying the requirement that the built-in Pabau tools do not cover, then reviews which records, forms or messages the solution needs to read or write. A fixed-price scope follows in writing. The build is tested with your staff and handed over with a full account of how it connects to Pabau. Access stays within the permissions your staff logins already have, so the solution cannot see more than your team can.
Is custom development safe with Pabau data?
Client files carry personal and health details, so safety depends on design choices made before any build. The solution should only read the records it needs, keep the access rules set in your Pabau account, and avoid copying client details into other tools unless agreed in writing. MILabs does not replace your privacy or clinical governance, and your clinic or salon remains responsible for consent, retention and who may view records.
What does custom development not cover for Pabau?
Routine setup that your team can usually carry out inside the account, such as changing appointment types or standard forms, stays with you, and clinical decisions stay with the clinician. Custom development puts its energy into bespoke tools shaped around how your salon or clinic runs. Scope is agreed in writing before work begins, so anything beyond it is quoted separately and you always know where you stand.
What does MILabs do after custom development for Pabau?
After handover, MILabs maintains the solution within your retainer, so fixes and adjustments to rules, forms or connections are handled without a new project each time. Your team receives a written account of how the build works and who owns each rule. When Pabau's own features change, or your clinic adds a new service, the solution can be reviewed and updated. You own the build throughout.
Can custom development start with part of Pabau?
Yes. A business does not need to replace its whole Pabau setup. A single gap, such as one intake form that feeds a specific team or one recurring report, can be scoped and built on its own. The existing Pabau records and diary stay as they are, and the custom piece connects to them. Starting narrow keeps the scope tight, and the wider setup can be reviewed once the first piece is in use.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.