Scoping, in writing
Fit
Stated before the form rather than after it, because the fastest way to waste your afternoon is to fill in nine questions and then be told no.
None of these is a judgement. They are the four reasons an assessment most often comes back as a no, and they are cheaper to read than to discover.
What comes back
Not a proposal deck. A short document that answers the four questions you would otherwise spend two calls establishing.
Which tier fits, and why not the one above it
Matched against the published ranges. If the tier below does the job, that is what comes back — a bigger build that solves a problem you do not have is a worse outcome for both of us.
What would have to integrate
Named against your actual practice management software. Where an integration is not possible, you are told that before money changes hands rather than during week three.
A build sequence with dates
What lands on day 7, what lands by day 21, and which parts depend on something only your team can supply.
Whether there is a slot
Intake is capped at 3 practices a month. If the next slot is six weeks out, the reply says six weeks.
Not ready to talk scope? Start with the free report instead — it asks for less and costs nothing.
Step 1 of 3 · The practice
For reference
Published, unchanged, and the same figures the assessment quotes against. Nothing is marked up after a conversation.
Solo and single-provider practices
The booking, reminder and payment layer that stops empty slots from being invisible. Live bookable page inside 7 days.
Practices that depend on repeat and recurring visits
Everything that stops a no-show, plus the portal, CRM and recall automation that bring the same client back without a phone call.
Practices whose brand is part of the price they charge
Your own native iOS and Android app, carrying your name in the store, mirroring the portal your clients already use.
Multi-location groups and practices with an existing PMS, EHR or POS
Scoped individually. Multi-location rollouts and PMS / EHR / POS integrations are quoted against your actual systems, not a package.
Terms, up front
Both of these are in the statement of work. They are here because reading them before you enquire is better than reading them after you sign.
Acceptance
The build is accepted when the client can complete a live booking, receive a reminder, and complete a test payment without error.
Not included
Unscoped mid-build feature requests
New scope during the build is quoted separately rather than absorbed. This is what protects the day-7 and 21-day milestones.
Third-party fees
Stripe processing, SMS sends and app store accounts are paid by you, directly to those providers. No markup passes through us.
Compliance certification work
We build with data minimisation as the default, but we are not a compliance certification provider and we do not claim any certification. Formal certification is a separate specialist engagement.
Content writing
Copy for your site pages is not included unless it is written into the statement of work.
Additional locations
Each location beyond the scoped build is quoted separately, under Custom / Enterprise.
Questions