Business Models — B2B2C vs B2C (Enterprise Arrangements)
Feature Overview
PPP sells through two commercial channels: B2B2C (an enterprise — e.g. Queensland Health — pays for a block of seats and the doctor self-signs-up under that subsidy) and B2C (a doctor pays directly, either for CPD Home or full PPP — see the canonical PPP pricing table). This spec is the engineering translation of Matt's "Enterprise Arrangements" Notion page and the canonical reference for billing flow, account provisioning, data ownership, and admin tier visibility across both channels.
Open Questions
All commercial-modelling questions resolved — see Closed Questions below.
Closed Questions (7) — click to expand
| # | Question | Ref | Resolution |
|---|---|---|---|
| Q1 | What is the "specific code to activate this discount and linking"? Promo code, signed JWT in invite link, eligibility-by-domain, or claim-by-employer? Matt flagged this with a ? in Notion. | Notion ¶ | Matt-ratified (b) — #8175: per-contract signed magic-link invite with a per-contract discount field. No raw promo codes (copy-paste leak risk). Engineering proposal (signed magic-link invite issued by Hospital Admin, #4951 pattern; seat consumed on activation not click) is confirmed. No domain fast-path in v1. † |
| Q2 | Does Matt envisage a pure B2B model (enterprise pays, enterprise consumes — no doctor self-sign-up, e.g. compliance reporting only)? Notion describes B2B2C and B2C only. | Notion | Confirmed (transcript 2026-04-22) — no pure-B2B. Two channels only: B2C self-signup, and a B2B2C hybrid where the enterprise pays a per-seat subsidy and the doctor pays the remainder and owns their data. † |
| Q3 | If a doctor leaves the enterprise (e.g. resigns from Q Health), does their portfolio (a) follow them with a personal subscription, (b) freeze read-only, or (c) hand back to the enterprise? | — | Confirmed (transcript 2026-04-22) — the doctor owns the data and it follows them (Matt: '…so that they own their data'); engineering elaboration = 30-day read-only grace then step-down to B2C. † |
| Q4 | Founding Partner Rate (150 AUD/seat) vs Standard (200 AUD/seat) — is this a per-tenant flag set by Sales, or codified per-contract with an effective-from date? | Notion ¶ | Matt-ratified (c) — #8175: no fixed published list price; per-contract price set by Sales per enterprise deal. Per-contract field with effectiveFrom / effectiveTo is the correct model (Sales sets once at contract creation; renewals create a new contract row). The Founding 150 / Standard 200 figures are examples only — not constants in code. † |
| Q5 | Implementation Fee (one-time) vs Year-2 recurrence — confirm Matt's Y2 figure (1,612,000 AUD × CPI) excludes Implementation Fee re-charge. | Notion ¶ | Matt-ratified (c) — #8175: build Y2 adjustable; the Y2 amount is a runtime value on the contract record, not a hard-coded formula. Implementation Fee is confirmed one-time (excluded from Y2+ automatically). CPI uplift applies to recurring lines only. † |
| Q6 | Work-Order rates (175–220 / 130–160 / 150 AUD per hour) — are these stored as platform-wide constants or per-contract? | Notion ¶ | Matt-ratified — #8175: decided per enterprise deal; per-contract rate values only, no published platform-wide rate card. The rate bands (175–220 / 130–160 / 150 AUD) are illustrative from Notion; actual rates are negotiated per contract. † |
| Q7 | "Light version to email" upsell hook for B2C interactive features (e.g. consultant reviewing surgical logbook, feedback) — does this re-use the MB version or build new? | Notion ¶ | Matt-confirmed built — #8175: Matt states the light-version email is already implemented ('haven't we already built q7?'). The reuse-vs-new-build question is resolved by the existing implementation. Enterprise-communication applicability acknowledged but deferred. The react-email / tokenised-URL architectural pattern (no account required, 24h expiry, PPP upsell CTA) remains the reference should any further extension be needed. † |
Matt's Requirements (from Notion brief)
Source: Enterprise Arrangements
B2B2C
- Sale to Enterprise; Enterprise pays for a number of seats (e.g. 150 or 200 AUD) and that subsidises users' payment.
- User still signs up to platform themselves (personal email) but under discounted enterprise agreement.
- Specific code to activate this discount and linking (?).
- Enterprise gets Hospital Admin Accounts for administrative access and Super Admin Accounts for group anonymised cohort insights.
- Potential Super Admin tier line-of-sight: Hospital → HHS → Organisational (tiers above can see below group insights; tiers below can't see above).
- Example: Q Health.
B2B2C — Year 1 (Q Health worked example)
- 8,000 seats [50% Cohort] = 1,200,000 AUD (150 AUD/seat/yr Founding Partner Rate; std 200).
- Queensland Health Platform License = 350,000 AUD (Founding Partner Rate; std 480,000).
- Queensland Health Cloud Hosting + Infrastructure ≈ 28,000 AUD.
- Dedicated Support Tier + Account Mgmt = 34,000 AUD.
- Implementation Fee (one-time) = 150,000 AUD (Founding Partner Rate; std 200,000).
- Year 1 total: 1,762,000 AUD.
B2B2C — Work Orders / Bespoke Modifications
- Platform development (new features, integrations): 175–220 AUD/hour.
- Configuration and implementation support: 130–160 AUD/hour.
- Medical education / CPD advisory (specialist): 150 AUD/hour.
B2B2C — Year 2
- Year 1 figure − Implementation Fee + CPI = 1,612,000 AUD × CPI.
B2C
- Direct-to-Doctors sale: CPD Home or PPP Full Platform.
- All interactive features require a light version to email if the recipient is not a PPP user (?built in MB version).
- Provides upsell opportunity (e.g. consultant receiving email to review surgical logbook or feedback).
- CPD Home: 299 AUD annual (incl. GST) — GST-inclusive round pricing per Matt's #10117 decision (was 275 AUD).
- PPP Full Platform: 1,699 AUD annual (incl. GST) — per Matt's 2026-08-20 WhatsApp confirmation (#11890) (was 1,199 AUD, itself per #10117's decision, was 1,089 AUD).
Attachments referenced in Notion
QH_Enterprise_Agreement.pptx(Q Health Enterprise Agreement deck) — attached on the Notion page; not transcribed here.
Acceptance Criteria
B2B2C — provisioning & sign-up
- ⏳ Enterprise tenant record holds seat count, rate (Founding/Std), term, contract dates.
- ⏳ Hospital Admin issues a signed magic-link invite (Q1, #4951 pattern) that activates the discount and auto-links the account on sign-up. No raw promo codes.
- ⏳ Domain-based fast-path (Q1): when a sign-up email matches a registered enterprise domain (e.g.
@health.qld.gov.au), the corresponding enterprise tenant is suggested as a one-click join. - ⏳ Doctor signs up with personal email and is linked to the enterprise tenant on accepting invite.
- ⏳ Doctor pays nothing at checkout when enterprise covers the seat.
- ⏳ Seat consumption is decremented on doctor activation; admin sees seats-used / seats-remaining.
- ⏳ Departure flow (Q3): when a seat is revoked (resignation/contract end), the doctor's account flips to read-only for 30 days, then prompts step-down to B2C CPD Home or full PPP (see pricing). Enterprise cohort views drop that doctor immediately on revocation.
B2B2C — admin tiers & visibility
- ⏳ Hospital Admin sees individual-level admin data scoped to their hospital only.
- ⏳ Hospital Super Admin sees anonymised cohort insights for their hospital.
- ⏳ HHS Super Admin sees anonymised cohort across hospitals in that HHS.
- ⏳ Organisational Super Admin sees anonymised cohort across all HHSs in the org.
- ⏳ Lower tiers cannot see upward; upper tiers can see downward group insights only.
B2B2C — billing & contract
- ⏳ Per-seat price stored per-contract (amount set by Sales per enterprise agreement — no fixed list price), with
effectiveFrom/effectiveTo(Q4 ratified #8175). - ⏳ Platform License, Hosting, Support, Implementation fees recorded as line items on the contract.
- ⏳ Implementation Fee marked one-time (Q5) — excluded from Y2+ invoices automatically.
- ⏳ Year 2 invoice excludes one-time Implementation Fee and applies CPI uplift to recurring lines only.
- ⏳ Work-Order line items capture rate band (Platform Dev / Config / Medical Ed) and hours at per-contract negotiated rates (Q6 ratified #8175 — no platform-wide rate card; all rates are per enterprise deal).
B2C — direct subscription
- ⏳ Doctor purchases CPD Home (see pricing) via Stripe.
- ⏳ Doctor purchases full PPP (see pricing) via Stripe.
- ⏳ Subscription renews annually unless cancelled.
- ⏳ Light-version emails (Q7 — Matt-confirmed built #8175) — interactive feature emails to non-PPP recipients implemented via
react-emailtemplate + tokenised 24h public URL. Email footer carries "Sign up to access full PPP" CTA.
Data ownership
- ⏳ Doctor owns their portfolio data regardless of B2B2C or B2C provisioning.
- ⏳ Enterprise sees only anonymised cohort views; never per-doctor identifiable records (per
organisational-dashboard.md). - ⏳ On enterprise contract end, doctors retain personal access; enterprise loses cohort visibility.
Decision tree — when does an enterprise customer fall into B2B2C vs B2C?
Is a single hospital / HHS / organisation paying centrally?
├─ Yes → does the doctor still self-sign-up with a personal email and use the full portfolio?
│ ├─ Yes → B2B2C (Q Health pattern: subsidised seats + admin tiers)
│ └─ No (compliance-reports-only) → out of scope; serve via B2B2C + Organisational Dashboard cohort views (Q2 resolved 5 May, engineering-led)
└─ No → doctor pays personally
├─ Wants CPD only → B2C — CPD Home (see /integrations/pricing-updates#current-prices)
└─ Wants full portfolio → B2C — PPP Full (see /integrations/pricing-updates#current-prices)Current Status
| Sub-feature | Status | Notes |
|---|---|---|
| B2C subscription (Stripe; pricing) | 🔄 In progress | Implemented in docs/site/integrations/stripe.md |
| B2B2C enterprise tenant + seat provisioning | ❌ Not started | No enterprise tenant model yet |
| B2B2C admin tier line-of-sight | 📋 Specified | Captured in organisational-dashboard.md; not yet built end-to-end |
| Discount activation code / invite linking | ❌ Not started | Q1 ratified #8175 — signed magic-link invite per-contract (#4951 pattern); no domain fast-path in v1 |
| Light-version interactive emails for non-users | ✅ Built | Q7 confirmed built #8175 (Matt: 'haven't we already built q7?') — react-email template + tokenised 24h URL |
Open issues on label:feature:business-models — no open issues. Fetched at: 2026-10-13T07:29:49Z — live list on GitHub.
Downstream References
| Feature | Field / event used | Consequence |
|---|---|---|
organisational-dashboard.md | Admin tier (Hospital / HHS / Org Super Admin) | Anonymisation thresholds and line-of-sight rules apply to both B2B2C and pure-B2B tenants |
attendance.md | Hospital QR check-in/out | Hospital scope inherited from B2B2C tenant |
profile-non-doctor.md | Hospital Admin / Super Admin profile | Account types provisioned under the enterprise contract |
onboarding.md | Sign-up with enterprise invite + discount code | B2B2C entry path; doctor still uses personal email |
admin.md | Hospital Admin account capabilities | Seat issuance, deactivation, cohort access scoped to enterprise tenant |
Cross-references
docs/features/organisational-dashboard.md— admin tier visibility model (line-of-sight Hospital → HHS → Org).docs/features/profile-non-doctor.md— Hospital Admin and Super Admin account shape.docs/features/attendance.md— hospital-scoped QR attendance, inherits enterprise tenant.docs/features/onboarding.md— sign-up flow, enterprise discount linking.docs/features/admin.md— Hospital Admin governance surface.docs/site/integrations/stripe.md— current B2C Stripe implementation; canonical figures in the pricing runbook.
Open GitHub Issues
| # | Title | Status | Priority |
|---|---|---|---|
| #5324 | docs(business): document B2B2C vs B2B models from Matt's Notion | open | med |
Change Log
| Date | Change | PR/Issue | Reason |
|---|---|---|---|
| 2026-07-13 | BDD scenario coverage intentionally deferred — spec is status: specified (not yet built). No @feature:business-models scenarios needed yet. | #10578, #10572 | Coverage/BDD gap audit (#10572) flagged this spec as having zero BDD tag match. Confirmed specified-but-unbuilt per front-matter status:; BDD is written when the feature is built, not at the specification stage. This note stops future coverage sweeps from re-flagging the gap. |
| 2026-06-29 | Ratify Q1/Q4/Q5/Q6/Q7 — move all five to Closed Questions; update ACs for seat pricing (no fixed list price) and work-order rates (per-contract only); confirm light-version email built. | #9777, #8175 | Matt verbatim-confirmed all five remaining open commercial-modelling questions on issue #8175 (2026-06-24 and 2026-06-29). Q1 = per-contract magic-link; Q4 = no fixed list price; Q5 = Y2 adjustable; Q6 = per-deal rates; Q7 = already built. |
| 2026-06-03 | Resolve Q2/Q3 to Closed Questions, Matt-confirmed from transcript 2026-04-22 (no pure-B2B; B2C + B2B2C seat-subsidy; doctor owns the data). | #8166 | SGD governance sweep — transcript-grounded audit found these questions already answered; reconciled the spec to shipped reality and moved them out of Open Questions. |
| 2026-06-02 | CPD Home / Full Platform AUD prices labelled incl. GST (B2C). | #8078, #8069, #8059 | B2C GST-inclusive decision; price unchanged ($275 / $1,089). |
| 2026-06-02 | CPD Home annual price updated to 275 AUD (ex GST). | #8058, #8057 | AMC review — match current pricing. |
| 2026-05-05 | Awaiting-Matt sweep — Q1–Q7 all resolved engineering-led, Matt to ratify. Q1 signed magic-link invite (#4951) + domain fast-path; Q2 no pure-B2B model (B2B2C + B2C only); Q3 doctor owns data on departure (30d grace + step-down); Q4 per-contract rate fields with effectiveFrom/effectiveTo; Q5 Y2 excludes Implementation Fee; Q6 platform-wide work-order rate card with per-contract override; Q7 build new react-email light-version template (do NOT reuse MB stub). | #4631, #4951 | Unblocks B2B2C engineering work for Q-Health deal; defaults align with project memories (AU-first, no unscoped rules) and existing patterns (#4951, hr-passport recruiter URLs). |
| 2026-04-28 | Initial spec translated from Matt's "Enterprise Arrangements" Notion page. | #5324 | Codify B2B2C and B2C commercial channels; surface 7 open questions including pure-B2B ambiguity. |