Setup and onboarding
What going live actually takes.
Setting up a clinic is a matter of days, not months, and most of that time is yours rather than ours. Here is the whole list, so you can see the size of it before you commit to anything.
What we need from you
You do not need all of it before we start. The first group blocks go-live; the rest can follow while we build.
The basics
These decide how the system behaves from the first minute. We cannot start without them.
- Clinic name, exactly as patients should see it
- Interface language: Kurdish, Arabic or English
- Currency and timezone
- Branch names, if you have more than one
Your team
Also settles which plan fits, since plans are priced by staff accounts.
- Everyone who needs an account, with their role
- Which of them are dentists who take appointments
- Who should be the owner account
Your treatments
The longest item on this list. Worth starting the day you decide, not the day we deploy.
- Your procedure list
- The price you charge for each
- Which are usually done in one visit and which run across several
Your identity
Optional, but it is the difference between the system feeling like yours on day one and feeling generic.
- Logo file, SVG or PNG
- Your brand colour
- Opening hours
- Phone, WhatsApp, email and address as patients should see them
- A prefix for appointment numbers, for example ARZ-00001
Existing records
Only if you are moving from another system or from paper. We will tell you what format is usable before you spend time on it.
- Patient list with contact details
- Treatment history, if you have it in a readable form
What we do
This is what the one-time setup fee covers. It is work, not a switch we flip.
- 01
We build your clinic
Your own database, your own container, your own namespace in file storage. Your procedures, prices, staff, roles and branches are configured and checked against how you actually work, not left as an empty system for you to fill in.
- 02
We prove it is isolated
Separate public and private file buckets, object versioning on both so a deleted X-ray is recoverable, and a check that the private bucket is genuinely unreachable from the internet. This is the step we will not skip.
- 03
We set up backups, and test one
Nightly database backups written off the database host and kept for 14 days. Then we restore one into a scratch database and confirm the row counts match. An untested backup is a hypothesis, not a backup.
- 04
We train your team
Reception on booking, the queue and taking payment. Dentists on charting chairside. You on the reporting. Separately, because they need different things.
- 05
We stay reachable
A direct line for the first weeks while habits settle, and someone who knows your deployment specifically rather than a ticket queue.
Ready when you are
You do not need to fill in a form. Send us what you have on WhatsApp and we will tell you what is still missing, or book a demo first and we will walk through the list together.