Cut It
You have a brief and a fixed budget. Sort the features into build, later and cut, then see how our call compares, with the reason for each one. Nothing you choose here leaves your browser.
Illustrative example The brief from our home page. Not client work.
A clinic booking assistant
A dental clinic loses money to missed appointments. Patients message to book and wait for a call back, and the front desk phones every patient the day before to remind them. The owner wants an AI assistant to fix it.
Your budget for the first release is 5 build points. Anything you put in Build spends them; Later and Cut are free.
Two features make the first release.
- Build first
Booking over WhatsApp, with reminders
Patients are already on WhatsApp, so there's nothing to install, and the reminder arrives where it will be read.
- Build first
Payment at the time of booking
It cuts no-shows with no AI at all. A paid slot is a slot people turn up for.
- Don't build
A custom-trained model
An off-the-shelf model does this job. A custom one costs more, needs data the clinic doesn't have, and changes nothing a patient notices.
- Cut, to 2
An admin dashboard with 14 reports
Keep the two reports someone will actually read. Nobody reads the other twelve, and each one is something to build and maintain.
- Later
No-show prediction
It needs months of real booking data first, and the first release is what collects it.
- Later
A voice assistant
Not until the text flow is proven. Voice is harder to get right and harder to test, so it waits for evidence from chat.
Why this cut
The two features that make the first release fix the problem the clinic has today, and neither needs a custom model. The later ones wait for the evidence the first release produces. The cut is where most of the money is saved.
The method behind it: The Scope Cut, and How to scope an AI product.