Three Specialist Advice Workspaces From One Codebase

The challenge

Wealth advisers, insurance advisers and mortgage brokers do similar paperwork with different words for everything. A wealth adviser talks about clients and portfolios, an insurance adviser about policies and cover, a broker about borrowers and lenders. One generic product felt like it was built for somebody else. Three separate products would have tripled the work of building and running them.

What we built

One FinPlan application that presents itself as a specialist product to each kind of adviser:

• Three brands and a general workspace: Cedar for wealth management, Sequoia for insurance and Oak for mortgage broking, each with its own colours, tagline, icon and terminology.
• Onboarding that picks the brand: six steps covering speciality, practice details, jurisdiction and a compliance acknowledgement, ending with sign-in through Google or Microsoft. The app takes on the brand's look the moment a speciality is chosen. Progress is saved in the browser, so an adviser can leave and pick up where they stopped.
• Regulator-aware copy: the jurisdiction step covers Australia, New Zealand and the United Kingdom, with copy that refers to ASIC, the FMA or the FCA as appropriate.
• Brand carried through sign-in: the chosen brand and onboarding answers travel through the Google or Microsoft sign-in, are saved to the account and are written into the session token, so the right workspace loads on every visit.
• Documents filtered by speciality: each brand sees the document types for its field, such as investment policy statements for Cedar, insurance comparisons for Sequoia and credit guides for Oak, alongside the shared file notes and fact finds.
• Themes as variables: brand colours are applied as CSS variables at runtime, so one set of components serves every brand.

Technology

The brand is stored per account in MongoDB and carried as a claim in the session cookie. Custom Spring Security sign-in handlers pass onboarding answers through the Google and Microsoft flows. The Next.js front end uses a brand context, CSS variables and Framer Motion for onboarding transitions and the animated sign-in background. Every brand runs on the same production deployment, which we operate as part of An AI Platform That Turns Client Meetings Into Finished Reports.