Insights · 13 min read
What a wealth management platform actually includes, why the custodian integration decides the project, and realistic cost ranges for a scoped build.
By GGP Editorial
When someone says "wealth management platform," they can mean three different products, and the difference decides the whole build. A robo-advisor manages portfolios automatically, with no human advisor in the loop. A trading platform gives people the tools to place their own orders. A wealth management platform is the third thing: the software a financial advisor or wealth manager uses to run their practice. That means onboarding clients, building and monitoring portfolios, financial planning, performance reporting, billing fees, and keeping documents organized. This article is about building that third thing.
I want to separate it from the robo-advisor cleanly, because the two get conflated in scoping calls and it costs people money. A robo-advisor makes investment decisions for the client. A wealth management platform supports a human who makes decisions with the client. I covered the automated version in our robo-advisor guide; it is a different product with a different compliance shape. It is also different from financial management or accounting software, which tracks income and ledgers rather than investment portfolios.
If you are a wealth manager, an RIA founder, a family office, or a fintech team building a tool advisors will pay for, this is for you. I will cover the modules, the custodian integration that decides whether the project ships, the compliance rules that shape the build, and realistic cost ranges.
A wealth management platform is the operating system of an advisory firm. At its center is a book of clients and their accounts. Around that center sit the functions advisors run their day on: onboarding and KYC, portfolio management, financial planning, performance reporting, fee billing, document storage, and a client portal. Most firms also need a lightweight CRM and workflow layer so the practice runs as one system instead of a pile of spreadsheets and file folders.
The value is the integration between these parts. A portfolio view that is not linked to the billing system means fees get calculated by hand at quarter-end. A document vault that is not linked to onboarding means compliance evidence lives in someone's inbox. The platform earns its keep when one client record drives onboarding, holdings, reporting, billing, and documents at once.
Buyers split into a few groups. Independent RIAs want to replace aging tools. Family offices want consolidated reporting across entities. Fintech startups want to sell a white-label platform to advisors. Banks want an advisor-facing layer over existing custody and product rails. The scope differs; the core modules are the same.
Here are the pieces, roughly in the order a client and their money move through them.
| Module | What it does | Notes |
|---|---|---|
| Onboarding and KYC | Collects identity, verifies the client, runs sanctions and PEP checks, captures suitability | Usually outsourced to a provider; see our KYC guide |
| Portfolio management | Holds positions and balances, supports rebalancing, model portfolios, and trade proposals | Advisors make the calls here; the system supports them |
| Financial planning | Goals, cash flow, retirement and tax projections | Often the module advisors demo first |
| Performance reporting | Time-weighted returns, statements, benchmarks, household-level views | The part clients actually read |
| Billing | AUM and flat fee schedules, invoicing, and fee runs | Easy to get subtly wrong |
| Document vault | Client documents, agreements, statements, with retention rules | Compliance evidence, not a file folder |
| Client portal | Web and mobile views of balances, holdings, documents, and messages | What clients think of as "the platform" |
| CRM and workflows | Client records, tasks, review scheduling, and team handoffs | Where the practice actually runs |
Most of these are not glamorous, and the glamorous one, the client portal, is the easiest to build. The custodian integration, the reporting engine, and the billing logic are where projects live or die.
In US wealth management, most advisors hold client assets with a custodian. Schwab, Fidelity, and Pershing (BNY) are the names that come up most. The platform reads account and position data from the custodian, sends trade and account-opening instructions, and reconciles everything back. That integration is the spine of the product, and it is also the main source of delay and risk.
A few things about it catch founders off guard. First, custodians differ: each has its own API, data formats, sandbox, and rules about what you can read and write. A platform supporting one custodian is a different scope from one supporting three. Second, not everything is a clean API. Older workflows move data through files, and settlement and corporate actions introduce timing that has to be modeled rather than assumed. Third, the sandbox is not production; the real edge cases appear only after you are live against real data.
Start this integration first. Everything else can be faked with sample data while you wait. The custodian integration cannot. If you are scoping a build, pick your first custodian before you write the first user story, because it changes the data model, the trade flow, and the timeline.
Performance reporting is the part clients actually read, and it is where trust is won or lost. The standard measure is the time-weighted return, which strips out the effect of deposits and withdrawals so the advisor's performance shows cleanly. Getting TWR right across accounts, households, and time periods is real financial engineering, and it is easy to get subtly wrong in ways that only show up when a client asks why their statement does not match their own spreadsheet.
Behind the reporting sit market data and corporate actions. Dividends, splits, and mergers have to be applied properly, or positions quietly stop reflecting reality and returns drift. Many platforms also pull in held-away assets through an account aggregation provider, so advisors can see a client's whole picture rather than only the money they manage.
The data model is the quiet foundation here. If you model a client, an account, a household, and a position the right way from day one, reporting, billing, and planning all build on top of it cleanly. If you bolt reporting on later, you will be reconciling forever. Our fintech architecture piece covers how to plan that structure before code.
Wealth management is a regulated activity, and the rules are not a checklist you add at the end. They shape the data model, the records you keep, and what the software is allowed to say.
In the US, firms providing investment advice are generally registered investment advisers under the SEC or their state, with a fiduciary duty and disclosure obligations. Performance claims in marketing are constrained by the SEC's marketing rule, so reporting numbers have to be defensible. In Europe, MiFID II governs investment services including suitability and reporting. The UK has the FCA, Brazil the CVM, Singapore the MAS. Each has its own registration and conduct rules, and the differences matter when you pick your first market.
For the build, this means a few concrete things. Suitability and onboarding records have to be auditable. Every recommendation and trade needs a trail that shows why it was made. Client communications and documents need retention rules. Security and data protection sit underneath all of it, which I covered in security requirements for fintech platforms.
This is not legal advice. Work out your regulatory scope with a compliance advisor before you write code. Retrofitting compliance into a built platform is the most expensive mistake in this category.
You have three honest paths, and they mirror the build vs buy software decision with a compliance twist.
Build when your service model or your workflow is the differentiator, or when you plan to white-label the platform to other advisors. This is the most expensive path and the one where experience matters most.
Buy a turnkey platform when you are an advisor who just needs the tools to run the practice. There are established providers that bundle onboarding, reporting, billing, and a portal. You trade control and margin for speed.
License or white-label when you are a fintech that wants to sell the platform to advisors but does not want to own every module. You build the brand, the onboarding, and the client experience, and integrate the parts you do not want to own.
The compliance burden is the deciding factor. In wealth management, building means you own the records, the reporting, and the audit trail. You should only take that on when the service model or the distribution justifies it.
A wealth management platform sits at the expensive end of fintech builds, a notch below a full robo-advisor with an automated rebalancing engine. Two things drive the price: the custodian integrations and the breadth of modules.
The table below shows the monthly rate of a dedicated engineer through a China-based team like ours. These are the published rates we quote international clients, and they include project management and QA.
| Level | Monthly rate (China-based, dedicated) |
|---|---|
| Junior (1 to 3 years) | $2,000 to $3,500 |
| Mid (3 to 6 years) | $3,000 to $5,500 |
| Senior (6+ years) | $5,000 to $8,000 |
| Architect / tech lead | $7,000 to $10,000 |
A focused MVP lands between $60,000 and $120,000. That covers onboarding with KYC, a portfolio view against one custodian, basic performance reporting, simple fee billing, and a client portal. A full production platform runs $150,000 to $450,000 or more, once you add financial planning, householding, document vault, multiple custodians, deep reporting, and the compliance and audit tooling a regulated firm needs.
Those are ranges, not quotes. The number that matters comes from a scoped proposal, and we wrote about getting there in how to estimate a custom software project. For the wider fintech budget picture, see how much does it cost to build a fintech app.
The drivers, roughly in order of impact:
Plan to spend the first weeks on the service model, the first custodian, and the regulatory scope, not on the app. If you do not know what "suitable" means for your product and your market, the software cannot enforce it. A focused MVP typically takes four to six months; a full production platform runs nine to eighteen months, set by the custodian integration and the compliance review.
If you are not sure an MVP is even the right first step, our fintech MVP guide walks through what to ship first and what to leave out.
Building the portal first. The client portal is the easy part and the part founders over-invest in. The custodian integration and the reporting engine are what make the product real.
Underestimating the custodian integration. Sandboxes, settlement timing, and edge cases around corporate actions eat months. Start it first, and pick one custodian before you scope the rest.
Treating billing as an afterthought. Fee schedules look simple until you have tiered AUM fees, household billing, and prorated charges. Getting a client's fee wrong is a fast way to lose them.
Ignoring the data model. If client, account, household, and position are not modeled cleanly up front, reporting and billing fight each other forever.
Skipping the audit trail. When a client questions a fee or a regulator asks why a trade was made, you need the answer in writing, down to the data that drove it.
GlobeSoft is a software development company founded in 2018, with 40-plus engineers and more than 300 delivered projects for over 100 clients across the US, Brazil, South Africa, and Singapore. We build custom software, AI products, SaaS platforms, and FinTech systems on a stack that includes Java, Spring Boot, Go, Python, React, Vue, and Node.
We have built a multi-market trading system that serves brokers across Hong Kong, US, and mainland China markets, plus financial management and payment products. Wealth management sits naturally on top of that work: the position data, the market data, the reporting, and the compliance trail are all problems we have already solved in production. You can read more about how we approach financial software in our fintech development services.
What we tell clients at the start is usually this: pick your first custodian and your first market, define the service model, and let us build the data model and the reporting around them. The portal comes last, not first.
If you are planning a wealth management platform, talk to us about your project. Tell us the market, the custodian you plan to use, and whether the platform is for your own practice or for advisors you want to serve. We will help you work through the build-versus-buy call, the scope, and what to ship first.
What is a wealth management platform?
It is the software a financial advisor or wealth manager uses to run their practice: onboarding and KYC, portfolio management, financial planning, performance reporting, billing, documents, and a client portal, all built around one client record.
How is it different from a robo-advisor?
A robo-advisor manages portfolios automatically with no human advisor. A wealth management platform supports a human advisor who makes decisions with the client. I covered the automated version in our robo-advisor guide.
How much does it cost to build a wealth management platform?
A focused MVP typically lands between $60,000 and $120,000. A full production platform runs $150,000 to $450,000 or more, depending on custodian integrations and module breadth. These are ranges, not quotes.
Do I need to be a registered investment adviser?
In most markets, firms providing investment advice are regulated: SEC or state registration in the US, MiFID II in Europe, the FCA in the UK, CVM in Brazil, MAS in Singapore. The requirements depend on your product and markets, so confirm with a compliance advisor.
What is the hardest part to build?
The custodian integration and the performance reporting engine. They look simple on a whiteboard and generate most of the real complexity and risk.
How long does it take to build?
Four to six months for a focused MVP, and nine to eighteen months for a full production platform, set mostly by the custodian integration and compliance review.
Tell us what you are building and where you are today. We typically reply within 24 hours.
