apointoo.
Request access
HIPAA

How to Calculate Unit Economics for a HIPAA Tenant

cmsapointoo··5 min read

Calculate unit economics for a healthcare tenant by separating pooled fixed costs, variable usage, tenant-specific onboarding, compliance reserve, support, and margin. A server bill alone cannot answer whether a tenant is profitable. The model must also show which costs are shared, which scale with tenants, and which arrive only when a contract requires a stronger boundary.

Use a dated worksheet and label every figure as provider price, internal estimate, quote, or unresolved. A healthy margin model is transparent about uncertainty rather than precise for appearance.

Cost surface and assumptions

Define one tenant unit before adding numbers. It might mean one clinic, one account, or one regional workload. State the included records, requests, users, support hours, retention, integrations, and region. If one tenant requires a dedicated database or account, do not include it in the pooled unit without a separate tier.

The Google Cloud Cloud Run Pricing page provides current request and resource pricing references. The AWS Lambda Pricing page provides a comparable runtime view. Both were retrieved 2026-08-15 and can change. Recalculate before a commercial commitment.

Risk analysis is part of the model because it describes the real environment. The HHS Guidance on Risk Analysis supports an environment-specific approach. Do not allocate a fixed program cost to tenants whose data boundary has not been proven.

For a cloud versus program split, read HIPAA cloud cost versus program cost. For pooling decisions, read pooled regional versus dedicated cost.

One-time work versus recurring work

Separate onboarding from recurring service. Onboarding may include contract and scope review, tenant configuration, membership setup, region assignment, key and secret provisioning, integration approval, evidence collection, and acceptance testing. Do not spread a one-time migration across a monthly line without showing the recovery period.

Recurring costs include platform resources, storage, backups, logs, support, access reviews, training, vendor reviews, restore drills, incident preparation, and policy refresh. Some are pooled. Some grow with the number of tenants. Some are triggered by a higher tier or a contract.

Model line Formula Label
Pooled fixed cost Annual program and shared platform cost / qualifying tenants Estimate or quote
Variable cloud Usage units x dated provider rate Provider price
Tenant support Expected hours x internal rate Internal estimate
Onboarding Setup hours + review + approved integration Scope estimate
Reserve Program, incident, and vendor buffer Management decision

Scenario table and unit formula

Use this formula:

annual tenant cost =
  pooled fixed cost / qualifying tenant count
  + variable cloud cost
  + support and integration labor
  + compliance reserve
  + tenant-specific vendor charges

Then calculate contribution margin:

contribution margin =
  tenant revenue
  - annual tenant cost
  - payment and tax costs

Show three cases rather than a single answer.

Case Tenant count What changes Decision
Low Few tenants Fixed program cost dominates Require onboarding recovery or delay launch
Expected Proven pooled cohort Fixed cost spreads, support is measured Review margin and reserve monthly
High Dedicated or regional tier Duplicated platform and evidence Quote an enterprise tier

Do not divide fixed costs across every prospect. Divide them across tenants using the same approved architecture and service boundary. A tenant that needs a dedicated account should carry its incremental platform and testing scope.

Uncertainty and approval gate

Keep unresolved items visible. Examples include actual support hours, legal review price, restore frequency, provider quotas, region count, contract-specific assessment, and a future plan change. Use a reserve rather than pretending the value is zero.

  1. Confirm the unit and data boundary with engineering and counsel.
  2. List pooled and tenant-specific cost lines.
  3. Apply provider pricing retrieved 2026-08-15 and note volatility.
  4. Add internal labor, support, testing, reserve, payment, and tax assumptions.
  5. Run low, expected, and high cases.
  6. Approve the price only after owners accept the high case.

See compliance reserve pricing and onboarding fee scope. Stop if a price implies a compliance guarantee or if a tenant is counted in a pool without a proven boundary.

Frequently asked questions

What is the largest unit-economics mistake?

The largest mistake is dividing every cost by every tenant. Only qualifying tenants on the same architecture should share fixed program costs. Dedicated infrastructure, custom retention, and separate assessment work belong in that tenant’s tier.

Should the monthly price cover onboarding?

It can, but the recovery period should be explicit. A separate onboarding fee makes one-time engineering, configuration, and approval work visible. If a fee is waived, record who funds the work and how margin changes.

Does a positive margin prove readiness?

No. Margin is a commercial measure. Readiness requires contracts, risk analysis, safeguards, tests, incident procedures, and evidence. Keep financial approval and legal or security approval as separate gates.

References

  • Google Cloud, Cloud Run Pricing, retrieved 2026-08-15: https://cloud.google.com/run/pricing
  • Amazon Web Services, AWS Lambda Pricing, retrieved 2026-08-15: https://aws.amazon.com/lambda/pricing/
  • U.S. Department of Health and Human Services, Guidance on Risk Analysis, retrieved 2026-08-15: https://www.hhs.gov/hipaa/for-professionals/security/guidance/guidance-risk-analysis/index.html

Related articles