Evidence Signal
Prior product lessons, with the Joan layer still being assembled.
Project Deep Dive
Joan
The convergence: customer-owned work intelligence under one roof.
The convergence: customer-owned work intelligence under one roof.
Owned work intelligenceBuilt project historyJoan
Flagship Case Study
The Owned Work-Intelligence Idea Behind Joan
Joan Platform is the customer-owned work-intelligence layer: the system that captures how people work with AI, turns it into governed owned memory, and re-injects that memory into the surfaces where work happens.
This project shows how I think about enterprise AI when the real asset is not a prompt or a chat. It is the durable operating memory of how people make decisions, prepare, follow up, and improve work over time.
Where the gap is
AI work is spreading faster than owned memory. Teams keep rebuilding context, losing corrections, and starting cold when the work moves across tools, people, and models.
What had to be true
The platform needs capture, governed memory, intelligence, runtime, reinjection, and interface layers so useful work intelligence can compound instead of disappearing.
Why it matters
This is the enterprise version of the AI operating-system problem: make the way work happens customer-owned, trusted, and portable across frontier AI surfaces.
Positioning Lens
Joan
Joan matters because model access is rented, but the way a company works should be owned. The product starts with revenue and meetings because those workflows expose context, memory, trust, and follow-through pressure immediately.
Signature platform decisions
- Converged several prior projects into one customer-owned work-intelligence platform direction.
- Made governed memory and reinjection the core product language rather than a dashboard or vendor silo.
- Set revenue as the first domain while leaving the kernel portable to meetings, teams, and future worker paths.
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.
AI work is getting more capable, but the most important asset is not the rented model. It is the owned middle: the governed memory, context, evidence, and operating history that lets work compound across people, tools, and models.
The Build
What I built to solve it
Joan is the product direction that brings lessons from prior builds into a customer-owned work-intelligence layer, while staying clear about what exists now and what is still being assembled.
Architecture 1
Customer-owned work intelligence under one roof.
Customer-owned work intelligence under one roof.
Architecture 2
Prior builds provide the evidence base for the product direction.
Prior builds provide the evidence base for the product direction.
Architecture 3
The page separates what has already been built from the broader Joan direction still being assembled.
The page separates what has already been built from the broader Joan direction still being assembled.
Value
What changed because it existed
This is the clearest evidence of practical value, system leverage, and execution quality.
Product role
Convergence
Joan now holds the primary company and product direction for owned work intelligence.
Built history
Prior builds
Meeting Sidekick, SalesSidekick, VibeOS, WorkspaceOS, SignalClaw, and other systems show the pattern behind Joan.
Boundary
Emerging layer
The broader Joan layer is still being assembled, while the existing projects show the pattern behind it.
Technical Layer
How the system is built
This is the implementation surface behind the work: the architecture choices, operating layers, integrations, and controls that make the project more than an idea.
Customer-owned work-intelligence architecture across capture, memory, governance, and reinjection
Product lessons from Meeting Sidekick, SalesSidekick, VibeOS, WorkspaceOS, and SignalClaw
Governed memory layer for decisions, corrections, receipts, skills, workflows, and agent behavior
Enterprise control surface for policy, approvals, exceptions, auditability, and portability
Microsoft-aligned deployment direction: Microsoft 365, Graph, Azure, Azure OpenAI, AI Search, and Key Vault
Build Story
How the thinking unfolded
This is the reasoning path behind the output, not just the finished artifact.
01
Problem definition
The work starts from a concrete operating problem: the convergence: customer-owned work intelligence under one roof.
02
System shape
Prior product lessons, with the Joan layer still being assembled. The public page focuses on the product vision, architecture, and proof signal.
03
Current representation
Project media will be added after the reviewed creative assets are approved.
Capability Signal
What this project demonstrates
Each project is a proof point. These are the capabilities it most clearly reveals.
Owned work intelligence
Owned work intelligence
Built project history
Built project history
Joan
Joan
Continue
Want to go deeper?
Ask the Latif AI Guide about the architecture, the commercial logic, or what this project says about how I approach hard problems.