1031 Exchange Management Software: Build Custom or Buy Accruit Exchange Manager Pro
Structure decides this, not volume. If you administer conventional forward exchanges through one bank, buy Accruit Exchange Manager Pro whether you close 100 a year or 800, because the product already models that lifecycle properly.
On this page
Structure decides this, not volume. If you administer conventional forward exchanges through one bank, buy Accruit Exchange Manager Pro whether you close 100 a year or 800, because the product already models that lifecycle properly. Fund a build only when reverse or improvement structures put exchange accommodation titleholder entities under your administration, or when per exchange bank accounts and dual control disbursement need to be enforced in software rather than described in a policy. Most qualified intermediary firms fall on the buy side of that line, and we tell them so.
When is off the shelf genuinely the right call here?
Accruit Exchange Manager Pro is the recognised product in this niche and it exists because the workflow is specific. It models the forward exchange lifecycle, generates the documents, tracks the deadlines and gives a coordinator somewhere to work that is not a folder plus a calendar reminder. For a qualified intermediary (QI) firm doing conventional forward deals, that is the sensible purchase, and a build would be capital better spent on business development.
Buy if most of these are true:
- You administer under roughly 100 exchanges a year, all of them forward deals.
- Your funds sit in a straightforward arrangement with one bank.
- Your document set is small and your counsel has settled the wording.
- Nobody in the firm is on the hook for administering a parked entity.
- You have no in house engineering and no appetite to own a system for its full life.
The part firms get wrong is assuming volume is the trigger. It is not. A firm closing 800 straightforward forward exchanges through a single bank arrangement is well served by a product, because every one of those 800 files is the same shape. A firm closing 200 where thirty are reverse or improvement structures is not, because those thirty are a different business wearing the same name.
There is also an honest floor below the product. A firm doing a handful of accommodations a year as a courtesy to title clients does not need software at all. It needs a written deadline procedure, a second person checking every computed date, and a bank arrangement its counsel is comfortable with. Buying a platform to administer twelve files a year is a subscription in search of a problem.
When does a custom build actually pay off?
Custom earns its cost when the part that hurts is the part no product models as a first class object. In this business that is almost always the parking arrangement.
A forward exchange is a linear record: transfer, identify, acquire, close. A reverse exchange creates an exchange accommodation titleholder (EAT) entity that takes title, holds its own bank account, carries insurance and property level obligations, runs a parking clock with a hard limit, and eventually transfers out. An improvement exchange adds construction draws, where only work completed inside the exchange period counts toward value received. Firms running those on the same spreadsheet as their forward files are administering an entity portfolio in a tool designed for a list.
Build when two or more of these hold:
- You regularly do reverse or improvement exchanges and administer EAT entities as an ongoing portfolio.
- Your bank arrangement involves per exchange accounts, positive pay and controls you want enforced by the system rather than described in a memo.
- Origination runs through title companies, brokers and accountants who need a portal to open and track exchanges.
- You sit alongside affiliated title or advisory businesses and need controlled data sharing without breaching the separation your structure depends on.
- Your service model includes analysis the product does not offer, such as boot support or partial exchange modelling.
One further trigger is worth naming. If your 180 day deadlines are being computed by hand as transfer date plus 180, you have a correctness problem rather than a tooling preference. The exchange period ends on the earlier of that date or the due date of the taxpayer's return for the year of transfer including extensions, and that is the deadline firms most often miss because it is the one nobody calculates.
How do they compare on the things that matter in this industry?
Deadline computation. Any competent product holds 45 and 180 day dates. The question to ask in a demonstration is what happens to a client who closes in November and does not extend their return. If the system cannot record the taxpayer's filing and extension position and treat the earlier date as operative, your coordinators are doing that arithmetic in their heads on every late year file.
Identification. A scanned letter in a document tab is storage. Structured identification is a control: each property carries an address or legal description and an estimated value, the system evaluates which quantity rule the taxpayer is relying on, and it warns while there is still time when four properties have been identified and the combined value sits well over the 200 percent limit. Revocations recorded as events let you reconstruct the effective set as at day 45, which is the fact that matters if it is ever challenged.
Funds control. This is the ground on which most build decisions are actually won. A ledger where every receipt and disbursement is attributable to an exchange, an account and an approver, where balances are computed rather than typed, and where corrections are reversing entries in append only history, is a different risk profile from a spreadsheet reconciled monthly.
Parked entities. Products treat these as notes attached to an exchange. A build treats the EAT as a record with its own clock, documents, bank account and exit transfer.
Data portability. Exchange records support a tax position and must remain producible for years after closing. Ask any vendor how you get the complete record out, including the audit trail rather than just a product export, and get the answer written into the contract.
What does total cost of ownership look like at your scale?
Put both paths on the same clock before comparing them. On the build side, from Digital Heroes delivery experience, a first release covering the exchange record with both statutory clocks, structured identification with rule evaluation, document generation and the funds ledger runs $50,000 to $110,000 and ships in 10 to 14 weeks, forward exchanges only. A full platform adding reverse and improvement structures, EAT administration, bank integration at account level, dual control disbursement and a referral partner portal runs $140,000 to $320,000 phased across 6 to 12 months.
The lines nobody quotes: infrastructure at $250 to $800 a month, driven by document storage and backup retention rather than compute, and growing every year because records have to stay producible. Support and enhancement at 12 to 18 percent of build cost annually if you want a partner reachable during closings. Two to four template revision cycles a year with your counsel, which is a legal cost rather than a software one. A few days a year on bank file format changes, and more in the year you switch institutions.
On the buy side, take your current renewal figure and add the fully loaded cost of staff time spent on work the product does not do: hand built calendar entries, identification letters read and filed by a person, spreadsheet reconciliation of the funds position, and reverse exchange records maintained outside the system. In firms of moderate size that second number is frequently larger than the first, and it is the number that decides the comparison.
Then set both against what you are actually insuring. A failed exchange is a taxable event for a client and a conversation with their counsel and your carrier. We will not invent a probability for that. What we will say is that a control enforced in software is a different exposure from a control that depends on a coordinator noticing something on a Thursday.
What does the hybrid look like, and when is it the honest answer?
For most firms reading this, the right move is neither a bigger subscription nor a ground up rewrite. It is to keep the product for the forward exchange lifecycle and build the thin layer where you are genuinely exposed.
Three layers are worth building on their own:
- A deadline engine. Anchors on the transfer date, computes both statutory dates including the return due date rule with filing and extension position recorded, and escalates on your schedule. In our delivery experience that is $18,000 to $30,000 over four to six weeks. It fixes the deadline you most often miss and touches nothing about funds.
- An EAT administration module. Entity records, parking clocks, lease and financing document tracking, construction draw requests with lien waivers, and the exit transfer. This is the part the product genuinely does not model, and it is where firms feel the pain first.
- A funds reconciliation layer. Daily import of the bank statement, per exchange attribution, computed balances and an exception queue when the ledger and the bank disagree.
The reason the hybrid usually wins is sequencing. Build the deadline engine or the EAT module first, run a full quarter on it, and you learn precisely which parts of the product you have outgrown. Firms that scope everything at once spend more in total than firms that phase, because the reverse structure work benefits from a settled ledger design that only exists once the forward side has run in production.
Which should you choose, by operator size and stage?
Here is the committed call. Find your row and act on it.
- Under 25 exchanges a year, forward only. No platform. A written deadline procedure, second person verification of every computed date, and a bank arrangement your counsel has signed off. Software here is overhead.
- 25 to 100 a year, forward only, one bank. Buy Accruit Exchange Manager Pro and run it properly. Spend the difference on referral relationships. We say this to firms regularly and it costs us work.
- 100 to 400 a year, forward only. Still buy, but add the deadline engine if late year closings are a meaningful share of your book and coordinators are computing the return due date rule by hand.
- Any volume with regular reverse or improvement work. Build the EAT layer above the product. Do not rebuild forward exchange document generation that already works.
- 200 or more a year with mixed structures, per exchange accounts, referral origination and affiliated businesses. Build the platform, phased. Forward exchanges and the funds ledger first, reverse structures once the ledger is proven, referral portal last.
Two conditions apply to every build row. Settle your document templates with counsel before kickoff rather than during the build, because template wording still under negotiation is the most common cause of a slipped date in this category. And appoint one decision owner with authority to settle drawdown rules, escalation timing and disbursement thresholds. The hard questions here are legal and operational rather than technical, and a firm that routes each one to a partners meeting adds weeks that arrive later as cost.
If you would rather scope this before committing budget, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- 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) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- 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) →
Frequently asked questions
Is Accruit Exchange Manager Pro enough if we do reverse exchanges?
It handles the forward exchange lifecycle properly, and firms doing an occasional reverse deal can manage the parked entity alongside it with discipline. The problem arrives when EAT administration becomes an ongoing portfolio rather than an exception, because the parking clock, the lease and financing documents, the construction draws and the exit transfer are not attributes of an exchange record. They belong to an entity you administer.
The practical test is whether anyone in your firm keeps a separate spreadsheet of parked properties. If they do, that spreadsheet is the thing worth building, not a replacement for the product.
What does it cost to switch off our current exchange platform?
The software migration is the small part. Closed files can be bulk loaded for retention because nothing is computed from them. Open exchanges are the expense: each one is entered and then verified by a second person against the existing calendar entry, because a single mis-anchored transfer date is a missed deadline rather than a data error. At around 140 open files that work has run about $6,000 in our delivery experience.
Budget the parallel running too. Keep the old calendar live until every exchange open at cutover has closed.
What happens if our current vendor changes its pricing?
Model it before it happens rather than after. Ask what the fee is tied to, meaning seats, exchanges opened, funds under administration or something else, and work out what your renewal looks like at double your current volume. If the fee scales with the thing your business is trying to grow, that is worth knowing while you still have time to react.
The stronger protection is portability. Get a written commitment on how the complete record leaves the system, including the audit trail, and test that export once a year rather than discovering its limits during a renewal negotiation.
How long does a custom exchange system take to build?
Ten to 14 weeks for a first release covering forward exchanges, both statutory clocks, structured identification and the funds ledger. Reverse and improvement structures with EAT administration add a further four to seven months depending on how many parking arrangements you run and whether construction draws are in scope.
The most common cause of a slipped date is template wording still being negotiated with counsel while development is running. Settle the templates before kickoff and the schedule holds.
Can we build only the deadline engine and keep everything else?
Yes, and for a firm not ready to commit to a full system it is a sensible first move. A deadline engine anchors on the transfer date, computes both statutory dates including the return due date rule with the taxpayer's filing and extension position recorded, and escalates on your schedule. In our delivery experience that is $18,000 to $30,000 over four to six weeks.
Be clear about what it does not do. It does not touch funds, and funds control is where the severe risk in this business sits.
Does high exchange volume on its own justify a build?
No, and this is the most common misread of the decision. Volume multiplies files of the same shape, and a product handles files of the same shape well. What justifies a build is variety: reverse and improvement structures, per exchange bank accounts with enforced authorisation, affiliated entities that need controlled data sharing, or referral partners who need their own view.
A firm at 800 forward exchanges through one bank should stay on the product. A firm at 200 with thirty parked entities under administration usually should not.
Should we replace the funds ledger or reconcile against it?
Start by reconciling. Import the daily bank statement, attribute every movement to an exchange, compute the balance and raise an exception when the ledger and the bank disagree. That gives you the control on day one without touching how money actually moves.
Automated per exchange account opening, positive pay and dual control disbursement enforced in software are worth having, but scope them after a conversation with your institution. What a bank exposes varies widely and it decides how much of that work is even possible.
What happens to our exchange records if the developer relationship ends?
Settle it in writing before kickoff. You should own the repository, the cloud infrastructure accounts and the unrestricted right to hire another firm to continue the work. At Digital Heroes the client owns the code from the first commit and the system runs in the client's own account.
This matters more here than in most categories because exchange records support a tax position and have to remain producible for years after closing. A record you cannot reach without somebody else's cooperation is not a record you control.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
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 people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
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.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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 Mahira.
Lead UI/UX Designer · Lucknow · 1 post on the site
Published · Last updated .
