A unified wealth platformfor advisors andtheir clients.
A regulated wealth manager replaced seven internal tools with one product. Built to be used daily by advisors, learned in hours by new joiners, and inspected without argument by compliance.
ClientConfidential. Mumbai, India.
SectorPrivate wealth management
ServicesStrategy, research, product design, AI architecture, engineering oversight
Timeline14 weeks to first release
EngagementOngoing. Advisory and design.
01 / 05
One product, one record.
Seven internal tools became one product surface. A client is one record, opened by advisors in three cities, inside the firm's own tenant.
02 / 05
Onboarding that finishes in one sitting.
The onboarding sequence we mapped in the field, not the one in the manual. Every handoff that used to add a day is gone. A new client is set up in one sitting.
03 / 05
Every field shows where it came from.
Compliance sees seven systems, advisors see one tool. Each field carries its source, so data lineage is a fact on the screen rather than a question in an email.
04 / 05
Learned in hours, not quarters.
A knowledge hub that searches the firm's own playbooks sits next to the work. New advisors ask it instead of a colleague, and the firm's own answers come back.
05 / 05
Live inside the firm's own tenant.
In daily use across the advisory team, on a quarterly review cadence. Nothing leaves the firm's Microsoft tenant.
I / Context
Eighty advisors, seven tools, and nobody sure where the client data lived.
The firm had grown to eighty advisors across three cities. Clients were onboarded through spreadsheets, vendor portals and email threads. Every handoff added a day. Compliance had flagged client data living in three systems with no clear lineage.
Leadership had one conviction: invest in one product, not seven integrations. They wanted a partner who could think through the regulated edges of the work, not a vendor who could only draw screens. Six firms pitched. We won on a two-page memo.
II / Approach
Four phases. The same people, start to finish.
Each phase had its own definition of done. The people who ran discovery ran the launch, with engineering oversight throughout.
01
Discovery, in the field
We sat with advisors in Mumbai, Pune and Bengaluru, and rode along on three client meetings. We mapped the onboarding sequence that happens in practice, not the one in the manual. The brief we wrote replaced four earlier internal documents.
Weeks 1 to 3
02
Architecture and compliance
The platform had to behave like one tool to advisors and like seven systems to compliance. We modelled the data flows, drew the role-based access matrix, and chose a stack that can be audited end to end. We worked with the compliance lead, not around her.
Weeks 3 to 5
03
Design and build, in parallel
Three surfaces: client onboarding, a portfolio review workspace, and a knowledge hub that searches the firm's own playbooks. Designed in two-week sprints, built alongside by the firm's engineers, with Osquare in every review and on every architectural call.
Weeks 5 to 14
04
Pilot, refine, embed
Released to twelve advisors first, with weekly research calls for a month. The onboarding sequence, the workspace defaults and the search all changed because of those sessions. Now in use across the full advisory team, on a quarterly review cadence we still run.
Ongoing
III / Outcomes
What changed in the first six months.
Seven internal tools are gone. New advisor onboarding moved from days to hours. Compliance has stopped flagging data lineage. Advisors open the platform because they want to, not because the firm makes them. That is the outcome we cared about most.
7→to 1Internal tools replaced by one product surface
80+Advisors in daily use across three cities
14wksFrom kick-off to first release with the pilot group
Tenant isolatedKnowledge hub trained on the firm's own playbooks
They did in eleven weeks what our previous vendor could not do in a year. Harder questions, fewer slides, and a product we actually use.