Public Defender Case Management Software: Custom vs Off-the-Shelf
Buy if you are a single office. Justice Works defenderData knows this domain, Journal Technologies JustWare integrates well where the court runs the same family, and Karpel serves defence offices competently.
On this page
Buy if you are a single office. Justice Works defenderData knows this domain, Journal Technologies JustWare integrates well where the court runs the same family, and Karpel serves defence offices competently. Build when you are a statewide commission or a multi-office system, when conflict checking has already missed an alias, or when voucher administration is consuming a full-time person.
What defenderData, JustWare and Karpel actually do well
A public defender office is the inverse of a law firm on three counts. You do not choose clients, a court appoints them. You do not bill anyone, but your time data decides whether a legislature believes your caseload claim. And the matter list arrives at a rate set by the prosecutor's filing decisions, which nobody consults you about. Commercial legal practice software assumes the opposite of all three, which is why general tools fail here and specialist ones do not.
Justice Works defenderData was built for exactly this population and shows it: appointments rather than engagements, no billing spine, case types that match how indigent defence work is actually categorised. Journal Technologies JustWare is a reasonable option, particularly where your court runs on the same family and docket integration is otherwise painful. Karpel serves defence offices as well as prosecution and is worth including in any comparison.
All three carry accumulated correctness you should not pay to rebuild: clients with multiple open matters, matters with codefendants, charges amended and dismissed separately, dispositions and sentences, and the calendar plumbing that keeps an attorney out of two courtrooms at once.
So for a single office of modest size with a manageable appointment volume and no assigned counsel panel to administer, buy. We say that regularly, and it costs us work. Software is not the binding constraint in most defender offices. Attorney headcount is, and money spent on a build is money not spent on a lawyer.
Where they stop: the conflict check and the weighted caseload
Two things break packaged products here, and both are structural rather than cosmetic.
The first is the conflict check, which every product implements as a name search and which is not a name search. Your office is offered an appointment on a case with four codefendants. A conflict exists if you currently represent or previously represented any codefendant, if a listed witness is a current or former client, if a complaining witness is a current client, and often if a codefendant's interests are adverse in ways only visible later. Name search fails predictably: aliases and street names, transliteration variants, married and maiden names, the same person entered with three dates of birth by three agencies, and a codefendant list arriving as unstructured text in a police referral. What the work needs is a person graph with identity resolution and typed relationship edges, returning the specific path that creates the concern, in seconds, while the attorney is standing in a courtroom.
The second is caseload. A capital case and a misdemeanour possession case are both one case, and everyone outside your office draws conclusions from the count. The standards still widely cited trace back to National Advisory Commission work from the 1970s, and there has since been substantial national effort to rebuild them from contemporary workload research. Whichever standard your jurisdiction adopts, the argument runs on data you must produce: case type mix, disposition stage, hours actually spent, and the share reaching trial. That means time capture in an office where nobody joined to fill in timesheets, which is a design problem before it is a technical one.
The third gap is administrative. Where you conflict out or exceed capacity, cases go to assigned counsel who submit vouchers. That is a payment operation with public money, rate and cap rules living in a memo, expert authorisations granted verbally and disputed at payment, and vouchers arriving months late so your own forecasting is guesswork.
A fourth gap decides daily practice more than any of them. Clients in custody move between facilities without notice, get released, and disappear from contact. The obligation to communicate does not bend for that, and in offices under scrutiny the contact record is precisely what gets examined. Most systems hold contact in free text case notes, which means the question of how many clients have not been contacted since appointment cannot be answered without reading every file. Contact should be structured events with a type, a date, an outcome and a location, and custody status should arrive from the jail feed rather than from memory.
The arithmetic: cost per attorney against the cost to build
Run the replacement case honestly first. A full platform at $380,000, with support and enhancement at 17 percent a year, costs roughly $700,000 across five years, or $140,000 a year. Spread across a statewide commission with 400 attorneys and a panel, that is about $29 per attorney per month, which no packaged licence will beat once you add the reporting layer a commission actually needs. Spread across a single fifteen attorney office, the same build is about $778 per attorney per month, which is indefensible.
The crossover sits near 120 attorneys, or at any point where more than five or six offices share one deployment. Below that line the packaged products win on price and on risk, and we will tell a chief defender so in a first meeting.
Voucher administration moves the line on its own. If an administrator spends most of a week on paper claims, rate checks and approval routing, that is a recurring salaried cost against a voucher module in the $70,000 to $120,000 range. It is usually the fastest measurable payback in the whole portfolio, and it produces the cost per case type by delivery model that a commission needs to defend a budget.
The cost to build indigent defence software
From the justice sector work Digital Heroes has delivered, a first release covering appointments, the person graph with conflict checking, case records, structured client contact and calendar integration runs $110,000 to $250,000 and ships in 14 to 20 weeks. A full platform adding weighted caseload with passive time capture, assigned counsel vouchers with authorisations and approvals, investigator and expert requests, discovery receipt handling and commission reporting runs $280,000 to $650,000 over 9 to 18 months.
Two lines belong in the funding request. Data migration runs 10 to 25 percent of build cost, and here it is the conflict graph that drives it, because prior representation records usually sit in a legacy system with no unique person identifier and the graph is only as good as what you can load. Year two onward runs 15 to 20 percent of build cost annually, covering court and jail interface changes, statutory changes, and the storage growth that arrives with digital discovery you did not ask for.
What raises the number: whether you are one office or a commission covering many offices and a panel, jail and court integrations that are worth the cost and never free, voucher payment integration with the state or county financial system, and discovery receipt at gigabyte scale, since you are on the receiving end of the same productions the prosecutor is generating.
Four situations where building wins outright
Regulatory fit. Your records are privileged and cannot be visible to the court or the prosecutor even when everyone shares a county network, a county identity provider and a county technology department. That single constraint eliminates a category of convenient integration and argues for separate stores, separate access administration and one directional inbound feeds. If you are also being measured against the ABA Ten Principles or a caseload standard, the evidence has to come from your own system.
Scale economics. Above roughly 120 attorneys, or across five or more offices sharing a deployment, the fixed cost divides down below per seat licensing and the commission gains reporting no product offers.
A workflow that is your advantage. The conflict graph is it. If you have discovered a conflict after appointment more than once because a name search missed an alias, that is structural and no amount of process fixes it.
Integration sprawl. Count them: the jail management system for custody and movement, the court for settings and dockets, the financial system for voucher payment, and whatever the prosecutor uses to hand you discovery. Once three or more feed one appointment record, the integration layer is the product.
How to decide in a week
Take twenty appointments from the last quarter and re-run the conflict check by hand, this time with every alias, every date of birth variant, every codefendant and every listed witness. Give it to two people working independently. Count the concerns that surface now and did not surface then. If the answer is more than one, you have your business case and it is a professional responsibility argument rather than a budget one.
Second, run a contact query you probably cannot run today: which clients currently in custody have had no attorney contact in the last thirty days, and which of those have a setting coming up. If answering that requires reading files, contact is living in case notes rather than as structured events, and that is a two week fix rather than a platform.
Third, time your voucher cycle. Measure days from submission to payment on ten recent claims and count how many needed a rate correction. That gives you the payback figure for the cheapest module on the list.
Then commission a paid discovery phase of two to four weeks, ending with a signed product requirements document covering the person graph and matching rules, the privilege boundary and access model, integrations, acceptance criteria and a fixed price. Digital Heroes writes that before any code and you keep it whichever firm builds. Contracts sign through our India LLP, US LLC or UK LTD, so the work assigns under your own law. We are the wrong firm if you need staff physically present in your offices, because we have no local office anywhere and will not say otherwise.
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.
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Analyst estimates place CRM implementation failure rates broadly between roughly 30% and 70% (Johnny Grow cites Forrester at 47%), with low user adoption repeatedly cited as a leading cause of failed CRM projects (this being Johnny Grow's own analysis, not a Forrester attribution). Source: Johnny Grow (industry analysis citing Gartner/Forrester) (2025) →
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- Per Sensor Tower's State of Mobile 2026, worldwide consumers spent about $85 billion on apps in 2025 (up 21% YoY), and for the first time non-game apps surpassed games in consumer spending; generative-AI in-app purchase revenue more than tripled to top $5 billion. Source: Sensor Tower (via TechCrunch) (2026) →
Frequently asked questions
How long does a conflict checking system take to build?
Fourteen to twenty weeks as part of a first release that also covers appointments, case records and client contact. The schedule risk sits in your historical data rather than in the graph itself, because prior representation records usually arrive without a unique person identifier and have to be resolved into people before the check means anything. Start that extraction in week one.
Who owns the case data and the code if we hire a development firm?
Your office must own the repository, the infrastructure accounts and every record from the first commit, and this belongs in the contract before kickoff. The stakes are higher than commercial software because the data is privileged. Client information sitting in infrastructure you cannot administer is a problem you would have to explain to bar counsel, and no procurement convenience is worth that exposure.
Can we keep defenderData and build only the voucher system?
Yes, and for many commissions it is the right first move. The incumbent keeps case records while the custom module holds rates and caps as dated data, prior authorisations for experts and investigators as linked requests, cap checks with an exception path rather than a rejection, judicial approval routing where the statute requires it, and a payment file to your financial system.
What is the difference between a defender system and a prosecutor system?
They look similar and are built on opposite assumptions. A prosecutor system starts from a referral and a charging decision and produces discovery. A defender system starts from an appointment, must run a conflict check before accepting work, receives discovery rather than producing it, and cannot share a data boundary with the court or the prosecution. Products built for one rarely fit the other without concessions.
Should a five attorney office build anything at all?
No. Buy a small case system, write a conflict procedure that includes aliases and codefendants, and put the remaining money toward investigator time. At that scale the fixed cost of a build cannot divide down far enough, and the risk of maintaining custom software with no technical staff is real. Revisit only if you join a multi-office consortium.
How much does migrating historical representation records cost?
Ten to twenty five percent of the build, weighted toward identity resolution rather than data movement. Every prior client has to become a person in the graph, with aliases and identifier variants reconciled, because a conflict check against unresolved records gives false confidence. Budget review time from staff who recognise the names, since some matches can only be confirmed by somebody who was there.
What happens if a conflict is discovered after appointment?
You move to withdraw, the case is reassigned to conflict counsel or the panel, and the office absorbs the wasted work and the credibility cost. What matters afterwards is whether you can show what the office knew at the time of appointment, which is why the determination should be stored rather than only the check. Repeated late discoveries are a structural failure, not carelessness.
Can county IT administer a defender system safely?
Only with a boundary you set explicitly. Shared identity providers, shared databases and county administrators with production access are standing risks even when nobody has looked. Ask for separate data stores, separate access administration, one directional inbound integrations and full access logging, and put it into any shared services agreement before it is signed rather than trying to unwind it afterwards.
How do we capture attorney time without attorneys resenting it?
Passively, wherever possible. Derive court appearances from the calendar and docket, log jail visits when the visit is scheduled and confirmed, timestamp documents when produced, and ask for manual entry only where no other signal exists. Anyone proposing a timesheet as the primary mechanism has not worked with a defender office, and the data you get from an unused system is worse than none.
Should a statewide commission build one system for every office?
Usually yes, and it is the strongest build case in this category. Packaged products are designed around a single office, while a commission's actual job is measuring delivery across offices, panels and contract counsel to defend a budget. Phase it: conflicts and appointments first, then contact and weighted caseload, then vouchers, since each stands alone and each is useful before the next arrives.
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.
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.
At what point does Retool cost more than building a custom tool?
The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How long does it take to build an internal tool from scratch?
A working first version typically ships in 4 to 8 weeks, and larger multi-module tools run 10 to 16 weeks. Across Digital Heroes internal tool projects the schedule splits into roughly one week of process mapping, 3 to 6 weeks of build, and 1 to 2 weeks of testing with your actual staff. The most common delay is not development but waiting on the client for sample data and workflow decisions, so name one internal owner before kickoff.
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 long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
What are the most common mistakes companies make when building internal tools?
The three failures Digital Heroes sees most: building for every department at once instead of nailing one workflow, designing without the end users so staff quietly go back to their spreadsheets, and leaving no named owner after launch so small bugs pile up until the tool dies. A subtler fourth is faithfully recreating the old spreadsheet, including its workarounds, instead of fixing the process first. Start with one team's most painful workflow and put the actual users in the room from week one.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
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 Zayn.
Director of Strategy · UK · London · 2 posts on the site
Published · Last updated .
