Reentry Services Software: Custom Build vs CaseWorthy and Apricot
Buy if you run one programme, serve under about 150 people a year and work with a single facility. Configure CaseWorthy or Apricot and put the difference into case managers.
On this page
Buy if you run one programme, serve under about 150 people a year and work with a single facility. Configure CaseWorthy or Apricot and put the difference into case managers. Build once you operate across several facilities and counties with different rules, hold milestone based outcome contracts, or need data sharing boundaries enforced by software rather than by training.
What CaseWorthy and Apricot actually do well
Your caseworkers came back from the facility last week with paper forms, and somebody spent Thursday typing them in. That is the moment a reentry programme starts pricing software. Be fair about the products first, because for most programmes they are the right answer.
CaseWorthy is a configurable human services case management platform with real reentry deployments, and configuration goes a long way if your programme fits a fairly standard shape. Apricot by Bonterra is easier to stand up, well adopted across nonprofits, and gets a small team off spreadsheets in weeks rather than quarters. Both handle assessments, service records, goal plans and standard grant reporting properly.
Buy if you run one programme, serve under about 150 people a year, work with a single facility and report on standard grant measures. Configure one of them, spend the difference on case managers, and revisit in two years. That is the honest answer for most reentry nonprofits and we give it regularly, including to organisations that arrived asking us to quote a platform. A build at that size formalises work two capable people already do well, and the money buys more good if it goes into rent assistance.
Where they stop: enrollment behind the wall and the release day plan
Three things push a programme past a configured product, and the first is the hardest.
A correctional facility is the most hostile environment a case management system can be asked to work in. Staff often cannot bring a personal device. Network access is restricted or absent, and what the approved laptop can reach is controlled by the department of corrections rather than by you. So the enrollment interview, the assessment, the goal plan and the consent forms all have to be captured offline and reconciled later, without creating duplicate records for someone enrolled twice at two facilities in the same week. Most platforms assume connectivity, so the workaround is paper transcribed afterwards, which is where duplicates and gaps come from and why the release plan often does not exist in the system until after release.
The second is that release day is a checklist with a deadline nobody controls. A bed that night. A state identification card, a birth certificate and a Social Security card, because without those there is no job and no lease. Medicaid suspended rather than terminated, so coverage resumes in days rather than weeks and the medication supply does not run out on day seven. A supervising officer who knows the address, and an address that matches the supervision paperwork. Case oriented systems answer questions about one person. The question a reentry director asks at eight in the morning is which deadlines fall this week across everyone, and that view is a different data model.
The third is consent. A release of information signed inside a facility has a scope and an expiry, and it governs what may be shared with a landlord, an employer or a supervising officer afterwards. Stored as a scanned signature in a documents folder it is evidence. Stored as a structured record with the scope encoded, it becomes a check the system runs before anything is sent.
The arithmetic: per user licences against the cost to build
Reduce your quotes to cost per staff user per year, then add the configuration and the annual configuration changes, because in this category the implementation cost frequently exceeds the licence.
Suppose licences land at $150 per user per month and you have 20 staff who need access. That is $36,000 a year, plus configuration work each time a funder changes a service definition. Against a build costing once plus roughly 15 to 20 percent annually, the licence alone rarely justifies switching.
What does justify it is participants crossed with facilities. Below roughly 150 participants a year at one facility, buy. Past roughly 400 participants a year across three or more facilities and counties, each with its own access rules, identification numbering and data sharing agreement, a build wins, because each of those relationships is configuration work a vendor schedules against their roadmap rather than your monitoring visit.
If you hold a pay for outcomes contract, add one more line. Money arrives on evidence rather than on effort, so the cost of a weak evidence trail is not an audit finding, it is an unpaid invoice. Work out what proportion of your milestone claims last year needed a person to assemble supporting documents by hand, and price that against a system where the evidence requirement is attached to the milestone at the moment it is recorded.
Then there is the hours figure that nobody puts in a business case. Count the staff time spent transcribing paper after every facility visit, and the senior time spent assembling a milestone invoice from exports. In programmes we have worked with, that is most of a full time role, and it is a role doing data entry instead of sitting with people.
What a custom build actually costs
From Digital Heroes delivery experience, a first release covering offline pre release enrollment, the release day plan, housing and employment placement tracking and service documentation mapped to your funder's definitions runs $70,000 to $150,000 and ships in 12 to 18 weeks. A full platform adding supervision partner coordination, benefits application tracking, employer and landlord confirmation flows, milestone based outcome contracts with invoicing and cohort based outcome reporting runs $180,000 to $400,000 over 8 to 14 months.
Data migration runs 10 to 25 percent of build cost. Closed cases load cheaply. Open cases are the expense, because each needs verifying by a second person, and identity matching across records created at different facilities under different numbering is genuinely difficult work that cannot be rushed.
Year two runs 15 to 20 percent of build cost annually, and in this category a large share of it is funder driven. Service definitions and reporting formats change, new grants arrive with new eligibility rules, and each change is real work rather than a settings screen.
What pushes the number up: the count of facilities and jurisdictions. Offline capability, which is engineering rather than a caching option. Whether you provide substance use disorder treatment, since those records carry additional federal confidentiality protections under 42 CFR Part 2 that shape the architecture and should be confirmed with your counsel. Milestone contract billing, which is a financial system rather than a report. And structured exchange with a state system, where the schedule risk belongs to the other agency.
The four situations where building wins
Regulatory fit comes first and it is unusually sharp here. Data sharing with corrections and community supervision is governed by specific agreements stating what may be shared, in which direction and for what purpose. Encoding those boundaries as enforced rules rather than staff training is not something a configured product does well, and the consequence of getting it wrong is a suspended agreement and a programme with no access to the facility. Where 42 CFR Part 2 applies, the architecture changes rather than the settings.
Scale economics is the participant and facility count above. Three facilities in three counties is three sets of rules, and configuration does not scale that way.
Third is the workflow that is genuinely your competitive advantage, and for reentry that is the release day plan itself. A dashboard of everyone releasing in the next thirty days with unresolved items, ordered by days remaining rather than by case, is the single most used screen in these builds and the reason funders renew.
Fourth is integration sprawl. A corrections system, a supervision system, a benefits process, a housing partner and a funder database is five relationships around one person, and none of them report to you. Coordination across organisations that do not answer to each other is exactly what generic case management does not do.
How to decide in a week: shadow one release
Pick one person releasing next week and follow their file end to end. Write down where every fact lives: the arrival address, the identification documents and their status, the benefits position, the housing confirmation, the supervision reporting instruction, the signed consent and its scope.
Count how many of those live only in somebody's head, an email, or a spreadsheet outside the system. Then ask your system to list every person releasing in the next thirty days with an unresolved identification document. If it cannot produce that list in under a minute, you have found the gap, and it is the gap that costs people their first job.
Run a paid discovery phase before committing budget. Ours produces a signed product requirements document covering the case and person model, offline enrollment and conflict handling, consent scope enforcement, milestone definitions 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. Over 2,000 projects, more than fifty specialists, checkable on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing.
We are the wrong firm for you if you need a partner to interpret your funder's cooperative agreement. We will build to requirements your counsel and your funder confirm, and we will say so plainly rather than guessing 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.
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- Sensor Tower's State of Mobile 2026 reports that global users spent 5.3 trillion hours in iOS and Google Play apps in 2025 (+3.8% YoY), roughly 3.6 hours per day per mobile user. (Note: the page does not itself contrast app time vs. mobile-browser time, so the 'overwhelming majority of time in apps vs browsers' framing is not directly supported by this source.). Source: Sensor Tower (2026) →
- 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) →
Frequently asked questions
How much does custom reentry case management software cost?
A first release covering offline pre release enrollment, release day planning, placement tracking and funder aligned service documentation runs $70,000 to $150,000. Adding supervision coordination, benefits tracking, partner confirmation flows, milestone contract invoicing and cohort reporting takes it to $180,000 to $400,000. The number of correctional facilities and jurisdictions drives the price more than participant volume does.
How can software work inside a correctional facility with no connectivity?
By storing the assessment and consent forms locally on a device the facility will actually permit, queueing everything, and synchronising when the device returns to a network. The hard part is conflict handling, because two staff may enrol the same person at different sites in the same week. Ask any developer that specific question before you look at a single screen.
How long does it take to build reentry program software?
Twelve to eighteen weeks for the first release, and eight to fourteen months for a full platform. Schedule risk usually sits outside development. Facility access rules, a data sharing agreement awaiting signature, and a state agency working to its own timetable all move at their own pace, so sequence the build to deliver value before those dependencies land.
Who owns the code and participant data if we commission a build?
You should own the repository, the cloud accounts and the right to hire another firm, settled in writing before kickoff. At Digital Heroes the client owns the code from the first commit. This matters here because your data sharing agreements are with your organisation, and records covered by them have to remain under your control rather than a vendor's.
What extra rules apply if our program provides substance use disorder treatment?
Those records carry additional federal confidentiality protections under 42 CFR Part 2, which are stricter than general health privacy expectations and shape the architecture rather than the settings. Confirm the applicable requirements with your own counsel and hold the developer to them. If a development firm has never encountered Part 2, treat that blank look as disqualifying rather than as something to teach.
How do you measure recidivism when the programme does not hold the data?
Through a periodic matchback against a state criminal justice dataset under an agreement, for a cohort defined by enrollment date. Your software's job is making cohorts precise and reproducible: enrollment date, programme, dosage of service received and exit reason recorded consistently. Definitions vary between rearrest, reconviction and return to custody, and the window is commonly one, two or three years.
What happens if a participant moves to another county or programme?
It should be a recorded transfer with a receiving party and a documented handover, not a manual re-entry into somebody else's system. The person leaves the case on a specific date, the services already delivered stay attributed correctly, and the consent record governs what may be shared with the receiving organisation. Re-entering by hand is how duplicate identities are created.
Can employers and landlords be given access without them logging in?
Yes, and that is the realistic design. Landlords and employers will not adopt your software. Use a single purpose link that confirms continued employment or tenancy for a milestone, with the consent record checked before anything identifying is sent. Supervising officers usually cannot use your system at all, so plan a scheduled exchange where the agreement permits one.
What is the difference between grant reporting and a milestone contract?
Grant reporting counts services delivered against a funder's definitions. A milestone contract pays on evidence of outcomes: enrollment, placement, ninety day job retention, twelve month housing stability. That is a financial workflow with a verification step and an invoice, not a checkbox on a case. Products treat milestones as case attributes, which is why invoices end up assembled from exports.
We serve 120 people a year from one facility. Should we build?
No. Configure a commercial case management platform, write down your release day checklist, and give one person responsibility for tracking identification documents and benefits status across the caseload. Revisit when you add facilities in other counties, when a pay for outcomes contract arrives, or when staff are routinely transcribing paper forms after every facility visit.
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 do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Should we build our internal tool in Retool instead of hiring developers?
Retool is the right choice if someone on your team is comfortable with SQL and JavaScript and the audience is a handful of technical users, because a basic CRUD dashboard comes together in days. Hire developers when non-technical staff will use the tool daily, when the logic goes beyond forms sitting on a database, or when per-seat pricing stings, since Retool's Business tier lists at $50 per standard user per month. A pattern Digital Heroes sees often: companies arrive after a year on Retool with a tool nobody can maintain because the one person who built it has left.
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.
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.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
How do I know when spreadsheets are no longer enough to run my operations?
Replace the spreadsheet once more than three people edit it, versions travel by email, or a single broken formula could cost real money. Other reliable signals: staff keep personal shadow copies, month-end reporting takes days of manual assembly, and nobody can say who changed a number or why. In Digital Heroes discovery calls the tipping point is almost always a specific expensive error, a mispriced quote, a missed order, or payroll built on a tab someone sorted wrong.
What does an internal tool cost for a small business with 20 to 50 employees?
Plan on $5,000 to $15,000 for a focused tool that replaces one painful spreadsheet workflow, such as job scheduling, quoting, or PTO tracking. In Digital Heroes projects at this size, the sweet spot is one core workflow, two or three user roles, and a single integration, usually QuickBooks or Google Workspace. Quotes far below $5,000 usually mean a template with your logo on it rather than software built around your process.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other internal tools companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
