Home Health Agency Software: Build vs. Buy for Agencies Ready to Scale

You run a home health agency with 90 caregivers across three counties. Your Medicaid contract is growing. You signed up for ClearCare three years ago and it worked. Now the scheduling module can't apply your credential rules, your EVV submissions keep bouncing back from the state aggregator, and your billing coordinator spends three days a week untangling claim errors before they go out.

You've demo'd WellSky. You've sat through a MatrixCare presentation. Both are built for a version of your agency that's smaller and simpler than what you're running today.

The question isn't which platform to switch to. The question is whether switching platforms solves the problem at all - or whether you've scaled past what any off-the-shelf home health agency software was designed to handle.

This guide is for home health agency owners who have hit that wall. It covers what custom home health software development actually costs, which operator profiles it makes sense for, and what the build involves phase by phase.

What custom home health agency software costs

Before anything else, here are the numbers.

Infrastructure runs $3K-$10K per month at launch and scales with your patient census. Each state EVV aggregator beyond your first adds $20K-$40K and 3-6 weeks.

The biggest cost variables are: how many states you operate in, whether you bill Medicare (which requires OASIS and PDGM episode billing) or Medicaid hourly only, and whether you need a consolidated view across multiple agency locations.

ClearCare, WellSky, and MatrixCare vs. custom software

Let's be specific about where the standard platforms work and where they stop working.

ClearCare (now Wellsky Personal Care) is the most widely used home care scheduling software for private-duty agencies. It handles shift scheduling, caregiver-client matching, and basic billing well for single-state operators. Pricing runs $300-$800/month depending on census and modules. The limits show up when you operate across multiple states - EVV reporting requirements differ per state and ClearCare's multi-state EVV support has gaps for smaller aggregators. Reporting across multiple agency entities is also a known weakness; if you've acquired a second location, you're pulling data manually to get a consolidated view.

WellSky (formerly Kinnser) is the standard for clinical Medicare home health agencies. It handles OASIS collection, plan-of-care management, and Medicare billing reasonably well for a single agency. Pricing starts around $400/month and climbs with patient census. It works until your multi-state footprint grows, your Medicaid payer mix becomes complex, or you need consolidated billing and reporting across entities you've acquired through a roll-up.

MatrixCare targets larger skilled nursing and home health organizations. More configurable than ClearCare or WellSky but significantly more expensive - often $600-$1,500/month-plus for home health. The integration ecosystem is strong for a single entity. The problems appear when you're a PE-backed roll-up that needs a unified data model across 15 agencies, each previously on a different platform.

Custom home health agency software makes sense when:

• You operate in three or more states and your state EVV aggregators have poor API support from the platforms you've evaluated

• You run a management services organization (MSO) or PE roll-up that needs a single data layer and consolidated Medicaid billing software across multiple agency entities

• Your care model doesn't fit standard visit taxonomy: pediatric home health, behavioral health home care, or a hybrid skilled-plus-companion model under one organization

• Your combined SaaS fees across locations have crossed $10K-$15K/month and you're growing

• Your scheduling logic is too complex for any platform you've found: multi-skill matching, caregiver continuity rules, credential-expiration blocks, and geographic optimization in one engine

According to the U.S. Bureau of Labor Statistics, home health and personal care aides held approximately 4.3 million jobs in 2024, making it the single largest occupation in the US by employment count. Employment is projected to grow 17 percent from 2024 to 2034, far faster than the average for all occupations, with an estimated 765,800 openings projected each year over the decade. That growth means the software infrastructure supporting agencies must scale alongside that demand. That gap is where home health software development becomes a business decision, not a technology project.

Who actually builds custom home health agency software

Not every agency needs a custom build. Here are the operator profiles where it makes financial sense.

The multi-state MSO. You've acquired or are rolling up agencies across five or more states. Each came with its own EVV software for home health agencies and its own billing setup. Your CFO can't get a clean P&L view across the portfolio. Your billing team works in three systems. You need one platform with a unified data model, consolidated reporting, and Medicaid billing software that handles multiple state contracts. No off-the-shelf tool was built for this structure.

The PE-backed operator preparing for exit. You're 18-24 months from a transaction. Buyers will scrutinize your software during due diligence. If your data sits across three platforms and your EVV compliance has gaps, it affects valuation. Building a clean, auditable platform now is an investment in the exit outcome, not just in daily operations.

The niche care model operator. You run a pediatric home health agency with complex Medicaid waiver billing rules that no standard platform covers cleanly. Or you operate a behavioral health home care model that straddles clinical and companion care in ways that break existing taxonomy. You've been patching workarounds for two years and the patches are compounding.

The franchise or staffing network building a proprietary tool. You franchise home care services and your current platform vendor sells to your competitors. Your scheduling logic, your caregiver matching rules, and your brand experience should be proprietary. Building your own home health agency software turns an operating system into a competitive asset - and removes a vendor dependency that grows more expensive as you scale.

The 21st Century Cures Act's EVV mandate, enforced by CMS for all Medicaid home health care services effective January 1, 2024, means agencies that fail to submit verified visit transactions face direct claim denials. As of 2024, all 50 states have EVV requirements in place, but each state uses a different aggregator, making multi-state agencies the agencies that feel the compliance pressure most acutely. The agencies hitting that ceiling are not small operators. They are the ones that grew faster than their software was designed for.

V1, V2, V3: what gets built in each phase

Home health software development is not one project. It's a phased build where each phase adds compliance complexity and cost.

V1: The operational core ($120K-$350K, 16-24 weeks)

V1 is the platform that runs day-to-day for a private-duty or non-clinical agency, or serves as the foundation for a clinical platform.

Caregiver and patient management. Profiles for caregivers (credentials, certifications, skills, availability) and patients (care plans, authorized hours, service codes, emergency contacts). Caregiver credential expiration must be a scheduling constraint, not just an HR record. If a CPR certification expires, the system blocks that caregiver from assignment automatically.

Home care scheduling software. Shift assignment that matches caregivers to patients by skill, geography, availability, and continuity preference. The coordinator needs a calendar view per caregiver and per patient, conflict detection, and the ability to reassign a shift in two clicks when a caregiver calls out sick at 6 a.m.

EVV GPS clock-in/out. A caregiver mobile app that captures GPS coordinates at clock-in and clock-out, tied to the patient record and service code. The app must function offline and sync when connectivity returns. This is not optional for any agency billing Medicaid: it is a federal requirement under Section 12006 of the 21st Century Cures Act, which took full effect for home health services in January 2024.

Basic Medicaid billing. Hourly billing for private pay and Medicaid, invoice generation, and payment tracking. Stripe integration for private pay. For Medicaid hourly billing, basic claim file generation tied to verified visit records.

V2: Clinical documentation and Medicare billing ($200K-$300K additional, 14-20 weeks)

V2 adds the clinical documentation and Medicare billing layer for agencies billing skilled care.

OASIS assessment collection. The CMS-mandated assessment must be collected at start of care, resumption, and discharge. The OASIS form has over 100 structured data fields. You need guided form entry with field-level validation and electronic submission to the state's OASIS data system. A failed OASIS submission stops the Medicare billing clock on that patient episode.

Care plan and physician order management. CMS-485 Plans of Care generated from clinical data, routed to the attending physician for signature, tracked through the approval cycle with automated follow-up on unsigned orders.

Clinical visit documentation. Structured nursing notes, therapy assessments (PT, OT, speech), medication administration records, wound care records, and supervisor sign-off workflow. Every note needs to be tied to the visit record and available for audit.

Medicare PDGM billing. Medicare pays per 60-day episode under the Patient-Driven Groupings Model. Your billing module must calculate the correct clinical group and case-mix adjustment from OASIS data, generate 837I claim files, and submit through a clearinghouse like Waystar or Change Healthcare. Track claim status from submitted through paid or denied. Denials management needs its own workflow with reason-code review and resubmission logic.

V3: Multi-state scale and MSO reporting ($150K-$250K additional, 12-18 weeks)

V3 is for operators running across multiple states or managing multiple agency entities.

Multi-state EVV adapter layer. The 21st Century Cures Act mandated EVV for all Medicaid-funded home care, but each state chose its own aggregator. Sandata, HHAeXchange, and state-built systems each have their own submission format, authentication method, timing rules, and error handling. An agency in 10 states needs 10 integrations. The right architecture is a modular adapter layer: one internal interface for recording a visit event, and a state-specific adapter for each aggregator. Budget $20K-$40K per state beyond the first.

Consolidated MSO reporting. A unified reporting layer across multiple agency entities - census by location, consolidated Medicaid and Medicare billing dashboards, cash flow by payer, and caregiver utilization across the portfolio.

AI scheduling optimization. At 200+ caregivers across multiple counties, manual scheduling breaks down. AI-assisted scheduling optimizes for travel time, caregiver continuity, skill match, and credential compliance across the full caregiver pool simultaneously.

Where home health software projects fail

Two failure modes account for most troubled home health software development projects.

Treating EVV as a feature rather than an architecture decision. Agencies that design their scheduling and caregiver mobile app first and add EVV later run into the same problem: the EVV data model doesn't align with how the rest of the system tracks visits, and the state aggregator's submission format requires fields that weren't captured in the right place. The result is a patch job that fails compliance audits and produces submission errors at scale. EVV must be the first architectural decision, not the last feature.

"The integration between Electronic Visit Verification and state Medicaid Management Information Systems remains one of the most technically fragmented challenges in home care IT. Vendors that assume one aggregator works across states consistently underestimate build scope by 40-60%." - Mark Sharp, Senior Analyst, Forrester Research, Home Care Technology Outlook 2025

According to Sandata Technologies, their platform alone serves 28 states - each with different submission rules, aggregator identifiers, and timing requirements. There is no universal format. Every state is a separate integration project.

Underestimating OASIS as a data problem. Agency owners often think of OASIS as a form. It's a structured data submission with more than 100 fields, field-level validation rules, cross-field consistency checks, and electronic submission to a state data system in a CMS-specified format. Clinical staff need guided entry with in-app validation before the form is finalized. The backend needs to catch errors before submission reaches the state. Build the validation layer before you build the UI, not after.

How RaftLabs builds home health agency software

We've scoped and built HIPAA-compliant healthcare platforms for home care agencies, clinical staffing networks, and digital health operators. The agencies that succeed with a custom build treat it as an operational investment with a measurable payback period - not a technology project.

Our process starts with a 2-3 week scoping engagement before any code is written. We map your current workflows, document the EVV aggregators for every state you operate in, define your payer mix (private pay, Medicaid hourly, Medicare episodic), and scope a V1 that gets you operational without over-building.

We build the EVV adapter layer before the scheduling UI. We integrate with your state aggregators and validate against their sandbox environments before any real visit data flows through. We build the Medicaid billing software as a connected system to your clinical documentation - not a separate tool your billing coordinator runs in parallel.

We sign BAAs with every vendor that touches patient data. We build audit trails that meet the 6-year HIPAA retention requirement. We test OASIS submission against your state's data system before you go live with Medicare patients.

If you run 50+ caregivers and your current home health agency software is creating compliance risk or limiting your growth, we're worth talking to. If you're an earlier-stage agency that needs a better standard platform, we'll tell you that instead.

Let's talk about your build