The Home Health Software Market in 2026

Start with a warning that will save you an afternoon of confusion: published market-size figures for this category differ by a factor of five. Mordor Intelligence values the home healthcare software market at $4.51 billion in 2025, forecasting $8.20 billion by 2030 at a 13.0% compound annual growth rate (Mordor Intelligence, 2025). Market Research Future, using a wider definition, puts “home health software” at $23.74 billion in 2025 growing to $91.24 billion by 2035 (Market Research Future, 2025), and other publishers land somewhere in between. The difference is scope: some reports count only agency-side clinical and back-office platforms, others add remote patient monitoring, telehealth and hardware. Your plan should not quote the biggest number. It should say which slice you are selling into and size that slice from the bottom up.

The bottom-up version is easier to defend than it looks. The Medicare Payment Advisory Commission counted more than 12,000 home health agencies certified to participate in Medicare in 2024, of which 9,961 actually treated traditional Medicare patients; about 2.7 million fee-for-service beneficiaries received home health care, and Medicare spent $16.0 billion on it (MedPAC, March 2025 Report to Congress). Multiply roughly 10,000 active agencies by a realistic annual contract value of $12,000 to $30,000 and you reach a serviceable ceiling of $120 million to $300 million for Medicare-certified agency software alone, before Medicaid-only personal care agencies, hospice and private-pay home care are added. That is a real market, and it is small enough that a focused newcomer can take a few hundred customers without needing the whole thing.

Why agencies keep buying software even when payment is shrinking

The demand drivers are regulatory, not fashionable. In November 2025 CMS issued the calendar-year 2026 home health payment rule, an aggregate payment decrease of 1.3%, about $220 million, effective 1 January 2026 (Home Health Care News, November 2025). The rule combines a 2.4% rate update with a permanent adjustment of about 1% and a temporary reduction of roughly 2.7%, and it also moves the weighting of the Home Health Value-Based Purchasing score so that OASIS-based and claims-based measures rise from 35% to 40% of the total for larger agencies while patient-experience survey measures fall from 30% to 20% (Axxess, CY 2026 rule summary). Agencies are also now required to submit all-payer OASIS data. Shrinking rates and a heavier documentation burden push operators in one direction: they need software that catches coding errors before a claim leaves the building, and they will pay for it because a single avoidable audit finding costs more than a year of subscription.

The second driver is electronic visit verification. The 21st Century Cures Act of 2016 requires EVV for Medicaid-funded personal care and home health services, and states have been rolling it out in waves. Florida went live with HHAeXchange as its fee-for-service vendor on 1 October 2024; Michigan switched home health fee-for-service to HHAeXchange on 1 April 2024; California runs a state system built on Sandata; Arizona runs an in-house system through AHCCCS (HHAeXchange EVV guide, Florida AHCA). Every one of those states publishes its own data-submission specification. For a software founder that fragmentation is the moat and the burden at the same time: whichever vendor handles state aggregator integrations cleanly sells to agencies that cannot afford a payment denial for a missing visit record.

The third driver is consolidation among the customers themselves. Home health transaction volume rose 4.1% year on year, with private-equity add-ons making up about 38% of deals and strategic buyers 43.5% (Axis Care, 2025 trends). When a platform buys five agencies it standardises them onto one system, which is great news for a vendor with enterprise multi-branch features and poor news for a vendor that sells only to single-site start-ups.

How big is the opportunity outside the United States?

In England the structure is different and the timing is ahead of the US. NHS England's target that 80% of registered adult social care providers should use a digital social care record was met by July 2025, up from 41% in 2021 (CareOS market map, 2026). That makes the UK a replacement and add-on market rather than a greenfield one: providers are swapping rostering, medicines administration and family-portal modules and want assured, DCB0129-compliant suppliers. A plan that targets the UK has to say plainly that the product category is called “domiciliary care software” there and the buyer is a care-agency registered manager, not a Medicare-certified home health agency administrator.

What Agency Owners Search For Before They Buy

A software business is sold through its buyers' questions. These are the ones that appear around the keyword “home health software”, and each is a line your sales page and your plan's go-to-market section should answer in the first screen.

What is the best software for a new home health agency?

Buyers ask for a ranking and settle for a shortlist. Reviewers commonly describe Axxess as the most accessible EMR for startup and smaller Medicare-certified agencies, WellSky as the most widely used, and Homecare Homebase as the strongest option for large multi-branch operators (Avee Care buyer's guide, 2026). Your plan has to explain which of those three positions you are not trying to occupy.

How much does home health software cost per month?

Published starting prices vary: Axxess from about $899 per user per month, WellSky from about $800, KanTime from about $2,000 per month in total. Estimates for small agencies run $1,500 to $5,000 monthly for Homecare Homebase, $1,000 to $3,500 for WellSky, $1,000 to $3,000 for KanTime and $500 to $2,500 for Axxess (SelectHub, 2026; LaunchAdvisor, 2026). Treat these as third-party estimates, because most vendors hide prices behind a demo, and note that opacity as an opening for a challenger who publishes a price.

Do home health agencies need EVV software?

Where a state pays for Medicaid home health through fee-for-service or managed care, yes. EVV is mandated federally and payment is reduced or denied when visit data is missing. Many agencies get an aggregator's free EVV tool and still buy a full system on top; your plan should say whether you integrate with the aggregator, replace it, or both.

Is it cheaper to build custom home health software than to subscribe?

For an agency, almost never. Custom builds are quoted at $200,000 to $1,000,000 or more, and they leave the agency to own compliance updates every time CMS changes OASIS or PDGM logic. That fact is useful to a founder in two ways: it explains why buyers choose subscriptions, and it gives you a ready answer to the investor who asks why customers would not build their own.

What It Costs to Build and Launch the Product

There is no rent, stock or fit-out here. The money goes to people, compliance and the time it takes to earn trust. Published developer estimates put a minimum viable home care product, meaning core scheduling, a caregiver mobile app and EVV compliance, at $60,000 to $150,000 over three to six months, and a full-scale platform with multiple modules and integrations at $200,000 to $500,000 over 12 to 18 months, with ongoing maintenance of 15% to 20% of the original build cost each year (Leanware, home care software development guide). A clinical EHR layer is where budgets split: estimates for custom EMR work run from roughly $40,000 for a basic build to $4 million for an enterprise platform (CapMinds, 2026). UK founders usually convert these at roughly 78 pence on the dollar, so a UK build is about £47,000 to £118,000 for the MVP.

An 18-month seed budget for a focused agency platform

The table below is a worked planning budget, not a quote. It assumes a $950,000 seed round and a three-engineer core team using a mix of US and nearshore talent.

• Engineering (3 FTE, 18 months, blended loaded cost about $140K each): about $630,000. For reference, the US Bureau of Labor Statistics reports a median software developer wage of $133,080 (May 2024) with the top decile above $211,450
• Clinical product lead (RN or former agency director, part-time): $50,000–$70,000, the cheapest credibility an agency-facing product can buy
• HIPAA programme and SOC 2 Type II: $40,000–$70,000 in year one, then $27,000–$45,000 on renewal
• State EVV certification and aggregator integration work: $20,000–$35,000 per initial state, mostly engineering time and test cycles
• Cloud hosting, logging, backups and a HIPAA-eligible environment: $24,000–$40,000 over the period
• Sales, marketing and pilots: $90,000–$130,000, including a conference presence at one state home care association meeting
• Legal, cyber and errors-and-omissions insurance: $25,000–$40,000, including template customer agreements and a business associate agreement

Total: roughly $880,000 to $1.0 million before contingency. A lean founder who writes the first version alone and sells to five agencies on a pilot can start nearer $60,000 to $90,000 and let early revenue pay for the SOC 2 audit, but the plan should say clearly that agencies will not sign a multi-year contract with a vendor who cannot show a security report.

The compliance line most first-time founders under-budget

Healthcare software buyers send security questionnaires before they send purchase orders. First-year HIPAA compliance for a small start-up is quoted at $8,000 to $25,000, with annual upkeep at 30% to 60% of that (Invision, HIPAA cost guide, 2026), and a first-year SOC 2 Type II using compliance automation runs about $39,000 to $70,000 (ComplyJet, 2026). A team with a mature HIPAA programme already has 40% to 60% of the SOC 2 security controls in place, so do them in that order and show the sequencing in your plan.

The Vendors You Will Be Compared With

A buyer shortlists three to five names. Yours is one of them only if the plan shows you understand why the other four exist. The numbers below come from vendor pages and third-party directories and should be re-checked before they go into a lender's pack.

The integration partners you will not be able to avoid

• EVV aggregators: Sandata and HHAeXchange are the two names that recur in state programmes. Plan the certification effort for each state you sell into
• Clearinghouses and billing: claims for Medicare Administrative Contractors flow through a clearinghouse; confirm the one you will connect to and the fee per claim
• Telephony and messaging: HIPAA-eligible SMS and voice for caregiver check-ins, priced per message
• Payroll and HR: caregiver time data has to reach payroll accurately, which is why agencies often buy on the strength of one payroll integration
• Hospital and referral sources: inbound referral and discharge feeds from health systems, increasingly delivered through HL7 or FHIR interfaces

Here is the domain insight worth writing into your positioning: Mordor puts the top five vendors at about 45% of annual sales, which means the remaining 55% is still split among hundreds of smaller products. Vertical specialisation, such as a pediatric private-duty platform or a hospice-plus-home-health product for rural agencies, is how new entrants have found a defensible customer base. Being a slightly cheaper copy of the generalists is not.

Pricing, Margins and Unit Economics

Home health software is sold three ways: per user per month, per active patient or census, and as a percentage of revenue or collections for billing-heavy offerings. The right choice depends on who feels the pain. Per-user pricing penalises a growing agency for hiring clinicians, which is the one thing a lender wants it to do. A census-based price tracks the agency's own revenue and is easier to explain in a budget meeting. Many founders land on a hybrid: a platform fee plus a per-active-patient charge, with onboarding priced separately so that the sales team never discounts implementation to close a deal.

A worked example you can adapt

The following figures are planning assumptions, not benchmarks. Suppose a vendor charges a platform fee of $450 a month plus $12 per active patient, and the average customer carries 75 active patients. Monthly revenue per agency is $450 + (75 × $12) = $1,350, or $16,200 a year. After 36 months the vendor has 140 agencies, for annual recurring revenue of about $2.27 million. Gross margin of 78% after hosting, support staff and third-party fees such as clearinghouse and messaging costs leaves $1.77 million of gross profit.

Now test it. If customer acquisition cost is $14,000 (a 70-day sales cycle, a part-time clinical demo specialist and trade show costs) and annual logo churn is 14%, lifetime value is roughly ($16,200 × 78%) ÷ 14% = $90,300, which is a lifetime-value-to-cost ratio of about 6.4 to 1, and the payback period is $14,000 ÷ ($1,350 × 78%) = about 13 months. Change one variable at a time in your model. A churn rate of 25% cuts lifetime value to about $50,500 and drops the ratio to 3.6. Agencies that close or get acquired cause most of this churn, which is exactly why the customers' own consolidation, covered in the market section above, belongs in the plan rather than in an appendix.

Where revenue grows beyond subscriptions

• Implementation and training: a fixed fee of $1,500 to $6,000 per agency, depending on branch count and data migration
• Billing services: a percentage of collected revenue, typically sold to agencies that do not want to hire a biller
• Add-on modules: referral management, family portals, analytics for HHCAHPS and quality-score tracking
• Data and interoperability fees: priced per interface for hospital or payer connections

Because 60% of the market's spend comes from agencies themselves, the plan should show how revenue per customer rises as the customer grows. Net revenue retention above 100% is the number that makes investors comfortable, and it comes from census growth and modules, not from price increases.

Funding a Healthcare Software Company

The mainstream small-business loan programmes were designed for businesses with assets and operating history. A software company has neither in its first year, and the plan has to be honest about which door fits.

SBA 7(a): useful, but usually later

The SBA 7(a) programme lends up to $5 million, but in practice most lenders expect at least two years in business, a personal credit score in the 620 to 680 range or higher, and a software company whose revenue is recurring and documented (Port 51 Lending; SBA 7(a) overview). The right NAICS classification for a product company is 511210, Software Publishers; a firm that mainly builds custom software for clients falls under 541511. Pick the one that matches your revenue source, because lenders cross-check it. For a start-up with no revenue, the 7(a) is typically a stage-two instrument: it works once annual recurring revenue is stable and the loan funds expansion of a sales team or a services acquisition, not the initial build.

The routes that usually fund the first build

• Founder funding and a clinical co-founder: agencies buy from people they trust, so a former agency owner on the cap table is worth real money
• Pilot revenue: five agencies paying $500 a month for a co-development pilot gives $30,000 a year and, more importantly, reference customers
• Angel and pre-seed equity: $250,000 to $750,000, typically from healthcare operators and prior health-IT founders
• Seed equity: $1 million to $3 million once you show ten to twenty paying agencies and a repeatable sales motion
• Venture debt and revenue-based finance: available after steady ARR; AlayaCare's US$37 million Series C, raised to fund acquisitions, shows how scale players use it
• UK: the Start Up Loans scheme offers up to £25,000 per founder at 6% fixed, and Innovate UK grants and R&D tax relief suit a product with genuine technical risk

One more point investors will raise: exit logic. This is a sector where the customers are being rolled up and the vendors are acquiring each other (WellSky bought Bonafide; AlayaCare bought Delta Health, AcuteNet and Nightingale; Jonas Software bought TurnPoint in 2025). A plan that names the likely acquirers and what they would pay for, such as a state-specific EVV capability or a vertical niche with loyal customers, gives investors an exit story with real names in it.

Compliance: HIPAA, EVV, CMS and Abroad

A software company does not need a state licence to sell to home health agencies. It needs a security and quality story that survives a customer's lawyer. Your plan should read this section as a gating list: what is legally required, what is contractually required, and what is a sales credential only.

United States

• HIPAA business associate status: because you handle protected health information on behalf of agencies, you sign business associate agreements and must run a security risk analysis, access controls, audit logging, encryption and breach notification procedures. First-year programmes run $8,000 to $25,000 for a small team
• EVV under the 21st Century Cures Act: states choose an open-vendor or a single-vendor model. In open-vendor states you must send visit data to a state aggregator in the prescribed format; in single-vendor states agencies use the state's system, and your product can only sit alongside it
• CMS data requirements your product must support: OASIS assessment submission, now all-payer, PDGM grouping logic, Home Health Value-Based Purchasing reporting and HHCAHPS survey processes, with revised survey questions from April 2026 (Axxess rule summary)
• ONC health IT certification: optional for most agency products, because home health agencies are not in the programmes that require certified EHR technology. It matters if you sell to physician practices or want the credential for procurement. Certification is quoted at three to nine months and six-figure effort
• SOC 2 Type II: a contractual expectation rather than a statute, and the document buyers ask for first
• State privacy laws: a growing patchwork, including consumer health data statutes, that you should map before you market to patients or families

United Kingdom

• DCB0129 clinical risk management: required for manufacturers of health IT systems; it asks for a clinical safety officer, a hazard log and a safety case (Person Centred Software on DCB0129). Each deploying organisation then owns its DCB0160 duties
• Digital Technology Assessment Criteria (DTAC): the NHS England baseline for clinical safety, data protection, technical security, interoperability and usability
• Assured supplier list for digital social care records: being on the national list makes funding and ICB conversations easier (NHS England assured solutions)
• UK GDPR and the Data Protection Act 2018: health data is special category data, so register with the ICO, run a data protection impact assessment and keep a records-of-processing register
• CQC alignment: the Care Quality Commission regulates care providers, not software, but its assessment framework shapes what your reporting module must evidence

Canada

• In Ontario you will usually be an electronic service provider under the Personal Health Information Protection Act, which requires a written agreement setting scope, safeguards and limits on use (Fasken on PHIPA)
• PHIPA is an arrangement between custodian and provider, not a certificate you can display, so build your contract pack and security evidence rather than a badge
• Other provinces carry their own statutes, and data residency in Canada is a common procurement requirement

Six Mistakes That Stall Home Health Software Startups

These show up repeatedly in plans from technical founders who know how to build and have never sold to a clinical operator.

1. Building for a generic “healthcare provider”

A home health agency, a hospice, a Medicaid personal care agency and a private-duty nursing business each document, bill and report differently. A product that tries to serve all four ships slowly and wins none of them. Choose one, then name the payer, the state and the assessment form your first release handles.

2. Treating state EVV rules as a single requirement

Florida's fee-for-service programme runs through HHAeXchange, California's runs on a Sandata-based state system and Arizona's runs on an in-house AHCCCS platform. Budget the integration state by state, and sequence launches around the states with the largest open-vendor agency counts, not around where you happen to live.

3. Underestimating the sales cycle

Agency owners switch systems rarely and slowly, because moving patient charts mid-episode is risky. A 60 to 120 day cycle with a migration plan and a parallel-run period is normal. A plan that assumes a two-week close will be marked down by the first investor with sector experience.

4. Ignoring the CMS rule calendar

The 2026 rule changed quality weights, removed four social determinants items from OASIS and required all-payer OASIS submission. Each annual rule forces updates to PDGM grouping, OASIS item sets and survey processes. Your engineering plan needs a standing allocation, usually 15% to 20% of capacity, for regulatory change, and the budget should say so.

5. Hiding the price

Almost every incumbent says “request a demo”. A new vendor that publishes a clear, simple price is noticed immediately by a first-time agency owner comparing five tabs. If you must negotiate for enterprise, publish the starting tier and negotiate above it.

6. No clinical voice on the team

Nurses and therapists will not use a tool that adds clicks to their visit. A product designed only by engineers will test well in a demo and fail at the bedside. Name the clinical adviser in the plan, show their hours and put their name on the product roadmap.

Glossary for the Plan's Reader

A bank officer or a generalist angel may not know these terms. Define them once, early, and the rest of the plan reads faster.

• OASIS: the Outcome and Assessment Information Set, the standardised patient assessment home health agencies submit to CMS; software must collect, validate and transmit it
• PDGM: the Patient-Driven Groupings Model, the Medicare payment system that sets payment for each 30-day period by clinical grouping, functional level and comorbidities
• EVV: electronic visit verification, which confirms the type of service, the individual receiving it, the caregiver, the date, the location and the start and end times
• Aggregator: the state-selected system that receives EVV data from agencies and third-party vendors, with Sandata and HHAeXchange the most frequently named
• HHCAHPS: the Home Health Care Consumer Assessment of Healthcare Providers and Systems survey, whose results feed the agency's star rating
• HHVBP: Home Health Value-Based Purchasing, the Medicare programme that adjusts payment according to quality performance
• Business associate agreement (BAA): the contract in which a software company promises to protect patient data it handles for a covered entity
• DCB0129 / DCB0160: the English clinical risk standards for manufacturers and for deploying organisations respectively

An 18-Month Build and Launch Timeline

The sequence below assumes a seed-funded team that starts with three paying design partners. Compliance work runs in parallel with the build, since it gates the first contract rather than the first release.

Months 1 to 3: choose the wedge and sign design partners

Interview 30 agency owners, directors of nursing and billers. Pick a sub-segment, and sign three agencies as paying design partners at a discounted rate. Form the entity, adopt a security policy set and start the HIPAA risk analysis.

Months 4 to 8: ship the MVP in one state

Build scheduling, the caregiver mobile app and EVV for a single state, with the aggregator's test environment as the acceptance gate. Add OASIS capture if you are targeting Medicare-certified agencies. Begin the SOC 2 observation window as soon as controls are in place.

Months 9 to 12: bill and report

Add claims, PDGM grouping and quality dashboards. Move the three pilots to full pricing, collect case studies with figures such as reduced denials and faster billing, and raise the price list for new customers.

Months 13 to 18: repeat and expand

Target 20 to 30 paying agencies, certify in a second state, finish the SOC 2 Type II report and test one acquisition or channel partnership. If you plan to sell in England, begin the DCB0129 safety case and DTAC submission in this window.

The Technology Stack to Name in Your Plan

Investors in healthcare software do not need your whole architecture. They need to see that each choice reduces compliance risk or ships faster.

• Cloud and hosting: a HIPAA-eligible environment on AWS, Microsoft Azure or Google Cloud, with a signed business associate agreement from the cloud provider, encrypted storage and region-locked data where customers require it
• Interoperability: HL7 v2 and FHIR for hospital referral and discharge feeds, and the state aggregator's specified file or API format for EVV
• Mobile: a native or cross-platform caregiver app that works offline, because many patients live where signal is poor, and syncs GPS and time stamps once connection returns
• Compliance automation: a platform such as Vanta, Drata or Secureframe to collect SOC 2 evidence and keep the observation window clean
• Billing and clearinghouse: an established clearinghouse connection for Medicare Administrative Contractor claims, rather than building claim transmission yourself
• Analytics: a warehouse for the agency-level dashboards that sell the product to owners, such as days to bill, first-pass acceptance and star-rating drivers

Name the tools, the monthly cost of each and the person who owns them. A line such as “compliance platform, $10,000 to $18,000 a year, owned by the CTO” is more persuasive than a page of architecture diagrams.

Sample Business Plan Preview

Here is an extract from a home health software plan of the kind our team writes, so you can see the level of detail you will get:

What's Inside the Template

Every Avvale home health software plan is pre-structured for a software company selling into regulated care, including the sections investors and enterprise buyers scrutinise:

• Executive Summary – the segment, the wedge, the raise and the unit economics in 60 seconds
• Company & Compliance Overview – legal structure, HIPAA programme, SOC 2 timeline, state EVV certifications and UK or Canadian requirements
• Market Analysis – bottom-up sizing by agency count, plus the incumbent vendor comparison
• Product & Roadmap – modules, release sequence, regulatory-change capacity and the clinical advisory process
• Pricing & Revenue Model – platform and census pricing, implementation fees, add-on modules, net revenue retention
• Go-to-Market Plan – association events, referral partners, design-partner references and the sales cycle
• Operations & Technology – hosting, security, integrations, support model and tooling
• Management Team – clinical credentials, engineering depth and advisers

The optional Financial Forecast add-on (included in our $300/£250 and $1,000/£800 packages) provides a 5-year Excel model with MRR and ARR build, churn and expansion assumptions, hiring plan, cash runway and a compliance cost schedule. If you would rather have a specialist write it, our business plan writer service pairs you with a consultant who has built plans for healthcare technology ventures. You may also want to compare this page with our healthcare information exchange business plan template if interoperability is your core product, or our healthcare cloud computing business plan template if you are building the infrastructure layer. The AI in healthcare plan template suits founders adding clinical decision support or documentation automation. For a free starting point, see our free business plan templates hub.

Frequently Asked Questions