From raw meeting notes to polished doc in one message

You scribbled six bullets in a meeting. You need a shareable summary for people who weren't there. Here's how to let Navi do the 20 minutes of polishing for you.

The gap between "notes I took" and "doc I'd send" is usually an expensive commute. You have to re-read your scrawl, expand the shorthand, add the context the reader lacks, structure it into headings, share it with five people, and hope nobody asks a follow-up question that was already covered somewhere else.

Navi closes that gap in one message.

The setup

Right after a meeting ends, open Navi. Type your raw notes and ask for the polished version:

What comes back

A minute or two later, Navi has created the doc, pulled context from the meeting invite and related Notion / Linear activity, and shared it. What the three of you see:

Q2 Planning — April 16

Attendees: Sarah Chen, Dan Orozco, M.

Context. Q2 kicks off on April 29. This meeting was the final planning sync before the cycle plan goes to the team. Sarah, Dan, and I needed to agree on hiring targets, a budget envelope, and a timeline for cycle-plan publication.

Hiring plan. Two open roles carried forward: senior designer and growth engineer. Both need to be re-scoped before posting — Dan is owning that work. Sarah flagged concern about the designer pipeline given the market; Priya will help source candidates over the next two weeks.

Budget. Q1 came in 8% under plan, giving us room for one additional hire in Q2 without breaking the annual envelope. Decision pending the re-scoped role definitions above.

Timeline. Q2 kickoff in two weeks. Sarah, Dan, and I to finalize the hiring plan and publish the cycle plan by end of week.

Open questions.
• Should the extra hire slot go to design or growth?
• Are we on track for the external comms around Q2 launch?

You skim it. Tweak one or two things. Share it. Total time from meeting ending to a clean doc in Sarah and Dan's hands: under three minutes.

Why this is better than just writing it yourself

Two things happen when Navi does it that you wouldn't bother to do manually:

Context gets pulled in. The "context" paragraph isn't something you'd type — you'd assume the reader knows. Navi checks the calendar event, reads related Notion pages and Linear issues, and writes the context explicitly. For anyone who wasn't in the room, that paragraph is the whole point.

Open questions get named. The easy thing is to write the summary as a statement of what you decided. The valuable thing is to write the summary as a list of what's decided and what isn't. Navi pushes toward the latter.

Variations

• Notion destination. Replace "Create a Google Doc" with "Create a page in the Meeting Notes Notion database." Same shape, different home.
• Follow-up tasks. Append to the prompt: "Also create Linear issues for each action item and assign them to the right person." Navi will create them with links back to the meeting doc.
• Slide-deck summary. Append: "Then create a three-slide Google Slides deck summarizing the decisions — one slide per section." Doc + deck, one message.

The underlying pattern

Navi's best use case is this: you already did the thinking. You have the raw material. What you need is the glue — the summary, the context, the distribution, the follow-ups. That's all cheap work Navi does in parallel while you move on to the next thing.

Try it after your next meeting. Paste your notes. One prompt. Done.

← All posts