MILabs
Integrations

Custom development for Cliniko clinics

Custom development for businesses that run Cliniko, covering discovery, fixed-price scoping, integrations with existing systems and ongoing upkeep.

Updated 2026-09-01

Custom development with Cliniko

Cliniko runs the diary, client records, invoices and clinical notes for many allied health, physiotherapy, counselling and dental clinics. For most of the day-to-day work, that is enough. Some clinics eventually need something the software was never designed to do, such as an intake route shaped around how their own clinicians triage referrals, or a link between the diary and a billing process still kept in a spreadsheet. Custom development starts with a discovery session on the specific requirement, followed by a fixed-price scope so the decision is made before any code is written. The result might be a small internal tool that reads from Cliniko through its API, or a separate application that sits beside it. Because Cliniko holds the record of truth, every build must respect the permissions the clinic sets in its own account. The business keeps what is built, and maintenance falls under the existing retainer.

How it works

  1. Discovery: the team names the requirement, such as a referral intake form or a diary-to-invoice link, and records which Cliniko records it touches.

  2. Permissions check: the clinic confirms which access its Cliniko account allows, so the design fits what the platform exposes before any build begins.

  3. Fixed-price scope: a written plan lists the tool, its connection points with Cliniko, and each step where staff review output before anything is saved to a client file.

  4. Build: the tool is developed and tested against sample records where possible, so live client data is not used during testing.

  5. Handover: staff are shown how the tool works, and the business receives the code and documentation.

  6. Upkeep: when Cliniko or the clinic's needs change, maintenance is handled inside the retainer.

good questions, straight answers

Frequently asked questions

Who is custom development for among Cliniko users?
It suits clinics whose needs have outgrown their current setup. Typical cases include an intake process shaped around a particular referral pathway, or an internal tool that matches how the business really runs its diary and billing. Owners and team leads who can describe the requirement in plain terms are a good starting point, even before any technical plan exists.
Can custom development be done without a developer for Cliniko?
Building the software itself needs developers, because a custom application or integration involves writing and testing code. The clinic's role is different but still important. Staff describe the workflow, approve the scope, review drafts, and check the finished tool against real tasks. The written scope should show which parts of the build the clinic needs to check, so ask for that breakdown before agreeing to anything.
Who owns the result of custom development for Cliniko?
The business owns what is built. That covers the application or internal tool created for it, and the scope should spell out ownership before work starts. Cliniko remains the system of record, so the clinic's own Cliniko account, its data and its permission settings stay under its control. Any tool built to read from or write to Cliniko works within those settings, and the business decides who on its team can use the result.
How does a first conversation about custom development go for Cliniko?
The first conversation is a discovery call that starts through the enquiry form or by arrangement. You describe the requirement, the Cliniko records it touches, and the people who would use the result. The agency asks about the current workflow and any sensitive information involved. Building starts only after a written, fixed-price scope has been reviewed and agreed.
Is custom development right for a small Cliniko team?
Yes, when the requirement is specific and the work it removes happens often. A small team with one repetitive problem, such as an intake summary written by hand or a follow-up list kept in a notebook, may need only a narrow tool. Team size matters less than how often the task repeats. The discovery stage shows whether custom software is justified or whether a simpler, existing option would cover the need.
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.