Class Action Settlement Administration Software: Build or Outsource
The threshold is roughly eight settlements a year.
On this page
The threshold is roughly eight settlements a year. Below it, outsource: engage an established administrator such as Epiq, Angeion, JND or Kroll, pay the fee and let them carry the operational risk, because a court will reasonably question why an untested system built for one case was used to distribute a fund. Above it, when every case is stood up by hand and your capacity is capped by developers rather than by your operations team, a first release runs $100,000 to $220,000 in 16 to 24 weeks. Almost everyone asking this question runs fewer than eight and should outsource.
When is off the shelf genuinely the right call here?
There is no packaged product to buy in this category, and that is a fact about the work rather than a gap in the market. Every settlement agreement defines its own class, tiers, proof requirements, deadline calendar, deduction order, allocation formula and residual treatment, so there is no stable feature set to productise. The off the shelf option is therefore a firm, not a licence. Epiq, Angeion, JND and Kroll administer settlements as their business, and for most people reading this the correct move is to engage one of them.
Outsource without hesitation if you are handling a single settlement, however large. A court will reasonably ask why a fund was distributed through a system built for one case and never tested on another, and no budget makes that question go away. We decline this work when it is framed that way, and any developer who accepts it should worry you. The same answer holds if administration is a sideline. Two or three cases a year does not amortise a platform, and renting capacity from a firm running hundreds is cheaper on every axis including risk.
Outsource, too, if what you actually lack is process rather than software. Administrators sometimes conclude they need a platform when the real problem is that nobody has written down which parts of a settlement genuinely vary between cases and which parts they treat the same way every time. That document is a morning of a partner's time. If it turns out your last six mandates were structurally similar, your setup cost is a template problem, and templates are free.
When does a custom build actually pay off?
Administration has to be the business, and two or more of these have to be true. You run more than roughly eight settlements a year and each one is stood up by hand. Your fraud detection is a set of manual spot checks and you would be uncomfortable describing the methodology in a declaration. Allocation runs happen in spreadsheets that cannot be diffed against each other. Your notice reporting is assembled from vendor exports in the week before a filing. Or you are losing mandates to administrators whose portals and reporting are visibly better, which influences selection more than most firms like to admit.
The economic argument is repeatability, not features. If standing up a case takes three weeks of manual and engineering effort, your capacity is capped by your developers rather than by your operations team, and every additional mandate makes that worse rather than better. A platform earns its money when a new case is configured by an operations lead in days. If a developer is still required after release one, the build has not paid for itself and will not.
Price the alternative honestly before you decide. Take your last six mandates, count the engineering and operations days consumed before the first claim arrived, and multiply by your loaded day rate. Then add the mandates you did not pursue because capacity was already committed. That second number is the one firms consistently forget, and it is usually the larger of the two.
How do they compare on the things that matter in this industry?
Case setup. An administrator you hire absorbs setup entirely, which is exactly why outsourcing works below eight cases. A build shifts setup from engineering to configuration, but only if the settlement is expressed as data: class definition, tiers with eligibility and proof requirements, deadlines as named events with dependencies since a cure period runs from a deficiency notice date, deduction order, and an allocation grammar covering fixed payments, weighted units, caps, floors and pro rata scaling.
Identity. Defendants supply what their systems hold: a customer table, a former employee export and a warranty list, with the same person in all three under different spellings and two addresses, and identifiers unique only within each file. Whoever administers the case has to resolve that. The difference a platform makes is that notice deliverability, claim deduplication and final distribution all key off one resolved identity, so declaration numbers reconcile by construction rather than by a late spreadsheet.
Fraud. Consumer claim volumes are now a fraud problem rather than a data entry problem. Scoring beats blocking: submission velocity, device and network signals, reuse of addresses or payment instruments, mismatch against the class list, and similarity across uploaded proofs. The design requirement that costs real money is retaining the contributing signals on every decision, because your methodology may be described in a filing and a denial you cannot explain is a denial that gets reversed.
Allocation. It almost never runs once. Counsel asks what changes if a tier is capped differently, a late claim tranche is accepted, or the court adjusts the fee award. Spreadsheets cannot be diffed reliably, which is where the errors that reach a judge tend to originate.
What does total cost of ownership look like at your scale?
Release one is $100,000 to $220,000 over 16 to 24 weeks: the case configuration engine, class member ingestion with address hygiene and identity resolution, a brandable claims portal deployable per case in days, and deduplication with fraud scoring. A firm running about twelve settlements a year with consumer classes between 40,000 and 600,000 members landed at $195,000 across 21 weeks, toward the top of the band because fraud scoring covered device and network signals and the penetration test was scoped properly rather than treated as a formality.
Phase two, the versioned allocation engine plus payment rails with reissue handling, is typically $90,000 to $200,000. Phase three, notice orchestration, deficiency and cure workflows, tax reporting and court reportable exports, is $80,000 to $180,000. Full platform totals $250,000 to $600,000 across 9 to 18 months. Each additional payment rail is $25,000 to $60,000 on its own, because cheques, automated clearing house transfers, digital wallets and prepaid cards each carry distinct failure, reissue and reconciliation behaviour.
Running cost is $1,200 to $5,000 a month for hosting and document storage across concurrent cases, plus $15,000 to $40,000 a year for a security programme covering penetration testing, dependency monitoring and access reviews, plus 15 to 20 percent of build cost for support and change. Third party services, address validation, change of address processing, mail execution, banking rails and identity verification, price per record or per transaction and flow into case budgets rather than your software budget. Those are Digital Heroes delivery figures.
What does the hybrid look like, and when is it the honest answer?
The hybrid here is not a platform plus a thin layer, it is a spine plus rented infrastructure, and it is the shape we recommend to almost every administrator who builds at all. Build the configuration engine, the class member registry and one payment rail. Rent everything that is already a service: postal address validation and change of address processing, mail house execution, banking rails, identity verification, call centre telephony. Your platform orchestrates and reconciles them. Rebuilding any of that is how a $200,000 project becomes a $500,000 project with nothing extra to show a judge.
A second hybrid worth considering, particularly for a firm sitting just under the eight case threshold, is to keep outsourcing distribution while building only the front half. Configuration, registry and portal give you fast case setup and a claims experience that competes for mandates, while notice execution and payment rails stay with partners who already do them at scale. That splits the risk sensibly: the parts a court scrutinises most, money movement and notice reach, remain with firms who have done it hundreds of times, and the parts that cap your capacity come in house.
Sequencing is the other honest answer. Do not put notice orchestration first because it is the part counsel can see. It has to follow the registry, because a notice campaign that does not run off resolved identities produces declaration numbers you cannot reconcile against your distribution numbers. And do not build four payment rails before distributing anything, because that means debugging four reconciliation models simultaneously against real money.
Which should you choose, by operator size and stage?
One settlement, any size. Outsource. Epiq, Angeion, JND or Kroll. There is no version of this where building is the right answer, and we would tell you so on the first call.
Two or three cases a year, administration as a sideline. Outsource. The platform will not amortise, and the risk profile of an untested distribution system is the wrong risk to take for a secondary line of business.
Four to eight cases a year, growing. Build templates, not a platform. Standardise your portal, your class list intake format and your allocation spreadsheet structure. Write down which parts of a settlement genuinely vary. That document is the discovery input if you cross the threshold, and it is worth having regardless.
Eight or more cases a year, setup done by hand. Build the spine at $100,000 to $220,000, with one payment rail. Bring three or four completed settlement agreements of genuinely different shapes to discovery, because the configuration abstraction has to express settlements you have already administered rather than only the mandate in front of you. That sample is the single best predictor of how much rework happens in month six.
Established administrator with a filed correction in the past. Prioritise versioned allocation over everything else in phase two. Frozen inputs, recorded formula version, immutable results and a diff showing exactly which claimants moved. Retrofitting that after a second correction costs considerably more than building it now.
Whatever you choose, settle ownership in writing before kickoff. A system holding court reportable records for years should never sit on a supplier's cloud account.
When you are ready to turn this into a specification, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
- The performance gap between digital and AI leaders and laggards is widening: McKinsey reports leaders pull ahead on shareholder returns, and the average maturity spread between top and bottom performers jumped ~60% (from 10 points in 2016-19 to 16 points in 2020-22), reinforcing that the returns to transformation concentrate among top performers. Source: McKinsey & Company (2023) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- Nucleus Research's analysis of published analytics deployment case studies found business intelligence and analytics returned an average of $13.01 in benefits for every dollar spent, up from $10.66 three years earlier. Source: Nucleus Research (2014) →
Frequently asked questions
We have one large settlement. Should we build software for it?
No, and we decline the work when it is framed that way. Engage an established administrator such as Epiq, Angeion, JND or Kroll, pay the fee and let them carry the operational risk. A court will reasonably question why a fund was distributed through an untested system built for a single case, and there is no budget that answers that objection. The build case exists only when administration is your business and you run several settlements a year.
Why is there nothing off the shelf to compare a build against?
Because each settlement agreement defines its own class, tiers, proof requirements, deadlines, deduction order, allocation formula and residual treatment, so there is no stable feature set to productise. Administrators end up combining an internal database, a mail house, a banking portal and a per case web form. That is why the comparison is not against a licence fee but against your current cost of standing up cases by hand, plus the mandates you could not accept because capacity was committed.
How long does the first release take?
Sixteen to twenty four weeks. The pacing item is modelling the case configuration abstraction, because it has to express several settlements you have already administered rather than only the current one. Bring three or four completed agreements of genuinely different shapes to discovery. Put one operations lead on the project with authority to decide how the model expresses a settlement, and keep them there, because those calls cannot be made by committee.
What does it cost to switch away from our current administrator?
Ask precisely what leaves with you. A live case cannot be moved mid distribution in any practical sense, so switching happens between mandates, and the real question is whether historical class member records, notice delivery evidence, claim decisions and allocation runs come back in a form you can retain and reproduce. If they come back as summary reports rather than records, you cannot answer a later question about a case you were responsible for, which is a governance problem more than a cost one.
What happens if our administrator raises its per claim or per notice pricing?
Your exposure scales with case volume, which is exactly when you have least room to move, because pricing is renegotiated between mandates and your bid was already submitted. The realistic hedge is not building everything, it is owning the front half: configuration, registry and portal in house, notice execution and payment rails rented. That keeps a competitive claims experience under your control while leaving the volume priced services open to competition each time.
How much does each additional payment rail add?
Twenty five thousand to sixty thousand dollars per rail in our delivery experience. Cheques, automated clearing house transfers, digital wallets and prepaid cards each carry distinct failure modes, reissue and stop payment behaviour, uncashed instrument tracking and reconciliation models. Build one rail properly and distribute a settlement through it before adding another. Building four before distributing anything means debugging four reconciliation models at once against real money and real deadlines.
Can we save money by skipping allocation versioning?
You can, and it is the false economy we see most often. Allocation almost never runs once, because counsel asks what changes if a tier is capped differently, a late claim tranche is accepted, or the court adjusts the fee award, and each of those moves every claimant's number. Frozen inputs, a recorded formula version, immutable results and a diff showing exactly which claimants changed is where errors that would otherwise reach a judge get caught.
We run six settlements a year. What should we do instead of building?
Standardise rather than engineer. Fix one portal template, one class list intake format and one allocation spreadsheet structure, then write down which parts of a settlement genuinely vary between your cases and which you treat identically every time. That document costs a morning and often reveals that your setup problem is a template problem. It is also the discovery input if you cross into eight or more cases a year, so nothing is wasted.
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.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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.
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.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
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 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.
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.
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 Priyanka.
Senior UX Designer · UK · London · 2 posts on the site
Published · Last updated .
