Illustrative scenario — not a client
Clinic booking app with card payments
A two-location clinic where patients book their own appointments on their phones and pay by card when they book.
Reviewed by Atin Agarwal, IOanyT · 5 October 2026
Document 1 · Readable requirements
Plain prose, not a bullet dump
An excerpt. A real specification covers every screen and flow.
- R-01
A patient books a slot without calling
The patient chooses a location, a practitioner (or "anyone available") and a service, sees the free slots for the next four weeks, and books one. A slot is held for ten minutes while they pay; if payment does not complete, it is released.
- R-02
Payment is taken at booking
The full price of the service is charged by card at booking. The patient receives an email receipt and a confirmation with the address, the practitioner and a link to reschedule or cancel.
- R-03
Cancellation follows the clinic's rule
A patient can cancel or move a booking up to 24 hours before it starts, with a full refund. Inside 24 hours the booking can be moved once but not refunded. The clinic sets the cut-off.
- R-04
The front desk sees the day at a glance
Front-desk staff see each practitioner's bookings for the day, can mark a patient as arrived or no-show, and can book, move or cancel on a patient's behalf when they phone in.
- R-05
The clinic controls availability
Each practitioner has working hours per location, breaks and holidays. Changes apply to future slots only; existing bookings that clash are flagged to the front desk, never silently cancelled.
Document 2 · Wireframes
Every screen, to review
A few of the screens. Wireframes show what is on each screen and where — not the visual design.
Location
Practitioner
Physiotherapy · Thu 4:30
Name
Card
Thu 4:30 · Sector 18
- Cancel booking
- Get directions
- Receipt
Booked
Arrived
No-show
Swipe for more screens →
Document 3 · Walkthrough
A day in the life of the app
People catch missing scope in a story far more reliably than in a table of requirements.
At 9:10 a patient opens the clinic's link on her phone, picks the Sector 18 clinic and "anyone available" for a physiotherapy session, takes the 4:30 slot and pays by card. The confirmation arrives while she is still on the page. At 9:12 the booking appears on the front-desk board. The next afternoon a reminder email goes out. At 4:25 she arrives; the receptionist taps "arrived", and the practitioner sees her name turn green.
Document 4 · Scope
Defined by both lists
In this release
- Patients pick a clinic, a practitioner and a free slot
- Card payment taken at booking, with receipts by email
- Reminders by email the day before
- Front-desk view of the day's bookings, with reschedule and cancel
- Practitioner availability and holidays, set by the clinic
- Admin console for clinics, practitioners and prices
Not in this release
- Native mobile app (the web app works on phones)
- SMS reminders
- A second language
- Insurance claims
- Video consultations
On a real quote, each carries a price to add it later.
Document 5 · Assumptions register
What the price rests on
If one turns out to be wrong, that is a pre-agreed trigger to re-quote — not an argument.
- English only
- Two locations, under ten thousand patients
- The clinic provides practitioner photos and service descriptions
- The payment gateway has a standard API
Document 6 · The quote
Three tiers. Every line visible.
QA and security sit in every tier. They are never what a smaller tier removes.
| Line item | Lean | Standard | Premium |
|---|---|---|---|
| Booking flow: location, practitioner, slot | ● | ● | ● |
| Card payment at booking, with receipts | ● | ● | ● |
| Confirmation and reminder emails | ● | ● | ● |
| Patient self-service reschedule and cancel | ● | ● | ● |
| Front-desk board: arrived, no-show, book on behalf | ● | ● | ● |
| Admin console: clinics, practitioners, services, prices | — | ● | ● |
| Practitioner hours, breaks and holidays | — | ● | ● |
| Booking and revenue reporting | — | ● | ● |
| Waiting list for full days | — | — | ● |
| Multi-location reporting | — | — | ● |
| Priority support, three months | — | — | ● |
| Test coverage 80%+ | ● | ● | ● |
| Security review | ● | ● | ● |
| Dependency scanning | ● | ● | ● |
Your own quote shows a total for each tier, locked for 14 days from the moment it is issued.
Lean
Booking, card payments, email reminders and the front-desk board
Standard
Lean plus the admin console, practitioner availability rules and reporting
Premium
Standard plus a waiting list, multi-location reporting and priority support
An illustrative scenario, not a quote for your project. Your quote is built from your own specification, with a blended total on every line instead of a rate card, and locked for 14 days once issued.
What arrives
Enough to decide with. Then enough to build from.
| Artifact | Free | On signature |
|---|---|---|
| Readable requirements Plain prose, not a bullet dump | Included | |
| Wireframes Every screen, to review | Included | |
| Scope summary What the build covers | Included | |
| Explicit exclusions The "not in this release" list, with backlog prices | Included | |
| Assumptions register Every load-bearing assumption, stated | Included | |
| Three-tier itemized price Traceable line items | Included | |
| Machine-readable spec exports | On signature | |
| Editable wireframe files | On signature | |
| openapi.yaml The API contract | On signature | |
| Mapping CSVs | On signature | |
| Given/when/then suites | On signature | |
| Architecture decisions | On signature |
What arrives free
- Readable requirements Included Plain prose, not a bullet dump
- Wireframes Included Every screen, to review
- Scope summary Included What the build covers
- Explicit exclusions Included The "not in this release" list, with backlog prices
- Assumptions register Included Every load-bearing assumption, stated
- Three-tier itemized price Included Traceable line items
What arrives on signature
- Machine-readable spec exports On signature
- Editable wireframe files On signature
- openapi.yaml On signature
- Mapping CSVs On signature
- Given/when/then suites On signature
- Architecture decisions On signature
What happens next
From your description to the build
- 01
You describe it
In plain words. Today a person runs the intake with you by email.
- 02
It asks back
The questions a good engineer would ask, before anything is priced.
- 03
The documents arrive
Everything on this page, for your project, before you pay anything.
- 04
The price holds
The quote is locked for 14 days from the moment it is issued.
- 05
You sign, we build
Every requirement traced from quote line to accepted build. Changes priced before you approve them.
Defined by both lists
Get this quoted for your project.
No signature, no call. A business email unlocks the full quote.