Transfer Agency Software: Custom Build or License Deep Pool and Bravura
License. If you service one conventional fund range with standard dealing rules and a domestic investor base, Deep Pool or Bravura Sonata will do this properly and a build would be reckless.
On this page
License. If you service one conventional fund range with standard dealing rules and a domestic investor base, Deep Pool or Bravura Sonata will do this properly and a build would be reckless. Building becomes defensible when equalisation methods differ across your own funds, when investors sit in several tax jurisdictions, or when you sell servicing and the register is therefore your product.
What the packaged registry platforms actually do well
It is 11:52 and your dealing desk has eight instructions open against a noon cutoff. Two came clean through the portal. Three arrived as distributor PDFs, one naming an investor whose surname changed. One redemption crosses a lock up expiry by two days. That scene is why you are pricing software, and the first honest answer is that a licensed platform probably solves it.
SS&C, Deep Pool, Bravura Sonata and Temenos Multifonds are the real names in this market and none of them is weak. Deep Pool knows the offshore alternatives world and has for a long time. Bravura Sonata carries genuine depth for retail and wealth registers. Temenos Multifonds handles global fund servicing at scale. They hold the register, apply Net Asset Value (NAV), run settlement, generate contract notes and statements, and carry the tax reporting most administrators need.
If your dealing is conventional, buying is right and a custom register would be an expensive way to reach a worse version of what already exists. The register is the legal record of who owns what, and every downstream artefact, the distribution, the statement, the tax form, the audit confirmation, is derived from it. That is not a place to learn on the job.
Where they stop: the platforms are configured, not adapted
Here is the pattern that shows up again and again, and it is the thing nobody tells you during procurement. A firm licenses a platform, spends eighteen months implementing, and still runs three spreadsheets around it for the parts configuration would not stretch to. At that point you have paid for a platform and built a system anyway, and you own neither.
The stretch happens in three places. Dealing rules first: cutoff is fund specific and sometimes class specific, expressed in a time zone that is not where your operations team sits, with forward dealing where an instruction today prices two valuation points out, plus lock ups, gates and notice periods that differ per investor because of a side letter. Every edge is a place where a wrongly accepted deal gives one investor a price they were not entitled to and dilutes someone else.
Second, equalisation. If your funds equalise, a mid period subscription carries an equalisation credit or a contingent redemption depending on the method written into the offering document, and the performance fee allocation across investors who entered at different points is intricate. Series accounting solves the same problem differently by issuing a new series per dealing date and rolling up later. Both are correct. Packaged systems support the common methods and not the one your counsel drafted in 2019 for a single fund, and definitely not a range where two vehicles use different methods.
Third, intake. Every platform assumes clean structured instructions. Real dealing traffic is email, PDF, a distributor's own file layout, a legacy fax to email line, and occasionally a phone call followed by written confirmation. You will not move every distributor onto your portal, and the ones sending the largest tickets are frequently the least willing to change. That gap is not closed by configuration, so it is closed by a person retyping.
Custom versus off the shelf: the arithmetic per investor account
Compute your own rate. Take the annual licence, add hosting, and then add the consultant days you buy every year for configuration changes, because in this category that third line is the one that surprises people. Divide by investor accounts serviced. Firms rarely put those three together and the combined number is what you are actually comparing against.
On the build side, in Digital Heroes delivery experience a first release runs $150,000 to $300,000 across 16 to 24 weeks. Take the midpoint at $225,000, add migration and four years of support, and five years lands near $420,000, about $85,000 a year.
At $12 per investor account per year, $85,000 is roughly 7,000 accounts. That is the crossover on a straightforward fund range. At $30 per account, which is more typical where investor documentation and tax classification are handled for you, it falls to about 2,800 accounts. Below either line, license and keep the headcount.
Two things move that crossover more than account count does. Jurisdictions, because investor documentation and tax reporting differ per domicile and each is real work. And distributor commission structures, particularly trail commissions with clawback and tiered rebates, which are quietly among the most complex calculations in the whole system and are the first thing to end up in a spreadsheet outside the platform. If your commission logic already lives outside your register, the crossover has already happened and nobody has noticed.
What a custom build actually costs, from kickoff to steady state
A first release covering multi channel deal capture, a cutoff and eligibility engine, NAV application with dilution adjustment where applicable, and the register itself as append only storage runs $150,000 to $300,000 in 16 to 24 weeks. A full platform adding distributions and equalisation, distributor commission structures, investor documentation and portals, anti money laundering and know your customer workflow, and Foreign Account Tax Compliance Act and Common Reporting Standard reporting runs $400,000 to $1,000,000 across 12 to 18 months.
Migration runs 10 to 25 percent of build cost and in registry work it belongs at the top of that band, scoped and budgeted as a project inside the project. You are moving a live register with historical transactions, cost basis and tax classifications while dealing continues. The only design that survives is parallel running across several dealing cycles rather than a weekend cutover, and you should refuse any plan that says otherwise.
Year two and each year after runs 15 to 20 percent of build cost annually. That funds the things that move without asking you: a new fund with a different equalisation method, a distributor changing its file layout, a reporting schema revision in one domicile.
The line nobody quotes arrives at your bank. Automated per fund account reconciliation depends on what your institution exposes, and MT940 and the ISO 20022 camt.053 statement carry different levels of detail. Ask your bank what it can actually send before anyone scopes the cash matching engine.
The four situations where building wins
Regulatory fit. Investors across several domiciles means different documentation requirements, different tax classification, and reporting under both the Foreign Account Tax Compliance Act and the Common Reporting Standard in formats that are not the same. When the register sits in a platform and the tax classification sits in a spreadsheet, you discover the join every reporting season, and a wrong holding does not stay a wrong holding. It becomes a wrong distribution and then a wrong tax form.
Scale economics. Above roughly 7,000 investor accounts on a conventional range, or 2,800 on a fully serviced one, the licence plus the annual consultant days outrun the build.
A workflow that is your competitive advantage. If you are a fund administrator selling servicing, the register is your product. Outsourcing your product to a vendor is a strategic decision rather than an operational one, and it should be taken at board level rather than in a procurement cycle.
Integration sprawl across three or more systems. A fund accounting extract, a custodian or fund bank statement, several distributor files in different layouts, a screening provider for sanctions and politically exposed persons, and a tax reporting submission. Five counterparties, five formats, one register that has to reconcile to all of them.
How to decide in a week, then commission a written specification
Two tests, and they take an afternoon each. First, pick an investor and a date eighteen months ago. Reconstruct their holding as at that date and regenerate the statement exactly as it was sent, from the data as it stood then rather than as it stands now. If that means updating rows or reasoning from a backup, your storage design cannot answer a complaint or an audit, and that is a bigger problem than any feature gap.
Second, take one ordinary dealing day. Count every instruction by how it arrived: portal, file, email, PDF, telephone. Then count how many required a human to retype something into the register. That percentage is the size of the intake problem, and it is the number that decides whether extraction and a one click acceptance queue are worth building. Most desks guess low by half.
If both tests come back comfortable, license and revisit at scale. If the first one failed, fix storage before anything else. Then buy a specification rather than a build: at Digital Heroes a signed product requirements document covering the deal state machine, the cutoff and eligibility rules, the equalisation method per fund and acceptance criteria, written before any code exists and yours to take to three other firms.
We are the wrong firm for you if you want us to run your register as a service. We do not do outsourced administration, and we will not rebuild a fund accounting or NAV engine you already license. We are also wrong if nobody senior will settle the equalisation rules in writing, because those questions are legal rather than technical and routing each one to a partners meeting adds weeks that arrive later as cost. What we bring is more than fifty specialists, over 2,000 projects delivered, a named team you meet before signing, and India LLP, United States LLC and United Kingdom LTD entities so intellectual property assigns under law your own advisers already read. Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing are checkable in ten minutes.
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.
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- WordPress powers 41.5% of all websites and holds 59.2% of the market among sites running a known content management system, making it by far the most-used CMS on the web. Source: W3Techs (2026) →
Frequently asked questions
What is the difference between a transfer agency system and fund accounting software?
Fund accounting computes the Net Asset Value from the portfolio: valuation, accruals, fees and the fund level books. Transfer agency holds the register of investors and applies that price to subscriptions, redemptions and switches, then drives settlement, distributions, statements and tax reporting. They exchange data daily and they are separate systems with separate audit exposures. Building one does not mean touching the other, and it usually should not.
How much does migrating a live register cost?
Budget 10 to 25 percent of the build figure and expect to sit at the top of that band. You are moving historical transactions, cost basis and tax classifications while dealing continues, which means several parallel dealing cycles rather than a weekend cutover, plus reconciliation of every open position by holder. Scope it as a project inside the project with its own plan and its own sign off, not as a task at the end.
Who owns the register data if the developer relationship ends?
You must, and it should be in writing before kickoff: the repository in your own organisation, cloud infrastructure in accounts your firm owns, and full assignment of intellectual property. At Digital Heroes the client owns the code from the first commit. In a business where the register is the legal record of ownership, a supplier holding the code holds something that is not theirs to hold, whatever the contract says about service levels.
Can we keep our platform and build only the intake layer?
Yes, and for many administrators that is the highest return first move. Email and portable document format instructions become draft deals with investor, fund, class, amount and settlement details mapped to your register, presented to a human for one click acceptance with the original attached. The platform still holds the register. You remove the retyping and the received timestamp becomes a captured fact rather than a keying artefact.
How long before a custom register is safe to run live?
Sixteen to twenty four weeks to a first release, then several parallel dealing cycles before you rely on it. Do not compress the parallel period. The failure mode in this category is not a system that does not work, it is a system that works for the ordinary cases and diverges on the edges, and edges only appear across enough dealing days to include a late instruction, a failed settlement and a corporate action.
What happens if a distributor changes its file format without telling us?
The import should fail loudly into a quarantine queue rather than half succeed, and somebody should be paged. This is a design decision worth naming in the specification, because a partially imported distributor file is far more dangerous than a rejected one: it books some deals and silently drops others, and you find out at settlement. Budget a few days a year for format changes, because they arrive without notice.
Should we build if our dealing rules are standard but our volume is high?
No. High volume of identically shaped deals is exactly what a packaged platform handles well, and volume alone is the most common misread of this decision. What justifies a build is variety: differing equalisation methods across your own funds, several investor domiciles, side letter terms that change eligibility, or commission structures already living outside the platform. Variety, not throughput, is what configuration cannot absorb.
Can extraction of email instructions be trusted with real money?
Only with a human in the loop, and that is how it should be designed. The model reads the instruction, maps it to your register and produces a draft. A person accepts it, with the original attached to the record. Confidence is recorded per field, and anything uncertain routes to review rather than through it. Straight through acceptance rates climb after a few weeks of correction, but the review path never disappears.
What happens if we accept a deal after cutoff by mistake?
The investor receives a price they were not entitled to and other holders are diluted, which is a client conversation, a possible compensation payment and an audit finding rather than a data error. This is why received time has to be captured at true point of receipt and never edited, and why every rejection needs a reason code. When a distributor disputes a cutoff three weeks later you want a record, not a recollection.
Is it worth building if we service only one fund range today?
Usually not, and the useful question is what you expect to be servicing in three years. If the plan is a second range with a different equalisation method, investors in additional domiciles, or a distributor channel you have not built yet, the register design decisions made now will either accommodate that or force a rewrite. Design for it, license today, and revisit when the second range is real rather than planned.
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 is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
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.
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 does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
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.
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.
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.
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.
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
Published · Last updated .
