Clinics
RevKept
Clinic operations software covering booking integration, gap detection, outreach workflows, and staff tooling.
Type
Clinic ops workflow system
Sector
Healthcare / clinic operations
Status
Production with one clinic, two more onboarding
Role
Founder / product engineer
The problem
Recovering revenue meant fixing the workflow, not just sending more messages.
RevKept was built around a simple operational problem: clinics were losing revenue through cancellations, no-shows, and empty slots, while staff handled recovery through memory, diary checks, and ad hoc outreach. The job was not to add another dashboard. It was to turn that operational mess into a system that could detect usable capacity, trigger the right actions, and give staff one place to manage it.
What was breaking
- Empty appointment slots appeared with very little warning.
- Cancellations and no-shows meant lost revenue and wasted slots.
- Patients did not always rebook, so diary value quietly disappeared.
- Staff were patching the process together through messages, memory, and manual checks.
Operational constraints
- The software had to fit around a live clinic workflow rather than asking staff to adopt a separate process.
- Booking data changed quickly, so the system needed to act on useful signals fast enough to matter.
- Staff needed visibility and review, not a black-box automation layer acting without context.
- The product couldn't become another admin surface for staff to maintain.
What I built
A clinic ops system layered onto the existing booking workflow.
Booking system integration
Live API connection to the clinic's diary — no second source of truth for staff to maintain.
Automated gap detection
Surfaces newly available slots fast enough for them to still be commercially useful.
AI-assisted outreach
Automated messaging matched to the right standby patients, with staff review before sending.
Standby claiming workflow
Structured process for patients to take earlier appointments — replacing ad hoc texts and calls.
Staff operations dashboard
One place to see what changed, what needs attention, and what is still unresolved.
Systems involved
More than a dashboard on top of a diary.
Core systems
- Clinic booking-system API
- Automated workflow and message-routing logic
- Staff review and operations dashboard
- Patient standby / claiming flow
- Production deployment and maintained live environment
Why it was non-trivial
- This was not a greenfield app with invented data. It had to sit on top of a real booking system and real staff behaviour.
- The hard part was operational design: deciding what should trigger, what needed human review, and what the staff workflow should actually look like.
- The system had to turn fragmented operational knowledge into software without creating a second source of truth.