Custom vs off-the-shelf software: choosing the right solution for your home care agency
Home care and home health agency owners choose between a packaged agency system, a custom build and a mix of both. The deciding factors are specific to the agency: how your state collects EVV data, which payers you bill, how caregivers are paid, and whether you can get your own data out.
Should a home care agency buy off-the-shelf software or build custom?
Quick answer
Most home care agencies should buy an off-the-shelf agency system for scheduling, EVV and billing, then build custom software only where the package falls short: a family portal, a caregiver app or analytics. A full custom build fits when your state EVV model, payer mix or pay rules break every package. Agnotic Technologies builds those custom parts.
| Criterion | Off-the-shelf | Custom |
|---|---|---|
| Non-medical, private pay agency | Usually fits: scheduling, care notes and invoicing are standard | Rarely needed, except a branded family app or client portal |
| Medicaid personal care agency | Fits if it works with your state's EVV system or aggregator | Consider when you serve several states with different EVV models |
| Medicare-certified home health agency | Fits if it handles OASIS submission and your plan-of-care workflow | Rarely full custom; build add-ons such as visit analytics or referral intake |
| Mixed private pay, Medicaid and Medicare | Fits if one package bills all three without side spreadsheets | Hybrid: package for billing, custom layer to join the data |
| Live-in and overtime-heavy caregiving | Check overtime, travel time between clients and live-in rules in payroll exports | Custom pay rules engine when the package cannot model your agreements |
| Multi-state operations | Fits only if every state's EVV program is supported | Custom EVV connectors per state over a shared scheduling core |
| Data access and reporting | Check exports, APIs and how often data can be pulled | Your data lands in your own warehouse from the start |
What they are
What is Off-the-shelf
A packaged system for running an agency: client intake, caregiver scheduling, visit verification, care notes, billing and payroll exports. It is configured rather than written, updated by the vendor, and usually already connected to common state EVV systems and clearinghouses.
What is Custom
Software built for your agency: anything from a full agency platform to one component, such as a caregiver mobile app, a family portal or an analytics layer on top of a packaged system. You own the code and decide what changes, and you carry its upkeep.
Key differences
How does your state's EVV model decide the choice?
Section 12006 of the 21st Century Cures Act requires electronic visit verification for Medicaid personal care services, from 2019, and home health care services, from 2023. An EVV system must verify six things: the type of service, the person receiving it, the date, the location, the person providing it, and the start and end times. States meet that differently: some supply one system every agency must use, others accept data from an agency's own system. Check your state's EVV program documentation before you shortlist any package.
Why do pay rules break packaged software?
Under 29 CFR 552.109(a), third party employers of caregivers providing companionship services cannot claim the minimum wage and overtime exemption, even when the family is a joint employer. Agencies therefore pay overtime and must count hours across clients, often with travel time and live-in arrangements. If a package cannot model your rules, staff fix payroll by hand each period, which is where a custom rules engine pays for itself.
What does Medicare home health add to the decision?
Medicare-certified agencies submit OASIS assessments: under 42 CFR 484.45(a), each completed assessment must be encoded and transmitted to the CMS system within 30 days. Packages built for home health already handle that submission and the plan-of-care workflow, so a custom build rarely makes sense for the core. Our home health software page covers the OASIS and EVV features we build when it does.
What should you check in a vendor's data export and APIs?
Whether you can pull clients, caregivers, visits, EVV records, notes, invoices and payroll lines through an API or scheduled export; how often; in what format; and whether the export includes history or only current records. Without that, every custom add-on depends on manual downloads.
What does a hybrid look like for a home care agency?
Keep the packaged system as the record for scheduling, EVV, billing and payroll. Build around it: a family portal that shows visit times and care notes, a caregiver app for tasks the package app lacks, or a warehouse that joins visits, payroll and outcomes. Each piece reads from the package's API and writes back only where the vendor allows.
When to use each
When to use Off-the-shelf agency software
- You operate in one or two states whose EVV programs the package already supports.
- Your payer mix and visit types match what the package was built for.
- Your pay rules can be expressed in the package's payroll settings.
- You want to start billing quickly without an engineering team.
When to use Custom build
- You serve several states whose EVV models no single package handles well.
- Your pay agreements, overtime and travel time rules break package payroll settings.
- Families or referral partners expect a portal or app the package does not offer.
- You need your data in your own warehouse for analytics the package cannot run.
Which questions should you ask a home care software vendor?
1. Which states' EVV programs do you support today, and how do you send data to each: the state's own system or its aggregator?
2. Can your payroll export handle our overtime, travel time and live-in rules? Show us with our own pay agreements.
3. Which payers and claim formats do you bill, and how are rejections returned to us?
4. For home health: how do you handle OASIS submission and corrections?
5. Do you offer an API? Which records can we read and write, and are there limits on calls?
6. Can we export all our data, with history, at any time and when we leave?
7. Will you sign a BAA, and which subcontractors handle our clients' data?