The model The engine Examples Working together Book a scoping call
Factory — example builds
[ Example build — Bayfield Wealth Partners ]

Bayfield came to us to replace their CRM and fix a client portal nobody used — without touching the portfolio system that calculates performance and bills fees. They were clicking their own households three weeks later, and live in seven months.

$1.4B · 22 peopleRIA, offices in Toronto and Vancouver
Kept their portfolio systemperformance and billing never moved
Prototype in 3 weekslive in month seven

Bayfield Wealth Partners is an example, not a client. The firm and the numbers are made up. The shape of the problem, the parts of the engine, and the way a build runs are real.

[ № 01 — The situation ]

Five systems, one advisor, one meeting

None of this is unusual. It is what happens when a firm buys the pieces separately over ten years.

The CRM

A contact list wearing a CRM badge

It holds names, emails and a notes field. It cannot hold a household with a corporation and a family trust in it, so the real shape of a client lives in the advisor’s head and in a spreadsheet on their desktop.

Onboarding

Onboarding runs on PDFs and chasing

A new client means forms by email, a signature chase and an assistant tracking returns on a printed checklist. Nobody in the firm can say how many onboardings are half finished right now.

The portal

A portal that is really a download page

Clients sign in, find a statement they already got in the mail, and leave. Fewer than one in five signed in at all last year, so every question still arrives as an email to the advisor.

“I want one place to work. Right now an advisor opens five things to prepare for one meeting.”

Managing partner, first scoping session
[ № 02 — The constraint ]

What they would not replace

Every firm has one system it cannot move. That is not a reason to stop — it is a fact the build has to design around.

Stays exactly where it is

The portfolio system stays

It calculates performance and it bills fees. Both are audited and both reconcile to the custodian. Replacing it is a two-year project this firm refuses to take on right now, so we do not touch it. We read from it, every day, and the numbers on the new desk are its numbers. The system you cannot move becomes a feed, not a blocker.

[ № 03 — The scoping sprint ]

What we learned first

Three working sessions and a look at their real data, at our cost, before anybody signed anything.

01

Households are the real unit, not accounts

About 60% of their accounts belong to a household that includes a corporation or a trust. Their CRM had no way to hold that, so the structure of the book only existed in people’s heads. Everything else we built depends on getting this right first.

02

The five tabs were four systems and a spreadsheet

We timed meeting preparation with two advisors: 40 minutes, and most of it was copying numbers between the portfolio system, the planning tool and a Word document.

03

The portal was not really the problem

Clients ignored it because it showed less than the statement they already had. A portal is only worth building on top of a client record that is complete. Fix the record first, and the portal has something to say.

04

Their data was cleaner than they feared

Two weeks in we had their real households on screen. The surprises were small and fixable: about sixty duplicate contacts, and three accounts with no owner recorded anywhere.

[ № 04 — The build ]

The household desk

One screen per household. Everyone in it and how they connect, every account with values read live from the portfolio system, the workflow that is open right now, the last meeting note, and what the client has actually seen. The advisor opens one thing before a meeting, and the client portal shows the same numbers, so there is never a second version of the truth.

Bayfield · Household desk Yours
Household · Kwan
Kwan household4 people · 3 entities
David KwanClient
Amy KwanSpouse
Kwan Holdings Inc.Holdco
Kwan Family Trust2 beneficiaries
Ella & Tom KwanChildren
Portal
Last sign-in4 days ago
Last viewedReview pack
Outstanding1 document
Accounts · read live from the portfolio system
RRSPDavid$842,300
Corporate accountKwan Holdings Inc.$2,140,000
TFSAAmy$148,900
Non-registeredKwan Family Trust$610,400
Household$3,741,600
Open workflow
Annual review 2026step 3 of 6due 12 Sep
KYC refreshed Statements in Trust minutes outstanding Review pack ready
Last meeting · 14 Aug

Sale of the operating company closes in Q1. David wants the proceeds split between the holdco and the trust. Revisit the RRSP drawdown before year end.

Illustrative screen. The account values come from the portfolio system Bayfield kept; everything around them lives in the engine.

[ № 05 — The parts ]

What it was assembled from

Most of this already existed and ran in production. Bayfield paid for the part that makes their firm different.

In the engine

Client and household records

People, relationships, households and the corporate entities behind them. This is the piece their CRM could not do.

In the engine

The whole financial picture

Accounts, insurance, property and private holdings, with owners and entities attached and a balance sheet that rolls up properly.

In the engine

Onboarding and workflows

Templates, requirement sets, forms, and the chasing of whatever is still outstanding.

In the engine

Documents and reporting

Review packages and proposals generated from live data, in their brand.

In the engine

Client portal and mobile

A portal, iOS and Android apps, and embeddable forms.

In the engine

Permissions and audit history

Every change traced to a person and a moment, from the first release.

In the engine

The AI layer

Drafting a meeting note from the record, with the advisor editing and signing off.

Built for them

The portfolio system feed

A daily read of positions, performance and fee data, reconciled, one way only.

Built for them

The meeting-prep view

The one screen the whole build is really about, laid out the way their advisors work.

Built for them

Their portal experience

What a Bayfield client sees, in Bayfield’s brand, showing the same numbers as the desk.

Seven of the ten pieces already existed. Three were built for Bayfield.

[ № 06 — The line ]

How it actually ran

Free at the start, monthly after that, and they could stop at the end of any month.

01

A free scoping sprint

Three sessions with two advisors, an assistant and the COO. We followed one real client meeting from the calendar invitation to the follow-up email.

2–3 weeks · Free
02

A prototype on their households

Their top 40 households, loaded from a portfolio export, on the desk, clickable. They reacted to something real instead of a slide.

Week 3
03

Monthly releases

The desk. Then onboarding and the workflow queue. Then the portal. Then meeting prep and review packages. Each one signed off before the next started.

Months 1–6
04

Live, then looked after

The firm moved across one team at a time. The old CRM was switched off in month seven, once nobody had opened it for three weeks.

Month 7
[ № 07 — The result ]

What changed

What the firm actually noticed, in the order they noticed it.

BeforeAfter
Meeting prep: 40 minutes across five tabs
8 minutes on one screen
Onboarding tracked on a printed checklist
A queue that shows what is outstanding, for the whole firm
Portal sign-ins: 18% of clients in a year
61% in the first quarter after launch
“What happened with this household?” — ask three people
One screen, with the history attached
The book’s real structure lived in advisors’ heads
It lives in the system, and it survives an advisor leaving

Illustrative figures for an example build.

[ № 08 — Optionality ]

Where it goes next

This is the part that is hard to buy anywhere else. You are not choosing a product roadmap — you are choosing yours.

Up next

The next two releases

Already agreed and dated.

  • Planning inside the desk — goals and cash flow read from the client’s real holdings
  • Annual review packages that assemble themselves from live data
  • Meeting notes drafted by an agent, with the advisor editing and signing off
The longer game

Bring the rest in, when you want to

The system they kept does not have to stay forever.

  • Performance and fee billing move onto the engine
  • Run both side by side for a year and compare the numbers before deciding
  • The portfolio system becomes a choice, not a dependency
  • No migration weekend, because the data has been flowing the whole time
Or pause

Or stop, and keep what you have

Pausing is a normal outcome, not a failure.

  • Stop the build team at the end of any month
  • The desk stays live and in production
  • Tax rules, custodian feeds and models keep updating underneath
  • Start again when the next thing actually matters

You choose the direction each month. Nothing about this build makes the next decision for you.

[ More — Other example builds ]

Same engine, different firm

[ Get started ]

Your firm is not Bayfield Wealth Partners

Tell us how yours runs and what you wish it did instead. Half an hour on a call. We'll tell you what's already built, what we'd have to make, roughly what it costs, and whether it's worth doing at all. Scoping after that is free.

or email us directly at factory@superadvisor.ai
Factory by Super Advisor — the wealth software factory