Area Agency on Aging Case Management Software: Configure WellSky, or Build the Authorisation Layer?
The threshold most area agencies on aging can use is roughly $6M a year in authorised services across three or more funding streams.
On this page
The threshold most area agencies on aging can use is roughly $6M a year in authorised services across three or more funding streams. Below that, running one or two Older Americans Act titles with a provider network you can count on two hands, buy: WellSky Aging and Disability will do the programme reporting properly and a build is an expensive way to reach the same place. Above it, and particularly once Medicaid waiver case management sits alongside Older Americans Act services, two governance regimes meet on one client and the money side stops fitting any configuration. That is where building pays, and it is the money side rather than the clinical workflow that justifies it.
When is off the shelf genuinely the right call here?
The market here is genuinely mature, which is not true of every category we write about. WellSky Aging and Disability, descended from the product most directors have used at some point, handles Older Americans Act reporting properly and is the default for good reason. Eccovia ClientTrack is highly configurable. PeerPlace fits particular statewide deployments well. None of them fails at what it was built for.
If you run one or two Title III programmes without waiver case management, with a provider network small enough that month end reconciliation is a morning rather than a week, buy and configure. The programme report will come out correctly, your caseload will be held properly, and a custom project would be an expensive way to reproduce something that already works.
Buy and stop, too, if your state licenses the system centrally. Many agencies do not actually hold the decision, and where a statewide platform is mandated the sensible move is to work the configuration hard and keep a clean local record of anything the platform cannot express. Building beside a mandated system is possible, but it needs a specific gap and a state relationship that permits it.
The honest test is where your finance team spends month end. If provider invoices are checked against authorisations inside the system and exceptions are rare, the tooling is doing its job. The build case in this category almost always announces itself as a workbook.
When does a custom build actually pay off?
Two or more of the following usually settle it. You authorise over roughly $6M a year across three or more funding streams. You perform waiver case management alongside Older Americans Act services, so two rulebooks meet on one client and each has its own eligibility, unit rate, cap and reporting obligation. Your finance team spends more than a week a month reconciling provider invoices. You maintain waiting lists and cannot explain your prioritisation with data. Or your state has changed rates, reporting or conflict free case management requirements and your current configuration is a consulting engagement away from compliance every time.
The argument that carries a board is exposure rather than efficiency, and it runs both directions. You pay for units nobody authorised, and you also fail to notice a client authorised for daily visits who received four in a month, which is a service failure hiding inside a payment process. The second one is the finding that hurts, because it is a person rather than a variance.
The pattern we see is not that the products fail. It is that agencies above a certain size run them for the client record and run the money in spreadsheets beside them, and the spreadsheets are where the risk concentrates. When a state reviewer asks why 43 meals were charged to a funding source the client's eligibility did not cover in March, the answer is currently in somebody's head.
The third trigger is the waiting list, which is usually the least defensible process in an agency and the one with the most human consequence.
How do they compare on the things that matter in this industry?
The comparison worth making is about where configuration runs out.
- Funding as rules, not fields. Most systems treat funding as an attribute of a service. It is a rule set with its own arithmetic, so a client moving from a state programme to a waiver on the 14th needs a clean split with both segments retained and reportable. Ask any vendor to demonstrate that split rather than describe it.
- Authorisation as a commitment. Service, provider, rate, unit cap, date range, funding source and the eligibility condition that must hold. Whether the system will refuse to authorise against a source the client does not currently qualify for is the difference between preventing a finding and discovering one.
- Invoice validation depth. Matching submitted units to authorisation on rate, date range, remaining units, provider eligibility and client funding eligibility on the date of service, with an exception queue. Totals that look plausible are not validation.
- Electronic visit verification. Visit data exists wherever Medicaid personal care applies, because it is a federal requirement under the Cures Act. Whether your system can ingest your state aggregator's feed and match it to authorisations decides if verification and payment ever meet.
- Waitlist prioritisation. Versioned scoring applied from assessment data with visible reasoning, versus a coordinator ranking names. One of those can answer a legislator.
- Caregiver modelling. Whether caregiver and care recipient are separate people with a typed relationship, or a duplicate record with a note.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, a focused first release covering assessment, care planning and service authorisation with funding stream rules, plus provider contracts and rates, runs $80,000 to $160,000 and ships in 12 to 18 weeks. A full platform adding provider unit capture with validation, invoice generation, waitlist prioritisation, caregiver programme support and programme reporting runs $200,000 to $500,000 phased over 8 to 14 months.
The number of funding streams you bring in on day one moves the estimate most, because each stream is a rule set with its own eligibility, unit rate, cap and reporting obligation rather than a value in a dropdown. Two Older Americans Act titles is a contained build. Adding Medicaid waiver case management alongside them roughly doubles the authorisation work, because two governance regimes now meet on one client.
Other drivers: electronic visit verification integration, where the aggregator or vendor your state selected determines how pleasant that work is and you do not get to choose. Provider network size, since onboarding forty subcontracted providers to a submission portal is change management rather than software. And any state specific assessment instrument with licensing conditions attached.
On the running side, expect the standing cost to be rule maintenance rather than infrastructure. Rates change, caps change, a state redefines a unit, and somebody has to version the crosswalk so prior years remain reportable exactly as they were filed. Name that person. An agency where nobody owns rule currency ends up with a system that is confidently out of date.
What does the hybrid look like, and when is it the honest answer?
For most agencies above the buy line the hybrid is the right shape, and it is cheaper than either extreme. Keep WellSky Aging and Disability or ClientTrack for the client record, assessment and programme reporting, and build only the money layer beside it: authorisations with funding stream rules, provider unit capture with validation, and invoice generation from validated units.
That split works because the boundary is clean. The case management side is what the products do well and what your staff already know. The authorisation and payment side is where local rules, state variation and three funding streams collide, and it is where the spreadsheets are. Building only that piece keeps your clinical workflow untouched, which also removes most of the change management risk from the project.
The sequencing advice follows from it: implement authorisations and provider unit validation first and leave assessment where it is for another year. The money problems are the expensive ones and they can be fixed without touching how a care manager does a home visit.
The smallest credible build is provider unit validation on its own. Providers submit units through a portal or a defined file, or the system ingests the electronic visit verification feed, and each unit is matched to an authorisation and checked. Exceptions land in a queue with a reason. It is a fraction of the first release band, it closes the exposure that runs in both directions, and it produces the evidence for anything you decide to fund after it.
Which should you choose, by operator size and stage?
One or two Title III programmes, no waiver, small provider network: buy and configure. Put your effort into rate tables and provider contracts being accurate in the system rather than in a folder, which will pay off whatever you decide later.
Growing agency approaching $6M in authorisations, two funding streams: buy, then measure one thing. Time the month end reconciliation for three consecutive months and count the exceptions found. If it is under a week and exceptions are rare, keep configuring. If it is over a week, you are already funding the build in salary.
Above roughly $6M across three or more streams: build the money layer and keep the case management product. Start with authorisations and unit validation, and expect the funding rules discovery to take longer than the engineering, because the rules exist across several people who do not agree yet.
Agencies performing waiver case management alongside Older Americans Act services: build. This is the population where two rulebooks meet on one client, where conflict free case management separation may apply, and where no single configuration expresses both regimes without a workbook underneath.
Agencies with waiting lists at any size: build the prioritisation register even if you build nothing else. Versioned scoring with visible reasoning, time on list, offers made and outcome at removal, including people who died waiting, is a number every director should be able to state and almost none can.
When you are ready to turn this into a specification, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- Gallup reports global employee engagement fell to 20% in 2025 (its lowest since 2020, down from a 2022-2023 peak of 23%), and estimates low engagement costs the world economy an estimated $10 trillion in lost productivity, or 9% of global GDP. (Note: this figure appears in Gallup's evergreen State of the Global Workplace page, currently reflecting the 2026 edition reporting on 2025 data.). Source: Gallup (2025) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
Frequently asked questions
What does it cost to move off WellSky or ClientTrack later?
The client history is the expensive part, because aging services records span years of a person's life and a partial export is not much use to a successor system or to a state reviewer.
Settle this before you need it: contract for a full structured export on demand rather than on exit, including assessments, authorisations, units and the crosswalks behind your reporting. If you build the money layer beside the product, that half is already yours, which materially shortens any future migration.
What happens if our state changes the system or the vendor changes pricing?
Many agencies do not hold this decision, because the platform is licensed centrally, and that is exactly the argument for keeping your local logic outside it. Authorisation rules, provider rates and validated unit history that live in your own layer survive a statewide platform change.
Where you do hold the decision, treat a repricing as a prompt to check your export rights rather than as a reason to build. The build case has to rest on reconciliation time and payment exposure, which are measurable this quarter.
How long does it take to build the authorisation and invoicing layer?
Twelve to 18 weeks for a first release covering assessment, care planning and authorisations with funding stream rules plus provider contracts and rates, in our delivery experience. Provider unit validation on its own can land faster as a standalone piece.
The schedule risk is rule discovery rather than engineering. Funding rules usually live across several people who have never had to reconcile their versions, and pinning them down is the phase that slips. Agencies that appoint one decision owner for rule questions move noticeably faster.
Is WellSky Aging and Disability enough for an agency doing waiver case management?
It handles the Older Americans Act side properly, including programme reporting, and it is the default for good reason. The strain appears when waiver services sit alongside, because two governance regimes then meet on one client with different eligibility, unit rates, caps and reporting obligations.
The pattern we see is that the client record stays in the product and the money moves into spreadsheets beside it. If that describes your agency, the gap is authorisation and reconciliation rather than case management, and it is the gap worth building.
How should software handle a client funded from several sources?
Treat funding as a rule set rather than a field on a service. Each authorisation carries the funding source, rate, unit cap, effective dates and the eligibility condition that has to hold, so a client moving from a state programme to a Medicaid waiver mid month produces a clean split with both segments retained and reportable.
The system should also refuse to authorise against a source whose eligibility the client does not currently meet. That single rule removes a whole category of audit finding at the point of entry rather than at review.
Does electronic visit verification change the build or buy decision?
It raises the value of building wherever you touch Medicaid personal care, because the visit data already exists as a federal requirement under the Cures Act and is usually stranded in a state aggregator or vendor portal that never meets your authorisation data.
Ingesting that feed and matching it to authorisations closes the loop between verification and payment. How much work that is depends heavily on which aggregator your state selected, which you do not control, so get a specific answer about your state before scoping anything.
Can a purchased system make our waiting list defensible?
Only if it holds prioritisation as versioned scoring applied automatically from assessment data, with the reasoning visible for each person's position. Most agencies end up with a coordinator ranking names in a spreadsheet against a rubric nobody has revisited since the last director.
Record time on list, reassessment prompts, offers made and outcome at removal, including people who died waiting. When a legislator asks how long an older adult waits in a rural county, or an advocate asks whether prioritisation disadvantages a group, that data is the difference between an answer and an anecdote.
Why do caregiver programmes need special modelling?
Because under the family caregiver programme the person you serve is the caregiver, while eligibility relates to the care recipient, who is a distinct individual. Systems that assume one client per record push agencies into duplicate records or relationship fields that reporting cannot use.
The consequence is that respite hours get recorded against the wrong person and the caregiver's own service history becomes unreadable. Modelling caregiver and care recipient as separate people with a typed relationship, and letting a service be delivered to one on behalf of the other, is a small decision with large reporting consequences.
Who owns the code when an agency builds our internal tool?
You should, outright, with full IP transfer in the contract and the code delivered to a repository you control, such as your own GitHub organization. Digital Heroes transfers complete ownership on final payment as standard practice, and any agency that keeps the code or licenses it back to you is building a dependency you will pay for later. Confirm you also own the hosting, domain, and database accounts, since many of the vendor disputes Digital Heroes gets called into involve infrastructure registered under the agency's name.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?
Yes, and integrations are usually the strongest argument for going custom instead of chaining tools together with Zapier. QuickBooks, Salesforce, Shopify, Stripe, Slack, and Google Workspace all have mature APIs, and each integration typically adds $1,500 to $5,000 to a Digital Heroes build depending on how much two-way syncing you need. The honest caveat is legacy industry software without an API, which may need file-based imports instead of a live connection, so list every system in the first conversation.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
At what point does Retool cost more than building a custom tool?
The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.
When does a company outgrow Airtable?
The usual breaking points are record limits, permissions, and automation complexity. Airtable's Team plan caps each base at 50,000 records and Business at 125,000, so operations logging thousands of rows a month hit the ceiling within a year or two. The other trigger Digital Heroes sees constantly is permissions: restricting who can view specific fields or records is clumsy below Airtable's Enterprise tier, which becomes a genuine problem once salaries, pricing, or client contracts live in the base.
How much does a custom internal tool cost to build?
Most custom internal tools cost $8,000 to $40,000 to build, based on Digital Heroes delivery data across 2,000+ client projects. A single-purpose tool like an approval dashboard or inventory tracker sits at the low end, while a multi-department platform with role-based access and several integrations pushes past $40,000. The three biggest cost drivers are the number of user roles, the number of systems the tool must connect to, and custom reporting requirements.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other internal tools companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
