Financial Crime Case Management: Build Custom or Buy Verafin, Abrigo, Unit21 or Hummingbird
The threshold is retrieval time per case, not filing volume. If your investigators lose more than an hour per case pulling evidence from systems no vendor will integrate with on your timeline, the build case is real.
On this page
The threshold is retrieval time per case, not filing volume. If your investigators lose more than an hour per case pulling evidence from systems no vendor will integrate with on your timeline, the build case is real. If they lose ten minutes because your product set is conventional and your case tool already reaches it, buy and spend the effort on narrative standards instead. Most community banks and credit unions sit on the buy side and should stay there. When building is right, the first release runs $80,000 to $180,000 over 12 to 16 weeks, and the number is driven by how many internal source systems you connect rather than by how many reports you file.
When is off the shelf genuinely the right call here?
Buy if you are a community bank or credit union filing a modest number of suspicious activity reports with a conventional product set. Verafin and Abrigo were built around institutions of exactly that shape, they carry integrated filing, and integrated filing is worth a lot. A build will not beat them at that profile and will take a year to reach parity with something you already have running.
Buy NICE Actimize if you need enterprise breadth across many detection domains and have the configuration capacity to match. That last clause matters more than the first. Actimize covers a great deal of ground and expects an internal team able to configure it, so the honest question is whether you have that capacity rather than whether the product has the coverage.
Buy Unit21 or Hummingbird if your priority is investigator experience and you can live within their case model. Both are genuinely well built modern tools with a working environment far ahead of the older generation, and they will have your team running in weeks rather than months.
The thing to be clear eyed about with all of them is what buying does not remove. Each imposes a case model and a set of assumptions about your data, and connecting your own core banking platform, card system, lending system, wire application and support desk remains your work and your cost either way. If most of your retrieval time comes from systems the vendor does not reach, buying a better case tool improves the writing experience and leaves the two hours in place. That is a fair trade at low volume and a poor one at high volume, which is the whole decision in one sentence.
When does a custom build actually pay off?
Build when two or more of these are true. Your investigators lose more than an hour per case to retrieval across systems no vendor will integrate with on your timeline. Your case types include activity vendor models handle poorly, such as sub merchant flows, digital asset movement, or partner banking programmes where the customer of your customer is the subject. You have had a finding on timeliness or on continuing activity. You file across more than one jurisdiction. Or a look back review has already shown you cannot reproduce filings and their supporting evidence reliably.
That last one usually decides it without any arithmetic. Submitting a report is not the hard part. The hard part arrives three years later when a review or a subpoena asks you to produce the filing, the evidence it rested on, the analysis supporting the conclusion, who approved it and when, and what happened to the customer afterwards. If the answer is a shared drive folder and an investigator who has since left, the exposure is already priced into your operation whether or not it appears in a budget.
The design distinction that separates a real build from an expensive one is reference against copy. When an investigator pastes transaction detail into a document, that copy becomes the record. It is unlinked, it cannot be refreshed, and if the underlying data is later corrected the case still shows the old figures with no indication anything changed. A proper build holds pointers into your own systems, renders them into the working view, and snapshots the rendered evidence at the moment of filing so the package is frozen while live links remain for open cases.
How do they compare on the things that matter in this industry?
- Evidence assembly. This is the real comparison. A bought tool attaches what you give it. A build assembles from your own sources, which is where the hour per case goes. Ask any vendor precisely which of your systems they will read from and on what timeline before you compare anything else.
- Reproducibility. Frozen packages at filing, with live references retained for open cases, is roughly $18,000 of a build of this shape and it is the line we would refuse to cut. Check whether your current tool can produce a three year old filing exactly as it stood, including the analysis, the approver and the timestamps.
- Confidentiality as a control. Disclosing the existence of a filing to the subject is prohibited, so case level access control with a full access log is a control rather than a setting. This is the strongest argument against running cases in a general purpose ticketing tool, where visibility defaults are permissive and can change with a vendor upgrade you did not schedule.
- Continuing activity. Most tools leave the trigger as a date in someone's calendar. The person who set it changes teams and the review is missed. A build creates the review automatically at filing, with an owner, a due date and the transactions since the last filing pre assembled.
- Per seat economics. Note whether seats are the pricing unit in your renewal, because that determines what team growth costs you over three years. A build carries a maintenance line rather than a headcount multiplier.
- Data portability. Case history is a regulatory record you must retain and produce for years. Any arrangement where your filing history sits in a tenancy you cannot fully export from should be refused, bought or built.
What does total cost of ownership look like at your scale?
Take a mid sized institution with a growing partner banking programme whose investigators currently assemble packages from four systems by hand. They connect all four in release one because retrieval time is the whole problem. Discovery, evidence template definition and narrative standard capture with the Bank Secrecy Act officer is $12,000. The case object holding references to alerts, customers, transactions and related parties, with rendered evidence views, is $30,000. Four source system connectors at roughly $11,000 each is $44,000. The structured narrative with required sections by case type and a reviewer gap check is $22,000. Approval workflow with the internal deadline computed from the detection date rather than the case open date is $14,000. Frozen filing packages with retrieval tooling is $18,000. Case level access control with a full access log is $16,000. Infrastructure and independent security review is $9,000. That totals $165,000.
Phase two, meaning continuing activity scheduling, quality assurance sampling and link analysis across related subjects, is roughly $70,000 to $140,000 and moves the programme into the upper band.
Running costs are 15 to 20 percent of build cost a year in Digital Heroes delivery experience, weighted towards connector maintenance. Core banking upgrades, card platform migrations and lending system changes all touch connectors, and each one becomes a small piece of work you now own. Retention storage grows continuously and does not stop, because frozen packages must stay accessible for the full window whether or not the case is active. Access reviews recur on your own policy cycle, since confidentiality is a control somebody has to periodically confirm.
What does the hybrid look like, and when is it the honest answer?
The hybrid here is unusually clean, and for a large share of institutions it is the right answer. Keep your existing alert sources. Rebuilding detection alongside case management is how a sixteen week project becomes a year, and detection tuning is a separate discipline with a separate evidence base. Keep integrated filing wherever you already have it. Then build only the evidence assembly layer that feeds whichever case tool you are using.
Concretely, that means connectors into your core, cards, lending and support systems that produce a consistent, referenced evidence package per subject, delivered into the case tool your investigators already work in. You are buying the workflow, the narrative environment and the filing path, and building the part no vendor will build for you on your timeline. Connect the two systems supplying most of the evidence first. In most institutions the core banking platform and the transaction store together cover the majority of what goes into a package, and the remaining systems contribute detail rather than substance.
There is also a cheaper tier that is genuinely useful and should not be confused with either option. A case tracker, meaning a workflow with statuses, owners and deadlines but no evidence assembly, costs $30,000 to $55,000. It fixes timeliness and none of the assembly problem. If a quote sits far below the first release band, that is what you are being offered, so check whether evidence is being assembled or merely attached.
One piece of work pays for itself whatever you decide: writing down your narrative standard as required sections by case type. Most institutions hold it as a training document and a review habit. Your Bank Secrecy Act officer can turn it into a specification in a fortnight, and it improves your existing process immediately whether or not you build anything.
Which should you choose, by operator size and stage?
Community bank or credit union, conventional product set, modest monthly volume. Buy Verafin or Abrigo and stop. Put your effort into narrative standards and evidence templates inside the tool you already pay for. That effort is cheap, immediate and is where the quality of your filings actually improves.
Regional bank with a partner banking or sponsor programme. This is where vendor case models start to strain, because the subject is often the customer of your customer and the evidence sits across systems the vendor does not reach. Hybrid first: keep the case tool, build the connectors and the referenced evidence package. Escalate to a full build only once retrieval time is solved and reproducibility is still failing.
Payments or digital asset firm with non standard typologies. Build, and build the case object properly from the first commit with reference rather than copy. Vendor models were not designed around your flows, and forcing them tends to produce a package that reads well and cannot be reconstructed.
Multi entity group filing across more than one jurisdiction. Full platform, phased across seven to fourteen months. Different regimes need different packages built from the same evidence, with different narrative requirements and different retention rules, which is a second output path rather than a template change. Scope phase two after a quarter of live use, and sample cases closed without filing alongside filed ones. A pattern of no filing decisions on a particular typology is precisely what a look back review exists to surface.
If you want a second opinion before signing anything, 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) →
- This analysis cites IDC research that companies lose 20-30% of revenue annually to inefficiencies caused by data silos, Gartner's estimate that poor data quality costs organizations at least $12.9 million per year on average, and a Salesforce benchmark that 80% of IT leaders say data silos hinder digital transformation - illustrating the business case for integrating systems. Source: Cherry Bekaert (citing IDC, Gartner, Salesforce, DATAVERSITY) (2024) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
Frequently asked questions
What does it cost to switch off Verafin or Abrigo once we have built?
The switch itself is less painful than the retention obligation around it. Case history is a regulatory record you must keep accessible for years, so plan to keep the legacy system queryable for the retention window rather than migrating everything. We generally advise against migrating cases beyond that window, because cases whose evidence links no longer resolve produce a record that looks complete and is not. Run both in parallel for a few weeks before relying on the new one, which is the only reliable way to find a field your policy assumed was populated.
What happens if our case vendor raises prices or changes its seat model?
Check whether seats are the pricing unit in your current renewal, because that determines what growth costs you over three years, and a financial crime team usually grows with the business rather than shrinking. The hybrid position is the practical hedge: once the evidence assembly layer and the connectors belong to you, the case tool becomes a workflow you could replace rather than the place your institution's investigative memory lives. That is where your bargaining power at renewal actually comes from.
How long does the first release take?
Twelve to sixteen weeks, with discovery in front of it. Weeks one to eight build the case object and the first two connectors, which is where retrieval time starts falling, and weeks nine to sixteen add the remaining connectors, the structured narrative, approval workflow and the frozen filing package. Budget investigator time for a parallel run before you rely on it, because that is when you discover the data quality problems nobody had a reason to notice before.
Are Unit21 or Hummingbird a better answer than building?
For many institutions, yes. Both are well built modern case tools with an investigator experience far ahead of the older generation, and they will get you running far faster than any build. The constraint is that they impose a case model and assumptions about your data, so connecting your core, cards, lending and support systems is still your work and your cost. If most of your hour per case comes from those systems, the tool improves the writing and leaves the retrieval where it was.
What does a single source system connector cost?
Roughly $11,000 as a planning figure, with a wide range because the cost sits in the data quality conversation rather than the code. A well documented system with a stable interface is at the lower end, and a system whose identifiers do not match anything else in the institution sits well above it. Count your systems honestly before taking any quote, including the ones investigators open in a browser rather than query, because those are the ones that never make it into scope.
How does the software handle the 30 day filing deadline?
By computing the internal deadline from the detection date rather than from the date someone opened the case, then driving the approval workflow from it. A suspicious activity report is due within 30 calendar days of initial detection of facts that may form a basis for filing, extended to 60 where no subject has been identified, with continuing activity reviewed on a rolling basis. Timeliness is objectively measurable, which is why it is usually the first thing an examiner tests.
Can we keep our existing alerting and only build the case side?
Yes, and you should. Rebuilding detection alongside case management is the most common way a sixteen week project becomes a year, and detection tuning is a separate discipline with its own evidence base and its own tuning history you do not want to discard. Take your alerts as an input, build the case object and the evidence assembly behind it, and revisit detection as a wholly separate decision once investigators are working in a system that shows its working.
Where does artificial intelligence help in an investigation workflow?
In two supervised places: drafting the factual sections of a narrative from structured evidence so the investigator edits rather than types, and checking a completed narrative for missing required elements before it reaches a reviewer. What it must not do is form the suspicion or make the filing decision, because that judgement has to be attributable to a named person under your policy and defensible years later. Treat it as a drafting assistant with a human accountable for every word filed.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
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.
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.
When does a company outgrow Airtable?
The usual breaking points are record limits, permissions, and automation complexity. Airtable's Team plan caps each base at 50,000 records and Business at 125,000, so operations logging thousands of rows a month hit the ceiling within a year or two. The other trigger Digital Heroes sees constantly is permissions: restricting who can view specific fields or records is clumsy below Airtable's Enterprise tier, which becomes a genuine problem once salaries, pricing, or client contracts live in the base.
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.
What tech stack should an internal tool be built with?
Boring and popular: a React or Next.js frontend, a Node.js or Python backend, and PostgreSQL covers the vast majority of internal tools and keeps future hiring easy. The stack matters far less than whether a different developer can pick the code up in two years, so require documentation as a deliverable and avoid anything exotic. Treat it as a red flag if an agency pushes a proprietary platform only they maintain, because that quietly converts your tool into a subscription to that agency.
What should I prepare before contacting an agency about an internal tool?
Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.
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.
Can a custom internal tool connect to QuickBooks, Salesforce, and the other software we already use?
Yes, and integrations are usually the strongest argument for going custom instead of chaining tools together with Zapier. QuickBooks, Salesforce, Shopify, Stripe, Slack, and Google Workspace all have mature APIs, and each integration typically adds $1,500 to $5,000 to a Digital Heroes build depending on how much two-way syncing you need. The honest caveat is legacy industry software without an API, which may need file-based imports instead of a live connection, so list every system in the first conversation.
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
Published · Last updated .
