Disaster Case Management Software: Keep CaseWorthy or Apricot, and Build the Duplication Layer Above Them
Roughly $3M of unmet needs funding is where this turns, not household count.
On this page
Roughly $3M of unmet needs funding is where this turns, not household count. A single agency working under about 200 households, distributing its own funds with no committee spanning several organisations, should configure CaseWorthy or Apricot by Bonterra, keep a disciplined award ledger with one owner, and put the difference into case managers. Above that threshold, or once federal disaster recovery money with formal duplication requirements is involved, the arithmetic stops being something a person can hold. The cheapest credible move then is not a replacement: keep your case platform and build the ledger and duplication engine beside it for roughly $50,000 to $75,000.
When is off the shelf genuinely the right call here?
CaseWorthy and Apricot by Bonterra are capable configurable case management platforms used seriously across human services. The Coordinated Assistance Network exists so relief agencies can see that a household is already known to someone else, and it earns its place during a response. None of these should be rebuilt.
Buy, and stop reading here, if this describes you:
- A single agency working under roughly 200 households.
- Your own funds, one set of rules, no federal disaster recovery money.
- No unmet needs committee drawing from several organisations.
- Cases you expect to close inside a year rather than carry for five.
- An award ledger a spreadsheet with one named owner can hold accurately.
At that scale the duplication arithmetic is small enough for a person to reason about, and a build is not a good use of restricted funds.
Two further points that hold at any size. Participate in the Coordinated Assistance Network regardless of what else you do, because cross agency awareness already exists and rebuilding it is a waste of money. And if you are reading this during an active response, understand that urgency is itself a cost driver: standing a system up in the weeks after an event costs materially more than the same system built in a calm period, because discovery competes with a live operation and every decision needs somebody currently working sixteen hour days.
When does a custom build actually pay off?
It pays off at the point where a committee is making a legal determination from a folder read aloud.
Picture the Tuesday evening seven months after the storm. Nine people from six organisations in a church hall. Case 412 is an uninsured homeowner whose roof and subfloor need $41,000 of work. Federal individual assistance paid something, a loan was approved and not accepted, her policy paid for wind but not water, a faith based partner bought appliances, and the state programme has her application pending. The committee must decide tonight how much to release, and the arithmetic that determines the legal answer is being read from a folder.
Get it wrong and this is not a bookkeeping error. The Stafford Act prohibits duplication of benefits, federal grantees are required to recover duplicated assistance, and a subrecipient that awarded twice for the same repair can be required to repay long after the money reached a contractor and the roof went on.
Build when two or more of these are true:
- You are moving over roughly $3M of unmet needs funding.
- Your committee draws from several organisations who need different views of the same household.
- You administer or expect to administer federal disaster recovery funds with formal duplication requirements.
- Your cases will run for years across complete staff turnover.
- A funder has already asked you to demonstrate how a specific award was calculated, and the answer took a week to assemble.
How do they compare on the things that matter in this industry?
Duplication as category arithmetic. Ask a supplier to model duplication of benefits on a whiteboard. If they draw a total assistance field, they will build a case tracker and you will keep the workbook. The question is never whether a household received assistance, it is whether they received assistance for the same need. A personal property award does not offset a roof. A wind settlement does not offset flood damage to a subfloor. An approved loan the household declined is treated differently from one they accepted. What you want is line items with source, programme, category, amount, date and status, offset category against category, with the working visible.
Verified loss by component. Most recovery groups document what a household received well and what they lost poorly. Federal inspection summaries, contractor estimates, volunteer photo sets and case narratives cover different scopes and disagree with each other, and none is stored as a structured number tied to a part of the home. Without loss captured by component, unmet need is a case manager's judgement written in prose rather than a reproducible calculation.
Conditional awards. Ask what happens when a committee approves an award conditional on a state programme declining, and the denial arrives eight months later. A supplier who has done this builds a watcher. One who has not will offer a reminder field, and the case sits dormant until somebody remembers.
Partial visibility between partners. A household may be worked by a national voluntary organisation, a faith based partner, legal aid and a state funded case manager at once. Ask how a partner sees the assistance ledger without seeing counselling notes or immigration status, and how consent is recorded and expired. If the answer is separate logins with different roles, press further.
Offline intake. Early intake happens in shelters, parking lots and neighbourhoods without power. Ask any supplier to demonstrate intake with the network disconnected before you sign, because retrofitting offline behaviour into a connected application is close to a rewrite.
Records outliving the organisation. Long term recovery groups formally dissolve while case records and retention obligations continue. Decide who holds the data at wind up before you start.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, a first release runs $70,000 to $140,000 over 10 to 16 weeks, covering the household record, verified loss by damage component, the assistance ledger with categorised line items, the duplication of benefits engine and case management with document capture. A full platform runs $180,000 to $400,000 over 6 to 12 months, adding the committee workflow with conditional awards, partner scoped access, contractor disbursement with completion evidence, volunteer work order integration and funder reporting.
A long term recovery group working roughly 900 households, moving about $6M, with five partner organisations and two funding sources carrying different duplication rules, priced its first release at $137,000: discovery with duplication rule mapping $11,000, household and damage component model $20,000, assistance ledger $17,000, duplication engine $23,000, case management with offline intake $22,000, committee workflow with readiness gate and conditional award watchers $19,000, partner scoped access for two partners $16,000, and testing with training $9,000. A single agency working 200 households against one funding source with no partner sharing lands nearer $75,000.
Beyond that: $15,000 to $30,000 for each additional funding source with distinct rules, mostly discovery and category mapping rather than engineering; $16,000 to $30,000 for the first two partner organisations, with subsequent partners being configuration; and $12,000 to $22,000 for offline intake.
Annually, support and enhancement runs 12 to 18 percent of build cost. Document storage settles at $150 to $500 a month for a group of that size, covering damage photographs, contractor estimates, award letters and identity documents against multi year retention. Then two lines groups routinely miss. Cases outlive the grant that funded the software, so hosting and support must be budgeted past the end of your case management grant, which is a board conversation to have before you start rather than in year three. And the wind up export, delivering a complete readable archive to whichever entity inherits the retention obligation, is a defined piece of work that is far cheaper to plan than to improvise.
What does the hybrid look like, and when is it the honest answer?
This is the recommendation for most recovery groups that already licence a case platform. Keep the incumbent for general programme case management. Build only the recovery specific layer beside it.
That layer is the assistance ledger, the duplication engine and a minimal household record with verified loss by component, at roughly $50,000 to $75,000. Case notes, documents and the general workflow stay where they are. What you get is the one thing your committee needs on a Tuesday night and an auditor needs two years later: a figure with its working attached, showing exactly which awards were offset against which losses.
Sequence the rest deliberately:
- Committee workflow second, roughly $19,000. A readiness gate so cases only reach the agenda when required evidence is complete, plus conditional award watchers. Agenda automation is convenience. The arithmetic was the urgent part.
- Partner access third, $16,000 to $30,000. Limit phase one to two partners. The consent model you build for two extends to the fifth cheaply, and designing for five before any of them have agreed to participate is speculative work.
- Contractor disbursement and funder reporting last. Paying for work that was never finished is the second most common finding after duplication, so it matters, but it matters after the money is being allocated correctly.
One more reduction that is genuinely free. Agree your verification standard before kickoff: which source of damage evidence wins when a federal inspection summary, a contractor estimate and a volunteer photo set disagree. That is a policy decision no developer can make for you, and unresolved it becomes billable discovery.
Which should you choose, by operator size and stage?
Find your row and act on it.
- Single agency, under 200 households, own funds. Buy CaseWorthy or Apricot by Bonterra, keep a disciplined ledger with one named owner, join the Coordinated Assistance Network, and spend the difference on case managers.
- Between 200 and 900 households, one funding source, no committee. Still buy, but write your duplication rules and verification standard down now, while nothing is happening. That documentation is free and it takes a chunk out of any future build.
- Over $3M in unmet needs funding, or federal disaster recovery money. This is the decision point. Keep your case platform and build the ledger and duplication engine, roughly $50,000 to $75,000, before considering anything larger.
- A committee drawing from several organisations. Build the full first release including the committee workflow and partner access for your two most active partners, roughly $137,000 at the shape described above.
- Currently in an active response with no system. Build the narrow opening move: structured intake with offline capture, the household and damage component model and the assistance ledger, $35,000 to $60,000 in five to seven weeks. That gets you taking intake in structured form on day four instead of collecting a thousand paper forms you will spend six months transcribing.
Two conditions apply. Settle ownership before kickoff, meaning the repository, the cloud accounts, a usable data export and the right to hire anyone else, because the entity that built the system may not exist in five years and the cases will. And insist that loss is captured by component with a source and a date rather than as one total.
When you are ready to turn this into a specification, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Acquiring a new customer is five to 25 times more expensive than retaining an existing one, and research by Frederick Reichheld of Bain & Company found that increasing customer retention rates by 5% increases profits by 25% to 95% - underscoring the ROI of support that keeps customers. Source: Harvard Business Review / Bain & Company (2014) →
- McKinsey found personalization most often drives 10-15% revenue lift, and companies that grow faster drive roughly 40% more of their revenue from personalization than slower-growing peers. Source: McKinsey & Company (2021) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- A later Nucleus Research review of analytics software ROI case studies found customers received $9.01 in benefits for every dollar spent on analytics technology, showing returns vary with deployment factors but remain strongly positive. Source: Nucleus Research (2019) →
Frequently asked questions
Can we keep CaseWorthy or Apricot and build only the duplication layer?
Yes, and for most recovery groups that already licence one of them it is the right first move. Case notes, documents and general workflow stay where they are, and you build the assistance ledger, the duplication engine and a minimal household record with verified loss by component beside them.
That is roughly $50,000 to $75,000 and it replaces the award workbook sitting next to your case system, which is what your committee actually runs on today. The trade is that the existing renewal continues, and that should be stated openly in the business case.
What does it cost to move our existing case records into a new system?
The migration itself is usually modest. The expensive part is that most historic records lack the structure the new calculation needs: loss captured by component with a source, and assistance recorded as categorised line items with statuses.
Plan to migrate identity, contact and document data, then re-derive the ledger for open cases only rather than for everything ever worked. Closed cases can stay readable in the old system. Ask, in writing, how a full export leaves any platform you are considering, because at wind up somebody inherits the retention obligation.
What happens if our case platform's licence cost rises?
It is a real risk in a sector funded on shorter cycles than the cases themselves. The practical response is the hybrid: once the recovery specific layer is yours, the platform is providing general case management you can price against alternatives rather than a bundle nothing else is measured against.
Budget hosting and support past the end of your current case management grant regardless. Major events produce cases open for three to five years across multiple funding cycles, and a board conversation about that is much easier before the build than in year three.
How long does it take, and can it be stood up during a response?
Ten to sixteen weeks for a first release. It can be stood up during a response, and it costs more when you do, because discovery competes with a live operation and every decision needs somebody working sixteen hour days.
If you are already responding, build intake, the damage component model and the assistance ledger first, in five to seven weeks at $35,000 to $60,000, and add the committee workflow around month three when funding decisions start. The best time to build this is when nothing is happening.
Is CaseWorthy or Apricot enough on its own?
For a single agency under roughly 200 households with its own funds and no cross organisation committee, yes, and you should take it. Both are capable configurable platforms and the difference is better spent on case managers.
What neither models natively is verified loss by damage component, categorised assistance with statuses including declined and pending, and the arithmetic between them. That is why recovery groups running these products still maintain a parallel award workbook, and the workbook is what a build replaces.
Why does each additional funding source add cost?
Because each source defines what offsets what differently, and that definition has to be modelled rather than remembered. Approved loans a household declined are treated differently from accepted ones, and community development block grant disaster recovery funds carry their own specific guidance.
Expect $15,000 to $30,000 per additional source with distinct rules, mostly in discovery and category mapping. The rule set needs effective dates, because historic awards must keep the rules that applied when they were made.
How much does partner organisation access add?
$16,000 to $30,000 for the first two partners, covering scoped visibility, consent recorded per organisation and per information category with an expiry, and enforcement at the point the record is read rather than described in a memorandum of understanding.
Subsequent partners are configuration rather than engineering. Design it at the start, because bolting partial visibility onto a system that assumed full access is expensive and usually ends up incomplete. It is also what determines whether other agencies actually participate.
Do we need offline intake, and what does it cost?
Yes, and it typically adds $12,000 to $22,000. Early intake happens in shelters, parking lots and neighbourhoods without power, and a system requiring connectivity in those conditions means paper forms and a six month transcription project afterwards.
Ask any developer to demonstrate the intake application with the network disconnected before you sign. Retrofitting offline behaviour into an application that assumed connectivity is close to a rewrite, so it is not a phase two item.
Who owns the source code when an agency builds my CRM?
You should own it completely, through a written IP assignment that transfers copyright on final payment, with the code sitting in a repository you control from day one. Watch for contracts that only grant a "license to use," which quietly keeps ownership with the agency and locks you in for every future change. Open-source libraries inside the project keep their own licenses, which is normal; your business logic must be exclusively yours.
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.
How long until a custom CRM pays for itself?
For teams replacing per-seat tools, 18 to 30 months is the honest range, driven by eliminated license fees plus the admin hours saved on spreadsheet workarounds. A 20-user team leaving Salesforce Enterprise recovers about $39,600 a year in list-price licenses alone against a typical $40,000 to $60,000 build. Payback arrives faster when the system automates a revenue task like quote generation or follow-up sequences instead of only storing records.
Can we start with a small MVP version of the CRM and add features later?
Yes, starting small is how most successful projects run: launch with contacts, one pipeline, activity logging, and your two most-used integrations, then extend in monthly or quarterly cycles. At Digital Heroes an MVP scope like that typically ships in 10 to 12 weeks for $15,000 to $30,000. The projects that fail usually tried to clone every Salesforce feature on day one instead of the six workflows the team actually uses.
At what team size does building a custom CRM get cheaper than paying for Salesforce?
The crossover usually lands between 15 and 25 users. Salesforce Enterprise lists at $165 per user per month, so a 20-person team pays roughly $39,600 a year indefinitely, while a $45,000 custom build plus $8,000 to $12,000 in annual upkeep breaks even in about 18 months. Below 10 users, Salesforce or Zoho is almost always the cheaper path and a good agency will tell you that.
How does a custom CRM handle GDPR, HIPAA, or other compliance requirements?
Compliance has to be designed in from the schema up: field-level encryption, role-based access, audit logs, retention rules, and for GDPR a working way to export and delete a person's data on request. Custom can actually be the stronger option because you decide exactly where data lives, including keeping it in-country or on your own servers, which off-the-shelf tools do not always allow on lower tiers. If HIPAA applies, confirm the agency will sign a business associate agreement and has shipped healthcare systems before, because that experience is not implied.
How do I vet a CRM development agency before signing a contract?
Ask to see two live CRMs they built for businesses your size and talk to those clients about what happened after launch, not during the sales process. Then pin down three specifics: who owns the code (you should, fully, on final payment), what a change request costs after go-live, and how they plan data migration. An agency that cannot walk you through a migration plan on the first call will improvise yours.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
Should I hire a freelancer or an agency to build my CRM?
A strong freelancer works for a single-pipeline tool under roughly $15,000, but a CRM your company runs on needs design, backend, and QA skills plus someone available when the original builder moves on. The most expensive projects Digital Heroes inherits are freelancer builds abandoned at 80 percent, where finishing cost more than starting with a team would have. If you do go freelance, require the code to live in your own repository from week one.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
Who can build a custom CRM software system?
Digital Heroes builds custom CRM software 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 CRM software 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 .
