Business Metrics and Unit Economics Questions

Unit economics break down whether a SaaS business model is healthy and they directly inform architecture and support choices.

Definitions:

• CAC (Customer Acquisition Cost): sales + marketing spent to win one customer.
• LTV (Lifetime Value): revenue expected from a customer over their lifetime = ARPA / churn * gross margin.
• Gross margin: revenue minus direct costs (hosting, third‑party licenses) / revenue.
• Contribution margin: gross margin minus variable costs like onboarding and per‑customer support; shows margin available to cover fixed costs and profit.

How metrics influence architecture:

• High CAC / long payback requires low per-customer OPEX to hit payback targets → favors multi-tenant to amortize infra and ops costs.
• Low churn and high LTV justify investing in richer isolation or bespoke features for strategic accounts.
• Low gross margin (e.g., heavy compute/DB costs) pushes you to optimize tenancy, better resource pooling, or limit expensive single-tenant instances.
• Contribution margin per customer drives support SLAs: low margin → automated self‑service; high margin → white‑glove support and possibly single‑tenant options.

Concrete threshold scenarios favoring single‑tenant:

• Customers paying >$100k–$250k ARR and LTV:CAC >3 — you can justify per-tenant infrastructure and dedicated support.
• Regulatory/contractual requirements (HIPAA, PCI, certain government classifications) requiring physical or network isolation.
• When per-customer customizations require schema changes or significantly different performance profiles that would complicate multi-tenant code paths.
• If a single customer represents >10–20% of revenue (concentration risk), prefer isolated deployment for control and SLAs.

Practical trade-offs:

• Start multi-tenant with strong tenant isolation boundaries (row-level encryption, tenant-aware RBAC, network segmentation) and offer VPC/VPN, bring-your-key for sensitive customers.
• Only convert to single-tenant when ARR, compliance, or technical divergence cross the thresholds above; document additional operational and support cost impacts and price appropriately (annual premium, onboarding fee, dedicated SRE).
  This approach keeps costs efficient for SMBs while enabling premium, compliant offerings for large enterprise customers.