Meetings are where work actually happens — and where the most gets lost. Dex closes the loop on both ends: context in before the meeting, and capture out after it, with the follow-through tracked until it's done.

Before: /meeting-prep

Tell Dex which meeting ("prep me for the 2pm with Northwind") or just run /meeting-prep before a calendar event. Dex assembles a brief from what it already knows:

  • who's attending, with each person's history and what they care about
  • the company page, if it's an external account
  • open action items between you and the attendees
  • related past discussions — including thematically related ones, not just files with a matching name

The quality of prep compounds with your history. In week one it's thin; after a month of processed meetings, it's the kind of brief a good chief of staff would hand you.

After, with a recorder: automatic capture

If you've connected Granola, meetings flow in on their own. A daily background sync fetches new meetings, and /process-meetings turns them into structured memory:

  • a filed note per meeting — summary, decisions, action items
  • tasks created for your action items, with proper tracking IDs
  • person pages updated with what each attendee said and committed to
  • links to related projects, so the meeting connects to the work it affects

Dex also reads for the soft stuff regex would miss — "we should probably revisit pricing next quarter" gets flagged as a likely follow-up, not lost as filler. And after someone shows up in a couple of meetings across different weeks, Dex creates (or offers to create, your choice) a page for them automatically.

After, without a recorder: just tell Dex

No transcript tool? The loop still works — you're the capture device:

Walking back from the roadmap review
just out of the roadmap review with Sarah and Tom. we agreed to cut the reporting feature from Q3. Tom owns telling the beta customers by Friday. Sarah was skeptical about the timeline — worth watching.
Filing…
Meeting note — 2026-07-28 - Roadmap Review.md
decision logged: reporting feature cut from Q3
Work — creating task
^task-20260728-014 · Tom: notify beta customers · due Fri
Person pages — updating
Sarah_Chen.md (timeline concern) · Tom_Osei.md (owns comms)
Done. Anything you committed to that I missed?
yeah — I said I'd revisit the pricing question next month
Work — creating follow-up
revisit pricing · due late August · owner: you

One rambled paragraph while you walk back to your desk; Dex does the filing — and asks the question a good chief of staff always asks: what did you commit to?

The follow-through

Action items aren't sticky notes — they're tracked tasks that appear in your daily plan, linked from the meeting where they were born and the people they involve. When you say "done with the beta customer emails," the completion is recorded everywhere the task appears. Nothing depends on you remembering to check a list.

What the prep brief surfaces in your world

Deal stage and momentum, the champion's last words, open commitments both ways, and the pricing question you should expect.

Two prompts that upgrade meeting prep

The standard brief tells you about them. These make the prep about you:

Copy-paste prompt / Quiz me before I walk in 
Before my [TIME] with [WHO]: don't just brief me — quiz me. One question
at a time: What's my actual goal for this meeting? What am I willing to
concede? What must I not leave without? What's the question I'm hoping
they don't ask? Then give me the brief, shaped around my answers.
Copy-paste prompt / The other side of the table 
Based on everything in my notes about [PERSON] and their company: write
the prep document THEY would write for this meeting with me. What do they
want out of it? What's their read on how it's going? What will they push
on? Now — what should I do differently, knowing that?

Make it your own: the second one is unreasonably effective before negotiations and renewals. More like these in Prompts to steal.

Where meetings live

Every meeting note is a plain file in 00-Inbox/Meetings/, named by date and topic. Six months from now you can ask "what did we decide about pricing in the spring?" and Dex will find it — by meaning, not just keywords, if you've enabled semantic search.

A realistic meeting day

  1. 9:00 — /daily-plan flags that your 2pm is with a customer whose renewal stalled last quarter.
  2. 1:50 — /meeting-prep gives you the two-minute read: attendees, history, the open commitment your team hasn't delivered.
  3. 3:00 — the meeting synced from Granola; /process-meetings extracts the three action items, assigns yours into today's plan.
  4. 5:30 — /daily-review notices one action item is untouched and carries it to tomorrow's Must list.
MAKE THIS PAGE ABOUT YOU

Don't just read this — paste it into your own Dex and it becomes a lesson about your actual work.

First, fetch and read the page I'm referring to: https://heydex.ai/help/meetings.md

I just read the Dex Guide's meetings page. Find my highest-stakes meeting
in the next few days and run the full loop on it with me, live: prep me
now — attendees, history, open promises, the question I should be ready
for. After it happens, I'll come back and debrief you in one rambling
paragraph, and you do the filing: note, decisions, tasks, people pages.
This one meeting is the demo. Deal?