Portfolio Rebalancing and Tax Optimization Software: Build or Buy
Buy. For a registered investment adviser under roughly 1,500 taxable accounts, Orion Eclipse, iRebal, Tamarac or Smartleaf will rebalance well enough that the difference never reaches a client statement.
On this page
Buy. For a registered investment adviser under roughly 1,500 taxable accounts, Orion Eclipse, iRebal, Tamarac or Smartleaf will rebalance well enough that the difference never reaches a client statement. Build only when your operations team maintains spreadsheets for restrictions the tool cannot express, or when the engine is your product because you run a turnkey asset management program.
What the off the shelf products actually do well
These are capable systems and we recommend them regularly, including to firms who arrive asking us to build. Orion Eclipse is a genuine rebalancer with real tax lot awareness, embedded in a platform many advisers already pay for, which means the position and lot data is already reconciled before the optimiser sees it. iRebal comes with Schwab custody at no separate licence and handles model drift, cash raises and trade generation properly for most firms who use it. Tamarac pairs rebalancing with reporting and a client portal in one place. Vestmark and Envestnet run at real scale for large sponsors.
Then the specialists. Smartleaf is built specifically around tax management and does that job well. LifeYield is built around asset location and household coordination and is the most thought through product in that particular corner. Firms that built their name on tax aware transitions have productised the multi year transition budget in a way most general rebalancers have not.
Say the awkward part early. If most of your client assets sit in tax deferred accounts, none of this matters and a straightforward drift based rebalancer is enough, because there are no realised gains, no holding periods and no wash sales inside an individual retirement account. If your taxable book is a few hundred accounts, an adviser reviewing a rebalance by hand is genuinely feasible and cheaper than anything you would commission. Most firms reading this should buy, and we say so on discovery calls that then do not turn into projects.
Where they stop: the wash sale that crosses account boundaries
The workflow generic products model badly is the household, and the sharpest example is the wash sale. Section 1091 of the Internal Revenue Code looks back thirty days and forward thirty days, and it does not respect your account boundaries. A loss harvested in a taxable account is disallowed if a substantially identical security is purchased in the client's individual retirement account inside that window, and in that case the basis adjustment is lost outright rather than deferred. The usual culprit is a dividend reinvestment nobody switched off, running on a schedule nobody is watching, in an account you do not even trade.
A rebalancer that checks wash sales inside one account is worse than no check at all, because it manufactures confidence. What is needed is a household level purchase calendar covering every linked account including the ones you only observe, and including scheduled future activity such as reinvestments and recurring contributions, with the constraint applied in both directions in time. That is unglamorous plumbing, and it is the whole difference between a tax aware system and a system that says it is tax aware.
The second stopping point is the constraint set. Real accounts carry restrictions: no employer stock, hold this bond to maturity, keep $40,000 liquid for a March property purchase, do not exceed fifteen percent in any single name, transition this inherited portfolio across three years inside an annual realised gain budget. The interesting cases are the conflicts. The model wants to sell, the gain budget says no, the drift policy says drift must be corrected. Something gives, and most products hand you a trade list without naming which constraint bound. An adviser who can tell a client the portfolio is off model because correcting it this year would have cost $9,000 in tax is having a conversation. An adviser holding a trade list is having an argument.
The arithmetic: per account pricing against a build
Rebalancers are priced per account per year, in basis points on assets under management, or bundled free with a custodian relationship. Use your own agreement. Call it $14 per account per year for illustration. Twelve hundred accounts is $16,800. Four thousand accounts is $56,000. On a basis point contract, call it 1.5 basis points on $1.5 billion, which is $225,000 a year and rises with markets rather than with the work performed.
A first release runs $100,000 to $220,000 over fourteen to twenty weeks, with year two at 15 to 20 percent. Amortise a $170,000 build across five years including support and you carry roughly $60,000 a year.
On the per account illustration the crossover sits near 4,300 accounts, which is a large firm. On the basis point illustration it arrives far earlier, somewhere around $400 million in assets, because a fee tied to market value is not tied to anything you receive. That is the number worth checking on your own contract before anything else in this article. If your rebalancing fee scales with the thing your business is trying to grow, model your renewal at double today's assets and see whether you still like it.
What a custom build actually costs
A first release covering a household and account model that reflects your real hierarchy, position and lot ingestion from your largest custodian with daily reconciliation, drift detection at account and household level, lot level trade generation with wash sale windows applied across the whole household, per account realised gain budgets, and a trade blotter with override reasons and an immutable release record runs $100,000 to $220,000 across fourteen to twenty weeks.
A full platform adding asset location across account types, multi year transition budgets for low basis legacy positions, direct indexing style harvesting and full custodian trade file integration runs $250,000 to $650,000 phased over nine to fifteen months.
Data migration lands at 10 to 25 percent, and in this category it is lot level reconciliation rather than record loading. Cost basis, acquisition dates and holding periods have to agree with the custodian to the share, because a wrong acquisition date produces a confidently wrong tax decision. Budget for it honestly.
Year two runs 15 to 20 percent annually. What pushes the build up: custodian count, because each brings its own file formats, position reporting quirks and trade rejection semantics, and adding one is weeks rather than configuration; harvesting across hundreds of individual securities, which changes the optimisation size; options and concentrated stock handling; and multi year planning, which means modelling future tax years rather than only this one.
The four situations where building wins
Regulatory fit. Every released trade has to be evidenced. Books and records obligations under the Investment Advisers Act mean an override needs a reason and an approver retained immutably, because the first question a regulator or a client asks is why this account traded differently from the model. Products give you a trade list and a summary rather than the optimiser's reasoning, and reconstructing intent after the fact is not the same as recording it.
Scale economics. Past roughly 4,300 taxable accounts on a per account contract, or past about $400 million on a basis point contract, the licence stops being the cheap option and the comparison turns on control.
A workflow that is your competitive advantage. If after tax outcomes are how you win clients, the engine is the product rather than a utility. A turnkey asset management program whose rebalancer is what sponsors are actually buying should not rent it, and should certainly not have its differentiator sit behind another firm's roadmap.
Integration sprawl across three or more systems. Multiple custodians, a portfolio accounting system, a client reporting platform and a financial planning tool, each with its own account identifiers and its own idea of a household. A Schwab position file, a Fidelity trade upload and a Pershing execution report are three separate problems with three separate rejection behaviours, and once you are handling all three by hand, the layer joining them is the asset.
How to decide in a week
Run the replay. It costs five days and settles the question.
- Monday: take your last full rebalance and recompute it at the lot level rather than the position level, applying highest cost first and then long term first, and price the difference in realised gain.
- Tuesday: search every linked account, including retirement accounts you do not trade, for purchases inside thirty days either side of that rebalance. Count the wash sales nobody flagged.
- Wednesday: list every restriction your operations team currently handles in a spreadsheet. That list is your specification.
- Thursday: pick ten accounts that traded off model last quarter and see whether anyone can state which constraint bound and why.
- Friday: reread your rebalancing contract and model the renewal at double today's assets under management.
If the replay argues for a build, buy discovery before you buy code. Three weeks at a fixed fee produces a written specification covering the household model, the constraint hierarchy with conflicts resolved on paper rather than in production, the custodian interfaces named individually, and acceptance criteria stated as a reprice of a historic rebalance. Digital Heroes signs a product requirements document before development begins, contracts through India LLP, US LLC and UK LTD entities so the intellectual property assignment sits under law your own counsel already reads, and you keep the specification regardless. We are the wrong firm for an adviser with three hundred accounts and a working product, and we would rather say so than take the engagement.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- 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) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
- An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
Frequently asked questions
How much does custom tax aware rebalancing software cost?
A first release with household modelling, drift detection, lot level trade generation under wash sale constraints and a reviewable blotter runs $100,000 to $220,000 and ships in fourteen to twenty weeks. Adding asset location, multi year transition budgets, harvesting at scale and full custodian integration takes it to $250,000 to $650,000 across nine to fifteen months. Lot level data reconciliation adds a further 10 to 25 percent.
How long does it take to build a rebalancing engine?
Fourteen to twenty weeks for a first release covering taxable accounts at your largest custodian across your main models. The schedule risk sits in two places: reconciling lot level data from custodians, which is messier than firms expect, and pinning down the constraint hierarchy, because most firms have never written down what happens when the drift policy and the realised gain budget disagree with each other.
Who owns the code if an agency builds our rebalancing engine?
You should own the repository, the cloud accounts and the unrestricted right to hire another firm, settled in writing before kickoff. If the engine is what turns your models into client outcomes, it is a core asset rather than a utility, and a vendor holding it holds your investment process. Ask the question at proposal stage, because a firm that hedges then will not improve after the contract is signed.
What happens if a client refuses to sell a low basis inherited position?
It becomes a hard constraint on the optimisation rather than an exception someone remembers. The account holds a permanently excluded position, the model targets redistribute around it, and the drift report explains why the account sits off model. If the client will sell gradually, it becomes a multi year transition with an annual realised gain budget, which needs the system to model future tax years rather than only the current one.
Can we build only the wash sale checker and keep our rebalancer?
Yes, and for firms not ready to commit it is a sensible first step. A household purchase calendar covering every linked account, including retirement accounts you do not trade and scheduled future reinvestments, can run alongside your existing tool and block or flag proposed trades before release. It is a fraction of a full engine and it removes the exposure most advisers do not currently see.
Should we build if most client assets are in retirement accounts?
No, and we would tell you so directly. Tax aware rebalancing exists to manage realised gains, holding periods and wash sales, and none of those constraints apply inside a tax deferred account. If the large majority of assets sit there, a straightforward drift based rebalancer is sufficient. The threshold is the size and count of your taxable book, not total assets under management.
What is the difference between rebalancing and tax loss harvesting?
Rebalancing moves an account back toward its target allocation when drift exceeds tolerance. Harvesting deliberately realises losses to offset gains elsewhere, then reinvests in something not substantially identical to keep exposure. They interact badly if run separately, because a harvest can create drift and a rebalance can undo a harvest or trigger a wash sale, which is why the same engine should carry both.
How do we handle multiple custodians without doubling the cost?
Start with your largest custodian and taxable accounts only, then add the others once the model is proven. Each custodian brings its own position file format, reporting quirks and trade rejection semantics, so treat each addition as weeks of work rather than a configuration change. Retirement accounts carry no tax constraint and are the easy case, so proving the hard case first is the right order.
Can software explain to a client why their account traded off model?
It should, and this is one of the clearer arguments for owning the engine. An explicit optimisation with a stated objective and ranked constraints can name the binding constraint per account, so the adviser can say the portfolio stayed off model because correcting it this year would have realised a specific dollar amount of gain. A trade list without that reasoning leaves the adviser defending a decision nobody recorded.
What happens if our rebalancing vendor raises its fee at renewal?
Model it now rather than then. Check whether your fee is tied to accounts, seats or assets under management, and work out the renewal at double today's assets. A fee that scales with the thing you are trying to grow is worth knowing about while you still have time to react. Then get a written commitment on how lot level data and audit history leave the system.
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.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
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.
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 do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
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.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
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.
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 Amelia.
Senior Brand Designer · UK · London · 1 post on the site
Published · Last updated .
