How Much Does Tax Aware Rebalancing Software Cost in 2026?
A custom tax aware rebalancing engine runs $100,000 to $650,000 depending on how far you take it, and the single decision that moves that number most is how many custodians you must trade through.
On this page
A custom tax aware rebalancing engine runs $100,000 to $650,000 depending on how far you take it, and the single decision that moves that number most is how many custodians you must trade through. Each one brings its own position and tax lot file, its own trade upload format and its own rejection semantics, and adding a second is real weeks of engineering rather than a configuration screen. A firm on one custodian gets a first release for meaningfully less than a firm on three, and custodian count is the driver advisory firms consistently underestimate when they set the budget.
The bands a rebalancing engine build falls into
There are two honest bands, plus a narrower first step that is worth naming.
The first release band is $100,000 to $220,000 over 14 to 20 weeks. That covers a household and account model that reflects your actual hierarchy, position and tax lot ingestion from your custodians with daily reconciliation, drift detection at account and household level including cash, lot level trade generation with wash sale windows applied across the whole household, per account realised gain budgets with the binding constraint reported, a reviewable trade blotter, and custodian trade file generation with execution status coming back. Taxable accounts, your main models, your largest custodian first.
The full platform band is $250,000 to $650,000 phased across 9 to 15 months. That adds asset location across account types, multi year transition budgets for low basis legacy holdings, direct indexing style loss harvesting across hundreds of individual securities, options and concentrated stock handling, and every remaining custodian.
Below the first band there is a genuinely useful narrower build: a household wash sale calendar and lot level tax impact preview that sits alongside your existing rebalancer, so a trade list gets checked before release rather than after. In our delivery experience that is $35,000 to $60,000 over six to eight weeks. It stops the specific failure that embarrasses firms and changes nothing else about how you trade.
What drives a rebalancing build up
Custodian count is first, and it is not linear in the direction you hope. Every custodian has its own tax lot file with its own quirks about how transfers, corporate actions and reinvestments are represented, its own trade upload format, and its own way of telling you a trade was rejected. A firm on Schwab, Fidelity and Pershing is solving three data problems and three execution problems, not one problem three times.
Direct indexing style harvesting is second and it is a step change. Moving from forty funds per model to several hundred individual securities changes the size of the optimisation, the volume of lot data you reconcile nightly, and the number of wash sale relationships you must track. It is a different engineering problem wearing the same name.
Multi year transition planning is third. A single year optimisation is hard. A transition that models future tax years against an annual realised gain budget, with positions the client will not sell held out, needs a forward model rather than a snapshot.
Options and concentrated stock add their own handling, including cost basis behaviour that does not resemble anything else in the book.
Then there is the constraint hierarchy itself. Most firms have never written down what happens when the drift policy and the gain budget disagree, and the weeks spent settling that in a room with your investment committee are real project weeks.
What keeps the number down
Start with your largest custodian only. Prove the ingestion, reconciliation and trade file loop on one, then add the second with a known pattern rather than an unknown one. Firms that sequence this way spend less in total.
Start with taxable accounts only. Retirement accounts carry no realised gain constraint and no holding period question, so they are the easy case, and proving the hard case first is the correct order. They still need to appear in the wash sale calendar, but they do not need to be traded by the new engine on day one.
Bring the constraint hierarchy to kickoff already settled. Write down the objective, rank the constraints, and state what gives when two of them conflict. That single document is worth more to the schedule than any engineering decision, and producing it costs you a fortnight of investment committee time rather than a fortnight of developer time.
Limit release one to your main models rather than every sleeve variant that has accumulated over a decade. Sleeve structures multiply the test surface faster than they multiply the value.
Finally, appoint one decision owner from operations who can answer a question the same day. In this domain the questions are about your investment process rather than about software, and a firm that routes each one through a committee adds weeks that show up as cost.
A worked example that adds up
An advisory firm with roughly 4,200 taxable accounts across twelve models, two custodians, no direct indexing yet, and an operations team currently checking trades against a spreadsheet before release.
- Discovery, with the constraint hierarchy and household definitions written down and signed off: $14,000
- Household and account model including sleeves and traded versus observed accounts: $19,000
- Position and tax lot ingestion from the first custodian with daily reconciliation: $17,000
- Position and tax lot ingestion from the second custodian: $14,000
- Drift detection at account and household level including cash drift: $16,000
- Lot level trade generation with selectable lot policies per account: $28,000
- Household wash sale calendar covering untraded retirement accounts and scheduled purchases: $22,000
- Realised gain budgets with the binding constraint named per account: $18,000
- Trade blotter with review, override reasons and an immutable release record: $17,000
- Custodian trade file generation and execution status ingestion: $15,000
- Testing and two full cycles of parallel running against the existing rebalancer: $16,000
That totals $196,000, inside the first release band and near its top because of the second custodian and the size of the model set. The same functional scope on one custodian with six models lands nearer $155,000.
If that firm later adds asset location across account types, multi year transition budgets, harvesting across individual securities and a third custodian, expect a further $120,000 to $260,000, taking the platform to roughly $316,000 to $456,000 in total.
How the spend phases
Discovery is three to four weeks and typically 10 to 14 percent of the first release. It produces the constraint hierarchy, the household definition and a written answer to the question of what happens when the drift policy and the gain budget disagree. Firms that skip it discover the answer during user acceptance testing, which is the most expensive time to find it.
Weeks four to ten are custodian ingestion and reconciliation, roughly 30 percent. This is unglamorous and it is where schedules slip, because tax lot data is messier than every firm expects and the mess only appears at volume.
Weeks ten to sixteen are the optimisation and the wash sale calendar, around 40 percent. That is the heart of the system and it is deliberately built against a settled data layer rather than alongside one.
The final three to four weeks are the blotter, trade file generation and parallel running, around 18 percent. Run the new engine beside the existing one for at least two full rebalance cycles and reconcile the differences line by line. Every difference is either a bug or a decision you did not know you were making, and both are worth finding before a client does.
The ongoing costs nobody quotes
Infrastructure for a system of this shape runs $700 to $2,500 a month in our delivery experience, driven by nightly lot reconciliation volume rather than by user count. Direct indexing pushes that materially higher because the lot count per account rises by an order of magnitude.
Custodian file maintenance is a standing cost. Formats change, new fields appear, and a corporate action will eventually arrive represented in a way your parser has never seen. Budget several days a year per custodian, and more in any year you add one.
Model and constraint changes are ongoing by design. Every new restriction type your firm agrees to support is a small piece of work, and firms underestimate how often that happens once operations discover the system can express things the old tool could not.
Support and enhancement typically runs 12 to 18 percent of the build cost annually. Rebalancing runs on a calendar and a failure on trade day is not a next business day problem, so this figure assumes someone is reachable during your release window.
Finally, budget review time. Regulators and clients both ask why an account traded differently from its model, and the answer comes from a person reading the system's output, not from the system alone.
Comparing a build against your current renewal
Do this arithmetic before you commission anything. Take your annual rebalancing platform cost, whether it is a line item or bundled into a broader subscription. Add the fully loaded cost of the operations time spent on what the tool cannot express: the spreadsheets that hold restrictions, the manual checks before release, the accounts pulled out of the batch and traded by hand, and the reconciliation of what the tool proposed against what the custodian actually did.
Then price the thing you are really buying, which is after tax outcome you can evidence. If your firm competes on tax management and cannot currently show a prospect what it delivered, the gap is a revenue question rather than an efficiency one, and it is the reason turnkey programmes build rather than buy.
Do not put a number on avoided tax that you cannot defend. What you can defend is the count of wash sales your current process created last year and the number of short term gains realised on model changes, both of which are sitting in your own data and neither of which most firms have ever counted. Count them first. That figure is your real business case.
When buying beats building
If most of your client assets sit in tax deferred accounts, do not build. The entire premise of the project disappears, because realised gains, holding periods and wash sales do not apply inside those accounts. A straightforward drift based rebalancer is sufficient and the capital belongs elsewhere.
If you run under roughly 300 accounts, do not build either. An advisor reviewing a rebalance manually is genuinely feasible at that scale and materially cheaper. Volume is what makes automation pay here, and below the threshold it does not.
If you already run Orion Eclipse or Envestnet and your investment process fits their model and household hierarchy without side spreadsheets, stay. You would be paying to reproduce something you own. Smartleaf is worth a serious look if tax management specifically is your gap, and LifeYield if the gap is asset location across a household. We recommend all of these regularly.
Build when two or more of these are true: you trade thousands of taxable accounts, your operations team maintains workbooks for restrictions the tool cannot express, you need to tell a client which constraint prevented a trade and cannot, you serve several custodians and each is a manual step, you run multi year transitions for low basis legacy portfolios, or you are a turnkey programme whose rebalancing engine is effectively your product rather than a tool you consume.
If you would rather scope this before committing budget, 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.
- Across 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
Frequently asked questions
What is the total cost of custom tax aware rebalancing software?
A first release covering household modelling, custodian lot ingestion, drift detection, lot level trade generation with household wash sale constraints, realised gain budgets and a reviewable blotter runs $100,000 to $220,000 and ships in 14 to 20 weeks in our delivery experience. A full platform adding asset location, multi year transitions, harvesting across individual securities and every remaining custodian runs $250,000 to $650,000 over 9 to 15 months.
Custodian count moves the number more than account count does. A firm with 8,000 accounts on one custodian is cheaper to serve than a firm with 3,000 across three.
What does it cost to run each year after launch?
Infrastructure sits at $700 to $2,500 a month for a system of this shape, driven by nightly tax lot reconciliation volume rather than by how many people log in. Direct indexing raises that materially, because lot counts per account rise by an order of magnitude.
Support and enhancement typically runs 12 to 18 percent of the build cost annually, and that figure assumes someone is reachable on trade day rather than the next business morning. Add several days a year per custodian for file format changes, plus whatever your firm spends adding new restriction types once operations realise the system can express them.
How long does a rebalancing engine take to build?
Fourteen to 20 weeks for a first release covering taxable accounts at your largest custodian across your main models. Asset location, multi year transitions and harvesting across individual securities add a further five to ten months depending on how many custodians remain.
The schedule risk sits in two places. Custodian lot reconciliation is messier than firms expect and the mess only shows at volume. And most firms have never written down what happens when the drift policy and the realised gain budget conflict, so settling that costs investment committee weeks before it costs developer weeks.
Is Orion Eclipse cheaper than building our own rebalancer?
Yes, and if your investment process fits its model and household hierarchy without side spreadsheets, it is the right choice. It is a capable rebalancer with genuine tax lot awareness, embedded in a platform many firms already pay for, and rebuilding that is a poor use of capital.
The comparison changes when your process does not fit. The reliable tell is a spreadsheet: if operations maintains workbooks holding the restrictions, sleeve rules or transition budgets the tool cannot express, you are already paying for a custom system, just in salary rather than software, and without the audit trail.
Why does each additional custodian cost so much?
Because a custodian is three separate problems, not one. The position and tax lot file has its own representation of transfers, corporate actions and reinvestments. The trade upload has its own format and its own validation. And the execution report has its own way of telling you a trade was rejected, which matters because a silently vanished trade is worse than a failed one.
In the worked example above the second custodian added $14,000 to ingestion alone, before its share of testing. Ask any developer to name the custodian and the specific interface they have written against rather than accepting a general claim.
Can we build only the wash sale checker first?
Yes, and it is a sensible first move for a firm not ready to replace its rebalancer. A household level purchase calendar covering every linked account including untraded retirement accounts and scheduled activity such as dividend reinvestment, plus a lot level tax impact preview on a proposed trade list, runs $35,000 to $60,000 over six to eight weeks.
It sits beside your existing tool and checks its output before release. That fixes the specific failure that embarrasses firms, which is a loss disallowed by a purchase in an account nobody was watching, without committing to the full engine.
How much does direct indexing style harvesting add?
Enough that it should be scoped as its own phase rather than a feature. Moving from funds to several hundred individual securities per account changes the optimisation size, multiplies the nightly lot volume you reconcile, and expands the wash sale relationship set you must track across the household.
It is a large part of why the full platform band reaches $650,000 and it also raises the ongoing infrastructure figure permanently. Prove the engine on fund based models first, then extend, rather than attempting both at once.
What does parallel running add to the budget and why bother?
In the worked example, testing plus two full cycles of parallel running was $16,000, roughly 8 percent of the first release. Run the new engine alongside the existing one and reconcile every difference in the proposed trade list line by line.
Every difference is either a defect or a decision your firm did not know it was making. Both are worth finding before a client's tax package finds them the following January, and the second category is often the more valuable discovery.
What is the cheapest credible version of this system?
Around $100,000 for a firm with one custodian, a handful of models, taxable accounts only, and a constraint hierarchy already written down before kickoff. That buys household modelling, lot ingestion with daily reconciliation, drift detection, lot level generation with household wash sale constraints, a blotter and trade file generation.
Anything materially below that is a drift report rather than a rebalancing engine. Be sceptical of a quote under $80,000 for full first release scope, because custodian reconciliation alone consistently absorbs more effort than a fixed price assumes.
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.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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 should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
If we build for 20 users now, will the software cope with 500 later?
It should, without a rewrite, if it was built on a standard cloud stack; going from 20 to 500 users is mostly a hosting configuration change costing hundreds a month, not a second project. What actually breaks under growth is sloppier work: database queries never indexed for volume and features designed assuming one office's worth of data. Before signing, ask the vendor what happens to the system at ten times today's data, and listen for a specific answer.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Zoe.
Senior Brand Designer · New-york · 8 posts on the site
Published · Last updated .
