Conflicts and Independence Clearance Software: Build or Buy at Your Firm Size
Below roughly 40 fee earners in one office with a single practice area and no audit line, buy. Intapp Conflicts does the core job properly and the money is better spent on intake discipline than on software.
On this page
Below roughly 40 fee earners in one office with a single practice area and no audit line, buy. Intapp Conflicts does the core job properly and the money is better spent on intake discipline than on software. The threshold is precision rather than headcount: once reviewers are reading hundreds of hits per matter to find the one that matters, clearance has become the bottleneck on revenue and no workflow product fixes that, because precision comes from your entity data rather than from features. Most firms cross that line somewhere past 100 fee earners.
When is off the shelf genuinely the right call here?
Buy if you are a single office firm under roughly 40 fee earners with one practice area and no audit line. Intapp Conflicts is the established product in this category and it does the core job properly: structured intake, searching firm records, workflow and approvals. Firms with straightforward practices run it successfully and we would not push anyone off it without a specific reason. At that size the money is better spent on intake discipline, because discipline is what actually determines whether the answers are right.
Buy also if your current problem is that you have no structured intake at all. A packaged product gets you to a baseline faster than a build, and you can revisit the question in two years with real data about where it hurts rather than with a theory. Commissioning a bespoke clearance system before you have ever run a structured intake process is buying a solution to a problem you have not yet described.
Buy if your practice is genuinely uniform. One jurisdiction, one imputation rule, one engagement type, no alliance structure. Rule chains that vary by office, jurisdiction, practice line and engagement type are what exceed a packaged configuration model, and a firm without that variation is not paying for anything it does not use.
The signal that buying is still right is measurable and worth taking before any other step. Pull fifty recent clearances and record how many hits were returned and how many mattered. If reviewers are reading twenty hits to find one relevant relationship, your product is doing its job. If they are reading three hundred and eighty, the problem is your entity data, and no product will fix that either.
When does a custom build actually pay off?
Build when two or more of these are true. Reviewers are reading hundreds of hits per matter and clearance has become the bottleneck on revenue. You run audit and advisory lines under one independence regime and the packaged model cannot express your rule chains. You hire laterals regularly and each one is a manual confidential exercise under time pressure. You have been in a disqualification fight or an inspection where you could not produce evidence of a wall being in force. Or your firm operates through an alliance or verein structure where imputation genuinely differs across member firms.
The capability that earns the money is entity resolution, not better searching. Everything downstream depends on knowing which entity you are actually talking about. Intake receives a name, sometimes a trading name, sometimes a misspelling, sometimes a group name where the counterparty is a subsidiary two levels down in another jurisdiction. Your own database holds the same entity four ways because four different secretaries opened matters over fifteen years. Normalising names, storing aliases, attaching external references such as company registry numbers and legal entity identifiers, and joining to corporate family data so a subsidiary hit surfaces its parent, is what produces precision. A rule chain running over unresolved names cannot be made precise however clever the rules are.
The second is explainable scoring. Reviewers need a ranked list with reasons, not a list of matches: high risk because the party is a current client in an active matter, same industry, lawyer in the same office; low risk because the name matched a dissolved entity with no activity in eleven years. Two design rules matter. Every score must be explainable in plain language, because a reviewer will not trust a number, and the scoring model must be versioned, because in two years somebody will ask what the system knew and how it ranked on the day you cleared the matter.
How do they compare on the things that matter in this industry?
- Precision ceiling. Whichever route you take, precision is limited by the entity data you attach. Thin corporate family information and unreconciled party records produce noise regardless of the product, which is why a data cleanup is worth doing before any procurement decision.
- Rule chain expression. Rules that vary by office, jurisdiction, practice line and engagement type multiply rather than nest. Ask any vendor to model two jurisdictions with different imputation treatment during evaluation and watch how much configuration effort it takes.
- Wall enforcement. A wall recorded in a conflicts database but not provisioned in iManage or NetDocuments is a policy, not a control. Check whether declaring a wall triggers restrictions in your document and practice management systems or only sets a status.
- Evidence generation. The pack you need during a disqualification motion is acknowledgements, access logs and attestations proving a screen was in force on a specific date. Generated is a different product from assembled.
- Independence obligations. Restricted entity list ingestion, structured holdings declarations, non audit service pre approvals and cooling off tracking are a second rule model over the same entity graph rather than extra fields on the first.
- Configuration as a permanent role. Where a packaged model cannot express your rule chains, configuration stops being a setup task and becomes a job. Price that role, because it is the recurring cost most firms leave out of the comparison.
What does total cost of ownership look like at your scale?
A first release covering structured intake, party resolution with corporate family matching, explainable hit scoring, a configurable rule chain and a reviewer workbench runs $90,000 to $200,000 and ships in 14 to 20 weeks. A 220 fee earner firm across three offices and two jurisdictions, no audit line, came in at $163,000 over 18 weeks. The largest single line in that build was historical party reconciliation at $52,000, which is not an anomaly. It is the reason the existing system returned hundreds of hits per matter.
The full platform adding ethical wall provisioning into document and practice management, waiver and advance waiver registers with scope and expiry, restricted entity list ingestion, personal holdings declarations, service pre approval workflows and an immutable clearance audit trail runs $250,000 to $600,000 across 9 to 18 months. Walls alone are typically $70,000 to $160,000 as phase two. Audit independence is $80,000 to $200,000 as phase three.
Running costs are 15 to 20 percent of build cost annually. Hosting for a firm of a few hundred fee earners is $400 to $1,500 a month, higher if you retain full clearance evidence packs for every matter, which you should. Two lines get missed. Corporate family data is licensed rather than bought and scales with how many entities you resolve against. And somebody has to own the party graph as a named responsibility, because new matters introduce new entities and resolution quality degrades quietly until reviewers stop trusting the scores again.
Against that, the licence figure is the smaller half of the comparison. Take a month of clearances, count the hits reviewed per matter and the senior hours spent reading them, and multiply by charge out rate. Then count the matters where clearance was the reason a client waited.
What does the hybrid look like, and when is it the honest answer?
There are two hybrids here and both are more sensible than a full replacement for most firms.
The first is to keep your packaged product as the intake, workflow and approval system, and build only the resolution and scoring layer that feeds it. Party names get normalised, aliased, matched to external identifiers and joined to corporate family data, then hits are ranked with plain language reasons before a reviewer sees them. That is where the reviewer hours are, and it leaves the approval process, the records of decision and your existing training untouched. It is also the phase that produces a measurable before and after number, which makes any later phase far easier to fund.
The second applies to firms with an audit line. Keep the packaged product for legal conflicts, which is what it was designed for, and build only the independence module: scheduled restricted entity list ingestion, structured holdings declarations using identifiers rather than free text, non audit service pre approval workflows and cooling off tracking. That earns its money through continuous evaluation, because an annual declaration form leaves you out of date for eleven months of every year.
The ordering rule is the same in both cases and it is not negotiable. Data and scoring first, enforcement second. A wall provisioned against an unresolved party is a control applied to the wrong entity, which is worse than no control because it produces confidence you have not earned.
Which should you choose, by operator size and stage?
Under 40 fee earners, one office, one practice area, no audit line: buy Intapp Conflicts and spend the difference on intake discipline. A thirty lawyer firm should not be commissioning clearance software, and we say so regularly.
Forty to 150 fee earners, two or three offices, one jurisdiction, reviewers coping: keep the packaged product and run the fifty clearance measurement once a year. It costs a day of somebody's time and it tells you whether precision is drifting before it becomes a problem, which is a cheaper form of monitoring than a procurement exercise.
Above roughly 150 fee earners with multiple jurisdictions and reviewers reading hundreds of hits per matter: build the resolution and scoring layer beside your existing product. Limit release one to one office and one practice line. Reviewer hours saved show up in the first month, which is what makes the second phase fundable.
Firms with audit and advisory lines under one independence regime: build, and treat independence as its own rule model over the same entity graph rather than as an extension of the conflicts model. This is the strongest build case in the category, because the packaged products in this market grew out of legal conflicts and the obligations differ in kind.
Alliance or verein structures where imputation genuinely differs across member firms: build, because no packaged configuration model expresses that cleanly and the workaround is a permanent human process. In every case, own the repository, the cloud accounts and the right to hire another firm. A clearance system holds your firm's institutional memory of every relationship it has ever had, and that belongs to the partnership.
If you would rather scope this before committing budget, 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 can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- In PMI's 2014 Pulse of the Profession report on requirements management, inaccurate requirements management is cited as a leading cause of project failure, with 47% of unsuccessful projects failing to meet goals due to poor requirements management. Source: Project Management Institute (PMI) (2014) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- This World Bank report argues that digital technology adoption raises SME competitiveness, productivity and resilience, while documenting that smaller firms consistently lag larger ones in digital adoption - a gap that constrains their growth and market reach. Source: World Bank (2022) →
Frequently asked questions
What does it cost to switch off Intapp Conflicts or a similar product?
The migration itself is rarely the hard part, because clearance decisions are historical records rather than live state. The hard part is that your resolved parties, aliases and any corporate family links you built inside the product need to come out in a structured form, and the value of those took years to accumulate.
Ask for a sample export covering parties with aliases, matters, clearance decisions with their reasons, and any wall records with acknowledgements, and confirm you can generate it yourself. Retention expectations here run long, because a decision may be challenged years later.
What happens if our conflicts vendor raises prices at renewal?
Your position depends almost entirely on where your rule chains live. If they are encoded in a vendor's configuration and your general counsel cannot describe them without opening the product, a renewal conversation is short.
Two practical steps. Keep a written statement of your rule chains outside the system, maintained by the general counsel or independence office, so the knowledge is yours rather than the product's. And model per user pricing against your real population, since fee earners, conflicts staff, finance and risk all touch intake and the seat count is usually larger than the initial quote assumed.
How long does a clearance build take?
Fourteen to twenty weeks for a first release. The pacing item is almost always data: reconciling years of inconsistently recorded clients, matters and parties into a resolved entity graph, plus agreeing rule chains with the general counsel or independence office.
Firms that have already run a data cleanup, or that limit release one to one office and one practice line, move noticeably faster than firms trying to model the whole partnership at once. Rule chains are usually held as practice rather than documentation, and eliciting them during build is expensive elapsed time.
Is Intapp Conflicts enough for a firm with an audit line?
It handles structured intake, searching firm records, workflow and approvals properly, and firms run it successfully. The limits worth testing yourself are three. Whether it expresses rule chains that differ by office, jurisdiction and engagement type without configuration becoming a permanent role. Whether declaring a wall provisions restrictions in iManage or NetDocuments rather than setting a status. And whether independence obligations fit its model.
That last one is the specific issue for audit firms. Restricted entity lists, personal holdings declarations, service pre approvals and cooling off periods form a second rule model over the same entity graph, and it grew up separately from legal conflicts.
Why does historical data reconciliation cost so much?
Because it is the work that produces precision, and there is no shortcut. The same entity is recorded four ways because four generations of staff opened matters over fifteen years, so names have to be normalised, aliases stored, external references such as company registry numbers attached, and parties joined to corporate family data.
Expect $30,000 to $70,000 depending on record volume and quality. Skipping it gives you a faster search over the same noisy data, and reviewers still read hundreds of hits. Running a cleanup before the build rather than inside it lowers the figure meaningfully.
Can we build only the scoring layer and keep our existing product?
Yes, and for most firms it is the sensible first move. The resolution and scoring layer sits beside the packaged product, normalises and resolves parties, joins corporate family data and hands reviewers a ranked list with plain language reasons before they open anything.
Your approval workflow, your decision records and your staff training stay where they are. It also produces the before and after number that makes any later phase fundable, which is why we recommend taking a fifty clearance baseline measurement before a line of code is written.
Can machine assistance make the clearance decision itself?
No, and any vendor suggesting otherwise should worry you. The decision stays with a human who holds the authority, and the system's job is to hand that person a ranked, evidenced queue plus a frozen record of what was known at the time.
Where machine assistance genuinely reduces workload is narrower and useful: classifying party roles from a matter description, spotting that two spellings are the same entity, and extracting parties from an engagement letter or term sheet. All of that feeds resolution and scoring rather than replacing judgement.
What does ethical wall provisioning add, and can it wait?
Typically $70,000 to $160,000 as phase two, and yes it should wait, because a wall provisioned against an unresolved party is a control applied to the wrong entity. Data and scoring first, enforcement second.
What it buys is a wall as an executable object: declaring it provisions restrictions through document and practice management systems, collects acknowledgements, logs access attempts by screened personnel and runs periodic attestations, with the evidence pack generated rather than assembled. Firms that have been through a disqualification motion buy this without being asked twice.
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 my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
How do I calculate the ROI of a custom internal tool?
Count hours first: multiply the weekly hours staff spend on the manual process by their loaded hourly cost, then add the cost of errors such as mispriced quotes or missed renewals. A tool saving a 10-person team 5 hours each per week recovers about 2,500 hours a year, which repays a $20,000 to $30,000 build well inside a year at typical wages. Most internal tools Digital Heroes delivers reach payback in 6 to 18 months, with quoting and billing tools at the fast end because they plug revenue leaks, not just time.
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 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.
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.
How many developers does it take to build an internal tool?
Two to four people covers nearly every internal tool: one or two developers, a part-time designer, and a project manager who doubles as your single point of contact. Internal tools rarely need consumer-product polish, so a full-time dedicated designer is usually wasted budget. On Digital Heroes projects, a two-person core team handles the typical 4 to 8 week build, with a specialist pulled in briefly for a tricky integration or a security review.
Should we build the whole internal tool at once or start with an MVP?
Start with a version that fully replaces one workflow, ship it in 4 to 6 weeks, and let real usage set the roadmap. Internal tools have a captive audience, so you learn within days which features matter, and across Digital Heroes projects roughly a third of initially requested features never get built once staff work with version one. Phasing also spreads the spend: a $40,000 vision becomes a $15,000 phase one that starts paying for itself while phase two is scoped.
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 Saanvi.
Senior Shopify Engineer · B2B · Delhi · 1 post on the site
Published · Last updated .
