Current State
Prep, in-call capture, and a 6-output closeout.
Project
Meeting Sidekick
A digital employee for every meeting.
A digital employee for every meeting.
Meeting lifecycleGoverned runtimeCloseoutJoan4U
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 are where relationships, commitments, risk, and follow-up are created, but most tools only summarize after the fact. Meeting Sidekick is the product answer: prepare before the meeting, reason during it, and close out the work afterward.
The Build
What I built around the problem
Meeting Sidekick is the Joan4U meeting product direction: research and prep before meetings, in-call capture and reasoning during meetings, and a 6-output closeout plus digital workers for follow-up.
Architecture 1
Pre-meeting research over people, companies, assets, and objectives.
Pre-meeting research over people, companies, assets, and objectives.
Architecture 2
In-call listening and reasoning for technical, sales, and general meeting support.
In-call listening and reasoning for technical, sales, and general meeting support.
Architecture 3
Post-call closeout plus follow-up workers that can gather assets, create materials, and execute next steps.
Post-call closeout plus follow-up workers that can gather assets, create materials, and execute next steps.
Reality Check
Meetings are high leverage because they are messy
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
A meeting system has to do more than summarize nicely after the fact. It has to deal with incomplete context, live ambiguity, relationship risk, and follow-up that people actually trust.
02
What had to change
The product direction moved toward the full meeting lifecycle: prep, live support, closeout, and follow-up workers, with governance around what the system should and should not do.
03
Current boundary
Meeting Sidekick is an active product direction. The honest claim is the current build path, not a declaration that every live-meeting behavior is solved.
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
active
Meeting Sidekick is shown here as a major current project.
Current signal
Prep, in-call capture, and a 6-output closeout.
documented product direction with live in-call work grounded in the operating record
Public boundary
Current framing
documented product direction with live in-call work grounded in the operating record
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.
Joan4U meeting runtime for prep, live capture, reasoning, closeout, and follow-up work
Recall-style meeting capture and transcript intake boundary for live meeting context
Skill layer for sales assistance, technical assistance, meeting marshal behavior, and follow-up routing
Post-meeting worker queue for assets, research, presentations, emails, and CRM-ready follow-through
Governed memory and receipt model so every meeting improves the next brief
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: a digital employee for every meeting.
02
System shape
Prep, in-call capture, and a 6-output closeout. 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.
Meeting lifecycle
Meeting lifecycle
Governed runtime
Governed runtime
Closeout
Closeout
Joan4U
Joan4U
Continue
Want to go deeper?
Ask the Latif AI Guide about the architecture, the commercial logic, or the hard lessons behind this project.