Current State
Microsoft foundation, secure client journey, and service controls.
Project
Joans
Wealth-management AI for fiduciary client work.
Wealth-management AI for fiduciary client work.
Wealth managementFiduciaryMicrosoftClient work
The Problem
What problem was worth solving?
I build things to solve a specific pain, not to decorate a portfolio. This is the pressure that made this project necessary.
A wealth-management practice cannot adopt AI as loose chat activity. It needs a practice-controlled system that respects fiduciary judgment, controls context, structures client work, and keeps the practice rather than the model at the center.
The Build
What I built around the problem
Joans is a Microsoft-based wealth-management AI system for Impact Investors, with secure client journeys, reviewed services, and practice-controlled workflow support.
Architecture 1
Firm-owned AI work layer for wealth-management and fiduciary work.
Firm-owned AI work layer for wealth-management and fiduciary work.
Architecture 2
Microsoft foundation with security, governance, and client-journey controls.
Microsoft foundation with security, governance, and client-journey controls.
Architecture 3
Designed to keep client context, judgment, services, and practice memory under the firm's control.
Designed to keep client context, judgment, services, and practice memory under the firm's control.
Reality Check
Current boundary
The point is not to pretend the work was clean. This is what the project taught, where it changed shape, or where the boundary still matters.
01
What this page should do
This page should explain why the project mattered without turning unfinished, private, or earlier work into a bigger claim than the public record supports.
02
Status
Joans is currently represented as in build. The useful parts of the story are kept visible, but the page should stay clear about what is current and what is history.
03
Boundary
Client-sensitive details stay out of public copy unless they belong in an approved case study.
Value
What changed because it existed
This is the practical value of the work. Where a project is unfinished, shelved, or still changing, the value is tied to what it actually taught.
Current status
in build
Joans is shown here as a major current project.
Current signal
Microsoft foundation, secure client journey, and service controls.
foundation documented; build still in progress
Public boundary
Current framing
foundation documented; build still in progress
Technical Layer
How the system is built
This is the implementation behind the work: the architecture choices, integrations, controls, and workflow decisions that made the project real enough to learn from.
Microsoft 365 and Azure foundation for secure advisor/client work
Practice-owned client journey layer for onboarding, service workflows, and review moments
Governed context and memory layer for fiduciary work without exposing private client architecture
Service framework for research, client preparation, and advisor operating support
Security-first architecture boundary: public page explains the framework, not private IIN internals
Build Story
How the thinking unfolded
This is the reasoning path behind the output, not only the finished artifact.
01
Problem definition
The work starts from a concrete operating problem: wealth-management AI for fiduciary client work.
02
System shape
Microsoft foundation, secure client journey, and service controls. The public page focuses on the product vision, architecture, and current signal.
03
Current representation
Project media will be added after the reviewed creative assets are approved.
Evidence
What this project shows
This evidence is strongest when it is tied to specific work rather than broad claims.
Wealth management
Wealth management
Fiduciary
Fiduciary
Microsoft
Microsoft
Client work
Client work
Continue
Want to go deeper?
Ask the Latif AI Guide about the architecture, the commercial logic, or the hard lessons behind this project.