Child Welfare Case Management Software: Build a Module or Buy the Product
The line is whether you are a state or a provider.
On this page
The line is whether you are a state or a provider. A private child placing agency or a small county contracting entity should buy: Casebook covers case management at that scale, Binti covers foster and adoptive family licensing well, and a hosted product will be running before a build reaches a first release. A state agency should not replace its statewide system either, because a Comprehensive Child Welfare Information System, known as CCWIS, is a multi year programme with federal cost allocation attached rather than a project. What states should build is one module where a specific failure is measurable, at $150,000 to $400,000 over 4 to 8 months.
When is off the shelf genuinely the right call here?
For most organisations that are not states. Casebook covers case management for a private provider agency or a small county contracting entity, and it does it now rather than in eight months. Binti handles foster and adoptive family licensing genuinely well, including background check status by household member, training completion, home study and renewal. Northwoods sits alongside either as a document and content layer without pretending to be the case record.
Buy, and commission nothing, if this describes you. A private child placing agency with a few dozen staff. A contracting entity serving one county. Licensing work that fits what a hosted product already models. And no contract clause imposing documentation or reporting requirements the product cannot meet. At that scale a custom build is not defensible against software that already does most of it, and the difference is months during which children still need placements.
Buy also, at any scale, when the thing failing is caseload size rather than software. A worker carrying twice a manageable caseload documents late because there is no time, not because the form is slow. Software that returns an hour a week is worth buying. Software sold as a substitute for staffing is not, and it will be judged in eighteen months against an outcome it was never able to move.
There is a third case worth naming for states. If you are part way through a funded comprehensive system transfer with a signed contract, commissioning a parallel module fragments the data quality plan you have already committed to and starts an argument over which system owns the record. Finish the transfer, then build against what it does badly, with evidence rather than a theory.
When does a custom build actually pay off?
When a specific part of the workflow is failing in a way you can measure, and the packaged options do not reach it.
- Contact documentation is late and the standard is federal. The monthly caseworker visit measure is a condition of funding and carries a requirement about where the visit occurs. If workers write notes in a phone and transcribe on Thursday what happened on Tuesday, that is a tooling problem the desk based systems created.
- Placement decisions run on stale capacity. A removal at eleven at night needs licensed capacity, current occupancy including a placement made an hour ago, licence restrictions, tribal placement preferences, distance to the school of origin and kinship options already on the case. A bed list accurate as of last Friday is not that.
- Court reports consume worker days. The factual sections already exist in the record and are being retyped, which is how reports end up containing contradictions that opposing counsel finds.
- A federal data element cannot be produced cleanly. If a submission errors out or a review sample does not support what the data said, the cause is usually that the field is not part of doing the work.
- You are going modular without a shared record. Build the person, case, placement and provider spine yourself, because no vendor will build it for your benefit.
How do they compare on the things that matter in this industry?
Five comparisons, and only one is about screens.
Where documentation happens. Legacy systems assume a desk and a connection and present thirty fields, half of which do not apply. An offline first application captures the visit at the kitchen table, records location and participants, prompts only the fields relevant to that case type, and syncs when the device finds a network. The capture timestamp is evidence, which is why proof of when capture actually occurred has to survive the sync rather than be reconstructed from it.
How identity is resolved. A child appears three times under two surnames and a misspelling. This is the foundational problem in the domain, and a developer who has not thought about it will build you a fourth duplicate. Ask the question before anyone quotes.
Whether placement is a search or a list. Binti is strong on the licensing side. The gap that stays open is the join between licence status, live capacity and the specific constraints on this case tonight, and that join is state specific because your licence types and placement preference law are state specific.
Whether federal elements are byproducts. Removal reasons, permanency goal changes, tribal inquiry and discharge reasons should be captured at the moment of the decision in the worker's own language and mapped underneath, with validation running continuously rather than at submission.
Whether a module owns its data or writes back. This is the single largest cost variable in the category and it is not a feature question.
What does total cost of ownership look like at your scale?
One band per module. A well scoped module runs $150,000 to $400,000 over 4 to 8 months in Digital Heroes delivery experience, covering something like offline mobile contact documentation with supervisory oversight, placement matching, provider licensing with renewals and live capacity, court report generation, or intake and screening.
A state agency with roughly 1,400 caseworkers, flagged on contact documentation timeliness, keeping the statewide system and posting contacts back into it, came to $319,000 across seven months. Hold on to one number from that build. The write back adapter at $58,000 plus the sync engine at $44,000 came to $102,000, roughly a third of the project, and neither produces a screen anyone will demonstrate to a legislator. That is the honest shape of this category: the visible application is the cheap part.
Annual cost is $30,000 to $70,000 for a module of that size, most of it absorbed keeping the write back working as the statewide system changes underneath it. Then five lines that belong in the programme budget rather than the software budget. Both mobile operating systems ship major versions annually and either can break an offline sync path, so a regression pass per platform per year is a fixed cost rather than an incident. Instrument and policy revisions change the module and prior determinations must remain explainable under the old rules. Judicial districts revise required formats on their own timetable. Federal review cycles concentrate real engineering into a short window. And training is continuous rather than annual, because turnover in this field makes it so.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In child welfare this is not a fallback, it is the pragmatic path most states are now taking.
Leave the statewide system of record in place. Keep Northwoods for documents if you have it, keep Binti for licensing, keep Casebook where a provider network uses it. Then replace only the part workers touch daily and avoid every day, which is almost always mobile contact documentation. The module reads what it needs and posts contacts back, and the rest of the system carries on being conservative, which is what it is for.
There is a cheaper hybrid worth putting on the table before anyone commits. A module that owns its own data, with a nightly export rather than a live write back, is dramatically less expensive than the same module bolted into a legacy core. Provider licensing is the obvious candidate, because it can legitimately be the system of record for licensing. If your business case survives without a live write path, take it, because you have just removed a third of the cost and most of the schedule risk.
The hybrid stops being honest in one situation. If the module needs to write into a legacy core the incumbent will not open, price that reality at the start. Without a write path you are buying a read only application that duplicates data entry rather than removing it, which is the opposite of the problem you set out to solve, and no amount of design will disguise it from the workers using it.
Which should you choose, by operator size and stage?
- Private child placing agency, a few dozen staff. Buy Casebook, and Binti if you licence homes. Commission nothing. The build case only appears if a state contract imposes documentation or reporting the product cannot meet.
- County contracting entity serving one county. Buy. Your problem is almost never a data model, and a hosted product plus disciplined practice will outperform a half owned custom system.
- State mid way through a funded system transfer. Buy, and finish it. A parallel module fragments the data quality plan and creates an ownership argument over the same records.
- State with a measurable failure in one workflow. Build that module, and only that module. Contact documentation is usually the highest value first component because it is the failure that becomes a federal finding.
- State going modular deliberately. Build the shared person, case, placement and provider record first, then buy or build components against it. Modules keeping their own copy of the child record produce four systems that disagree about who a child is, which is worse than one monolith.
- Any state contemplating a full statewide replacement as a custom build. Do not. Those programmes run multi year with federal review and carry political risk that outlives the administration that started them.
One discipline regardless of stage. Pilot in two counties with different practice cultures and different connectivity, not one. A single county pilot proves the module works somewhere. Two prove it works in conditions the rest of the state will recognise, and it is cheap insurance against a rollout that stalls in month two.
If you want that decision made properly rather than quickly, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
Frequently asked questions
What does it cost to switch systems or migrate off a legacy core?
In most cases you should not switch. The pragmatic pattern leaves the statewide system in place and builds the module workers touch daily, so there is no migration to fund and the certified reporting stays where it already works.
Where switching cost genuinely applies is a provider agency moving between hosted products. Ask what a full export contains, whether contact history leaves with its capture timestamps intact, and whether documents come out in a form another system could read. Child welfare records carry retention obligations measured in decades, so export fidelity matters far beyond the contract term.
What happens if our vendor changes its pricing or per user terms?
Model it on caseworker headcount growth and turnover rather than today's staffing, because per user components rise exactly when you are hiring against a caseload problem.
The defence is portability rather than a different vendor. Secure written confirmation that you can export case, person, placement and provider data, plus documents, in a documented structured form on demand. An agency that already runs a shared record spine is in a much stronger position at renewal, which is a benefit of that spine that rarely reaches the business case.
How long does a child welfare module take to build?
Four to eight months from kickoff to production for a single module. Add time before that for the federal planning document review, since costs claimed for federal financial participation flow through an approval process running on its own schedule.
Agencies that treat the project as starting at vendor selection routinely lose a quarter to that step. Build the review window into the timeline, and start the cost allocation documentation early enough that it survives a later audit rather than being assembled afterwards.
Is Casebook or Binti enough, and where exactly does it stop?
For a private provider agency, Casebook covers case management at that scale and will be running long before a build reaches a first release. Binti handles foster and adoptive family licensing well and is worth keeping even if you build elsewhere.
Where they stop is the state specific join. Licence status, live capacity and the constraints on a case tonight, including tribal placement preference order and school of origin, depend on your licence types and your state law. Judge them on that ground rather than on general capability.
Do we need an offline mobile application or is a mobile web view enough?
Buy offline only where the fieldwork genuinely demands it. Home visits in rural areas happen without signal and the capture timestamp is evidence, so contact documentation usually does need it.
A provider licensing or court report module used at a desk does not, and skipping the sync engine removes a substantial cost. In the worked example the sync engine alone was $44,000. Be honest about where the work actually happens before deciding, because paying for offline capability nobody uses is the most avoidable overspend in this category.
Why does writing back into the legacy system cost so much?
Because the module has to post records into a system it does not control, reconcile what it posted, and behave correctly when that system rejects a record at two in the morning. In the worked example the write back adapter and sync engine together were roughly a third of the project.
It produces no screen anyone will demonstrate, which is why it is the line most often missing from an optimistic quote. Ask for it to be priced separately so that an overrun there is visible rather than absorbed into the application budget.
Can we start with something smaller than a full module?
Yes. A module that owns its own data with a nightly export, rather than a live write back, is dramatically cheaper and carries far less schedule risk. Provider licensing is the natural candidate because it can legitimately be the system of record for licensing.
Deferring assessment scoring is another lever. Capture the instrument as structured data first and add automated scoring once the field trusts the capture, since scoring rules, thresholds and override documentation have to be exact and versioned.
Who owns the code and the data if we contract a custom module?
The agency should own the repository, the database and the infrastructure accounts, with the unrestricted right to move the work to another firm. At Digital Heroes the client owns the code from the first commit.
Child welfare records carry retention obligations measured in decades and confidentiality rules stricter than ordinary personal data, which makes vendor held infrastructure a governance problem rather than a convenience. Settle it before kickoff, alongside a documented handoff, because leadership and vendors both change more often than the records do.
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.
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.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
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 is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
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.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
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
More from James.
Senior Copywriter · New-york · 14 posts on the site
Published · Last updated .
