Revenue Architecture for Caregiving + Home Health Software in 2027 (CMS Regulatory Moat, PE Roll-up)

The agency on the whiteboard: what a real deal looks like

Picture the account that shows up most often in a home health software pipeline. A privately held agency runs eleven branches across two states, employs roughly 900 caregivers and 140 clinicians, and bills a mix of Medicare fee-for-service episodes, Medicaid waiver personal care hours, and a growing slice of Medicare Advantage contracted visits. The administrator uses one system for scheduling and EVV, a second for clinical documentation and OASIS, a spreadsheet for authorizations, and a billing clearinghouse bolted to the side. Days sales outstanding sits somewhere north of 45. Nobody can answer "which branches are losing money on which payer" without three days of manual work.

That agency is not shopping for features. It is shopping for two things: cash getting collected faster, and the certainty that when CMS changes a rule, the software will already know about it. The moment PDGM replaced the old 60-day episode model with 30-day payment periods and case-mix groupings, every agency in the country discovered that its documentation habits were now a revenue variable. The same thing happened when OASIS-E landed with new social determinants items, and again when the Notice of Admission replaced the Request for Anticipated Payment and turned a five-day filing window into a per-day payment penalty for late submission.

So the buying committee looks different than in horizontal SaaS. The owner or CEO cares about margin per branch. The CFO cares about DSO, denial rate, and whether the platform can model a value-based purchasing adjustment before it hits the remit. The Chief Clinical Officer cares about documentation burden per visit and clinician turnover — because in Caregiving, turnover is the cost line that eats every other efficiency. Compliance cares about survey readiness and audit trails. IT is a gatekeeper, not a champion. On an enterprise network you will name eight to sixteen stakeholders, and on a PE-backed platform you add the sponsor's operating partner, who cares about one thing: can every acquired agency be on this system inside two quarters.

The practical consequence for Revenue Architecture is that discovery cannot be generic. A rep who opens with "tell me about your workflow" loses to a rep who opens with "walk me through your last three LUPA episodes and your NOA late-filing rate." The second conversation produces a number, and a number produces a business case. Vertical software in this market sells against a quantified leak — recaptured revenue on episodes that were being underbilled, avoided penalties on late notices, hours of documentation time returned per clinician per week — not against a feature grid. Build the discovery script around the leak and the rest of the architecture follows: segmentation by branch count, sales cycle by committee size, and expansion by the number of caregivers on the platform rather than the number of seats.

How the regulatory moat converts into booked revenue

The moat mechanic is worth spelling out precisely, because most teams describe it vaguely and then fail to staff it. CMS publishes proposed rules for home health payment on an annual cycle, takes comment, and finalizes late in the calendar year for a January effective date. Between proposed and final there is a window — typically several months — in which agencies know a change is coming but do not know its exact shape. That window is the entire sales opportunity.

A vendor that treats regulatory work as a compliance chore ships an update in December, notifies customers by release note, and hopes support absorbs the calls. A vendor that treats it as Revenue Architecture does something else: it publishes an analysis of the proposed rule within days, runs a modeling tool that shows each existing customer its projected payment impact under the proposal, and puts a named specialist on the road doing webinars and state-association sessions. That specialist is not a product marketer. They are a quota-carrying overlay whose variable compensation is tied to transition support delivered and revenue protection attributed.

The conversion path is mechanical. Modeling output creates a quantified anxiety in the install base, which drives module expansion — analytics, coding assistance, denial management. The same modeling output, run against a prospect's publicly available or self-reported case mix, becomes the highest-converting outbound asset the company has, because it is the only piece of collateral that speaks to the CFO in dollars. And once a transition lands cleanly, the reference is durable in a way that a feature reference never is: agencies talk to each other constantly through state associations, and "they got us through it without a cash-flow gap" is the sentence that wins the next three deals.

The loop closes at the sponsor. Private equity and strategic consolidation in home health and hospice has been sustained for a decade, and the largest platforms — including UnitedHealth's Optum, which acquired both LHC Group and Amedisys, and sponsor-backed platforms such as AccentCare — run continuous acquisition programs. When a platform standardizes on your system, every subsequent tuck-in acquisition arrives as a migration project rather than a competitive deal. That is why the roll-up channel is a distinct motion with its own account managers rather than a coverage assignment inside enterprise. The parent contract is the sale; the acquired agencies are the annuity.

One adjacent effect worth designing for: the same dynamic exists one door over in hospice, palliative care, home infusion, and non-medical personal care. The payment systems differ, but the structure of the buyer is nearly identical, and agencies increasingly operate multiple service lines under one roof. Vendors that build the regulatory function once and apply it across adjacent line items get a second and third expansion motion out of a single investment.

The numbers: ACV bands, coverage, and retention math

Treat the figures below as planning bands for a model, not as published results. They reflect the shape of vertical healthcare software economics and should be recalibrated against your own closed-won data within two quarters.

Segment and ACV. A single-site to three-site agency typically lands in a low five-figure annual contract — roughly $10K to $50K — covering scheduling, EVV, clinical documentation, OASIS, and billing. A four-to-thirty-branch operator lands in the low-to-mid six figures, commonly $100K to $700K, once multi-location scheduling, value-based reporting, and analytics attach. Enterprise networks above thirty branches run from the high six figures into eight figures, driven by multi-state consolidation, custom data warehousing, and service-line breadth. Price on branches and active caregivers rather than named users; caregiver headcount is the metric that grows, and tying price to it makes expansion automatic rather than negotiated.

Cycle and win rate. SMB closes in two to six months with a single decision-maker and converts in the mid-twenties percent from qualified opportunity. Mid-market runs four to nine months across six or more stakeholders and converts in the high teens to low twenties. Enterprise runs six to fifteen months, occasionally longer when a sponsor transaction is pending, and converts in the low-to-high teens. Coverage should scale with cycle length and stakeholder count: roughly 3.5x at SMB, 4.5x at mid-market, 5x at enterprise, measured at the top of the qualified funnel and re-cut at the first economic-buyer meeting.

Retention. Gross revenue retention is the number that actually tells you whether the product works; net tells you whether the pricing model works. Target gross retention in the low-to-mid nineties across all segments — churn in this market is usually agency closure, acquisition by a platform on a different system, or a botched implementation, not competitive displacement. Net revenue retention should climb by segment: modest single-digit expansion at SMB, low double digits at mid-market, and high-teens to mid-twenties at enterprise where branch growth, acquisitions, and module attach compound.

Where expansion comes from. Rank the levers honestly. Branch count growth is the largest and the least controllable. Caregiver count growth is second and is a genuine tailwind — Bureau of Labor Statistics projections have home health and personal care aides among the fastest-growing occupations in the country, driven by the demographic wave of Americans turning 65. Module attach is third and the most controllable: documentation assistance, coding support, scheduling optimization, remote monitoring integration, and value-based contracting analytics. Price uplift at renewal is fourth and should never carry more than a quarter of the expansion plan.

Compensation. Keep segments on separate plans with separate ramps; a 60-day SMB cycle and a 400-day enterprise cycle cannot share a quota clock. A 50/50 base-to-variable split is standard through mid-market, shifting toward 45/55 at enterprise with multi-year bookings vested across the contract term and a meaningful recoverable draw during a ramp that realistically runs two to three quarters. Overlay roles — the regulatory specialist, the solutions consultant, the roll-up channel manager — should sit at a lower variable percentage with credit shared rather than split, because splitting credit is how you teach reps to avoid the overlay. Customer success carries an expansion number plus separate logo and gross-retention gates, and the gross-retention gate must be a threshold, not a slider, or CSMs will trade renewals for expansion.

Implementation. Charge for it and staff it as a profit-neutral function, not a loss leader. Implementation for a multi-branch agency involves data migration from at least two legacy systems, payer enrollment, EVV state-aggregator connectivity, and clinician training across shifts. Underpricing it produces the single most reliable predictor of first-year churn: a go-live that slips past the customer's next payroll cycle.

Trade-offs: build the moat, buy the channel, or rent the intelligence

Every CRO in this category faces the same three-way allocation and cannot fully fund all of it. The trade-offs are real and the wrong choice is survivable but expensive.

Build the regulatory function in-house. Cost is a small, senior, permanent team — regulatory analysts, a clinical coding lead, and a field-facing specialist — plus the engineering capacity to ship rule changes on a fixed annual cadence. The payoff is a defensible position that compounds, because each transition cycle deepens the reference base. The risk is that the function reads as overhead in a board deck; it does not produce attributable bookings unless you instrument it deliberately with a "regulatory-influenced pipeline" field and a revenue-protection attribution model. Instrument it in quarter one or it gets cut in quarter six.

Buy the channel. Partnering into PE platforms and strategic acquirers gets you volume without proportional field cost, and migration revenue at predictable margins. The cost is concentration: when a single sponsor represents a large share of enterprise ARR, you have a customer who knows it and prices accordingly at renewal. There is also a strategic hazard — payer-owned platforms may standardize on systems for reasons that have nothing to do with product quality. Cap sponsor concentration explicitly in the plan and grow independent multi-location logos as ballast, even at worse unit economics.

Rent the intelligence layer. Documentation assistance, coding support, and scheduling optimization can be built or licensed. Licensing gets you to market a year earlier and turns a capital decision into a variable cost; building gets you margin and defensibility. The middle path most vendors take — license first, then build behind the interface — works if and only if the pricing model is decoupled from the vendor's cost basis from day one. Price these modules per caregiver per month so the expansion motion survives a swap of the underlying provider. And be conservative in claims: clinical documentation tooling in a regulated setting requires human review, and overselling autonomy creates a compliance exposure that costs more than the ARR it wins.

A fourth option deserves mention because teams reach for it too early: geographic or payer-type expansion. Moving from Medicare-certified home health into Medicaid waiver personal care, or from one state's EVV aggregator into six, looks like a cheap TAM unlock on a slide. It is not. Each state Medicaid program is effectively a separate integration and a separate compliance surface. Sequence it after the moat is built, not instead of it.

Pitfalls that quietly cap the model

Treating regulatory work as engineering hygiene. The most common structural error. The updates ship, the customers are technically compliant, and none of it converts to revenue because no one owns the commercial motion around it. Fix: a named specialist with a variable comp component, a modeling asset produced within two weeks of every proposed rule, and a pipeline field that tags regulatory-influenced opportunities so the function's contribution is visible at board level.

No dedicated roll-up tracking. If acquired-agency migrations arrive as inbound support tickets rather than as a tracked pipeline with owners and dates, you will discover migrations six months late and lose some of them to whichever system the acquired agency already ran. Fix: a channel account manager per major platform relationship, a standing quarterly business review with the sponsor's operating team, and a migration pipeline reported alongside new logo.

One comp plan across segments. An SMB rep on an enterprise plan starves during ramp; an enterprise rep on an SMB plan optimizes for volume and brings in deals the implementation team cannot absorb. Fix: separate plans, separate ramp curves, separate quota-setting inputs, and a promotion path between them so the SMB bench feeds mid-market.

Selling seats in a market that buys caregivers. Seat-based pricing caps you at the administrative headcount, which barely grows, while the caregiver population — the thing your software actually touches — grows fast. Fix: price the platform on branches and active caregivers, with modules priced per caregiver per month.

Underfunding implementation and calling it customer success. Go-live quality is the dominant first-year churn variable in this category. A CSM cannot rescue a migration that was scoped at half the necessary hours. Fix: separate the functions, charge for implementation, gate go-live on a payroll-cycle-safe cutover date, and give the CSM a clean handoff with documented success criteria.

Forecasting on rep confidence. Enterprise deals in this market slip for reasons the rep cannot see — a pending transaction, a state survey, a payer contract renegotiation. Fix: weight the forecast on stage exit criteria that require verifiable artifacts (a signed mutual action plan, a named CFO meeting, a completed security review), and run install-base expansion as a separate forecast line once the customer count is large enough that expansion exceeds new logo.

Ignoring the adjacent service lines. Agencies expanding into hospice, palliative, or private-duty are making a purchase decision whether or not you are in the room. Fix: instrument service-line signals in the install base and route them to CSM-led expansion plays rather than waiting for a competitive RFP.

Related questions

How large should the regulatory team be at $30M ARR?

Small and senior. Two to four people: a regulatory analyst tracking rulemaking, a clinical coding lead, and one or two field-facing specialists. The leverage comes from the modeling asset they produce, which scales infinitely, not from headcount.

Should implementation report to sales or to customer success?

Neither, ideally. Run it as its own function reporting to the CRO with a margin target and a go-live quality metric. Under sales it gets over-promised; under customer success it gets under-resourced because CS is measured on retention, not delivery capacity.

When does the PE roll-up channel justify dedicated headcount?

Once acquired-agency migrations exceed roughly a quarter of enterprise new logo volume, or when any single sponsor relationship represents more than one enterprise contract. Before that, assign it to an enterprise AE as a named-account overlay.

How do you price AI documentation modules without cannibalizing the core platform?

Price per caregiver per month, separate from the platform line, and gate the accelerator on activation plus 90 days of sustained usage. Bundling it into the base contract converts a durable expansion lever into a one-time discount.

What is the fastest signal that a mid-market deal is real?

The CFO produces a number — DSO, denial rate, or late-notice penalties — in the second meeting. Deals that stay in clinical-workflow conversation past meeting three close at a materially lower rate.

FAQ

How do CMS payment rule changes actually affect vendor win rates?

They change the buying trigger. Between a proposed and final rule, agencies face quantified uncertainty about next year's cash flow, and a vendor who can model the impact for a specific agency's case mix is selling certainty rather than features. Vendors who ship updates silently capture none of that demand, and the gap is widest in enterprise deals where the CFO owns the decision.

What net revenue retention should a home health software company target?

Plan for modest single-digit net expansion in SMB, low double digits in mid-market, and high-teens or better in enterprise, with gross retention in the low-to-mid nineties everywhere. If gross retention is below 90%, stop investing in expansion motions and fix implementation quality first — net retention built on top of a leaky base is a temporary number.

Is the roll-up channel a sales motion or a partnership motion?

Both, sequenced. Winning the parent platform contract is an enterprise sales motion with a sponsor stakeholder. Everything after that — the steady stream of acquired agencies migrating onto the standard — is a partnership motion run by an account manager with a migration pipeline, service-level commitments, and a quarterly review with the sponsor's operating team.

Should pricing be per user, per branch, or per caregiver?

Per branch for the platform, per caregiver per month for modules. Per-user pricing anchors you to administrative headcount, which is flat, and creates a perverse incentive for customers to share logins. Caregiver-based pricing tracks the growth in the underlying workforce and makes expansion largely automatic between renewals.

What is the most underestimated cost in this business model?

State-by-state Medicaid and EVV integration work. Each state aggregator is effectively a separate product surface with its own certification, and the cost does not amortize the way a single national Medicare integration does. Model it per state before committing to a geographic expansion plan.

How should the forecast change once the install base gets large?

Split it. Run new logo and install-base expansion as separate forecast lines with separate owners and separate cadences — new logo weekly, expansion monthly against the renewal calendar. Once expansion is the majority of the plan, the renewal calendar, not the deal pipeline, becomes the primary forecasting instrument.

Sources

• https://www.cms.gov/medicare/payment/prospective-payment-systems/home-health-pps
• https://www.cms.gov/medicare/quality/home-health/oasis-data-sets
• https://www.cms.gov/priorities/innovation/innovation-models/expanded-home-health-value-based-purchasing-model
• https://www.medicaid.gov/medicaid/home-community-based-services/guidance/electronic-visit-verification-evv/index.html
• https://www.medpac.gov/
• https://www.bls.gov/ooh/healthcare/home-health-aides-and-personal-care-aides.htm
• https://www.census.gov/library/stories/2018/03/graying-america.html
• https://www.kff.org/medicare/
• https://www.bain.com/insights/topics/global-healthcare-private-equity-report/
• https://www.unitedhealthgroup.com/newsroom.html

Related on PULSE

• [Revenue Architecture for Senior Care and Home Health Agencies in 2027 — The Complete Operator Guide](/knowledge/ra0036)
• [Revenue Architecture for Medical Device + SaMD Software in 2027 (Regulatory Outcomes, Reimbursement)](/knowledge/ra0142)
• [Revenue Architecture for HVAC + Plumbing + Electrical Contractor Software in 2027 (ServiceTitan Moat, Consumer Financing Flywheel, PE Roll-Up Wave)](/knowledge/ra0163)
• [Revenue Architecture for Funeral Home + Cemetery + Cremation Software in 2027 (Preneed Differentiator, Tribute Tech Consolidation, PE Roll-Up Channel)](/knowledge/ra0159)
• [How do you architect revenue operations for a home services software company in 2027?](/knowledge/ra0382)