Delivery
The operating principle
A fixed sequence, because an unpredictable build is the expensive kind
Most practice owners have already bought software that arrived late, or arrived and was never switched on. Both usually trace back to the same thing: no written scope, no milestone anyone could check, and no agreed definition of finished.
The seven phases below are the answer to that. They do not change per client — what changes is how much is being built inside them.
Scope is written before money moves
The statement of work names what is being built, what is excluded and what acceptance means. It is signed first, which is what makes the rest of the sequence predictable.
Something is live in week one
The booking page goes live on day 7, before the reminder layer, payments and dashboard are finished. Real appointments start arriving while the rest of the build continues.
Done is a test, not an opinion
Acceptance is three things you can check yourself — a live booking, a received reminder and a cleared test payment. Nobody signs off on a feeling.
Your input is bounded on purpose
One short call, one written intake, one design review round, one walk-through and one training session. Done-for-you means the work is not handed back to you halfway.
At a glance
- Phases
- Seven, in fixed order
- First milestone
- A live, bookable page on day 7
- Entry build
- 21 days, with a live booking page on day 7
- Payment points
- Two — deposit, then launch
WebtureXperts onboards a maximum of 3 new practices per month — every build is done personally, not templated at scale. Why intake is capped.
The seven phases
What happens, what you do, and where the money sits
Read down the right-hand column and you have the complete list of what is asked of your practice. It is deliberately short.
- Phase 01
Contract
A statement of work defining exactly what is being built, what is excluded, and what the acceptance criteria are. Nothing starts before it is signed.
What you do
Review and sign the SOW.
Milestone
40–50% deposit before any work begins.
- Phase 02
Discovery
A 20-minute call plus an async intake. We map how bookings actually move through your practice today, collect brand assets, and set up technical access.
What you do
One short call, then a written intake you can complete between patients.
- Phase 03
Design
The booking flow and admin dashboard are designed against your real appointment types. At Tier 2 and 3 the portal and app wireframes are designed here too.
What you do
One round of review on the flow before anything is built.
- Phase 04
Development
The booking engine, payment layer, reminder sequences and admin panel are built. Your booking page goes live on day 7 — before the rest of the system is finished.
What you do
Nothing, unless something in discovery turns out to be wrong.
Milestone
Day-7 Fast-Launch: a live, bookable page.
- Phase 05
QA
Booking flow tested end to end, payments tested in Stripe sandbox, reminder delivery tested against real email and SMS endpoints.
What you do
Walk the flow yourself once and tell us what feels wrong.
- Phase 06
Launch
Go-live, then training for whoever runs the front desk. Not a video library — a working session on the system they will actually use.
What you do
Attend training with your front-desk team.
Milestone
Final build payment; Care Plan billing begins.
- Phase 07
Care Plan
Hosting, monitoring and security patching, a fixed allocation of change-request hours each month, and a reporting and strategy touchpoint at your tier's cadence.
What you do
Send change requests as they come up.
Phases 1 to 6 are the build. Phase 7 is what the system runs on afterwards, and it is the only phase with no end date — which is why it is billed monthly rather than folded into the build fee.
The 21 days
What the entry build looks like as a calendar
The No-Show Shield build, day by day. Larger tiers add work after day 21 rather than delaying the point where bookings start arriving.
- Days 1–7
Discovery to live booking page
A 20-minute discovery call and async intake, then your booking page goes live and starts taking real appointments. This is the Fast-Launch milestone.
- Days 8–14
Reminders, payments, dashboard
Email and SMS reminder sequences, Stripe payment and deposit collection, and the owner admin dashboard are connected and tested.
- Days 15–21
QA, training, launch
Full QA pass, front-desk training, launch, and Care Plan billing begins.
How the longer builds stack
Each tier is the one below it plus additional scope, so the delivery sequence never restarts and the day-7 milestone holds regardless of tier.
- No-Show Shield21 days, with a live booking page on day 7
- Client Retention EngineRoughly 5 weeks — the No-Show Shield build plus 3 weeks
- Signature Practice AppRoughly 8–9 weeks — the Retention Engine build plus 3–4 weeks
- Custom / EnterpriseSet during scoping
Why day 7 is the milestone that matters
A booking page that is live in week one starts capturing the after-hours requests your practice is currently losing to voicemail, while the reminder layer, payments and dashboard are still being built behind it.
It is also the earliest honest proof that the build is real. You are not asked to wait three weeks and trust a status update.
Definition of done
Three tests, all of which you can run yourself
Acceptance is not a sign-off meeting. It is a short list of things that either work or do not.
The build is accepted when the client can complete a live booking, receive a reminder, and complete a test payment without error.
- A real booking can be completed end to end on the live site.
- A reminder is received at the configured interval, over both email and SMS.
- A test payment clears through your own Stripe account without error.
Acceptance is also the point the 90-day performance window is measured from, so it is worth being precise about. What the guarantee commits to.
Everything asked of your practice
The complete input list, pulled out of the phases above so it can be read in one go.
- 01Contract. Review and sign the SOW.
- 02Discovery. One short call, then a written intake you can complete between patients.
- 03Design. One round of review on the flow before anything is built.
- 04Development. Nothing, unless something in discovery turns out to be wrong.
- 05QA. Walk the flow yourself once and tell us what feels wrong.
- 06Launch. Attend training with your front-desk team.
- 07Care Plan. Send change requests as they come up.
Two commercial milestones sit alongside those inputs: a 40–50% deposit before any work begins, and final build payment at launch, when Care Plan billing starts.
Outside the build
What is excluded, stated before you sign rather than after
Every item here is a real boundary. Naming them is what keeps the milestones and the fixed scope meaningful.
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.
Before any of this, find out whether the build is worth doing
The Recovered Revenue Report puts a written monthly figure on what your current booking flow leaks. If the number is small, we will tell you that instead of scoping a build.
After launch
Phase 7 — the Care Plan
A booking system is not a deliverable you file. It takes payments, sends messages on a schedule and holds your availability, which means it needs hosting, monitoring and patching for as long as it runs. That is what the Care Plan is, and it starts billing at launch rather than at signature.
It is also the vehicle the 90-day guarantee runs through. If the no-show rate has not measurably dropped in that window, the remedy is continued work under this plan at no additional charge — which is only possible because the plan exists.
Included
- Hosting, monitoring and security patching for the whole system.
- A fixed allocation of change-request hours each month.
- Reporting, plus a scheduled strategy touchpoint at your tier's cadence.
Not included
- Third-party fees you pay directly — Stripe processing, SMS sends, app store accounts.
- Unscoped mid-build feature requests.
- Compliance certification work.
- Content writing, unless agreed in the statement of work.
- Additional locations beyond the ones in scope.
Care Plan
$99–$699/mo
Set by tier, and confirmed in your statement of work before the deposit. The change-hour allocation and reporting cadence scale with the tier rather than being quoted per request.
How data is handled
The booking layer collects what it needs to schedule an appointment and take a payment. Clinical records stay in your clinical system, and no certification is claimed.
Questions
What owners ask before phase 1
Answers here restate the documented engagement terms. Where this page and your statement of work differ, the statement of work governs.
- How long does a build actually take?
- The entry build is 21 days, with a live booking page on day 7. Larger builds stack on top of it rather than restarting: Client Retention Engine is roughly 5 weeks — the no-show shield build plus 3 weeks, Signature Practice App is roughly 8–9 weeks — the retention engine build plus 3–4 weeks, and Custom / Enterprise is set during scoping.
- What happens before we pay anything?
- The Recovered Revenue Report and the System Assessment both come before any commitment and carry no charge. Once you decide to build, the statement of work is written and signed, and a 40–50% deposit is taken before work begins. Nothing is built on a verbal scope.
- How much of our time does this take?
- A 20-minute discovery call, a written intake you can complete between patients, one round of review on the booking flow, one walk-through during QA, and a training session for whoever runs the front desk. Outside those, phase 4 asks nothing of you unless discovery turned out to be wrong.
- What if we are slow getting things back to you?
- The phase inputs are what the schedule is measured from, so delays there move the launch date rather than compressing the build. That matters commercially as well: the 90-day guarantee window starts at launch, not at signature.
- Can we change the scope mid-build?
- New scope is quoted separately rather than absorbed into the current build. That is precisely what protects the day-7 and 21-day milestones — a build that silently accepts additions is a build with no delivery date.
- Do we have to replace our practice management system?
- No. The system sits across booking, reminders, payments and owner visibility; clinical records stay in the clinical system you already use. Where a PMS, EHR or POS integration is needed, it is scoped individually under Custom / Enterprise rather than assumed.
- When does Care Plan billing start?
- At launch, alongside the final build payment. Before that point there is no monthly fee, because there is no live system to host, monitor or patch. The Care Plan range is $99–$699/mo, set by tier.
Start at phase zero
Get the figure the build would be scoped against
The Recovered Revenue Report gives you a written monthly number for what your current booking flow leaks, plus a recorded teardown of where it goes. Three business days, no charge, and no obligation to start phase 1.
- 20 minutes discovery call, only if you want one
- 90-Day No-Show Recovery Guarantee
- 3 new practices a month