Clinic portal
The one screen the practice actually opens
Most of what a practice needs from us on a given day is: who wrote in, what did I say, and change that sentence on the website. The portal is those three things and stops there.
What it does
Read the inbox
Every enquiry, newest first, with its source and its consent record.
Move a patient forward
One tap per state, with an optional note. The move is recorded; it cannot be undone into a different number.
Edit the website
The same config the build reads. Change a service, a photo, an opening hour.
Never see another practice
The tenant boundary is in the contract, not in a filter someone remembered to apply.
Work on a phone
44px controls throughout. The front desk uses this standing up, between patients.
Stay out of the index
The portal is published noindex. It is a tool, not a page we want ranking.
Why it is this small
Because the contract is shared, not because features were cut
The portal derives its types from the same file the API validates against. Removing a field breaks the build on both sides in the same commit, instead of breaking a screen in production three days later. That is what buys the confidence to keep the surface small.
About the portal
How many people can use it?
As many as the practice has. It is priced per practice, not per seat — a two-person practice should not be paying twice to answer the same patient.
Can I see where a patient came from?
Yes, on the record itself: source, medium, campaign and the page they landed on. It is attached at capture, so it cannot be reconstructed wrongly later.
Does it replace my practice-management system?
No. It is the patient path and the public presence. Clinical records stay where they are.
Open it and try to break it
The demo is the real portal with real data in it, not a slideshow.