Prepare for meetings faster using AI-assisted workflows.
Reduce manual research, improve preparation quality, and generate better meeting context using practical AI systems.
The real reason you walk into meetings under-prepared.
It's rarely about effort. It's about not having a repeatable system for turning scattered information into clear context — fast.
- Repetitive preparationRe-doing the same kind of research before every call instead of running a system.
- Fragmented researchContext lives in five tabs — LinkedIn, the website, the CRM, the last email, your notes app.
- Poor meeting contextYou walk in knowing the agenda but not what each person in the room actually cares about.
- Generic questionsDefault discovery questions that don't move the conversation past surface-level answers.
- Manual follow-upWriting the same recap and next-steps email from scratch after every call.
Built for people who run on meetings.
If your week is shaped by 8–15 conversations and the quality of each one compounds — this system is for you.
Six steps. Roughly ten minutes.
Run them in order the first few times. Once the rhythm clicks, you'll cherry-pick the steps you need.
Understand the business before the conversation, not during it.
How to run it: Use Perplexity or ChatGPT with browsing to summarise the company: what they sell, who they sell to, recent news, funding, and strategic direction.
Know who's in the room and what they're likely to care about.
How to run it: For each attendee, generate a short profile: role, tenure, recent posts, and the priorities most relevant to your meeting.
Consolidate everything into a one-page brief you can scan in 60 seconds.
How to run it: Combine the company and stakeholder research into a single structured brief — context, attendees, likely outcomes, and risks.
Ask questions that surface real constraints, not surface-level answers.
How to run it: Prompt the model to draft 5 sharp, open-ended questions tailored to the company, the role of each attendee, and the meeting goal.
Capture the right things during the call — without having to think about format.
How to run it: Generate a lightweight notes template (context, key points, decisions, owners, next steps) and keep it open in Notion or Apple Notes.
Send a clear, specific recap within an hour of the call ending.
How to run it: Paste your notes back into the model and ask for a short follow-up email: what was discussed, what was agreed, and the single next step.
Four prompts. Run the whole system.
Tested across GPT-5, Claude Sonnet, and Gemini 2.5. Replace anything in {curly braces} before sending.
Act as my research assistant. Produce a one-page brief on {COMPANY}.
Sections:
1. What they do, in plain English (3 lines).
2. Who they sell to and how they make money.
3. Recent signals from the last 6 months: funding, hires, launches, public posts.
4. Strategic direction — what they appear to be betting on.
5. Three things that would matter to them in a meeting about {TOPIC}.
Tone: calm, direct, factual. No hype. Cite sources where possible.For each of these attendees, produce a short profile:
{ATTENDEES}
For each person include:
- Role and likely scope of responsibility
- One recent public signal (post, talk, hire, launch) if known
- The one thing they probably care most about in a meeting on {TOPIC}
- A talking point that would land with them specifically
Keep each profile to 4 lines maximum. No filler.I have a meeting with {ATTENDEES} from {COMPANY} about {TOPIC}.
Draft 5 strategic, open-ended questions I can ask. They should:
- Surface real constraints, not surface-level answers
- Be specific to this company and these people, not generic
- Mix at least one question about current process, one about success criteria, and one about what's already been tried
Avoid leading questions and anything that sounds like a sales script.Below are my notes from the meeting with {ATTENDEES} at {COMPANY}.
Notes:
"""
{NOTES}
"""
Write a follow-up email that:
1. Opens with one specific thing they said (not "great chatting today")
2. Recaps the 2 most important points in their language
3. Names the single next step we agreed on, with a date
4. Ends with one clear ask
Constraints: under 140 words. Match my tone — direct, warm, senior. No "circle back" or "synergy".What the system actually produces.
Two artefacts from a real-world prep cycle. Pricing review, three attendees, thirty-minute call.
- Acme is reviewing their current vendor stack ahead of a 2026 budget cycle.
- Pricing review was triggered by a 22% YoY increase on their last renewal.
- Likely outcome they want: a clear path to flat or reduced spend without losing functionality.
- Sarah Chen · VP OperationsOwns vendor budget. Cares about predictability and reporting.
- Marcus Lee · Head of RevOpsDay-to-day user. Cares about workflow continuity.
- Priya Singh · Finance PartnerJoined last quarter. Cares about unit economics, not features.
- 01What would a successful renewal look like to each of you, in one sentence?
- 02Where is the current setup costing you more time than money?
- 03What did you try last year that didn't work?
Subject: Quick recap + next step Sarah — picking up on your point about predictability heading into the 2026 cycle, here's what I took away: 1. The 22% jump on the last renewal is the real trigger, more than functionality. 2. Marcus is comfortable with the current workflow — the question is commercial, not product. Proposed next step: I'll send a flat-rate option scoped to your current usage by Tuesday, with two scenarios for Priya's unit-economics view. Workable? — You
Where this system tends to break.
AI should support your thinking — not replace it.
Use this system for the parts of preparation that are repetitive: research, structure, drafting. Keep the parts that matter — judgment, communication, strategy, the relationship in the room — yours.
- Operational leverage
- Workflow acceleration
- Preparation quality
- Judgment
- Communication
- Strategy & relationships