DMEDesk / platform overview
The operator’s desk.
Run the SaaS business without stepping into a customer’s patient records.
Needs the founder’s attention
One fictional account, a clear next action
Resolve Acme’s 3 rejected import rows
246 rows validate; no changes applied. Owner sign-off follows a clean rerun.
Review launch readiness →Verify BAA and privileged-access readiness
Do not ingest customer PHI before required agreements and access controls are approved.
Review control gates →Connect real lead capture before inviting prospects
The public walkthrough form is a non-persistent UI preview. It creates no sales record.
Preview the form →Tenant snapshot
All tenants →| DME company | Lifecycle | Seats | Plan thesis | Next action |
|---|---|---|---|---|
| Acme DME Fictional tenant · acme-preview | Pre-launch review | 3 / 15 | Core · $499/mo | Import review + owner sign-off |
Platform signals
Telemetry: not connected
No uptime, error-rate or usage claims are fabricated.
Billing provider: not connected
Stripe will be connected later, after the offer and launch flow are ready.
Illustrative operator activity · PST
Nov 7, 05:00 · Launch review queued
Acme fixture · 3 import rows require review
Nov 7, 04:45 · Core offer modeled
Acme fixture · $499/month + $999 launch
Platform boundary
This public prototype grants no administrative authority. A real console needs separate operator roles, enforced MFA, server-side authorization and audited support access. Shop admins must never inherit platform permissions; customer PHI stays out of sales and billing views.