One screen for clinics that run on appointments
A multi-tenant practice management system that brings the calendar, client records, session packages and payments of appointment-based businesses into one application.
- Product
- SeansGO
- Field
- SaaS · Healthcare
- Year
- 2026
- Live at
- seansgo.com
Problem
In small appointment-based businesses the calendar lives in a diary, payments in a ledger and client notes in a separate file. Working out how many sessions someone has left, or who still owes money, means counting by hand. Off-the-shelf booking tools either offer only a calendar or are hospital-scale systems that don't fit how a small practice runs.
Requirement
A single practitioner and a clinic with several specialists both had to be able to use the same system. Each clinic's data had to stay completely separate, staff could only see their own clinic, and clients were never meant to log in at all.
→Solution
We built it multi-tenant: every clinic runs isolated with its own data, and permission checks live in one service layer. The calendar is managed by drag and drop, session packages are tracked with remaining sessions and outstanding balance, and payments are reported split by cash, card and transfer. There is deliberately no client portal — only clinic staff have accounts.
How we approached it
- 01
The same one-way layer flow in every feature: repository → service → server action → interface. Permission checks sit in the service layer, never in the UI.
- 02
The clinic identity is embedded in the session token; access to another clinic's data is blocked at the data layer rather than hidden in the interface.
- 03
The online booking page needs no account — it's just a form. Even the one case where a client might have needed to log in is removed.
- 04
The calendar supports drag-to-move and edge-drag to change duration; the screen staff use most is operated with the fewest clicks.
- 05
Tests run in a forked pool with a single worker — parallel runs were producing false passes while testing multi-tenant data isolation.
Screens
Outcomes
We keep outcomes qualitative rather than claim numbers we haven't measured.
The whole operation on one screen
Calendar, client record, session package, payments and expenses live in the same application; separate ledgers and spreadsheets are no longer needed.
Complete data isolation between clinics
Several clinics run on the same installation and none can see another's data.
Less manual tracking
Remaining sessions, outstanding balance and monthly revenue are read from the system rather than counted by hand.
Infrastructure that can be handed over
The backup chain, environment variables and deployment process are all documented.
Built with
- Next.js
- React
- TypeScript
- Prisma
- PostgreSQL
- Auth.js
- Tailwind CSS
- TanStack Query
- Zod
- Vitest
If you have a question, let us start there.
Tell us what you are trying to do. On the first call we will tell you whether we are the right fit, roughly how long it takes and how we would approach it. No sales pitch.
orsenyazilim@gmail.com