Clinic App Starter · Industry version
A practice system built around recurring clients, treatment plans, and session packages — generated into code your practice owns.
Therapy and wellness work runs on relationships measured in months: the Tuesday-at-4 client, the ten-session package, the treatment plan you're both working. This starter reshapes the clinic system around that rhythm — and hands the practice the code.
01 · The problem
Medical clinic software assumes episodic visits: a patient appears, is treated, and leaves the schedule. Therapy inverts that — the default client is recurring, the same slot week after week, and the schedule is really a set of standing commitments with occasional gaps. Software without recurring slots as a first-class idea makes you rebook your entire caseload by hand, forever.
The clinical record is different too. A therapist or wellness practitioner works a plan — goals set, progress noted session by session, plan revised — and progress notes reference that arc. Generic visit notes capture each session as an island, which is precisely what supervision, outcomes tracking, and your own memory don't need.
And the money is cash-pay shaped. Clients buy packages, ask for sliding-scale rates, and — in therapy — request superbills to chase out-of-network reimbursement themselves. A billing model built for insurance claims handles none of this gracefully, so practitioners end up running the actual business in a spreadsheet next to the official system.
02 · Data model
Everything in the base Clinic starter —
patientspractitionersappointmentsintake_formsvisit_notesinvoices— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
treatment_plans | Goals, modality, and review dates per client — the arc that individual session notes attach to and progress is measured against. |
session_packages | Prepaid bundles with sessions remaining, expiry, and per-session value — decremented automatically as appointments complete. |
recurring_slots | Standing weekly or biweekly bookings per client and practitioner, generating appointments ahead and flagging conflicts early. |
03 · Screens
The calendar reads as standing commitments: recurring clients hold their slots, gaps show as openable capacity, and a client ending care releases a whole series at once. Rescheduling one week doesn't disturb the other fifty-one.
Each session note attaches to the client's active treatment plan, so progress reads as a thread, not a pile. Review dates surface when they're due — the difference between working a plan and merely having one.
Completed sessions decrement packages automatically, and cash-pay invoices can generate superbills with the service codes and details reimbursement requires. Sliding-scale rates live per client, applied without a workaround.
04 · In practice
Intake and consents complete before the first session; after it, the client takes a recurring slot and a treatment plan opens with initial goals. From then on the week runs itself — appointments generate, notes thread to the plan.
The package is sold once, tracked automatically: each completed session decrements the count, the balance shows on the client record, and the practitioner is prompted near the end — a renewal conversation, not a surprise.
Plans due for review surface as a list. The practitioner reads the session-note thread, updates goals, and sets the next review date — ten minutes per client, with every note already in one place.
As a first-class entity — recurring_slots generate appointments ahead, hold the client's time, and release the series cleanly when care ends. One-week reschedules don't break the pattern, which is the exact thing generic calendars get wrong.
Yes — invoices carry the service codes, practitioner details, and diagnosis fields a superbill needs, generated from the session data already in the system. You stay cash-pay; your clients get the paperwork reimbursement requires.
The shape fits any recurring-relationship practice — nutrition, coaching, massage, acupuncture. Rename treatment plans to programs, adjust the note structure to your modality, and the recurring, package, and progress machinery carries over unchanged.
Rates live on the client record and apply automatically at billing, and because the code is yours the policy can be exactly yours too — income-banded scales, legacy rates for long-term clients, package pricing that differs by modality.
Dual7 App Starters
A practice system built around recurring clients, treatment plans, and session packages — generated into code your practice owns. Describe your version to start — the output is a project you own.