How Much Does Mortgage Pipeline Hedging Software Cost in 2026?
$70,000 to $500,000, and the decision that moves it most is whether you retain servicing. Released servicing means best execution compares a service release premium against delivery, which is arithmetic.
On this page
$70,000 to $500,000, and the decision that moves it most is whether you retain servicing. Released servicing means best execution compares a service release premium against delivery, which is arithmetic. Retained servicing means valuing a servicing asset against prepayment expectations, and that is a genuine analytics workstream with its own data, its own assumptions and its own auditor conversation. A decision layer over a bought pricing engine, servicing released, lands at $70,000 to $150,000 in 10 to 16 weeks. Retained servicing, trade capture and profit and loss attribution push you into the $200,000 to $500,000 band over 8 to 14 months.
The bands a secondary marketing build falls into
The thin layer is the one most independent mortgage banks should buy. It sits on top of a pricing engine you keep, and it covers four things: an event driven position where every lock, change, cancellation, fallout and funding updates the requirement immediately, a loan level pull through model trained on your own funded history, best execution across only the outlets you are actually approved for, and a lock desk exception ledger. That runs $70,000 to $150,000 and ships in 10 to 16 weeks in our delivery experience.
The full desk platform adds trade capture with pair offs, margin call tracking against your broker dealer counterparties, reconciliation to their statements, investor commitment management and daily profit and loss attribution. That runs $200,000 to $500,000 phased over 8 to 14 months.
Our position on this category is unusual for a development firm: most lenders should never spend the second number. Keep the bought pricing engine, build only the decision layer, and revisit in two years. Rate sheet generation, investor pricing ingestion and loan level pricing adjustment maintenance are a permanent treadmill and no lender gains an edge by owning them.
What drives a secondary marketing build up
Retained servicing, as above, and it is worth being blunt about why. Once servicing is retained, best execution has to price the servicing asset, the buy up and buy down grid changes the coupon and therefore the pool a loan can enter, and every mark carries an assumption your auditor will ask about. That is not a feature, it is a second discipline inside the same project.
Delivery outlet count is second. Cash window, securitisation into pools, correspondent whole loan sale, assignment of trade, balance sheet, each with its own commitment structure and its own terms. Nine outlets is nine modelling problems, and the marginal ones are the awkward ones.
Broker dealer counterparty count is third, because each statement format is separate reconciliation work. Three counterparties means three reconciliations that have to agree with your own trade records, and a mismatch that nobody investigates is how a margin call surprises a desk.
The quality of your historical lock data is fourth and it is the one that ambushes projects. If your loan origination system never recorded the market level at the moment of lock, the model cannot learn rate incentive, and reconstructing that history from archived rate sheets is real weeks of work before any modelling begins.
What keeps the number down
Keep the pricing engine. Optimal Blue or Polly stays in the stack and you build above it. That single decision removes the largest and least differentiating chunk of scope in the category.
Start the pull through model on servicing released execution only. Get the coverage right first, with the position event driven and the model backtested, then add servicing valuation as phase two once the desk trusts the coverage number.
Restrict best execution to the outlets you genuinely deliver into today. Lenders routinely ask for every theoretical outlet modelled. If you have not delivered into an outlet in the last four quarters, leave it out and add it when you actually get approved. Each outlet you drop removes a commitment structure, a set of margin rules and a test suite from the estimate.
Build the exception ledger early even though it looks trivial. It is cheap, it needs no market data, and in most shops it is the feature that pays for the project, because nobody currently attributes the cost of extensions, relocks and renegotiations back to the branch or originator who asked.
A worked example that adds up
An independent mortgage bank originating roughly $280M a month, conventional agency plus some jumbo, servicing released today with a retention decision pending, nine delivery outlets, three broker dealer counterparties, keeping its existing pricing engine and pulling locks from Encompass. Here is the decision layer priced line by line.
- Event driven position fed from live lock, change, cancellation and funding events: $26,000
- Loan level pull through model trained on your own lock and funding history, with rate incentive recomputed live: $34,000
- Best execution across nine outlets including specified pool payups and commitment terms: $32,000
- Hedge recommendation by coupon and settlement month with coverage ratio and shock analysis: $18,000
- Lock desk exception ledger with amounts, approvers and attribution to branch and originator: $14,000
That totals $124,000, in the upper half of the thin layer band, which is where a desk at this volume with nine outlets normally sits. If your lock history lacks the market level at lock, add a data reconstruction phase before the $34,000 model line, and expect that phase to be measured in weeks rather than days.
Price it against one basis point on the pipeline. A desk at $280M a month carries roughly twice that in open commitments at any moment, and the arithmetic on a single bad morning is not a projection your board needs help with.
How the spend phases
Data assessment comes first and it decides everything else. Before any modelling, someone establishes whether your funded loan history contains the market level at lock, whether fallout is recorded cleanly, and whether channel, lock term and purpose are reliable fields. Roughly 10 percent of the budget, and it is the phase that most often changes the plan.
The event driven position and the exception ledger come next, because both deliver value without any model behind them. Your desk sees a current position instead of a morning export, and your margin reporting starts attributing exception cost immediately. That is usually a third of the spend and the fastest payback in the project.
The pull through model and best execution take the remaining budget and the most calendar. Validation matters more than construction: hold out a period of your own funded history, backtest the coverage the model would have recommended against what actually funded, and show error by rate incentive bucket. A model that reports accuracy without connecting to hedge coverage has not been validated.
The ongoing costs nobody quotes
Model maintenance is the recurring line. Pull through behaviour shifts with the rate environment, the channel mix and your own loan officer population, so the model needs periodic retraining and a monitoring view that shows when its error is drifting. Budget that as scheduled work rather than as a defect response.
Market data and pricing feeds continue as they are. A build does not reduce your data costs, and if anything a system that computes best execution across more outlets consumes more of them.
Plan 15 to 20 percent of the build cost per year across hosting, monitoring, integration upkeep and enhancements, and add the audit support cost. Rate lock commitments and forward sale commitments are carried at fair value, so somebody has to produce mark derivations every period. Designing that in makes it cheap. Retrofitting it makes it an annual scramble.
Comparing a build against your current renewal
Do not compare it against your pricing engine subscription, because you are keeping that. Compare it against the three things the build actually replaces: your hedge advisory fee if you pay one, the analyst hours consumed by the daily export and spreadsheet cycle, and the cost of the lag itself.
The lag is the number nobody computes and it is the largest. Take your average time between a lock arriving and the hedge being adjusted, take your open commitment balance, and ask your risk officer what a typical adverse intraday move against the unhedged portion is worth. Do it for the worst five days of last year rather than the average, because the average is not what hurts you.
Then add the exception cost you cannot currently see. Extensions, relocks, renegotiations and worst case pricing exceptions are granted daily by phone. Until they are ledgered, that spend is invisible, and in most shops a small number of producers consume a large share of it.
When buying beats building
If you originate under roughly $100 million a month in conventional agency product, sell best efforts and do not retain servicing, do not build. An MCT hedge advisory relationship plus a bought pricing engine covers your risk at a fraction of the cost, and at that volume the expertise is worth more than the software. We would tell you the same in a sales meeting.
Buy also if your desk is one experienced person who is genuinely on top of the pipeline. Software that formalises what a good secondary manager already does has a much weaker case than software that replaces what nobody is doing.
The build case starts around $200 million a month, or earlier if you retain servicing or are deciding whether to. It strengthens sharply when your products are not priced properly by any third party engine, which in practice means non-QM, jumbo held on balance sheet, construction to permanent, or a credit union pricing members differently from the market. And it becomes obvious when your position report is a manual export, because the export is the lag and the lag is the loss.
When you are ready to turn this into a specification, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. 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.
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
- 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) →
Frequently asked questions
How much does custom mortgage pipeline hedging software cost in total?
A decision layer built on top of a bought pricing engine, covering an event driven position, a pull through model, best execution and an exception ledger, runs $70,000 to $150,000 and ships in 10 to 16 weeks, based on Digital Heroes delivery experience. A full secondary desk platform with trade capture, margin call tracking and profit and loss attribution runs $200,000 to $500,000 over 8 to 14 months.
Whether you retain servicing and how many delivery outlets you carry move the number more than headcount does.
What does it cost to run each year?
Plan 15 to 20 percent of the build cost annually across hosting, monitoring, integration upkeep and enhancements. Add model maintenance as scheduled work, because pull through behaviour shifts with the rate environment and the channel mix and the model needs periodic retraining plus a view showing when its error is drifting.
Market data and pricing feed costs continue unchanged, and a system computing best execution across more outlets tends to consume more of them.
How long does it take to build?
Ten to 16 weeks for the decision layer, and 8 to 14 months for a full desk platform. The event driven position and the exception ledger deliver value first and can be live well before the model is finished.
The schedule risk is data rather than engineering. If your loan origination system never recorded the market level at lock, reconstructing that history from archived rate sheets happens before any modelling starts and is measured in weeks.
Should we replace Optimal Blue or build around it?
Build around it in almost every case. Rate sheet generation, investor pricing ingestion and loan level pricing adjustment maintenance are a permanent treadmill, and no lender gains an edge by owning them.
The edge is in the layer above: a pull through model trained on your own funded history, best execution restricted to the outlets you are actually approved for, and an exception ledger. Replacing the engine outright only makes sense when you originate products no third party engine prices properly.
Why does retaining servicing raise the cost so much?
Because it adds a second discipline inside the same project. Best execution has to value a servicing asset against prepayment expectations rather than compare a service release premium, the buy up and buy down grid changes the coupon and therefore the pool a loan can enter, and every mark carries an assumption your auditor will question.
Servicing released execution is arithmetic. Servicing retained execution is an analytics workstream with its own data and its own governance.
What is the cheapest useful version we could build?
The event driven position plus the lock desk exception ledger. Neither needs a model, both are cheap, and together they remove the structural lag between locks and hedge adjustments while making exception cost visible for the first time.
That combination sits near the bottom of the $70,000 to $150,000 band. Add the pull through model once you have confirmed your history contains the market level at lock, because without it the model cannot learn rate incentive.
How do we justify this to the board?
Price the lag rather than the software. Take your average time between a lock arriving and the hedge being adjusted, take your open commitment balance, and ask your risk officer what a typical adverse intraday move against the unhedged portion is worth. Run it on the worst five days of last year, not the average.
Then add the exception spend. Once extensions and renegotiations carry an amount and an approver, the realised margin report by producer usually settles the argument on its own.
We originate $80 million a month. Is a build justified?
Probably not, and we would say so before you asked. At that volume with conventional agency product and best efforts delivery, a hedge advisory relationship such as MCT covers your risk for a fraction of a build and the expertise matters more than the software.
The build case starts around $200 million a month, or earlier if you retain servicing, originate non-QM or jumbo portfolio product, or your position report is a manual export that lags the market by hours.
Who owns the pull through model if an agency builds it?
You should, along with the repository, the infrastructure accounts and the training data, written into the contract before kickoff. At Digital Heroes the client owns the code and the trained model from the first commit.
Your funded loan history is the asset that makes the model work and it must never sit inside a vendor account you cannot control or export. A developer who wants to retain the model is selling a subscription you cannot leave.
At what point does Retool cost more than building a custom tool?
The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.
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.
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.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How long does it take to build an internal tool from scratch?
A working first version typically ships in 4 to 8 weeks, and larger multi-module tools run 10 to 16 weeks. Across Digital Heroes internal tool projects the schedule splits into roughly one week of process mapping, 3 to 6 weeks of build, and 1 to 2 weeks of testing with your actual staff. The most common delay is not development but waiting on the client for sample data and workflow decisions, so name one internal owner before kickoff.
How do I vet a development agency for an internal tools project?
Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.
How do I know when spreadsheets are no longer enough to run my operations?
Replace the spreadsheet once more than three people edit it, versions travel by email, or a single broken formula could cost real money. Other reliable signals: staff keep personal shadow copies, month-end reporting takes days of manual assembly, and nobody can say who changed a number or why. In Digital Heroes discovery calls the tipping point is almost always a specific expensive error, a mispriced quote, a missed order, or payroll built on a tab someone sorted wrong.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How 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.
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 .