Solutions · Wealth and portfolio
One household, eleven asset classes.
What a family holds, across people, accounts and asset classes, in one view that staff can trust and clients can open. Built around how your firm reports, and yours to extend.
One household, as stored
- 10:02Client createdA household, risk profile ModerateCL-0058
- 10:04Investor addedTwo family members. The first is the primary investor
- 10:20Upload parsedMutual fund statement staged. Nothing in the portfolio has changed
- 10:31MF upload committedAfter the preview: one holder mapped, three folios created, one new fund
- 10:31MF holding updatedOne event for each affected folio
- 21:10MF holding updatedRevalued after the evening refresh. Actor: system
- 02:30Client net worth snapshottedA point on the trend line. Actor: system
- 09:15Client logged inOne-time code. The app reads the portfolio and cannot change it
Event names from the portfolio system that runs at a wealth advisory firm. The client code, times and counts are invented.
Running it today
The answer to "what are we worth" is assembled by hand.
A wealthy household does not hold one portfolio. It holds stocks, mutual funds, managed accounts, alternative funds, private equity, deposits, bonds, property, gold, bank accounts and insurance, across several family members, sometimes jointly, sometimes in more than one currency.
If you run a wealth firm, you know how the answer gets made. At one firm, before its system, statements were taken in over WhatsApp and ad hoc spreadsheets. There was no structured record of which investors made up a household, and portfolio reporting went back to the client over WhatsApp.
The record behind the advice lived in messages and ad hoc spreadsheets, not in a system.
Why own it
Your view of a household is your product.
Packaged portfolio tools cover what every adviser has in common: listed securities, one client, one return formula. They are built for the data feeds their vendor supports.
A wealth firm works differently. The client is a household, with joint holdings split by ownership. Return is stated one way for a deposit, another for a managed account and another for a house. Statements arrive in many layouts, and when a new fund house appears, someone has to teach the system to read it. In a rented tool that is a request to the vendor, and the asset class your client cares about most may simply not be on the roadmap.
What your client sees when they open the app is how they judge the firm. That is worth deciding yourself: which classes count, how return is shown, what appears and what does not.
What an owned system records
A statement is previewed before it changes anything.
In the system that runs at the wealth advisory firm, a statement is uploaded, read by a parser written for its layout, and staged. Nothing in the portfolio has changed. Staff see what the system understood and settle what it could not: an identity number that matches no investor, a folio with no account, a fund not seen before. Then they commit.
Each commit, revaluation and nightly net worth snapshot is an event. It is a record of what a household holds. It does not hold mandates, take instructions, rebalance or recommend. Because the record is kept this way:
- Trace. Each account's history shows who did what, when, and from which source file.
- Correct without overwriting. A later upload is a new commit, recorded after the earlier one. The earlier commit, who made it and when, stays in the event log.
- A trend that draws on history. The net worth trend is a line of stored nightly snapshots, not a figure recalculated afterwards.
Already handled
The hard parts, already built once.
Every item below was a real complication in one firm's data, modelled in the system built for that firm.
Wealth advisory firm: Portfolio management case study
One statement, a whole household
A consolidated mutual fund statement covers several people and folios. Each holder's tax identity number is matched to an investor, or mapped by staff in the preview.
Wealth advisory firm: Portfolio management case study
Many layouts, one preview
Statements arrive in many layouts, and each is read by a parser written for its layout. One PDF can hold several accounts, and is split into one commit for each.
Wealth advisory firm: Portfolio management case study
A price that is missing or stale
A fund with no price yet is valued at cost. A stale value is shown with its date. A refresh that fails flags the instrument; it is not skipped silently.
Wealth advisory firm: Portfolio management case study
Joint holdings and currencies
An account has holders whose shares sum to 100, and one currency. Household totals convert to a display currency, and say so when a rate is missing.
Wealth advisory firm: Portfolio management case study
Return is not one formula
Managed accounts use the statement's figure, deposits the stated rate, property and gold a simple return. All appear in one Return column. All appear in one Return column.
Wealth advisory firm: Portfolio management case study
Holders who are not individuals
A family entity or a private company can hold an account. It is entered as an investor like anyone else, inside the same household.
Wealth advisory firm: Portfolio management case study
Recorded, but not counted
Insurance policies are held with their renewal and maturity dates, and are deliberately left out of net worth.
Wealth advisory firm: Portfolio management case study
An app that only reads
The customer app, built for iPhone, Android and the web, signs a client in with a one-time code and shows the household. It cannot change the portfolio.
The first build
The first build describes your households and your statements.
The first build is not a pilot. It is where your firm's way of holding client data gets described, and every later system is built from that description. It is written with the staff who receive the statements and answer the questions.
Entities
The things your operation keeps track of.
- Households, investors and joint holders
- Your asset classes, and which count towards net worth
- Accounts, folios and currencies
- Your statement layouts. Each new one is a parser
Events
What happens to them, in your words.
- Statement uploaded, parsed, previewed
- Upload committed, and by whom
- Holding revalued
- Net worth snapshotted
Exceptions
What happens when it does not go to plan.
- An identity that matches nobody on file
- A fund or instrument not seen before
- A missing price or exchange rate
- How return is stated for each class
What carries forward from the foundation
The event log and roles and permissions come from the foundation, so the time goes into your asset classes and your layouts. What the client sees is designed with you: net worth, holdings, the family split, the trend, maturities.
What comes after
The household record is what later work builds on.
Once households, accounts and holdings are on record, a further statement layout, asset class or client-facing view is an addition, not a rebuild. Each sits on the history already held. It extends without a migration.
After the first build the framework becomes available to you. Your own engineers and product people can build the next system on it, or we carry on building for you. Both stay open. What that involves is settled in the first conversation, scoped to the engagement.
Get started
Tell us what your clients hold, and how you report it.
The asset classes, the statements you receive and what a client should see. The first conversation is about your households, not a demo.
coffee@jetbro.inWhatsApp +91 90999 62227