How do saas companies make money?

SaaS (Software as a Service) companies make money by charging for ongoing access to software—usually monthly or annually—rather than selling a one-time license. The “SaaS math” works when recurring revenue grows faster than the cost to acquire and support customers, and when customers stick around long enough to repay acquisition costs.

In medtech and digital health, the same core models apply, but the buying process (hospital procurement, security reviews, clinical validation), regulatory constraints (FDA pathways when software is a medical device), and reimbursement (CPT codes, payer coverage) heavily influence what you can charge, who pays, and how fast you can scale.

The core ways SaaS companies make money

Most SaaS revenue falls into a few patterns. You can mix them, but you should be able to explain your primary model in one sentence.

• Subscription (seat-based): Charge per user (“per seat”) per month/year. Common for clinician-facing tools (e.g., $X per clinician per month) or admin tools (per scheduler, per biller).
• Subscription (tiered plans): Charge by feature bundle (Basic/Pro/Enterprise). This is the default for many B2B SaaS products.
• Usage-based: Charge per unit of consumption (per API call, per message, per study processed, per patient monitored-day). This can align well with variable clinical volume.
• Platform + add-ons: Base subscription plus paid modules (e.g., analytics, audit logs, SSO, advanced integrations, multi-site management).
• Implementation and services: One-time fees for onboarding, integration, data migration, training, or workflow design. In pure SaaS, services are ideally a smaller portion of revenue, but in healthcare they’re often necessary to get live.
• Enterprise contracts: Annual commitments with negotiated pricing, often including security/compliance terms, uptime SLAs (service-level agreements), and support.

In healthcare, you’ll frequently see a “hybrid”: an annual platform fee (predictable) plus a usage component tied to patient volume or transactions (aligned with value).

How pricing actually works: value metric, packaging, and contracts

Pricing isn’t just “what number can we charge?” It’s a system: value metric + packaging + contract structure.

1) Choose a value metric that scales with customer value

A value metric is the unit you charge on that best tracks the value the customer receives. Examples in medtech SaaS:

• Per provider seat: Works when the software is used directly by clinicians and adoption is user-driven.
• Per facility / per site: Works for hospital-wide infrastructure tools (security, integration, device management).
• Per patient per month (PPPM): Common in remote patient monitoring (RPM) and care management workflows.
• Per study / per image / per report: Common in radiology/AI workflow tools and diagnostics operations.
• Per device managed: Common in connected device fleets and biomedical engineering asset monitoring.

If your value metric is misaligned (e.g., charging per seat when value is driven by patient volume), you’ll either undercharge power users or overcharge small users and increase churn (cancellations).

2) Package features to match buyer maturity

Packaging is how you bundle features into plans. In healthcare, “Enterprise” often isn’t just more features—it’s risk reduction:

• Security requirements (SSO, audit logs, role-based access control)
• Compliance documentation (SOC 2 reports, HIPAA BAAs)
• Integration support (HL7/FHIR interfaces, EHR integration)
• Uptime guarantees and support response times

These are real costs for you, so they justify higher pricing.

3) Use annual contracts to stabilize cash flow

Many B2B SaaS companies prefer annual prepay or annual contracts billed quarterly because it improves cash predictability and reduces churn. In hospital procurement, annual agreements are also common because budgeting cycles are annual.

Medtech-specific revenue drivers: who pays, and why they pay

In medtech SaaS, the hardest part is often not the pricing model—it’s identifying the economic buyer (the person with budget authority) and the value story that survives procurement scrutiny.

Hospital procurement and “budget owners”

Hospitals rarely buy software because it’s “cool.” They buy because it:

• Reduces cost (labor savings, fewer adverse events, fewer readmissions, reduced device downtime)
• Increases revenue (better documentation, improved throughput, improved coding capture)
• Reduces risk (compliance, auditability, cybersecurity, clinical safety)

Different stakeholders value different outcomes: a department chair may care about outcomes and workflow; IT cares about security and integration; finance cares about ROI (return on investment); compliance cares about audit trails.

Reimbursement: CPT codes and payer coverage can shape willingness to pay

If your SaaS enables billable clinical services, pricing can be anchored to reimbursement. For example, RPM programs may rely on specific CPT codes and payer policies. The exact revenue per patient varies by payer, setting, and documentation quality, so avoid building a pricing model that assumes a single reimbursement rate will hold everywhere.

A practical approach: price so the customer can achieve a clear margin after staffing and operational costs, even if reimbursement fluctuates.

Regulatory: when SaaS becomes Software as a Medical Device (SaMD)

If your software performs medical functions (e.g., diagnosis support, treatment recommendations), it may be regulated as SaMD. That can affect time-to-market and costs, which indirectly affects how you make money (longer sales cycles, higher compliance costs, need for clinical evidence).

Common FDA pathways you may hear:

• 510(k): You show “substantial equivalence” to a legally marketed predicate device.
• De Novo: For novel, low-to-moderate risk devices without a predicate.
• PMA (Premarket Approval): For higher-risk devices; typically more evidence-intensive.

If you need clinical studies, you may also need IRB approval (Institutional Review Board) for human subjects research. Plan for this in your runway and pricing: compliance isn’t optional overhead—it’s part of your cost of goods sold (COGS) and go-to-market.

The SaaS engine: what makes it profitable (MRR, churn, CAC, LTV)

SaaS companies don’t win just by charging subscriptions—they win by making the unit economics work. Here are the core terms (with plain-English definitions):

• MRR/ARR: Monthly/Annual Recurring Revenue—your predictable subscription revenue.
• Churn: The percentage of customers or revenue you lose over time (cancellations or downgrades).
• CAC (Customer Acquisition Cost): What it costs (sales + marketing) to win a customer.
• LTV (Lifetime Value): How much gross profit a customer generates over their lifetime.
• Gross margin: Revenue minus direct costs to deliver the service (hosting, support, third-party services). SaaS aims for high gross margins, but healthcare integrations and support can reduce them.

A simple way to think about it: you spend CAC upfront, then you earn it back over time through recurring gross profit. If churn is high or sales cycles are long and expensive, the model breaks.

In medtech, CAC can be higher because of security reviews, pilots, integrations, and procurement. That pushes many founders toward higher ACV (annual contract value) enterprise deals, or toward a wedge strategy (start in a smaller clinic segment with faster sales, then move upmarket).

Common medtech SaaS monetization patterns (and when to use them)

1. Clinic-first subscription: Start with outpatient clinics using per-provider or per-location pricing. Faster decisions, smaller contracts, less procurement friction.
2. Hospital enterprise platform: Higher ARR per customer, but longer sales cycles and heavier compliance/integration work. Often requires a clear ROI case and strong security posture.
3. Usage-based tied to volume: Works well when value scales with patient volume (e.g., per monitored patient-day). Helps adoption because small starts are affordable.
4. “Land and expand”: Start with one department or workflow, then expand to more sites, more modules, or more users. This is where add-ons and tiered packaging shine.

One caution: avoid pricing that depends on “future promised outcomes” you can’t measure. Procurement teams will ask how you quantify value, and clinicians will ask whether it adds clicks. Your pricing should map to measurable operational metrics (time saved, throughput, reduced no-shows, reduced device downtime) or clearly billable workflows.

What to do next

• Pick one primary value metric (seat, site, PPPM, per study) and write a one-sentence rationale for why it tracks customer value.
• Draft a 3-tier packaging table (Basic/Pro/Enterprise) that explicitly separates clinical workflow features from enterprise risk-reduction features (SSO, audit logs, integrations).
• Model your unit economics: estimate CAC (including pilots/integration time), gross margin, and a conservative churn assumption. If you don’t know, run scenarios (best/base/worst).
• Map the buyer chain for your target customer: champion, economic buyer, IT/security, compliance, procurement. Identify the one metric each cares about.
• Validate willingness to pay with 10 customer calls and a pricing test: present two price points and ask which is “too expensive,” “too cheap,” and “reasonable,” then refine.

If you want help pressure-testing your pricing and buyer chain, use the tools below.