Introduction: The Expensive Decisions Are Made Before Development Starts
Most home care platform projects don’t fail because of bad code. They fail because of decisions made months before a single line was written. An agency commits to building its own EVV system in a state that already mandates a specific vendor. A scoping document treats four states as one simple integration. A budget gets built around skilled home health features the agency never actually needed. Travel time between clients never gets captured, and the gap only shows up at payroll.
Every one of those is a question with a knowable answer, if someone asks it early enough. That’s the real value a home care technology consultant brings in 2026: not picking your tech stack, but catching the four or five decisions that quietly turn a defined project into an open-ended one.
This article walks through why 2026 is a decision point for so many agencies, the choices that actually determine outcomes, what a competent consultant reviews before scoping anything, how to get an honest build-versus-buy answer, and what a first conversation with a caregiver app development partner should sound like.
Why Is 2026 a Decision Point for Many Agencies?
Three things have converged, and none of them is a marketing deadline. The first is that EVV has matured from a compliance scramble into settled infrastructure. States have implemented their models, aggregator paths are established, and most agencies now have several years of real operating experience with these systems. That history matters. An agency evaluating a platform today can specify what it actually needs, instead of guessing at a requirement that’s still shifting underneath it.
The second is workforce economics. Minimum wage and overtime rules for agency-employed caregivers are firmly established, and turnover remains the industry’s central operating problem. Scheduling and payroll accuracy aren’t back-office details anymore. They directly affect margin and retention.
The third is consolidation. Agencies that have grown through acquisition are often running several inherited systems across multiple states. That’s the situation where a single custom or hybrid platform starts to make genuine economic sense, not just a nicer-to-have. Consolidating those systems into one is where home care software development starts to pay for itself.
None of this means every agency should build. It means the question is finally worth answering properly, instead of putting it off another year.
The Decisions That Determine the Outcome
1. The State EVV Model, Per State
Some states run a closed EVV model. In those states, an agency may be required to use the state’s designated system for capturing Medicaid visits. That single fact materially changes what a custom platform can and can’t do there. This determination needs to be confirmed directly with each state Medicaid agency, not assumed from a vendor’s marketing page. Getting the answer early can shrink a planned build into a much smaller integration project. It can also reveal that a full build is worth more than the agency originally expected.
2. Skilled or Not
Medicare-certified home health brings requirements a private-pay or Medicaid personal care agency simply doesn’t have. OASIS assessments, Conditions of Participation documentation, and episodic billing rules that change every year all add real complexity. Deciding whether the platform needs to support skilled services is a conscious choice, not a default. It’s also the single largest lever on project scope.
3. What Is Genuinely Not Configurable Today
Much of what feels like platform frustration is actually configuration frustration. The current system may already support what an agency needs; it just hasn’t been set up that way. Separating what truly can’t be configured from what simply hasn’t been tried yet is some of the cheapest work in the whole project. Sometimes, it ends the project entirely, in the agency’s favor.
4. How Pay Is Actually Calculated
Real payroll logic includes rates by client and service, shift differentials, and live-in or sleep-time arrangements. It also has to account for multi-client overtime, travel time, and mileage. Documented properly before scoping begins, this logic becomes a clear specification. Discovered mid-build instead, it becomes rework in the most sensitive part of the system.
5. What the Incumbent System Will Release
A new platform needs clean data on clients, caregivers, credentials, authorizations, schedules, and receivables. Export capability and terms should be confirmed with the current vendor well before any project timeline is agreed. Waiting until later can turn a simple data migration into a costly, last-minute negotiation.
What a Competent Consultant Reviews Before Scoping
A real pre-scoping review looks less like an interview and more like fieldwork. It should start with time spent alongside schedulers during a live day, not a structured requirements session. Watching how a call-off gets handled, how a shift actually gets filled, and which spreadsheets still exist alongside the official system reveals far more than any set of questions.
Time with caregivers matters just as much, including a ride-along where clients have given consent. The people using the app in doorways and kitchens know exactly where it fails. An app scoped only around office staff tends to demo well and get resisted daily.
From there, the review should produce a few concrete documents. A per-state EVV determination, confirmed with each state Medicaid agency, covering the model, the aggregator, onboarding requirements, and the timeline. A payer inventory that covers authorization, documentation, and billing behavior for every funder, with a clear recommendation on which ones get configured in release one. A pay rules document that captures how the agency actually calculates wages today, reviewed with employment counsel wherever the answer is unclear. A migration feasibility check on what the incumbent system will release, and in what form, with particular attention to schedules and active authorizations.
The review should end with an honest build-versus-buy read. That includes the real possibility that configuring the current platform, or replacing only part of it, is the better answer.
Reading the Answer: Buy, Build, or Replace One Layer
Buying makes sense for a large share of home care agencies. It’s the right call when an agency operates in one or two states with fairly conventional service lines. It also holds when existing platforms already carry the EVV connections and payer setups the agency actually needs. If the agency can’t free up the people a build would require, buying is the honest answer too. The same is true when software is simply a tool the agency uses, not something that makes it distinctive in the market. An advisor who never arrives at “buy” for any client isn’t really advising.
Building makes sense in narrower circumstances. It’s worth considering when scale makes per-caregiver software pricing compound into real money over time. It also applies when multi-state operations exceed what configuration alone can handle. A franchise system that needs a consistent, branded experience across every operator is a build case. So is a service model that simply doesn’t exist in any product on the market today.
There’s a third option that gets overlooked far too often: replacing just one layer. When frustration is concentrated in a single area, replacing only that part delivers most of the value at a fraction of the cost and risk. A custom family portal layered over an existing back office is one example. A purpose-built caregiver app feeding into an existing scheduler is another. Both are realistic, and both are far cheaper than replacing the whole platform. That portal layer is custom web application development rather than a full replacement.
What the First Conversation Should Cover
A capable partner starts by asking questions, not pitching a solution. Which states do you operate in, and what EVV model does each one run? Are you Medicare-certified? What does your payer mix look like today? How many caregivers do you employ, and what does turnover actually look like? What will your current system export, and in what form? How do your pay rules really work, in practice, not on paper? And what specifically is failing right now that configuration alone can’t fix?
The way they answer follow-up questions tells you just as much. A partner who can explain the difference between closed and provider-choice EVV models is engaging with the real problem. So is one who can explain why telephony capture still matters, or why travel time belongs in scheduling rather than as a payroll afterthought. One who can’t do any of that is quoting a scheduling application, not advising on your business.
It’s also fair to ask what they’d tackle first if you handed them a third of the budget. That answer quickly separates advisors from vendors. A good first conversation ends in agreement on the hard problems, not a number on a page.
Red Flags in the Conversation
Some warning signs are easy to spot once you know to look for them. A fixed price offered before any real discovery has happened is one. So is a partner who never asks which states you operate in. If EVV gets described as “one integration” regardless of how many states are involved, that’s a problem. Telephony capture dismissed as outdated legacy tech is another red flag.
So is skilled and non-medical care presented as a single, identical feature set. Travel time that never comes up in the conversation is worth noticing too. Migration priced as a round number, with no actual contact made to your current vendor, should give you pause. The same goes for a caregiver app scoped without any proposal to talk to an actual caregiver.
The quietest red flag is easy to miss. It’s a partner who never once considers that configuring what you already run, or replacing just one layer, might genuinely serve you better.
The strongest positive signal runs the other way. Look for a partner who asks to spend a day with your schedulers. One who wants to see a visit from the caregiver’s side, with client consent. And one who can describe your own operation back to you, including the workarounds your team stopped even noticing years ago.
Final Thoughts
The decisions that determine the outcome are made before development starts. Settling the per-state EVV determination, deciding the skilled question on purpose, and documenting how pay is genuinely calculated all matter. So does confirming what your current system will actually release. Owners who work through these before committing money end up in one of two good places. Either they de-risk a build that was genuinely worth doing, or they discover that a narrower change delivers most of the value anyway. Both outcomes are worth considerably more than the cost of the assessment itself.
If you’re weighing a custom platform against the system you run today, a structured assessment is what protects your budget before development begins. That means a per-state EVV determination, a conscious skilled-scope decision, documented pay rules, a migration feasibility check, and a costed comparison of staying, replacing one layer, or building new.
Talk to NewAgeSysIT about getting that assessment done properly. Learn more about digital transformation solutions from one of the leading AI software companies in the United States.
