.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Which Pricing Metric Fits Home Health Agencies SaaS Best per Seat per Transaction or per Outcome
Home health SaaS companies face a pricing choice that looks simple until it reaches the field. Charge per user, and the buyer can predict spend. Charge per transaction, and revenue expands with agency activity. Charge for outcomes, and the vendor appears to share risk with the customer. Each option has an intuitive appeal.
Yet a home health agency is not a generic workflow customer. Its economics are shaped by active patients, 30-day Medicare payment periods, payer rules, clinical documentation, Electronic Visit Verification, scheduling, and claims submission. A platform can have 200 caregiver logins one month and 260 the next without changing the agency’s underlying economic capacity nearly as much as a 30% increase in active patient volume would.
Monetizely’s position is clear: home health SaaS should use the active care period as its primary transaction meter. A fixed platform fee should cover the agency relationship, while the variable component should rise with active patients in a 30-day care period. Per-seat pricing ranks second and belongs only in narrow administrative add-ons. Per-outcome pricing should not carry the core subscription.
The pricing decision should begin with the agency’s business model, not the software’s login screen
Monetizely’s 5-Step Pricing Framework places the pricing metric in the middle of a disciplined sequence: set goals and identify customer segments; design packages for those segments; choose the metric; set price points; then make billing, sales, and customer success processes work around it. The order matters. A company that starts by asking whether a caregiver, scheduler, claim, or outcome is easiest to count will often choose a meter that is easy for the vendor but wrong for the buyer. As Monetizing Agentic AI argues, the metric should follow the customer’s source of value and the company’s cost to serve, not a passing market preference.
For home health SaaS, the buyer’s source of value is not a login. It is the agency’s ability to admit, schedule, document, bill, and manage care for an active patient population. Medicare’s Patient-Driven Groupings Model has used a 30-day payment period since January 1, 2020. Payment is adjusted for patient clinical characteristics, functional status, and other information reported through claims and OASIS assessments.
That payment structure does not dictate a SaaS price card. It does, however, reveal the economic unit that agency leaders recognize: a patient receiving active care during a defined period. A pricing model should meet that reality rather than force the agency to translate users into value.
A patient-centered transaction meter wins because it follows both agency value and vendor workload
“Per transaction” can mean almost anything. A vendor could charge per visit, claim, invoice, assessment, API call, or patient. Most of those choices would create the wrong incentives for a core home health operating platform.
A usable transaction meter should be an active care period:
This design gives the buyer a bill that rises when its agency grows. It also avoids punishing productive use of the software. A caregiver who completes five compliant notes should be encouraged, not treated as five new billable events.
Exhibit 1. The active care period is the strongest primary meter for core home health SaaS
| Metric | Rank | Verdict | What to do in practice |
|---|---|---|---|
| Per active care period | 1 | Use as the primary meter | Charge a platform fee plus a monthly or annual commitment tied to active patients in a 30-day care period |
| Per seat | 2 | Use only for narrow premium roles | Include broad caregiver and coordinator access; charge by seat only for scarce, high-value tools such as advanced analytics administration |
| Per claim, visit, or note | 3 | Avoid for the core platform | Reserve for discrete clearinghouse, validation, or payment-processing services where each event creates direct cost |
| Per outcome | 4 | Do not use for the core subscription | Measure outcomes for proof of value, renewals, and product improvement, not as the recurring billing trigger |
The ranking reflects a simple principle: the best meter grows with the agency’s care capacity while remaining understandable before the contract is signed.
Home health agencies already work inside a payment system organized around periods of care. CMS states that the Home Health Prospective Payment System pays a national standardized 30-day rate when the period meets the visit threshold, with case-mix and wage adjustments layered on top. For 2026, CMS continues to use 30-day periods under PDGM and adjusts payment based on patient and clinical information.
A SaaS company should not attempt to mirror the 432 PDGM case-mix groups in its price card. Doing so would create a quoting exercise that sales teams could not explain and customers could not audit. The point is more practical: an agency already forecasts census, admissions, recertifications, discharges, and periods of care. Those records make active care periods easier to budget and reconcile than a count of named users.
The difference is material. Consider an agency with 450 active patients, 60 office staff, and 900 caregivers who rotate through mobile access. A per-seat contract may charge for 960 people even if many caregivers work only a few shifts in a month. An active-care-period model instead tracks the agency’s operating scale: how many patients it is serving.
Exhibit 2. A scoring view shows why the care period outperforms seats and outcomes
| Evaluation criterion | Per active care period | Per seat | Per outcome |
|---|---|---|---|
| Tracks the agency’s revenue-producing activity | 5 | 2 | 3 |
| Fits annual budgeting and census forecasting | 5 | 4 | 1 |
| Works across caregivers, schedulers, clinicians, and administrators | 5 | 2 | 2 |
| Uses data the agency can verify | 5 | 5 | 2 |
| Avoids disputes over clinical attribution | 5 | 5 | 1 |
| Supports predictable vendor expansion revenue | 5 | 2 | 2 |
| Total score out of 30 | 30 | 20 | 11 |
The active care period wins because it links the subscription to the agency’s economic scale without making the software vendor responsible for clinical outcomes it does not control.
The strongest evidence comes from adjacent markets. Successful usage models do not charge on every internal software action. They charge on the event that represents the customer’s real demand for the service.
Home health software vendors have already moved in that direction. CareSmartz360 states that its pricing is based on total active clients per month rather than rigid per-user licenses. AxisCare says its pricing is tailored to agency size and the number of clients served. Neither vendor publishes a simple per-seat rate as the central buying decision.
Outside home health, transaction pricing succeeds when the transaction is both countable and economically meaningful. Stripe charges for successful payments. Twilio charges per message. Plaid offers per-request products that bill for successful API calls. Stedi, a healthcare clearinghouse platform, charges by eligibility check, claim submission, ERA, and related transaction types while including unlimited users and providers in its production plans.
Exhibit 3. Named B2B SaaS companies show how the meter follows the real unit of demand
| Vendor | Meter in use | Why the meter fits the product | Date and source |
|---|---|---|---|
| CareSmartz360 | Active clients per month | Agency-management value grows with the active client base, not the number of staff logins | Pricing page accessed September 3, 2026 |
| AxisCare | Number of clients served | Agency size and care volume are the stated pricing anchors | Pricing page accessed September 3, 2026 |
| Stedi | Eligibility checks, claims, ERAs, and other healthcare transactions | Each event uses clearinghouse connectivity and has a discrete operational cost | Pricing page accessed September 3, 2026 |
| Stripe | Successful card transaction | Revenue and payment-processing cost occur when payment succeeds | Pricing page accessed September 3, 2026 |
| Twilio | Message segment or message | Carrier and delivery activity occur with each message | U.S. pricing page accessed September 3, 2026 |
| Plaid | Successful API call for per-request products | The customer receives a defined data response through a specific request | Pricing page accessed September 3, 2026 |
The common pattern is not “usage pricing” in the abstract. Each company charges on an event the buyer recognizes as the reason it purchased the service.
For home health SaaS, the active care period plays the same role. It is broader than a claim, more stable than a visit, and closer to agency value than a user account.
A seat is a useful meter when each user is a stable, skilled knowledge worker who receives distinct value from the software. Salesforce, Microsoft 365, and professional design software can use per-user pricing because the user is both the buyer’s cost center and the product’s unit of value.
Home health agencies operate differently. The organization needs widespread access to work safely. Caregivers need mobile schedules, visit confirmation, care plans, and secure messaging. Coordinators need scheduling tools. Clinical staff need documentation and quality workflows. Billing staff need claims and remittance data. Restricting access to preserve a seat count creates operational friction exactly where the product is supposed to remove it.
CareSmartz360 makes the market signal explicit by contrasting active-client pricing with per-user licenses. AxisCare also organizes its offers around client counts, including ranges from fewer than 15 clients to more than 1,000 clients. Those choices reflect a practical reality: caregiver headcount can swing with staffing availability, seasonal demand, and local labor conditions. Patient volume remains the stronger measure of agency scale.
The seat meter breaks in three predictable ways:
- It taxes adoption. A growing agency limits caregiver, family, branch, or contractor access to avoid a higher bill.
- It disconnects price from value. An agency that doubles census without adding office staff may pay the same amount despite receiving far more operational value.
- It makes expansion revenue fragile. A customer can reduce named users during a staffing adjustment even when patient volume and platform dependence remain high.
Monetizely’s position is not that seats should disappear from every home health product. Seats can work for an advanced financial-planning workspace, a developer console, or a specialist analytics module used by five regional leaders. They should not determine the price of the operating system that every caregiver and coordinator needs to use.
Stedi provides a useful boundary case. Its published rates charge, for example, per eligibility check and per claim submission, and its production accounts include unlimited user seats and providers. That architecture works because Stedi’s product performs a discrete network transaction. An eligibility inquiry, 837 claim, or 835 remittance is a recognizable unit of service with a direct connection to payer infrastructure.
A core home health platform performs a different job. It coordinates the work before and after the claim: intake, plan of care, visit scheduling, EVV, documentation, payroll inputs, billing preparation, compliance, reporting, and communication. Charging per claim would make a corrected claim billable again even though the agency has not received new platform value. Charging per visit would penalize a higher-acuity patient with more frequent care. Charging per note would reward unnecessary documentation volume.
The right architecture separates the core system from discrete network services.
Exhibit 4. A fixed base plus active care periods creates a clear pricing architecture
| Price component | Recommended meter | What it covers | Why it belongs there |
|---|---|---|---|
| Core platform | Annual platform fee | Security, support, core workflow access, integrations, reporting, and broad user access | These costs and benefits exist before the first patient is added |
| Scale component | Active care periods | Growth in scheduling, documentation, billing workflow, and compliance activity | The agency receives more value as its active patient base expands |
| Clearinghouse services | Per transaction, where applicable | Eligibility checks, claim submission, remittances, attachments, and validations | Each service has a distinct, auditable payer-network event |
| Implementation | One-time project fee | Data migration, configuration, training, and go-live support | One-time labor should not be disguised as recurring product usage |
| Premium specialist tools | Limited named-user add-on | Advanced financial modeling, enterprise administration, or custom-data tools | Value may sit with a small, stable set of expert users |
The primary meter remains the active care period. The other charges should support that core design rather than compete with it.
Outcome-based pricing has obvious appeal in healthcare. Agencies care about hospitalization rates, functional improvement, medication management, patient experience, and payment performance. CMS measures home health quality through OASIS assessments, Medicare fee-for-service claims, and the Home Health CAHPS survey.
Those facts make outcomes important. They do not make them a sound core SaaS billing trigger.
CMS itself risk-adjusts many home health outcome and utilization measures to account for differences in patient populations. The agency’s results can depend on age, prior condition, functional status, social support, referral quality, caregiver availability, physician participation, patient adherence, and post-discharge care. CMS also reported on May 4, 2026, that certain 2025 OASIS-based measures had been calculated using outdated risk-adjustment coefficients because of a processing issue.
A software vendor cannot write a durable subscription contract around a score that may be calculated months after the care period, revised through technical updates, or influenced by factors outside the product’s reach. Even a well-designed platform improves the agency’s ability to document, coordinate, and monitor care. It does not control every clinical decision or patient circumstance.
Outcome metrics have a better role in the commercial relationship:
- Use them in the business case to show why the platform matters.
- Track them in quarterly value reviews.
- Use them to guide product investment and customer-success priorities.
- Avoid making them the recurring invoice line for the core operating platform.
A vendor can promise reliable software, compliant workflows, usable data, and measurable operational improvement. It should not promise ownership of a patient’s clinical trajectory.
The active-care-period model needs two qualities that can appear to conflict: predictability for the agency and expansion revenue for the vendor. A committed annual platform fee with included active-care-period capacity achieves both.
The agency knows its minimum spend. The vendor knows it will recover fixed costs for onboarding, support, compliance, and the base product. Expansion occurs when the agency’s census moves beyond its committed capacity, not when a manager forgets to remove a departing employee from the user list.
Exhibit 5. The model produces a spend curve that a CFO can forecast
| Agency profile | Average active care periods per month | Example annual platform commitment | Example annual scale charge | Example annual software spend |
|---|---|---|---|---|
| Emerging agency | 250 | $18,000 | $0 | $18,000 |
| Growing agency | 500 | $18,000 | $19,200 | $37,200 |
| Multi-branch agency | 900 | $18,000 | $57,600 | $75,600 |
The table shows the desired commercial behavior: price stays stable at the entry level, then rises in direct proportion to patient-care scale rather than workforce churn.
A rate card should also include annual commitments and monthly visibility. Agencies should see active-care-period counts in the product dashboard, receive alerts at 80% and 100% of committed capacity, and have a clear true-up rule. Billing disputes decline when the customer can reproduce the count from the same operational data it uses to manage census.
Four decisions will turn the metric into a scalable pricing system
Define the customer segments before setting the rate. Separate emerging agencies, growth-stage multi-branch operators, and enterprise providers with complex payer mixes. The primary meter can remain active care periods, while package depth, support, integrations, and contract structure change by segment.
Build pricing capacity into the annual plan. Sell a committed number of active care periods with enough headroom for normal census variation. Reserve true-ups for sustained expansion, not seasonal swings or one unusually busy month.
Pay sales teams for durable patient-volume commitments. Compensation based only on booked ARR can encourage low initial commitments and painful renewal conversations. Reward commitments that reflect expected 12-month census and clean expansion when agencies grow.
Make the customer’s census forecast part of every renewal conversation. Customer success should review admissions, discharges, branch additions, payer mix, and expected patient volume 90 to 120 days before renewal. That discussion turns expansion into planning rather than surprise billing.
Use quality and financial outcomes as evidence, not as the invoice. Show the agency how faster documentation, cleaner claims, better authorization tracking, and lower administrative burden support its business. Keep the subscription tied to the activity the platform can measure cleanly and serve reliably.
Assumptions
The recommended meter applies to core SaaS sold to Medicare-certified home health agencies and adjacent home-based care providers. The example prices and scoring in Exhibits 2 and 5 are modeled figures, not market benchmarks. “Active care period” should be configured to reflect payer mix, state requirements, and the agency’s documented service activity, while maintaining one count per patient per qualifying 30-day period.
Footnotes
- https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- https://www.getmonetizely.com/monetizing-agentic-ai-book-saas/step-1-goals-and-segmentation
- https://www.getmonetizely.com/monetizing-agentic-ai-book-saas/step-2-packaging-designing-offers-that-fit
- https://www.getmonetizely.com/monetizing-agentic-ai-book-saas/step-3-choosing-the-right-pricing-metric
- https://www.getmonetizely.com/monetizing-agentic-ai-book-saas/step-4-finding-the-right-price-points
- https://www.getmonetizely.com/monetizing-agentic-ai-book-saas/step-5-operationalizing-agentic-ai-pricing
- https://www.cms.gov/medicare/payment/prospective-payment-systems/home-health
- https://www.cms.gov/medicare/payment/prospective-payment-systems/home-health/home-health-grouper-software
- https://www.cms.gov/medicare/quality/home-health/home-health-quality-measures
- https://www.caresmartz360.com/pricing/
- https://axiscare.com/pricing/
- https://www.stedi.com/pricing
- https://stripe.com/pricing
- https://www.twilio.com/en-us/sms/pricing/us
- https://plaid.com/pricing/
- https://www.cms.gov/medicare/quality/home-health/home-health-qrp-spotlight-and-announcements