Bookings SaaS
that replaced spreadsheets.
A multi-location service business running on spreadsheets and WhatsApp. We shipped roles, reminders, payments and a calm ops dashboard, with the whole team trained in one session.
↑ steadyNo-shows
↓ controlledRepeat
↑ compounding
Bookings SaaS replacing sheets + WhatsApp
Bookings lived in three places: a shared sheet, a WhatsApp group and the memory of the front desk. No-shows, double-bookings and payment follow-ups ate the day.
Multi-location made permissions the real problem — owners, managers, front desk and therapists each needed a different view of the same schedule.
- —Modelled the operation first — locations, staff, services, availability — before drawing a single screen.
- —Built the booking loop end to end: customer books, staff sees it, a reminder goes out, payment is collected, no-show risk is visible.
- —Made the ops dashboard calm: today’s utilisation, revenue and exceptions in one glance — not a wall of charts nobody reads.
- —Trained the whole team in one session and left docs behind. Adoption was the acceptance test.
Four moves, no drift.
Model the operation
Locations, roles, services and availability mapped with the people who run the desk. The data model earns its keep here.
Build
Multi-tenant web app: roles, bookings, reminders and payments — boring tech, clean seams, analytics on the loop.
Launch at one location
One site runs on it for real before rollout. We watch the loop complete, then fix what the desk actually feels.
Roll out + harden
Remaining locations onboarded, staff trained, docs handed over. 30 days of fixes before a calm handover decision.
- Front desk hours
Bookings, reminders and payment follow-ups stop living in chat threads and a shared sheet.
- No-show control
Reminders and deposits on by default — the schedule protects itself without someone policing it.
- Owner visibility
Revenue, utilisation and exceptions per location, live — decisions stop waiting for month-end.
Client names + measured outcomes shared on intro call, with permission.
Support did not end at launch. When we needed help, they were there.
Facing
something similar?
Want a quote, need to talk through your version, or is your case different? Get in touch — we'll tell you the smallest build that gets there.