Refugee Resettlement Case Management Software: Custom Build vs ClientTrack and CaseWorthy
Buy if you resettle fewer than roughly 100 arrivals a year with one or two caseworkers. A structured shared drive, a calendar carrying the derived deadlines and a receipts folder honestly covers it.
On this page
Buy if you resettle fewer than roughly 100 arrivals a year with one or two caseworkers. A structured shared drive, a calendar carrying the derived deadlines and a receipts folder honestly covers it. Build once you pass roughly 250 arrivals, run several funded programmes with different eligibility, or find staff entering the same case into two systems every week.
What ClientTrack, CaseWorthy and Apricot actually do well
A family of seven landed at 11:40 on a Thursday night, the lease that fell through on Tuesday was replaced on Wednesday afternoon, and your resettlement director is tracking all of it on a whiteboard. Somebody has asked whether better software exists. Be fair about the products first, because they are competent and for many affiliates they are the right choice.
Eccovia ClientTrack is widely deployed across homelessness and social services and does what it was designed to do. CaseWorthy is configurable and covers a broad human services portfolio. Apricot by Bonterra stands up quickly and takes a small team off spreadsheets in weeks. All three handle assessments, service records, goal plans and standard grant reporting properly, and if resettlement is one programme inside a larger human services organisation, one of them is probably already your central system and should stay.
Buy if you resettle fewer than roughly 100 arrivals a year with one or two caseworkers. A well structured shared drive, a calendar carrying the derived deadlines, and a receipts folder genuinely works at that size. Custom software would be an expensive way to formalise what two people already do well, and the money belongs in rent assistance. We tell affiliates this regularly.
Where they stop: the clock starts on a date you did not choose
Generic case management models a client who presents with a need, gets assessed, receives services and closes when goals are met. Resettlement does not work that way at all.
Your client arrives on a plane on a date somebody else set, and the reception and placement period defined in your national agency's cooperative agreement starts a clock that does not care about your caseload, your staffing or whether the apartment was ready. Confirm the current requirements against that agreement rather than against any article, because the detail is revised. The operational point holds regardless of the version: every deadline derives from the arrival date, and the consequences of missing one land on the affiliate agreement rather than on an individual case plan.
Packaged systems compute due dates from enrolment, meaning the day your staff created the record. If the assurance came late, if a name was misspelled and the record created twice, or if the flight moved by a week, your due dates are wrong and displayed with total confidence. That is why so many affiliates run a second tracker nobody admits to.
The second gap is the shape of a case. A case arrives as seven people. Three months later two adults join a cousin in another state, which is secondary migration, and five remain. Or the anchor relative lives in a different city and services split across two affiliates from day one. A case needs dated membership so a person can leave on a specific date and the funded allocation reconciles correctly, and transfers need to be recorded transactions with a receiving party rather than manual re-entry somewhere else.
The third is per capita money. Rent, a security deposit, furniture, kitchen equipment, seasonal clothing and transport are documented per person, item by item, receipt by receipt. Right now that is a shoebox, a spreadsheet and a scramble two weeks before a monitoring visit.
The arithmetic: per user licences against the cost to build
Reduce your quotes to cost per staff user per year, then add configuration, because in this category the configuration bill and its annual repeat usually exceed the licence.
Suppose licences land at $140 per user per month across 18 staff. That is roughly $30,000 a year, plus a configuration change each time a funded programme revises a service definition. On its own that number never justifies a build.
What justifies it is arrivals crossed with funded programmes. Below roughly 100 arrivals a year on a single programme, buy. Past roughly 250 arrivals a year, or past three funded programmes with different eligibility and reporting, a build wins, because each programme is configuration work scheduled against a vendor roadmap rather than against your monitoring visit.
Language access belongs in the same calculation and rarely appears in one. Services must be delivered in a language the household understands, which means interpreters are booked, paid and sometimes unavailable on the day, and it means the caseworker who speaks that language carries a caseload nobody else can absorb. Price the interpreter spend and the uneven caseload together, because both are operational constraints rather than notes in a file, and neither shows up in a licence comparison.
Then measure the double entry. Count the placements your caseworkers enter into your national agency's database and then again into a local tracker, and the summaries emailed on top. Every transcription is a chance for divergence, and by quarter end the numbers disagree. Multiply the minutes by your arrival volume and you will usually find most of a full time role doing keyboard work instead of sitting with families.
What a custom build actually costs
From Digital Heroes delivery experience, a first release covering case and family unit records anchored to arrival date, derived milestones with evidence requirements, per capita expenditure documentation with receipt capture, and export in your national agency's required format runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding 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 runs $150,000 to $380,000 phased over 6 to 12 months.
Data migration runs 10 to 25 percent of build cost. Closed cases load cheaply. Open cases need a second person to verify every arrival date, because one mis-anchored date is a missed deadline rather than a data error, and every derived milestone inherits it.
Year two runs 15 to 20 percent of build cost annually, and here it is unusually funder driven. Required formats change, new programmes arrive with new eligibility rules, and each change is real work rather than a settings screen.
What pushes the number up: the count of distinct funded programmes, since each carries its own eligibility, service definitions and reporting. Integration with your national agency's systems, which depends entirely on what they expose. Multi site operations under different state coordinators. And document heavy workflows, because scanning, indexing and retaining identity and immigration records is a security obligation rather than a file upload. What keeps it down is building the arrival to core services path first and leaving employment, extended services and volunteers to phase two.
The four situations where building wins
Regulatory fit comes first. Your cooperative agreement sets service obligations counted from arrival, your state refugee coordinator wants reporting on their cadence, and programmes funded through the Office of Refugee Resettlement carry their own definitions. A monitoring finding on documentation or timeliness is not a report you regenerate. It is an affiliate agreement question, which is a different order of consequence.
Scale economics is the arrivals and programme count above.
Third is the workflow that is genuinely your competitive advantage, and here it is two features rather than a platform: the arrival anchored deadline engine and the per capita ledger. If a vendor cannot show you a caseload view sorted by days remaining against arrival date, they have not built for resettlement whatever the brochure says. Everything else in this category is ordinary case management you can buy.
Fourth is integration sprawl. Your national agency's database, a state reporting requirement, a benefits process, interpreter scheduling and a landlord or employer confirmation is five relationships around one household, and none of them run on your system. Coordination across organisations that do not report to each other is exactly what generic case management does not do.
How to decide in a week: rebuild one family's file
Pick one case that arrived four months ago. Give your team until Friday to produce the complete file: arrival date, every milestone with its evidence attached, every per capita expenditure line with a receipt and an allocation to named individuals, the language of service delivery and the version of each material issued.
Time it and count the gaps. Then ask a second question that takes one minute: list everyone arriving in the next thirty days with an unresolved item. If your system cannot answer that, you have found the reason the whiteboard exists, and no amount of configuration will replace it.
When the exercise says build, run a paid discovery phase first. Ours produces a signed product requirements document covering the case and person model with dated membership, derived milestones and evidence rules, the per capita ledger, submission formats and acceptance criteria, and you keep that document whether you build with us or take it to another firm. Digital Heroes holds India LLP, United States LLC and United Kingdom LTD entities so intellectual property assigns under your own law, and you meet the named team before signing rather than in month two. More than fifty specialists, over 2,000 projects delivered, and our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing.
We are the wrong firm for you if you want a developer to interpret your cooperative agreement or decide what a required format contains. We build to requirements you and your national agency confirm, and we will say so rather than guess at a compliance question that is not ours to answer.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- 76% of developers are using or planning to use AI tools in their development process in 2024 (up from 70% in 2023), with current active use rising to 62% from 44%; 81% agree increasing productivity is the biggest benefit of AI tools. Source: Stack Overflow (2024) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
- 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
How much does custom refugee resettlement case management software cost?
A first release covering case and family unit records anchored to arrival date, derived milestones with evidence requirements, per capita expenditure documentation and export in your national agency's format runs $60,000 to $130,000. A full platform adding employment tracking, language access, transfers and multi programme enrolment runs $150,000 to $380,000. The count of funded programmes drives price more than arrival volume.
How long does it take to build resettlement case management software?
Twelve to sixteen weeks for the first release and six to twelve months for a full platform. The schedule risk is usually the submission format, since it belongs to your national agency and changes on their timetable. Design with their current requirements in front of you, confirm them directly, and keep a submission log recording exactly what was sent and when.
Who owns the code and the client records if an agency builds it?
You should own the repository, the cloud accounts and the right to hire another firm, agreed in writing before kickoff. At Digital Heroes the client owns the code from the first commit. Affiliate funding moves with arrival numbers, and an affiliate locked into a vendor during a lean year is in a far worse position than one that owns its system outright.
What happens when an arrival date changes after the record is created?
Every derived milestone has to recompute automatically, and the change needs recording so you can show what the schedule was before and after. If dates do not move with the flight, your staff will keep a shadow spreadsheet forever and the build has failed on its central promise. Ask a vendor to demonstrate this with a live record rather than describe it.
Can custom software make per capita documentation audit ready?
Yes, and it is one of two features that justify a build. Expenditure lines are created against a case with an allocation rule, receipts are photographed at the point of purchase and attached immediately, client signature is captured on the same device at handover of goods, and the remaining balance per case is visible while there is still time to act on it.
What happens if a case splits or a family member moves to another state?
Model the case with dated membership so a person leaves on a specific date and the funded allocation reconciles correctly for those who remain. Secondary migration and affiliate transfers should be recorded transactions with a receiving party and a documented handover, not a manual re-entry elsewhere. Individual level services attach to people while case level services attach to the case.
Do we still have to enter data into our national agency's database?
Usually yes, and the aim is to enter it once. Your system becomes the operational source of record and produces submissions in the exact layouts required rather than a generic export somebody reformats by hand. Where the national agency offers an interface, integrate to it. Where it does not, generate a file matching the specification and keep a dated submission log.
How should interpreter and language access be handled in software?
Language belongs as an attribute on the person, interpreter bookings as a scheduled resource with cost tracked against the correct funding source, and materials issued to a household recorded with their language and version. Caseload balancing should account for language capability, otherwise one bilingual staff member quietly carries a third of the programme until she burns out.
Where does machine translation genuinely help, and where must it not be used?
It can draft routine written communications for a bilingual staff member to review before sending, which saves real time. It has no role in interpreting an explanation of rights, a benefits orientation or anything a client will act on legally. Any developer who suggests otherwise has not understood the exposure, and that answer alone should end the conversation.
We resettle 80 arrivals a year. Should we build custom software?
No. Put the derived deadlines into a shared calendar, keep receipts in a structured folder per case, and give one person responsibility for the arrival to core services checklist. Revisit when you pass roughly 250 arrivals, when a second funded programme arrives with different eligibility, or when a monitoring visit produces a finding on documentation or timeliness.
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.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
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.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
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 .
