Current State
Meeting Sidekick is the starting point; revenue and team modules fold underneath.
Project
Sidekick
The product family for meeting, revenue, and team workflows.
The product family for meeting, revenue, and team workflows.
Product familyMeetingsRevenue workflowsTeam memory
Flagship Case Study
The Sidekick product family
Meetings and revenue teams do not need another assistant floating beside the work. They need prep, context, commitments, closeout, corrections, and manager-readable outcomes in one product.
The product is intentionally focused: help teams prepare the work, run the meeting, close it out, and carry the next step into the systems they already use.
Where the pain lived
AI outputs were useful in the moment but easy to lose, disconnected from meeting history, and rarely tied back to account work or manager review.
What had to be true
The system needed trusted context, releases, receipts, corrections, shared/private boundaries, and rollback so teams could improve their AI work over time.
Why it matters
This is the bridge between one person getting help from AI and a team improving how the work gets prepared, executed, closed out, and reviewed.
Positioning Lens
Sidekick
Sidekick is the productized version of that belief: Meeting Sidekick is the starting point, revenue workflows are the next module, and the old SalesSidekick / Sidekick Genius names now fold under one product family.
Signature product decisions
- Folded Meeting Sidekick, SalesSidekick, and Sidekick Genius into one product family instead of presenting three separate public products.
- Made prep, closeout, memory, receipts, and correction loops the core product rather than a reporting afterthought.
- Kept consequential actions behind review so the product earns trust before automation expands.
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.
Meetings and revenue work create the context, commitments, risk, and follow-through that actually matter. Most AI tools still leave that work as isolated notes, chats, or assistant output. Sidekick turns it into a focused product family.
The Build
What I built around the problem
Sidekick folds Meeting Sidekick, SalesSidekick, and Sidekick Genius into one product family: meeting prep, live context, closeout, revenue workflows, team memory, receipts, and portability across the AI tools customers already use.
Architecture 1
Meeting Sidekick is the starting point: prepare the call, capture context, reason through the meeting, and close out the work.
Meeting Sidekick is the starting point: prepare the call, capture context, reason through the meeting, and close out the work.
Architecture 2
Sales/revenue modules carry account context, approved skills, evidence, receipts, and manager-readable outcomes.
Sales/revenue modules carry account context, approved skills, evidence, receipts, and manager-readable outcomes.
Architecture 3
The broader Sidekick product family can extend the same context and memory pattern into non-revenue team work.
The broader Sidekick product family can extend the same context and memory pattern into non-revenue team work.
Reality Check
The product is clearer when the old names stop competing
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 has been hard
The hard part has been separating the valuable product from the old habit of treating Meeting Sidekick, SalesSidekick, and Sidekick Genius as separate public companies.
02
What had to change
The sharper product language became one family: meeting and revenue workflows, context, receipts, corrections, team visibility, and memory.
03
Current boundary
Sidekick is the software direction. The old names stay reachable as history, modules, or aliases, but they should not clutter the front door.
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.
Product family
Sidekick
Sidekick is the product family for meeting, revenue, and team workflows.
Starting point
Meetings
Meeting Sidekick gives the product a concrete starting point: prep, live context, closeout, and follow-up.
Current boundary
Converged
The old names remain useful history and route aliases, but the public direction is one Sidekick product family.
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.
Meeting prep, live context, transcript intake, closeout, and follow-up workers
Revenue workflow modules for account context, approved skills, receipts, and coaching
Team memory and correction loops that travel across meetings, documents, CRM, and chat
Context and evidence shared with Joan
Microsoft-aligned deployment direction for M365, Teams, Graph, Dynamics, Azure, and Azure OpenAI
OpenAI, Anthropic, and Codex portability where the customer wants multiple AI tools
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: the product family for meeting, revenue, and team workflows.
02
System shape
Meeting Sidekick is the starting point; revenue and team modules fold underneath. 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.
Product family
Product family
Meetings
Meetings
Revenue workflows
Revenue workflows
Team memory
Team memory
Continue
Want to go deeper?
Ask the Latif AI Guide about the architecture, the commercial logic, or the hard lessons behind this project.