A connected practice system for CBT therapists, built end to end
- Role
- Sole end-to-end product owner and builder
- Years
- 2025 — 2026
- Status
- Private preview
- Stack
- Next.js, Supabase, Postgres, Stripe, TypeScript
Therapists were running a practice across a diary, a spreadsheet, an inbox and a filing cabinet, with client care and commercial admin split between tools that never spoke to each other. CBT Flow is one connected system covering the therapist application, client portal, CRM, CMS, billing, messaging, calendars and the data foundation underneath all of it.
The problem
A small therapy practice runs on a surprising number of disconnected parts: booking, intake, consent, session notes, treatment plans, homework sent to clients, invoicing, subscription limits, marketing pages and email follow-up.
Each of those has a tool. None of them share a client record. The therapist becomes the integration layer, re-entering the same details and reconciling the same appointment across four systems while trying to deliver clinical work.
The insight
The problem was never a missing feature. It was that no single system held the client, the plan, the sessions, the money and the communications together.
Building it as one product with a shared data foundation meant the operational workflows could finally reference each other: capacity affects booking, booking affects billing, the treatment plan drives the session workspace, and the session drives what the client sees in their portal.
What I built
- A public marketing site and CMS with structured publishing and SEO controls, so the practice's acquisition surface is part of the product rather than a separate website.
- A CRM covering the client lifecycle from first enquiry through onboarding, with a workflow builder for email, wait, condition and tag automation.
- The therapist application: caseload board, Treatment Plan with protocol application, and a session workspace that pulls context, plan, notes, resources and follow-up into one task-focused interface.
- A client portal closing the loop, so assignments and progress flow back to the therapist rather than sitting in an inbox.
- Commercial operations underneath: subscription entitlements, capacity logic, Stripe foundations, invoicing, reminders and reporting.
Key decisions
One data foundation before any feature work
Role-based access, consent evidence, eligibility controls and selected-field encryption were modelled at the start. Retrofitting permissions onto clinical data is close to a rewrite.
Restricted clinical administration
Administrative roles can operate the practice without reading clinical content. The separation is enforced in the data layer, not just hidden in the interface.
Automation kept deterministic
Scheduling, reminders, entitlements and workflow rules are ordinary software with predictable behaviour. This is a clinical context, and predictability matters more than sophistication.
Capacity as a first-class concept
Subscription tier, caseload capacity and booking availability are the same constraint expressed in three places, so they are modelled once.
Gallery
The connected system: site and CMS, CRM, application, data, billing, email and calendars
Proves: End-to-end systems thinking and connected architecture
Status and evidence
- Owner-reported: 20 therapists received private-preview access, completed onboarding and began using the product.
- CBT Flow was demonstrated live at the BABCP Annual Conference and Workshops 2026, held 14 to 16 July at the University of Warwick, Coventry.
- Product definition, systems architecture, UX, data model, implementation, integrations, deployment configuration and documentation were all my own work.
What this does not claim
- This is a private preview, not a fully production-ready or certified product.
- No clinical or business outcomes are claimed, and no adoption, revenue or conversion figures are published.
- No independent security audit or regulatory certification has been carried out.
- AI is not a central capability of this product and is not presented as one.