How Much Does Refugee Resettlement Case Management Software Cost in 2026?
A custom refugee resettlement case management system runs $60,000 to $380,000, and the single decision that moves the number most is how many separately funded programmes you administer.
On this page
A custom refugee resettlement case management system runs $60,000 to $380,000, and the single decision that moves the number most is how many separately funded programmes you administer. One programme, reception and placement only, sits at the bottom of the range because there is one eligibility rule set, one service catalogue and one reporting format. Add Matching Grant, refugee support services, preferred communities and a state funded employment contract and you have five eligibility engines, five service definitions and five reporting layouts, which is what pushes an affiliate from a $90,000 first release into a $300,000 platform.
The bands a resettlement case management build falls into
There are three honest price points in this category and the gap between them is scope, not quality.
A first release covering case and family unit records anchored to arrival date, service milestones derived from that date with evidence requirements attached, per capita expenditure documentation with receipt capture, and export in your national resettlement agency's required format runs $60,000 to $130,000 and ships in 12 to 16 weeks in our delivery experience. That release retires the shadow spreadsheet and it is enough to change how a monitoring visit goes.
A full platform adds employment placement and job retention tracking, interpreter and language access management, secondary migration and affiliate transfers, in kind goods inventory, volunteer coordination and multi programme enrolment. That runs $150,000 to $380,000 phased over 6 to 12 months.
Below both of those sits a fourth option nobody quotes because there is no invoice attached to it. If you resettle under about 100 arrivals a year with one caseworker, a structured shared drive plus a calendar with arrival anchored deadlines costs you a fortnight of someone's attention and nothing else. That is genuinely the right answer at that size, and we say so on first calls more often than affiliates expect.
What drives a resettlement build up
Programme count is the dominant driver and it compounds rather than adds. Each funded programme carries its own eligibility test, its own service definitions, its own allowable expenditure categories and its own reporting layout. Two programmes is not twice one programme, because a participant enrolled in both needs services attributed correctly to each funding source and the reconciliation logic between them is new work.
Integration with your national agency's systems is the second driver, and it is unpredictable in a way that other integrations are not, because what you can connect to depends entirely on what they expose. Budget for the possibility that the answer is a formatted file and a submission log rather than an interface.
Multi site operations under different state refugee coordinators add a jurisdictional dimension to reporting that behaves like additional programmes. Document heavy workflows are the quiet one: scanning, indexing and retaining immigration and identity documents is a security design with encryption, role based access, an access log and a retention schedule, not a file upload field, and treating it as the latter is how affiliates end up rebuilding in year two.
The last driver is data migration. Five years of case history spread across a national agency database, three spreadsheets and a folder of scanned receipts has to be parsed, reconciled and loaded, and the reconciliation is the expensive half.
What keeps the number down
Scope the first release to the arrival to core services path and nothing else. That path is where the compliance risk concentrates, it is what a monitoring visit examines, and it is the part your staff already know cold, which makes requirements gathering fast.
Leave employment tracking, volunteer coordination and in kind inventory for phase two. They matter, but they are not what produces a finding.
Accept your national agency's file format as it is rather than designing a flexible export engine that can produce any layout. You need one layout to work correctly. A configurable export builder is three weeks of engineering for a requirement you do not have.
Take opening balances rather than reconstructing history. Load open cases with their current milestone status and start the per capita ledger from a stated opening position agreed with your finance team. Reconstructing closed cases from receipts is archaeology and it belongs in a separate decision.
A worked example that adds up
An affiliate resettling roughly 600 arrivals a year across reception and placement plus Matching Grant, three caseworkers and one programme manager, wants the first release. Here is the shape of the quote.
- Discovery, cooperative agreement review and data model, three weeks: $12,000
- Case and family unit records with dated membership and split handling: $18,000
- Arrival anchored milestone engine with evidence requirements and recomputation: $22,000
- Per capita expenditure ledger with mobile receipt capture and signature: $26,000
- National agency export in required layout plus submission log: $16,000
- Document store with encryption, role based access and access logging: $12,000
- Caseload dashboard sorted by days remaining, plus supervisor views: $10,000
- Migration of open cases, user acceptance testing and staff training: $12,000
That totals $128,000, at the top of the first release band, delivered across 15 weeks. The two lines that a generic case management product cannot supply, the milestone engine and the per capita ledger, are $48,000 of that $128,000. Everything else is ordinary case management you could arguably buy, which is exactly the calculation you should run before committing.
How the spend phases
Roughly 10 percent of the first release budget goes on discovery before a line of code is written, and that portion is where resettlement projects are won or lost, because turning cooperative agreement language into executable milestone rules requires your programme manager rather than a business analyst.
The next 60 percent is build, invoiced against fortnightly demonstrations rather than against a fixed schedule, so you see the milestone engine working on real arrival dates in week six rather than in week fourteen.
The remaining 30 percent covers migration, parallel running and training. Insist on parallel running for at least one full arrival cycle, meaning the old spreadsheet and the new system both maintained, because that is when you discover the case your process handles informally and the software refuses.
Phase two, if you commission it, should be scoped after six months of live data. Affiliates consistently reprioritise once they can see which parts of the operation are actually slow.
The ongoing costs nobody quotes
Infrastructure runs $600 to $2,500 a month depending on document volume, and document volume is the variable that surprises people, because scanned immigration records and receipt photographs at 600 arrivals a year accumulate faster than case notes ever will. Storage is cheap. The access controls and audit logging around it are what you are actually paying for.
Budget a support and maintenance retainer of 15 to 20 percent of the build cost annually, in our delivery experience. That covers security patching, dependency upgrades, and the changes your national agency's reporting formats will force on you, which happen more often than anyone would like.
Then there are the costs internal to your organisation. Someone has to own the system, meaning approve configuration changes, maintain milestone rules when guidance is revised, and onboard new caseworkers. At affiliate scale that is typically 10 to 15 percent of a programme manager's week, and if nobody is assigned to it the system drifts from your actual process inside a year.
Comparing a build against your current renewal
Do this arithmetic before you commit either way. Take your current renewal quote for Eccovia ClientTrack, CaseWorthy or Apricot by Bonterra, whichever you run, and add the line items that are not in the subscription: configuration changes charged per request, the annual cost of the staff time spent maintaining the parallel spreadsheet, and any implementation fee amortised across the term. Multiply by three years.
Then set that against a $128,000 build plus three years of retainer and infrastructure, roughly $200,000 to $230,000 all in. For a large affiliate running several programmes the two numbers are often closer than the board expects, and the deciding factor is not price. It is whether the product can express your deadline model.
The honest test is this. Ask your current vendor to produce a caseload view sorted by days remaining against arrival date, across your whole caseload, with milestones that recompute when a flight changes. If they can, keep paying them. If the answer involves an export to Excel, you already know what the spreadsheet is for.
When buying beats building
Buy if you resettle fewer than roughly 100 arrivals a year. At that volume a disciplined shared drive, a calendar with deadlines derived from arrival dates, and an organised receipts process genuinely works, and $128,000 buys rent assistance or another caseworker, both of which help families more than software will.
Buy if resettlement is one programme inside a broad human services portfolio. Eccovia ClientTrack is widely deployed across homelessness and social services and it is a competent central record. In that situation the sensible spend is a small resettlement specific layer around it, typically $35,000 to $70,000, rather than replacing a system that serves four other programmes correctly.
Buy if you have no internal owner. A custom system without someone accountable for its configuration becomes a worse version of the product you replaced, and that outcome is entirely predictable at the point of purchase.
Build when two or more of these are true: you resettle more than about 250 arrivals a year, your staff enter the same case into two systems, your per capita documentation is assembled retroactively before monitoring, you operate more than one funded programme, or a monitoring visit has already produced a finding on documentation or timeliness. That last one is the most common trigger by a wide margin, and it is also the point at which the budget conversation stops being difficult.
If you would rather someone argued with your brief than agreed with it, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. 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.
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
Frequently asked questions
How much does refugee resettlement case management software cost in total?
A first release covering arrival anchored case records, derived service milestones with evidence requirements, per capita expenditure documentation and national agency exports runs $60,000 to $130,000 and ships in 12 to 16 weeks, based on Digital Heroes delivery experience. A full platform adding employment tracking, interpreter management, secondary migration, in kind inventory and multi programme enrolment runs $150,000 to $380,000 over 6 to 12 months.
The number of separately funded programmes you administer moves the figure more than arrival volume does, because each programme brings its own eligibility rules, service definitions and reporting layout.
What does it cost to run each year after launch?
Infrastructure runs $600 to $2,500 a month, driven mainly by document and receipt image volume rather than by case count, and most of that cost is the access control and audit logging around the storage rather than the storage itself. Add a support and maintenance retainer of 15 to 20 percent of build cost annually in our delivery experience, which covers security patching, dependency upgrades and the reporting format changes your national agency will issue.
Budget internal time too. Owning milestone rules and configuration is typically 10 to 15 percent of a programme manager's week.
How long does it take to build?
Twelve to 16 weeks for a first release. The critical path is rarely engineering. It is pinning down your national agency's current reporting formats and any available interface, because that specification is revised regularly and is often held by different people than the ones you speak to daily.
Start that conversation before development begins. Affiliates that do are consistently the ones that ship on time, and the ones that leave it until week ten consistently lose a month.
Is building cheaper than renewing Eccovia ClientTrack or CaseWorthy?
Run the arithmetic rather than assuming. Take your renewal quote, add configuration change fees charged per request, add the staff hours spent maintaining the parallel spreadsheet, amortise any implementation fee, and multiply by three years. Set that against roughly $200,000 to $230,000 for a $128,000 build plus three years of retainer and hosting.
Price is usually not the deciding factor. Ask your vendor to show a caseload view sorted by days remaining against arrival date, with milestones that recompute when a flight changes. If that requires an export to Excel, you have your answer.
What is the cheapest useful version we could commission?
Roughly $60,000 to $75,000 buys the arrival anchored milestone engine, a case model with dated family membership, and the per capita expenditure ledger with mobile receipt capture, on top of a basic case record. That is the compliance core and it is what a monitoring visit examines.
Leave employment tracking, volunteer coordination, in kind inventory and the national agency integration for phase two, and accept a manually assembled export in the interim. It is not elegant, and it removes the two failure modes that actually produce findings.
Why does adding a second funded programme cost so much?
Because programmes compound rather than add. Each carries its own eligibility test, service catalogue, allowable expenditure categories and reporting layout, and a participant enrolled in two needs services attributed correctly to each funding source with reconciliation logic between them that did not exist before.
In practice a second programme adds 30 to 50 percent to the first release scope in our experience, which is why an affiliate running reception and placement plus Matching Grant plus a state employment contract lands near the top of the band rather than the middle.
How much of the budget goes on data migration?
Typically 8 to 12 percent of a first release, and it is almost entirely reconciliation rather than loading. Case history spread across a national agency database, several spreadsheets and a receipts folder has to be matched participant by participant before anything can be imported.
You can cut this substantially by taking opening balances instead of reconstructing history. Load open cases with their current milestone status, start the per capita ledger from an opening position agreed with your finance team, and leave closed case archaeology as a separate decision with its own budget.
Do we need to pay for offline or mobile capability?
Mobile receipt capture is worth paying for and it sits inside the $26,000 per capita ledger line rather than being a separate cost, because a receipt photographed in a furniture store car park and attached immediately is the difference between an audit ready ledger and a shoebox. Full offline capability is generally not needed in resettlement, unlike field service work, since caseworkers are usually in homes, offices or schools with signal.
If your service area includes genuinely rural placements, raise it during scoping. Retrofitting offline sync later is expensive.
When is the money better spent on something other than software?
Under about 100 arrivals a year with one caseworker, without hesitation. A structured shared drive, a calendar with deadlines derived from arrival dates and a disciplined receipts process works, and $128,000 buys rent assistance or another caseworker.
Also skip the build if resettlement is one programme inside a broad human services portfolio already running on ClientTrack or CaseWorthy for four other programmes. A resettlement specific layer around what you have, typically $35,000 to $70,000, beats replacing a system that is serving the rest of your organisation correctly.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
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.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Who can build a custom software system?
Digital Heroes builds custom 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 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 .
