eDiscovery Management Software: Build or Buy at Your Matter Volume
The threshold here is not matter count, it is hosted volume.
On this page
The threshold here is not matter count, it is hosted volume. If your annual per gigabyte hosting spend across live matters is smaller than the $120,000 entry price of a custom hold, collection and assessment layer, buy a review platform, run a disciplined process and stop reading. Above that, and particularly above roughly $250,000 a year in hosting, the arithmetic turns, because culling before promotion is a saving that recurs every month for the life of every matter. Most firms fall below the line on review and above it on preservation, which is why the honest answer for the majority is buy the platform and build the layer around it.
When is off the shelf genuinely the right call here?
For review, almost always. Relativity is the most extensible platform in this market and carries the deepest ecosystem of third party applications around it. Everlaw and DISCO offer simpler commercial models and are easier for a case team to pick up without a certified administrator sitting alongside them. Nuix is the right answer when difficult processing rather than review is your actual bottleneck, and processing is a separate problem from review however often the two get bundled in a sales conversation.
If you are a firm handling ordinary matter volumes, buy one of those and put your effort into process discipline instead. A build that tries to displace them will be slower, less capable and permanently behind, because you would be reproducing years of hardening, analytics and scale inside a budget that cannot carry any of it. That is the clearest buy recommendation we give in any legal software category, and we give it without qualification.
Buy also when your matters are episodic. If you run a handful of cases a year, the fixed cost of operating your own preservation and assessment infrastructure never amortises across enough matters to justify it. A spreadsheet and a disciplined paralegal is a defensible process when the volumes are small enough for one person to hold the whole picture in their head, and pretending otherwise sells software rather than solving anything.
And buy, or rather contract, when you are a corporate department that pushes essentially all discovery to outside counsel and has no ambition to hold data yourself. In that arrangement your problem is a protocol and reporting problem before it is a software problem. Exhaust the outside counsel guidelines route first, because a well drafted discovery protocol costs a fraction of any build and often gets you most of the cost control you were after.
When does a custom build actually pay off?
The build that pays is not a review platform. It is the layer around one: legal hold and custodian tracking, collection orchestration with chain of custody, early case assessment that culls data before it reaches per gigabyte hosting, and a live matter cost model. In Digital Heroes delivery experience that first release runs $120,000 to $250,000 and ships in 16 to 22 weeks. Extending into review, privilege logging and Bates numbered production runs $400,000 to $900,000 over 10 to 18 months, and we recommend that scope to very few clients.
It pays when two or more of the following are true. Your legal hold tracking is a spreadsheet and a preservation question has already been raised against you. You cannot tell a client the cost consequence of a scoping decision at the moment the decision is being made, only six weeks later on an invoice. Your collections span several source systems and your chain of custody evidence is assembled from emails after the fact. You handle matters where data cannot leave a jurisdiction or must remain on infrastructure you control. Or you are a corporate department managing several outside firms and need one cost and protocol model across all of them.
That last case is the strongest and the least served by anything you can buy. Every product in this market sits on one side of the firm and client relationship, so none of them will model your panel firms against each other. A department that can compare cost per gigabyte across providers tends to change panel decisions quickly, and no purchased licence delivers that comparison because it is not the vendor's data to model.
How do they compare on the things that matter in this industry?
On analytics and scale, the purchased platforms win outright and it is not close. Threading, concept clustering, assisted review and the ability to hold a terabyte scale corpus without falling over represent sustained investment that a project budget does not reproduce. Treat that as settled.
On preservation, the picture reverses. A hold is not a notice, it is an ongoing obligation with custodians who join and leave, retention policies that must be suspended and verified, reminders that must be evidenced, and a release at matter close that matters as much as the issue. Purchased hold modules exist, but they rarely reach into your human resources (HR) directory to detect leavers automatically, and detecting a departing custodian before ordinary offboarding wipes their device is the whole point. Under Rule 37(e) the first question after a loss of electronically stored information is what steps you took, and a build lets you answer that from an evidence log rather than from memory.
On cost visibility, nothing you buy will show a partner the currency consequence of promoting a custodian set at the moment they promote it, because the vendor's revenue moves in the opposite direction from that number. This is not an accusation of bad faith. It is simply not a feature anyone is incentivised to build, so it stays absent.
On chat, both sides struggle. Slack and Teams conversations have no natural document boundary, and a message that references a cloud document by link is not the same artefact as an attachment. Whichever route you take, you need a documented review unit rule you can defend at a meet and confer. A build lets you write that rule down and enforce it. A purchased platform lets you accept the one it already implements, which is often fine and occasionally is not.
What does total cost of ownership look like at your scale?
Start with the build. Source system connectors run $12,000 to $35,000 each, and Microsoft 365, Google Workspace, Slack, Teams and mobile forensic tooling are five separate integrations with five export shapes and five permission models. Data volume adds $30,000 to $90,000, because terabyte scale text extraction, indexing and deduplication on your own infrastructure is genuine engineering rather than configuration. Multi jurisdiction handling adds $25,000 to $70,000 and changes the architecture rather than the settings. A production pipeline, if you take it in house, adds $45,000 to $110,000.
Then the running costs, which are the ones nobody quotes. A support retainer of 15 to 20 percent of build cost a year, because a broken collector during an active matter is not a ticket that waits. Your own assessment infrastructure at $20,000 to $60,000 a year for storage and compute holding metadata and extracted text before promotion. Connector maintenance at $8,000 to $18,000 per source per year, since chat platforms change their export capabilities on their own schedule. Security review and penetration testing at $12,000 to $30,000 a year, because outside counsel guidelines increasingly require evidence of it.
Now the number you are actually comparing against, which is not a licence fee. Take your hosted volume across live matters, multiply by your rate, annualise it, then ask what share would survive a disciplined assessment pass before promotion. Date filtering, custodian scoping, domain analysis, cross custodian deduplication, threading to suppress inclusive duplicates and removal of known system files do not shave a marginal slice off a corpus that was assembled by promoting everything under time pressure. Whatever they remove, they remove every month for the life of the matter. That recurrence is the entire commercial case, and if your hosted volume is small, the case simply is not there.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. For most firms and most corporate departments this is not a compromise, it is the correct architecture, and it is what we recommend more often than either pure option.
Concretely: keep hosting review where it is and keep paying for it, because you keep using it and it is a fair trade for what it does. Build holds as ongoing objects with directory sync, acknowledgement escalation and a recorded release. Build collection orchestration that records source, method, date range, custodian, operator and hashes into an evidence log that survives challenge, while continuing to call your existing processing engine rather than replacing it. Build the assessment layer that sits before hosting and prices every promotion decision in currency. That is roughly $196,000 on a two connector scope covering Microsoft 365 and Slack, and it leaves the hardest and most expensive parts of the problem with the people who have already solved them.
Sequence it so the hold module lands first. It is the smallest piece, it removes the preservation exposure that worries general counsel most, and it can go live months before anything else. Run the whole thing alongside two live matters before it becomes the process of record.
Which should you choose, by operator size and stage?
A firm under roughly 50 fee earners with episodic litigation should buy Everlaw or DISCO, agree a written hold procedure, and spend nothing on development. Your risk sits in process, not tooling, and a build would add a maintenance obligation you have nobody to carry.
A mid sized litigation practice with continuous matters and hosting spend that has started appearing in partner meetings should buy the review platform and build the hold and assessment layer, starting at the lower end of the $120,000 to $250,000 band with two connectors. Add the third and fourth source once the chain of custody model has proven itself on real matters.
A large firm or a corporate department with matters spanning several jurisdictions should buy review, build the full surrounding layer including the cost model, and treat data residency as an architectural constraint from day one rather than a deployment setting discovered in month four.
The only operator who should consider building review itself is one facing a client or regulatory requirement that forbids data leaving their own infrastructure. That is a multi year programme, it belongs at the top of the $400,000 to $900,000 band and beyond, and it should be entered with the residency constraint written down and signed off, not assumed.
If you would rather someone argued with your brief than agreed with it, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. 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 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) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
Frequently asked questions
What does it cost to switch review platforms once we are on one?
The licence is the small part. Budget for re processing and re promoting active matter data into the new platform, rebuilding coding layouts and privilege fields, retraining reviewers mid matter, and validating that Bates ranges from prior productions do not collide with the new numbering. Firms routinely underestimate the coding field mapping, because tags accumulate meaning that lives in reviewers' heads rather than in documentation.
The practical mitigation is to switch between matters rather than during them, and to insist on a documented export of coding data as a contract term before you sign, not after you want to leave.
What happens if our review platform raises its per gigabyte rate?
Your exposure is proportional to how much you promote, which is the variable you control. A firm with an assessment layer absorbs a rate rise by tightening promotion criteria. A firm without one absorbs it in full, every month, across every live matter, and finds out at renewal.
This is the honest reason the surrounding layer is worth building even though it does not replace anything. It converts a vendor pricing decision from something that happens to you into something you can respond to inside a fortnight.
How long does the custom layer take to build?
Sixteen to twenty two weeks for legal hold and custodian management, collection orchestration with chain of custody, pre hosting assessment and the matter cost model. Ten to eighteen months if review, privilege logging and validated production are in scope, which for most firms they should not be.
Sequence the hold module first so it goes live independently. It is the smallest piece and it removes the preservation exposure that general counsel worries about most, so it earns its keep before the rest of the project finishes.
How does building around Relativity compare to just buying more of Relativity?
They solve different problems. Buying more of Relativity gets you more review capacity, better analytics and more third party applications. It does not get you a preservation obligation tracked against your human resources directory, and it does not price a promotion decision in currency at the moment a partner makes it.
So the comparison is rarely either or. The firms that get this right keep the platform, use its extensibility where it fits, and build only what sits before the data reaches it.
Can we build a hold module and nothing else?
Yes, and for many firms that is the right first project. It is the smallest scope in the category, roughly 18 to 24 percent of the full layer budget, and it delivers value standing alone because preservation exposure does not depend on anything downstream.
Build it with custodians drawn from your directory so leavers are detected automatically, acknowledgement tracking with escalation, evidenced reminders, verified suspension of retention policies, and a recorded release at matter close. Holds left running forever are their own cost.
Is Nuix a substitute for building our own processing?
For most firms, yes. Processing is a solved and heavily invested problem, and Nuix handles difficult formats better than a project team will inside a first release. Orchestrate it rather than replacing it.
Where a build still earns its place is the chain of custody around processing: recording source, method, date range, custodian, operator and hashes so your evidence log is generated rather than reconstructed from emails when someone challenges it two years later.
What should we do about Slack and Teams under either route?
Decide a review unit rule and write it down, typically a channel and day boundary with participants preserved, because a conversation has no natural document boundary and you will be asked to explain your choice at a meet and confer.
Linked cloud documents are the harder half. The collected version may not be what the recipient saw. Resolve links where your tenancy permits and log the gap where it does not, because a documented gap is defensible and a silent one is not. That logging discipline is easier to guarantee in a build.
Who owns the code, and what happens to matter data at close?
You should own the repository and the infrastructure accounts, with hosting locations and encryption specified in writing before kickoff. At Digital Heroes the client owns the code from the first commit.
Agree the deletion process at matter close during the build rather than afterwards. Retaining client litigation data past the obligation is a liability rather than a service, and it is precisely the sort of thing that surfaces during a client security review.
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.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
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.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
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 Eleanor.
VP Client Services · UK & EU · London · 1 post on the site
Published · Last updated .
