DMEDesk / sales & subscription model
The business behind the desk.
Run the SaaS business without stepping into a customer’s patient records.
Sales pipeline
Fixture data only. The homepage form does not create a lead here.
| Company | Fit / stage | Proposed offer | Next step | Owner |
|---|---|---|---|---|
| Acme DME Fictional demo opportunity | Independent / hospice-contract Launch scoping | $499/mo Core + $999 launch | Resolve import rejects; agree scope | Darren · Founder role concept |
Commercial model · Thesis
Core subscription / monthly$499
Standard launch / one-time$999
Illustrative first-month total$1,498
Excludes any applicable taxes or additional scope. This arithmetic is a proposal, not an invoice or charge.
Growth / later / monthly$899
Only after Core and AI validation. Same 15 included seats; usage limits still to be established.
Stripe will be connected later.
Not connectedNo live customers, subscriptions, invoices, card collection, payment links or charges are created by this prototype.
- Later: company-only customer and subscription mapping
- Later: signed, replay-safe webhook entitlement updates
- Later: launch-fee invoicing and owner-approved tax policy
- Never: patient data or clinical documents in Stripe
Three different billing contexts
01
DMEDesk operator
This console models SaaS subscriptions, launch fees and sales—not hospice invoices.
02
Acme’s SaaS plan
The shop sees its own proposed DMEDesk subscription, seats and terms.
Shop subscription preview →03
Acme’s hospice invoices
Acme bills Lakeside Hospice for service periods and agreed per-diem rates.
Hospice invoice preview →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.