Rent a clinical loop you can't repurpose, use a generic portal with no loop at all, or join a marketplace that owns your clients. This is the fourth option.
Every practitioner in a sensitive field has the same fear: a platform operator reading, mining, or leaking the private substance of their client relationships. The operator here runs on metadata alone — that an event occurred, that an obligation is open or met, that a payment cleared — and is barred from the content by the architecture.
You pay per instance, not per seat. And when the engagement ends, your practice keeps the portal, the record, and the clients. The asset survives the relationship.
Everything about your practice is configuration. The system underneath never changes.
A new deployment is a vocabulary map and a domain configuration — not a rebuild.
Running in production against live client data today.
The privacy wall is the moat.
No clinical platform, generic portal, or marketplace can make this claim — each of them is built to do the opposite.
The operator structurally cannot read your clients' records
Not "we promise not to." The platform runs on metadata — that an event occurred, that an obligation is open or met, that a payment cleared — and the content sits behind a wall the architecture enforces. That is a privacy guarantee, not a privacy feature: the former can't be reversed by a future product decision.
The record belongs to your client and your practice
Marketplaces claim to respect users while owning everything they generate. This inverts the default — and the operator-blind wall is what makes the claim survive scrutiny rather than read as marketing.
You are paid directly, in your own currency
Conditional payments run through Stripe Connect destination charges: the platform orchestrates the flow but is not the merchant of record, so the practitioner is paid in local currency and the platform takes zero net margin on the transaction.
The obligation loop is the thing no portal has
Here is what you owe, here is your status, here is the nudge. Generic portals are document-and-billing hubs with no place for a prescribed obligation carrying a compliance state — which is why their logins get ignored.
Three categories, three structural failures.
The loop can't leave the clinic
The only incumbents with a mature obligation loop — but it's welded to healthcare protocols and adherence vocabulary, priced per seat for clinicians who bill payers, and built for the operator to hold the content.
Their core object is a document, not an obligation
Cheap, brandable, live in a day — and structurally the wrong tool. There is no place in them for a prescribed obligation with a compliance state, which is why they compete on price.
The operator owns the client, the transaction, and the data
Pay-per-minute wallets with the platform as sole merchant of record — the exact inverse of a practice that needs to own its record. This is the category our buyers are running from.
Any practice where the client owes something between engagements.
And where privacy the operator cannot breach is the reassurance the buyer most needs.
Immigration law
Clients owe deadline-bound documents, appointments, and filings — and a missed obligation can sink a case. High-anxiety, privacy-sensitive, often underserved communities: the client-owned checklist is the value.
Estate-planning execution
Clients must execute and fund instruments after the engagement — a notorious drop-off the lawyer currently cannot see at all.
Consulting & advisory follow-through
Implementation steps assigned between sessions, with no structured way to know whether they actually happened.
Therapy & counselling homework
Between-session assignments and check-ins, where operator blindness is not a nice-to-have but the premise.
Traditional & spiritual practice
The reference deployment: a practitioner records a reading, prescribes actions and restrictions, and tracks follow-through. Live in production — and demonstrable.
The scoping audit maps your real workflow into events and obligations, reads the privacy and regulatory lines your vertical sits near, and returns a go/no-go verdict.
The method is part of what you're buying.
Domain-model workshop
Your real workflow becomes events, obligations, and restrictions — signed off before any code is written.
Privacy-boundary read
Where the wall sits is cheap to design up front and ruinous to retrofit. This is the load-bearing decision of the whole build.
Fixed scope, fixed fee
The quote from scoping is the price. Scope changes are decisions you make, not invoices that arrive.
Handed over, documented
The instance, its database, and its documentation transfer to your practice. Every decision reconciled against the repository, not slideware.
Three stages, one sequence. Start at the first.
Only the scoping fee is charged today — and it is credited in full toward your build if you proceed.
Scoping engagement
A go/no-go verdict and a fixed build quote. Standalone value if you walk.
Scoping + full build
The finished portal, branded and private, handed over as an asset your practice owns.
Charges the $3,500 scoping fee and holds your build slot.
Build + retainer
Keeping the portal live, paid, and private — not "hosting and bug fixes".
Get the AI Project Scoping Kit.
The first step we take with every client is scoping the problem before touching the build. We've packaged that step as the AI Project Scoping Kit — a working system you can run yourself, useful even if you never hire us.
Get the Scoping Kit — $49A scoping conversation takes thirty minutes: your workflow, your obligations, your privacy line.
Book thirty minutes