Introduction: Two Questions That Size the Budget Before Any Feature Does
Two questions set the order of magnitude before any feature list produces a number, and they matter more than most line items in a home care software development cost estimate.
The first question is whether the platform serves Medicare-certified skilled home health, or non-medical personal care only. The skilled side brings OASIS, physician orders, discipline-specific documentation, Conditions of Participation requirements, and episodic Medicare billing that changes with annual rulemaking. It’s a materially larger project, and it comes with an ongoing maintenance commitment attached.
The second question is what EVV model each state operates. In a closed-model state, an agency may be required to use the state’s designated system for Medicaid visit capture, which shrinks what a custom platform actually does there. In a provider-choice state, the platform carries the whole flow, including aggregator onboarding. This is where custom software development and custom mobile app development actually start.
An estimate produced without settling both questions is answering a different question than the one being asked. This article covers staged cost and timeline, the skilled fork, cost drivers, forgotten line items, first-release scoping, and ongoing economics. All figures given are 2026 planning ranges rather than quotes.
Stage-by-Stage Cost and Timeline for 2026
Stage 1. Core Scheduling and Visit Capture ($95K–$175K, 5–7 months)
This stage covers client and caregiver records, care plans, and constraint-aware scheduling with overtime visibility. It includes the caregiver mobile app with offline capture and task completion, telephony fallback, change-of-condition routing, and role-based access. This is the platform an agency can actually run a day on.
Stage 2. EVV Transmission and Workforce Compliance (+$50K–$105K, 3–5 months)
This stage adds aggregator submission per state, rejection handling and correction workflow, and reconciliation views across the visit chain. It also covers credential and training expiry enforcement at scheduling time, and supervisory visit tracking where it applies. Cost here scales with state count, not with feature count.
Stage 3. Billing and Payroll (+$75K–$140K, 4–6 months)
This stage covers multi-payer billing across Medicaid programs and managed care, and private-pay invoicing with cards on file and statements. It also includes long-term care insurance documentation packages, and the pay rules engine covering rates, differentials, overtime, travel time, and mileage, with payroll export and an approval gate.
Stage 4. Family Portal, Communication and Reporting (+$45K–$90K, 3–4 months)
This stage adds the family portal with per-person access control, notifications, and private-pay payment. It also covers the operational reporting an owner actually runs the business on, including fill rate, overtime, utilization, EVV acceptance rate, and caregiver retention.
Full Non-Medical Platform
All four stages together run roughly $265K to $510K across 15 to 22 months. Medicare-certified skilled scope sits outside these figures, since caregiver app cost context and the scheduling console and family portal cost context each pull in custom mobile app development and web application development work as they’re built out. The skilled fork is covered in the next section.
The Skilled Fork: What Medicare-Certified Scope Adds
Adding Medicare-certified skilled home health isn’t a module on top of the non-medical build. It’s a second product that happens to share a scheduler.
It brings the comprehensive assessment, including OASIS, with its own submission requirements. It brings physician and allowed-practitioner orders driving the plan of care, with verbal order capture and authentication. It brings discipline-specific documentation for nursing and therapies, care coordination and discharge requirements, quality assessment and performance improvement, aide supervision tracking, and clinical records that meet Conditions of Participation content, retention, and access requirements.
Billing is effectively a separate system. Skilled home health runs on episodic payment across thirty-day periods under the Patient-Driven Groupings Model, with a Notice of Admission required at the start of care and value-based purchasing adjustments layered on top.
The part owners tend to underestimate is maintenance. Medicare home health requirements change through annual rulemaking, so the skilled side carries a permanent obligation to track and implement that change. It’s a recurring cost, not a one-time build.
For most agencies, the honest recommendation is to keep a certified product for the skilled side and build custom where the market serves them least. That comparison is worth costing explicitly before committing either way.
What Drives Cost Up
State count is the largest structural multiplier in this vertical. Each additional state can bring a different EVV model, a different aggregator with its own specification and onboarding, different licensure and training rules, and a different Medicaid program.
EVV model mix adds to that. Provider-choice states put the whole submission flow in scope, while closed-model states reduce it but add a handoff instead. Operating across both means building for both.
Payer mix is its own driver. Medicaid programs, managed care organizations, private pay, long-term care insurance, and VA each bring their own authorization, documentation, and billing behavior, and none of them can be treated as a variant of another.
Pay rules complexity matters too. Differentials, live-in and sleep-time arrangements, multi-client overtime, and travel time make the payroll engine one of the more intricate components of the platform, rather than a simple rate lookup.
Skilled scope adds cost for the reasons covered in the previous section.
Migration is often underweighted. Clients, caregivers, credentials, active authorizations, schedules, and open receivables all have to come across cleanly. Schedules in particular are unforgiving. A go-live with a wrong schedule means caregivers arriving at the wrong homes.
The Line Items Agencies Forget
Aggregator onboarding and certification per state is easy to underestimate. Testing cycles run on the vendor’s calendar, not the project’s, and that alone can stretch a timeline.
Telephony infrastructure is another one. Call-in and call-out capture needs phone numbers, routing, and per-minute costs budgeted in. This is genuinely necessary rather than legacy, and leaving it out of the budget means leaving out the clients who need it.
Caregiver device strategy carries real cost and policy implications either way. Whether the agency issues devices or relies on personal phones, someone has to account for stipends, data plans, device management, and a support path for a caregiver whose phone fails mid-shift.
Training and rollout across a distributed, high-turnover workforce is not a one-time event. It’s a permanent onboarding requirement, which makes in-app guidance a cost saving rather than a polish item.
Support capacity at go-live matters more than most budgets reflect. Caregivers call when clock-in fails, and they often call from a client’s doorstep. The support model needs to exist before launch, not after the first bad week.
Two more get missed regularly. Parallel running through cutover, and migration of historical visit data where it’s needed for audits.
What Keeps the First Release Manageable
Launch in one state first, and prove the whole chain there. Schedule, capture, submit, accept, bill, and pay all need to work end to end before a second state gets added. A single state working cleanly is worth more than partial coverage spread across four.
Starting with one branch or one service line, rather than the whole agency, is worth the same logic. Problems surface at a survivable scale instead of a costly one.
Capture should be built for all three methods from the start. This is the one place not to economize, because the clients who need telephony fallback are the same clients most likely to be missed without it.
Deferring the skilled side is worth considering unless the agency is genuinely committed to it. Keeping a certified product for that business permanently is a reasonable outcome, not a stopgap.
Schedule optimization algorithms can wait too. Constraint-aware manual scheduling with good visibility is enough for a first release.
Run in parallel through cutover, and choose a go-live date that isn’t a holiday week. In an operation where a failure means someone doesn’t get their morning visit, the conservative sequence is the correct one.
Ongoing Costs and the Comparison with Per-Caregiver Platforms
Ongoing costs cover hosting that scales with visit volume, telephony minutes, SMS and notification delivery, device management, backup and disaster recovery for a system the schedule depends on, and monitoring. A reasonable budget lands in the region of 15 to 25 percent of build cost annually.
Regulatory maintenance is genuinely recurring here. State EVV requirements move, licensure rules move, and on the skilled side, annual Medicare rulemaking moves too. Someone has to own implementing each change as it lands.
The honest comparison matters just as much as the build cost. Established home care platforms carry existing EVV connections in most states, existing payer setups, support, and a per-caregiver or per-client price with near-zero capital cost. For a single-state agency running conventional operations that needs to be live in weeks, that’s usually the right answer, and it’s worth saying so plainly.
Custom starts to make sense at scale. It fits multi-state operators whose configuration needs exceed what off-the-shelf platforms allow, franchise systems that need a consistent branded experience, and agencies whose service model existing products simply can’t represent.
The scoping work that protects this budget either way is covered in Why US Home Care Agency Owners Need a Technology Consultant in 2026.
Final Thoughts
Agencies that settle the skilled question and the state EVV model before pricing anything tend to arrive at a number they can actually build to. Budgeting by stage, and treating aggregator onboarding, telephony, caregiver devices, and go-live support as named line items rather than assumptions, gets them there. Many find that a narrower platform delivers most of the value they were actually after.
If you’re costing a custom home care platform, settling your skilled scope and your per-state EVV model before anything gets estimated matters. So does the pricing state count as the multiplier it actually is. Together, that produces a budget that survives contact with the build. That’s the kind of scoping NewAgeSysIT works through with agencies before a number gets attached to anything. Learn more about digital transformation solutions from one of the leading AI software companies in the United States.
