Workforce Development Board Case Management Software: Custom Build Versus Virtual OneStop and Bonterra
Buy, and never replace the state system. 5M a year in training should stay on Virtual OneStop or America's Job Link with a disciplined finance workbook.
On this page
Buy, and never replace the state system. A local board obligating under roughly $1.5M a year in training should stay on Virtual OneStop or America's Job Link with a disciplined finance workbook. Building becomes defensible only above about $4M in annual obligations, or once you administer funding outside WIOA Title I and your commitment position lives in one person's spreadsheet.
What the off-the-shelf products actually do well
A monitoring team pulls twenty participant files and three of them cannot prove the funding stream you charged. That is the fear that brings boards to this page, and it is worth saying early that software is often not the fix.
Start with what already works. Geographic Solutions Virtual OneStop and America's Job Link Alliance are statewide systems configured by your state agency, and they do the job they were built for: holding the participant record and producing the Participant Individual Record Layout that reaches the Department of Labor through the Workforce Integrated Performance System. They are not the problem, and a local board does not get to replace them.
Around them, real products exist and several are good. Bonterra, which now carries both Apricot and Efforts to Outcomes, is a serious case management platform with configurable forms and outcome tracking. CaseWorthy handles complex multi-programme social service caseloads. On the money side, MIP Fund Accounting and Sage Intacct both do fund accounting properly, with grant segments, indirect cost allocation and the reporting a single audit expects. Salesforce with a grants management build sits under a number of larger boards and works when somebody owns the configuration.
If you are a smaller board running one or two funding streams with a finance officer who genuinely has the workbook under control, that combination is correct and a build will not repay you. We say this to boards during procurement and it costs us bids.
Where they stop: the obligation nobody can see until month ten
Here is the workflow that none of the products above model, because it is local policy rather than programme design.
An individual training account is a commitment, not a transaction. You issue a voucher in March for a nine month programme. The provider invoices across three terms. Those terms straddle a programme year that runs July to June, so a single voucher spends against two allocations. Multiply by several hundred participants and several dozen providers, and the question your executive director has to answer at every board meeting is how much training money is genuinely left.
The state system records that a training service occurred. It does not hold your obligation. So the answer comes from a workbook maintained by one finance person reconciling provider invoices against issued vouchers by hand, and the failure mode is not fraud. It is over-commitment discovered in month ten, when there is nothing to do about it.
The second gap is evidence. Under Uniform Guidance in 2 CFR Part 200 a disallowed cost is repaid by the grantee, and the grantee is your board. The three findings that recur are eligibility documentation that does not actually support the stream charged, a voucher issued to a programme that had already left the eligible training provider list, and supportive service payments without adequate receipts or authority. Records have to survive the retention period in 2 CFR 200.334, which is three years from final expenditure report submission, and that clock is longer than most staff tenures.
Off-the-shelf case management holds the case. It does not hold the commitment, the provider contract and the eligibility evidence in one place your monitor can walk through.
The arithmetic: seats against a build, inside the administrative cap
This category has an arithmetic constraint the private sector does not. WIOA limits local administrative costs to ten percent of your local allocation, and your software spend competes inside that ceiling with finance staff, audit, insurance and the executive director's own time. So the comparison is not simply cheaper against dearer. It is what the ten percent buys.
Take your own quotes. Case management platforms in this space price per named user per month and add implementation and configuration in year one. Suppose the quote lands at $140 per user per month across sixty logins for career advisers, business services staff, finance and monitoring. That is $100,800 a year, plus a first year configuration fee that is frequently a similar figure again.
Against that, a focused first release sits at $80,000 to $160,000 once. The crossover in this sector is close to sixty named users, or roughly $4M in annual training obligations, whichever you reach first. Under those figures the subscription is proportionate and a build is not.
Above them, the number that decides it is not licence cost. It is the disallowed cost you repay from a budget with no line for it, plus the finance days lost to reconciliation every month. Both are calculable from your own last two monitoring reports.
What a custom build actually costs
These are Digital Heroes delivery bands across more than 2,000 projects. A focused first release covering document backed eligibility with funding stream assignment, individual training account obligation and budget control, and provider and contract management runs $80,000 to $160,000 and ships in 12 to 18 weeks. Adding youth element tracking with subcontractor performance, supportive service payment workflow, employer engagement and cohort forecasting brings it to $200,000 to $450,000 across 6 to 12 months.
The two costs that get left out of board packets:
- Migration accounts for 10 to 25 percent of the build. Closed files load in bulk because nothing is computed from them. Open obligations are the expense, because each voucher has to be entered and then verified against the finance workbook by a second person. A mis-entered obligation is a budget error rather than a data error.
- Year two and every year after costs 15 to 20 percent of the original build. Federal guidance letters change reporting expectations, your state changes its interface, new grants arrive with their own eligibility and allowable costs, and somebody has to keep the rules current. Boards that skip this line end up with a system nobody trusts by year three.
What drives cost up specifically: the number of non-WIOA funding streams you administer, since each carries its own eligibility and its own report; whether your state exposes any interface at all, because the no-interface case means designing for single entry without doubling adviser workload; direct payment workflows if the board issues supportive services itself rather than through a fiscal agent; and single audit expectations, which raise the bar on every audit trail that touches money.
The four situations where building wins
Four conditions, and you want at least two before going to procurement.
- Regulatory fit. Every eligibility criterion bound to the document that proves it, held under your retention rules and retrievable in one action three years later. Provider list status validated at the moment a voucher is issued rather than at audit. Approvals recorded as who approved what, when and under which authority, with amendments that do not erase the original. No configurable product does all four together.
- Scale economics. Past roughly sixty named users, per-seat pricing eats a share of a capped administrative budget that you need for people.
- A workflow that is your competitive advantage. For a board that is co-enrolment. One participant, one document set, two funding allocations with correct cost splitting. Two separate records is what you have now, and it is why your counts never reconcile.
- Integration sprawl across three or more systems. The state system, a fund accounting package, a case tool, a provider invoice folder and a commitment workbook is five places holding one voucher.
Not on the list: dissatisfaction with the state system. That is nearly always a configuration argument with your state agency, and a build will not resolve it.
How to decide in a week
Run this on Monday. Ask your finance officer for the uncommitted training balance by funding stream and programme year, as at close of business, and time how long it takes to produce. Then ask for the same figure as at the same date last quarter and see whether the two reconcile.
If the answer comes back the same day and reconciles, your workbook is working and you should not build. If it takes two days, you have just measured the problem, and you can price it by multiplying those days across a year.
Then run the evidence half. Pick five closed files at random and assemble the monitoring packet for each: eligibility documents tied to the stream charged, the plan, provider list status on the voucher date, payments with receipts, and the exit record. Time it, and note how many people you had to interrupt.
The proper next step is a paid discovery phase. At Digital Heroes that produces a signed product requirements document before any code exists, covering the obligation model, the eligibility evidence structure, the boundary with your state system and acceptance criteria. The board keeps that document whichever firm wins the procurement, which is useful when leadership changes. We contract through India LLP, US LLC and UK LTD entities so intellectual property assigns under law your own counsel reads, we field more than fifty specialists, and you meet the named team before signing.
We are the wrong partner if your procurement requires an onsite presence, or a firm that will also operate the system for you long term. We build it, document it and hand it over.
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.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- 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) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- One in four US employees report lacking career advancement opportunities; 48% of employees who participated in mentorship programs report high job satisfaction versus 29% of non-participants, and access to advancement opportunities ranges from 33% at organizations under 10 employees to 74% at those with 1,000+. Source: Gallup (2025) →
Frequently asked questions
Can a local board replace the state system of record?
No, unless you are the state agency that owns it. The statewide system carries the participant record and produces the federal submission, and standing up a competing system of record creates a permanent reconciliation burden your staff will carry forever. Build the layer the statewide configuration was never going to give twenty local boards: obligations, evidence, provider contracts, non-WIOA funding and local reporting.
What is the difference between Bonterra and a custom build for a board?
Bonterra, covering Apricot and Efforts to Outcomes, is a configurable case management platform that handles forms, services and outcomes well. What it does not model is a training voucher as a commitment with a schedule, an available balance and a programme year, or a provider contract with authorised costs. If your pain is casework, configure a product. If your pain is money, that is a different data model.
How long does implementation take and will advisers use it?
A first release ships in twelve to eighteen weeks, and adoption is decided almost entirely at intake. If document capture happens on a phone during the appointment and enrolment cannot complete while a required evidence slot is empty, the file is complete by construction. If capture is a scanning task for later, it will not happen and you will have bought a nicer interface over the same gaps.
Who owns the code and the participant records if we procure a build?
The board should own the repository, the cloud accounts and the unrestricted right to hire another firm, settled in writing before kickoff. At Digital Heroes the client owns the code from the first commit. Retention deserves explicit attention here, because files must outlive the federal retention period and often outlive the staff who created them, so agree the export format at the start rather than at the end.
What happens if a training provider leaves the eligible list mid-programme?
Participants already enrolled are generally handled under your state policy, but the exposure sits with vouchers issued after removal. That is a validation problem rather than a policy problem: check list status at the moment the voucher is cut, store the status you saw and the date you saw it, and the question becomes answerable years later when a monitor asks why the payment was made.
How much of our administrative allocation should software consume?
Local administrative costs are capped at ten percent of the local allocation, so every dollar of software competes with finance staff, audit and insurance inside that ceiling. Boards that treat software as an operational rather than administrative cost should get that classification confirmed with their state before signing, because the answer changes the affordable price by a wide margin.
Can one system hold funding streams outside WIOA Title I?
This is usually the strongest reason a mature board builds anything. State grants, apprenticeship funds and philanthropic dollars each carry their own eligibility, allowable costs and reporting, and statewide systems do not carry them, so they end up in separate workbooks. A build models funding streams generically, so one participant can be served under several with correct cost allocation and each funder gets its own report.
Should we build if we have never had a monitoring finding?
Probably not yet. A clean monitoring history means your current controls are working, and the honest advice is to keep the workbook and invest in a second finance day rather than in software. Revisit when the finance officer who holds the model in her head announces a retirement date, because that is when an undocumented control becomes a risk.
How do we handle a participant co-enrolled in two funding streams?
One participant record with one evidence set and two funding allocations, each carrying its own cost split. Two separate records is the common approach and it is why enrolment counts never reconcile between finance and programme reporting. Ask any developer to model this on a whiteboard before you talk price, because a system that cannot represent it will hand you the reconciliation problem you already have.
What should the first release include and what should wait?
Obligation and budget control plus document backed eligibility, and nothing else. Between them they address the disallowed cost exposure and the budget visibility problem, which are the two reasons a board approves a project. Youth element tracking, employer engagement and forecasting are genuinely valuable and belong in phase two, after finance has run a full quarter on the obligation ledger.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
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.
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.
What should I prepare before contacting an agency about an internal tool?
Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.
How much does a custom internal tool cost to build?
Most custom internal tools cost $8,000 to $40,000 to build, based on Digital Heroes delivery data across 2,000+ client projects. A single-purpose tool like an approval dashboard or inventory tracker sits at the low end, while a multi-department platform with role-based access and several integrations pushes past $40,000. The three biggest cost drivers are the number of user roles, the number of systems the tool must connect to, and custom reporting requirements.
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 owns the code when an agency builds our internal tool?
You should, outright, with full IP transfer in the contract and the code delivered to a repository you control, such as your own GitHub organization. Digital Heroes transfers complete ownership on final payment as standard practice, and any agency that keeps the code or licenses it back to you is building a dependency you will pay for later. Confirm you also own the hosting, domain, and database accounts, since many of the vendor disputes Digital Heroes gets called into involve infrastructure registered under the agency's name.
What does it cost to keep an internal tool running after launch, and do we need to hire a developer?
Budget 15 to 20 percent of the build cost per year, so a $25,000 tool runs roughly $300 to $400 a month covering hosting, security patches, dependency updates, and small tweaks, figures drawn from Digital Heroes maintenance contracts. You do not need an in-house developer; a monthly retainer with the agency that built it covers the typical internal tool comfortably. Hosting itself is cheap for internal audiences, often $20 to $100 a month, because you serve dozens of users rather than the open internet.
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
More from Charlie.
Senior Copywriter · UK · London · 3 posts on the site
Published · Last updated .
