What is saas cost?

SaaS cost is the total cost to create and operate a Software-as-a-Service product (software delivered over the internet on a subscription), including the costs to acquire customers and retain them. In medtech and digital health, SaaS cost also includes compliance and clinical workflow costs that many “normal SaaS” founders underestimate (privacy, security, validation, and hospital procurement).

What “SaaS cost” includes (the full stack)

Founders often mean one of three things when they ask about SaaS cost:

• Build cost: what it takes to develop the product to a usable, sellable state.
• Run cost: ongoing costs to host, maintain, secure, and support the product.
• Unit cost: cost per customer (or per patient/site) to deliver the service, used to compute margins and scalability.

A practical way to model SaaS cost is to split it into COGS and OpEx:

• COGS (Cost of Goods Sold): costs that scale with usage/customers (cloud compute, storage, third-party APIs, customer support time, SMS/telephony, per-user licenses, etc.).
• OpEx (Operating Expenses): costs that don’t scale directly per customer (engineering salaries, product management, G&A, security program overhead, sales team base salaries, etc.).

In investor and CFO language, SaaS cost is often discussed as gross margin (revenue minus COGS) and burn (cash spent per month). For medtech SaaS, your gross margin can look great on paper—until you include integration, compliance, and support realities.

Typical SaaS cost categories (with medtech-specific examples)

1) Product development (one-time-ish, but never truly ends)

• Engineering: app, backend, data pipelines, analytics, mobile, etc.
• UX/UI: clinician workflow design, reducing clicks, alert fatigue considerations.
• QA and testing: automated tests, regression testing, device/browser compatibility.
• Documentation: user guides, admin guides, release notes (often required by hospital IT).

If your product could be considered Software as a Medical Device (SaMD), development cost also includes design controls, traceability, and validation evidence. Even if you’re “just digital health,” enterprise buyers will still demand rigor.

2) Cloud infrastructure and data costs (often your core COGS)

• Compute: servers, containers, GPU/ML workloads (if applicable).
• Storage: databases, object storage, backups, log retention.
• Networking: bandwidth, VPNs, private links, egress fees.
• Observability: monitoring, logging, alerting tools.

In healthcare, data retention and audit logging can materially increase storage and logging costs. If you ingest imaging or waveforms, storage and egress can become a major driver.

3) Security, privacy, and compliance (medtech’s “hidden SaaS cost”)

Even when not strictly regulated as a medical device, healthcare SaaS commonly needs:

• HIPAA program costs (US): policies, training, risk assessments, vendor management, and a BAA (Business Associate Agreement) with key vendors.
• Security controls: encryption, key management, access controls, SSO, audit trails.
• Pen testing and vulnerability management.
• Compliance frameworks: SOC 2 Type I/II (common in enterprise SaaS), ISO 27001 (common internationally). Costs vary widely depending on scope and readiness.

If you are pursuing FDA clearance/authorization (510(k), De Novo, or PMA), you should also budget for quality system work, software validation, and cybersecurity documentation. The exact pathway and evidence requirements vary by product and risk.

4) Integrations and implementation (often the deal-killer in hospitals)

Hospital customers rarely “just sign up.” Expect costs for:

• EHR integration (e.g., HL7/FHIR interfaces), identity (SAML/SSO), and data mapping.
• Implementation: onboarding, configuration, workflow alignment, training.
• IT/security review: questionnaires, architecture diagrams, vendor risk management.

These costs can be partly COGS (implementation hours per customer) and partly OpEx (integration platform, integration engineers). In early-stage medtech SaaS, implementation effort is frequently the largest driver of “why margins aren’t SaaS-like yet.”

5) Customer support and clinical operations

• Support: ticketing tools, on-call rotations, SLAs (service level agreements).
• Clinical safety processes: escalation pathways, incident response, adverse event handling (if applicable).
• Training and adoption: especially for clinician-facing products where behavior change is the product.

6) Sales, marketing, and procurement friction (your CAC engine)

In SaaS, the cost to acquire a customer is called CAC (Customer Acquisition Cost). In hospitals, CAC is not just ads—it’s time, pilots, and procurement cycles.

• Sales: founder time, sales reps, commissions, travel, demos.
• Marketing: website, content, conferences, webinars.
• Pilots and evaluations: proof-of-concept builds, data work, clinician champions.
• Procurement: contracting, legal review, security review, vendor onboarding.

Reimbursement can also shape your go-to-market cost. If your product depends on billing (e.g., CPT codes), you may need billing workflow support, documentation, and evidence generation. If it requires clinical research, you may need IRB approval and study operations—costs that are not typical in consumer SaaS.

How to calculate SaaS cost: the 3 numbers that matter

1) Cost to serve (COGS) per customer

Compute a monthly “cost to serve” per customer/site:

• Cloud + third-party API usage attributable to that customer
• Support hours (tickets, training) × loaded hourly cost
• Implementation amortization (if you spend 40 hours onboarding, spread it across expected contract months)

This helps you estimate gross margin and whether you can scale without hiring proportionally.

2) CAC and payback period

CAC includes sales and marketing spend (and often a portion of salaries) divided by the number of new customers acquired in a period. A key derived metric is CAC payback: how many months of gross profit it takes to earn back CAC.

In hospital SaaS, payback can be longer because sales cycles are long and implementation is heavy. That’s not automatically bad, but it must match your pricing and funding plan.

3) LTV (Lifetime Value) and churn

LTV is the gross profit you expect from a customer over the life of the relationship. It depends on:

• ARPA/ARPU (average revenue per account/user)
• Gross margin
• Churn (how often customers cancel or fail to renew)

Medtech SaaS can have low churn once embedded in workflow, but only if you survive implementation and deliver measurable clinical/operational value.

Medtech-specific cost traps (and how to avoid them)

• Underestimating integration: Budget integration engineering early; sell “implementation fees” or price per site to cover it.
• Compliance as an afterthought: Retro-fitting security and audit trails is expensive. Build a minimal security baseline from day one (access control, logging, encryption, least privilege).
• Evidence generation: If outcomes claims drive purchasing or reimbursement, plan for study costs (possibly IRB) and analytics work.
• Pricing like consumer SaaS: Hospitals buy value and risk reduction, not seats. Consider pricing per site, per bed, per service line, or per monitored patient—aligned to who has budget authority.

What to do next

1. Build a one-page SaaS cost model splitting COGS vs OpEx, and list your top 10 cost drivers (integration, cloud, support, compliance, sales).
2. Estimate cost-to-serve per hospital site including implementation hours and ongoing support, then compute gross margin at your target price.
3. Map your regulatory and evidence needs: decide whether you are SaMD and which FDA pathway (510(k), De Novo, PMA) might apply; note any IRB or clinical study requirements.
4. Pressure-test pricing against procurement reality: identify the buyer (CMIO, department chair, IT, value analysis) and align pricing to their budget line.
5. Run a CAC/LTV sanity check using conservative assumptions (long sales cycle, heavy onboarding) before hiring sales or committing to big compliance spend.