How Much Does Asset Liability Management Software Cost in 2026?
Custom asset liability management software runs $95,000 to $650,000, and the variable that moves the number most is what your core banking system will actually expose. Balance, rate and maturity are easy.
On this page
Custom asset liability management software runs $95,000 to $650,000, and the variable that moves the number most is what your core banking system will actually expose. Balance, rate and maturity are easy. Rate floors, caps, reset index, lookback convention, amortisation type and prepayment penalty schedules are the attributes that make a cash flow real, and some cores will not release them without a custom report. If yours will not, you are funding a data acquisition project before any modelling starts, and that can be a quarter of the budget. Find out first.
The bands an asset liability management build falls into
The first release band is $95,000 to $210,000 over 16 to 22 weeks. That covers instrument level extraction and contractual cash flow generation, an assumption registry with versioning and approval, and net interest income plus economic value simulation across the standard shock set with drill down to the instruments driving each result. It is the release that turns the monthly committee package from a workbook into something reproducible.
The full platform band is $250,000 to $650,000 phased over 9 to 16 months. That adds behavioural deposit estimation from your own account history, back testing with variance decomposition, liquidity and funding concentration scenarios, board and committee reporting, and a validation evidence pack assembled as a by product rather than a project.
There is a narrower opening move that suits institutions with a specific finding to close. The assumption registry and behavioural deposit estimation alone, feeding your existing model rather than replacing it, runs $45,000 to $85,000 over ten to thirteen weeks. It produces the artefact a validator opens with, which is evidence that your deposit beta came from a regression on your own accounts rather than from a citation.
What drives an asset liability management build up
Core extract quality is first and occasionally it is the whole project. If floors, caps, reset conventions and penalty schedules are not available through a standard extract, someone has to build the report, negotiate the access or reconstruct the attributes from loan documents, and none of those is a week.
Investment portfolio complexity is second. A portfolio of plain agency and municipal holdings is straightforward. Structured securities need external cash flow projections rather than internally generated ones, which brings a data provider and a reconciliation into scope.
Derivatives are third. A swap portfolio pulls hedge accounting, collateral and counterparty exposure into the model, and each of those is a distinct piece of work with its own reviewers.
Multiple charters or a recent acquisition is fourth. Two cores means two extraction pipelines plus a reconciliation between them, and the reconciliation is usually harder than either pipeline.
Validation expectations are fifth. A team that treats the technical specification, estimation evidence and back testing as deliverables prices differently from one that treats them as documentation to write later, and the second team is not actually cheaper.
What keeps the number down
Do loans and non maturity deposits properly in phase one and use vendor supplied cash flows for the investment portfolio until phase two. That covers the part of the balance sheet where your risk actually lives, and it is where a validator will look first.
Estimate behavioural assumptions for your largest deposit products only in the first pass. A blended assumption across everything hides the segmentation that matters, but you do not need every product segmented on day one to fix that.
Leave liquidity to phase two. It shares most of the plumbing with interest rate risk, so building it later is efficient rather than wasteful, and the instrument level cash flows you build first feed both.
Do not reimplement your core's amortisation logic if you can extract the schedule. Reproducing amortisation from terms is a source of small persistent differences that consume weeks of reconciliation for no analytical gain.
Run parallel for two committee cycles rather than four. Two is enough to find what the old model was quietly excluding, and each additional cycle is duplicated staff effort.
A worked example that adds up
A community bank with roughly $2.6B in assets, one core, a conventional investment portfolio, no derivatives, and non maturity deposits making up a majority of funding.
- Discovery, including a data availability assessment against the core and a review of the current workbook: $14,000
- Instrument extraction and record model covering floors, caps, index, reset, lookback and amortisation type: $38,000
- Contractual cash flow generation per instrument with reconciliation against general ledger balances: $31,000
- Assumption registry with versioning, owner, estimation window and approval state: $19,000
- Net interest income and economic value simulation across the standard shock set, with instrument level drill down: $34,000
- Parallel running support across two committee cycles, testing and treasury training: $16,000
That totals $152,000, in the middle of the first release band, with extraction and cash flow generation carrying nearly half. An institution whose core exposes the full attribute set cleanly lands nearer $100,000. Adding behavioural deposit estimation, back testing, liquidity scenarios, committee reporting and the validation pack takes the same bank to roughly $330,000 to $420,000 in total across the following year.
How the spend phases
Discovery is two to three weeks and around 9 percent, and in this category it must include a genuine data availability assessment. Pull a real extract, check which attributes are present, and count how many loans are missing a floor or a reset convention. That count sets the price of everything after it.
Instrument extraction is the largest first release line at roughly 25 percent, weeks three to eleven. Where attributes are missing, the plan has to say explicitly how they will be sourced rather than assuming a default.
Cash flow generation is around 20 percent, weeks eight to fifteen, and it should reconcile to the general ledger before anything else is built on it.
The assumption registry is around 13 percent and is cheap relative to what it enables, since it is the artefact a validator opens with.
Simulation is roughly 22 percent, weeks thirteen to twenty. Instrument level drill down is the feature that changes how a treasurer uses the output, so it belongs in phase one rather than being deferred.
Parallel running, testing and training take the remaining 11 percent. Do not schedule the cutover in the same quarter as an examination.
The ongoing costs nobody quotes
Compute for the monthly run is modest in absolute terms and spiky in shape, because a full instrument level revaluation across several scenario sets is a burst rather than steady load. Typically $400 to $1,500 a month at this asset size, and it scales with scenario count rather than with balance sheet size.
Immutable run storage grows every cycle by design, because reproducibility means never overwriting. Each run keeps its instrument snapshot, assumption version and outputs, and that is the point rather than a defect.
Market data and index history is a subscription that continues. It is small relative to the build and it is not optional.
Assumption re estimation is a recurring analytical task rather than a software cost, but it belongs in the plan. Behavioural assumptions need refreshing as the rate environment moves, and an assumption estimated once in a single cycle is exactly the weakness you built the system to remove.
Support and enhancement typically runs 12 to 18 percent of build cost annually, with a spike in any year you add a charter, a derivative programme or a new product type.
Comparing a build against your current renewal
If you licence Abrigo, ZM Financial Systems, Empyrean Solutions, Quantitative Risk Management or Moody's Analytics, that renewal is a fair line to start from, and for many institutions it wins outright. These are capable engines and the calculation is rarely the reason to build.
The honest comparison is broader. Add the treasurer or analyst time spent rebuilding the committee package each month, which at most institutions is one named person and a known number of days. Add the consultant fees for the last deposit study, which is the assumption a validator will question hardest. Add whatever your last validation cost, plus the remediation if it produced findings on assumption documentation or the absence of back testing.
Then ask the question that actually decides it: can you reproduce the package from two quarters ago from data, or only show the file that was distributed? If the answer is the second, the vendor renewal is not solving your problem, because the engine was never the weak point. The assumptions, the instrument detail and the reproducibility are institution specific, they are precisely what validation examines, and every vendor leaves them as your homework.
When buying beats building
Buy if you are under roughly $700M in assets with a conventional balance sheet, no derivatives, a simple deposit book and no acquisitions pending. Abrigo, ZM Financial Systems or an outsourced modelling service will produce a defensible package for a fraction of a build, and an examiner will be satisfied with it.
Buy if your constraint is people rather than software. A model you cannot staff is worse than a service you can, and owning a system nobody in the building can explain is a worse position than renting one a vendor will explain for you.
Build when two or more of these are true. Your loan book has embedded options that your current model buckets away, so a portfolio with binding caps looks more asset sensitive than it is. Non maturity deposits are more than half your funding and your betas are borrowed rather than estimated from your own history. You cannot reproduce a prior run from data. Your last validation or examination produced findings on assumption documentation or the absence of back testing. Or your treasurer needs the model to answer strategy questions about funding and pricing rather than to produce a compliance table each month.
The engine is rarely the reason to build. The reason to build is that a model you cannot open, explain line by line and modify is not defensible in a validation review, regardless of how good the mathematics happens to be.
When the shortlist is down to two and you need a tiebreaker, 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. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
- Poor software quality cost the US economy an estimated $2.41 trillion in 2022, including roughly $1.52 trillion in accumulated technical debt, driven partly by unsuccessful development projects and low-quality legacy systems. Source: Consortium for Information & Software Quality (CISQ) - Herb Krasner (2022) →
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
Frequently asked questions
What is the total cost of custom asset liability management software?
A first release with instrument level cash flow generation, a versioned assumption registry and net interest income plus economic value simulation across standard rate shocks runs $95,000 to $210,000 over 16 to 22 weeks in our delivery experience. A full platform adding behavioural deposit estimation, back testing, liquidity scenarios and a validation evidence pack runs $250,000 to $650,000 over 9 to 16 months.
The biggest single variable is how much instrument detail your core will expose.
What does an asset liability model cost to run each year?
Compute for the monthly run is modest and spiky, typically $400 to $1,500 a month at a few billion in assets, scaling with scenario count rather than balance sheet size. Immutable run storage grows every cycle by design, since reproducibility means never overwriting a prior run.
Market data and index history is a continuing subscription. Support and enhancement runs 12 to 18 percent of build cost annually, with a spike in any year you add a charter or a new product type.
How long does it take to build, and can we run it in parallel?
Sixteen to 22 weeks for a first release, and you should run it in parallel for at least two committee cycles. Parallel running is where you find that the old model was quietly excluding a loan category or applying a stale prepayment vector.
Reconciling the two is genuinely useful rather than an overhead, but do not schedule the cutover in the same quarter as an examination.
Is Abrigo or ZM Financial Systems cheaper than building?
Yes, and for an institution under roughly $700 million with a plain balance sheet, no derivatives and a simple deposit book, buying is the better answer and a vendor model will satisfy an examiner.
These are capable engines. The limitation is that the engine is only as good as your instrument data and your assumptions, and both remain your responsibility on any platform. Institutions build when the assumptions, the embedded options and reproducibility are the actual problem.
Why does the core extract drive so much of the price?
Because balance, rate and maturity are easy and everything that shapes a real cash flow is not. Floors, caps, reset index, lookback convention, amortisation type and prepayment penalty schedules are what make a projection more than an approximation, and some cores will not release them without a custom report.
Pull a real extract during discovery and count how many loans are missing a floor or a reset convention. That count sets the price of the rest of the project.
Can we build just the deposit assumption work first?
Yes, and it is often the highest value opening move. An assumption registry plus behavioural deposit estimation from your own account level history, feeding your existing model rather than replacing it, runs $45,000 to $85,000 over ten to thirteen weeks.
It produces the artefact a validator opens with, which is a regression on your own accounts through an actual rate cycle rather than an industry average or a consultant study from a different environment.
How much does back testing add to the budget?
Typically $30,000 to $55,000, and most of that cost is the immutable run architecture rather than the comparison itself. Every run has to store the instrument snapshot, the assumption version, the scenario definitions and the code version so a run from four quarters ago can be compared against what the general ledger actually recorded.
The variance decomposition into volume, rate and behaviour effects is what makes the result usable, and it is the strongest evidence a model can offer that it is monitored.
Should liquidity be in scope from the start?
It shares most of the plumbing, so building interest rate risk first and adding liquidity in phase two is efficient rather than wasteful. Instrument level cash flows feed both a repricing view and a maturity ladder, and deposit behaviour assumptions serve both.
Liquidity adds funding concentration analysis and contingency scenarios, typically $50,000 to $110,000, including what happens if your largest depositors move a meaningful share of balances in a month.
What is the cheapest credible version of this system?
Around $95,000 for an institution whose core exposes the full instrument attribute set cleanly, with a conventional investment portfolio and no derivatives. That buys instrument extraction, contractual cash flow generation, the assumption registry and simulation across the standard shock set.
Be sceptical of a cheaper quote from anyone who describes a screen before they describe an instrument record. If floors, caps, index and reset conventions do not come up unprompted, the cash flows will be approximations wearing a good interface.
What do I need to prepare before contacting an agency about a dashboard project?
Bring three things: a list of your data sources with who controls access to each, the 5 to 10 recurring decisions the dashboard should support, and examples of the reports or spreadsheets it will replace. That package lets an agency quote in days instead of weeks, and in our discovery work it cuts the audit phase roughly in half. You do not need wireframes or a technical spec; a good agency produces those with you.
How long does it take to build a custom BI dashboard?
A working first version usually ships in 4 to 8 weeks, and a full production build with multiple integrations and permissions takes 3 to 6 months. In Digital Heroes delivery experience, schedules slip on data access, meaning credentials, API approvals, and cleanup of source data, far more often than on the dashboard screens themselves. Lining up access to every data source before kickoff routinely saves 2 to 3 weeks.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
Can one dashboard pull from QuickBooks, Salesforce, and Google Analytics at the same time?
Yes, and combining sources like that is the main reason to build custom instead of living inside each tool's built-in reports. The standard pattern syncs each source into one warehouse using connectors such as Fivetran or Airbyte, then joins them there, so marketing spend, pipeline, and revenue finally sit in a single view. Each additional source typically adds 1 to 2 weeks to the build, mostly for field mapping and reconciliation.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
Will a custom dashboard stay fast once our data hits millions of rows?
Yes, if it aggregates before it displays; no dashboard should scan millions of raw rows on every page load. The standard techniques are pre-aggregated summary tables, incremental refresh, and caching, which keep typical page loads under 2 seconds even on datasets in the hundreds of millions of rows. Ask your vendor how the dashboard behaves at 10 times your current data volume; a good one gives a specific answer about aggregation, not just a bigger server.
How does a custom dashboard handle compliance requirements like SOC 2, HIPAA, or GDPR?
A custom build gives you direct control over the controls auditors ask about: single sign-on, role-based access, audit logs, encryption, data residency, and deletion workflows. For HIPAA specifically, you can keep protected health information inside your own cloud account under a business associate agreement with your host instead of trusting a third-party BI vendor's handling. Expect compliance work to add 2 to 4 weeks and roughly 10 to 15 percent to the build, so raise it in the first conversation, not after design is done.
What are the most common mistakes companies make on dashboard projects?
The four we see most: designing charts before modeling the data, cramming 30 metrics onto one screen so nothing stands out, letting every team define revenue slightly differently, and skipping data quality checks so the dashboard confidently displays wrong numbers. The wrong-numbers failure is the fatal one, because a dashboard loses trust once and never fully earns it back. Spend the first weeks on metric definitions and data quality, not on colors.
Why do BI dashboard quotes range from $25k to $200k for what sounds like the same project?
Four variables move the price: how many data sources you connect and how messy they are, real-time versus daily refresh, permission complexity, and whether outside customers will log in. A three-source internal dashboard with daily refresh sits near the bottom of that range, while a customer-facing product with row-level security and live data sits near the top. Wildly different quotes are usually pricing different assumptions about those four things, so pin them down in writing before comparing.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards 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 business intelligence dashboards 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 .
