AI meeting notes for product managers

Where product managers lose information in meetings

Most of a PM's evidence is spoken. A customer explains a workaround, an engineer flags a constraint in a requirements session, a sales lead repeats a request in a roadmap review. The loss happens in a few predictable places.

• Typing while listening. You either take good notes or ask good follow-up questions. Doing both means the follow-up that would have uncovered the real problem never gets asked.
• Paraphrase drift. "Customer finds reporting confusing" in your notes was "I rebuild this chart by hand every Friday" on the call. The second sentence is the one that gets a feature prioritized.
• Interviews scattered across documents. Six weeks into discovery, the notes live in four places with four formats, so comparing them is a weekend project.
• Decisions with no record. A stakeholder sync agrees to cut scope, and two weeks later nobody remembers who agreed or why.

There is also the bot question. Many note takers join the call as a participant, which you then explain at the start of every customer conversation. Natively captures your computer's system audio and microphone instead, so it works in Zoom, Teams, Google Meet in a browser, Webex or Slack huddles without adding anyone to the call. That does not remove the need to ask permission, covered below.

A user interview from prep to synthesis

1. 1Before: set up the meetingWith your calendar connected, Natively names the meeting after the event and knows who was invited. Pick the User interview template and type your three or four hypotheses into the notes so the summary has something to test against.
2. 2During: listen, mark momentsType short markers ("pricing!", "workaround") rather than full sentences. The transcript labels you separately from the customer. If they share a spreadsheet or dashboard on screen, take a screenshot and ask about it, for example "what columns are they tracking by hand?"
3. 3During: check coverageBefore wrapping up, ask Natively "which of my hypotheses has she not talked about yet?" It answers from the live transcript, so you can use the last five minutes well.
4. 4Right after: review the notesNatively writes a summary, sections and action items from the transcript next to your own markers. Spend two minutes correcting anything it got wrong while the call is fresh.
5. 5Later: share and compareSend the notes to a Notion page for the research database or a Slack channel for the team, then use the interview in cross-interview questions as described next.

Synthesizing eight interviews without rereading eight transcripts

Natively keeps a local search index over your meetings, so you can ask questions across all of them. For a round of eight discovery interviews, a workable synthesis pass looks like this.

1. Ask the broad question: "Which customers mentioned exporting data, and what were they trying to do?"
2. Ask for the counter-evidence: "Who said the current export is good enough?" A synthesis that only collects agreement is a confirmation exercise.
3. Ask about intensity: "Who described a workaround they do every week?" Frequency of pain is more useful than mentions.
4. Open each meeting the answers point to and copy the exact sentence from its transcript into your synthesis doc.
5. Write the finding in your own words, with the quotes underneath, and share it from Notion.

Product meetings mapped to what to use in Natively

Note templates are part of Pro, and the one-time 30-minute free trial lets you try them on a real interview first. See pricing for the plans. The notepad page shows how your typed notes and the generated notes sit side by side.

Setting up Natively for product work

1. 1Install on your computerNatively runs on macOS 12 or later and Windows 10 or 11 (x64). Allow the microphone and audio access it asks for.
2. 2Choose how speech is transcribedUse your own key for a speech provider such as Deepgram or Soniox, or an on-device model such as Whisper or Parakeet. Set the language your customers speak; 46 languages are available, depending on the provider.
3. 3Choose the AI modelUse your own key for OpenAI, Claude, Gemini or another provider, a local Ollama model, or the hosted Natively API. This model writes the notes and answers your questions.
4. 4Connect your calendar and destinationsAdd Google Calendar, Outlook, Apple Calendar (Mac only) or an ICS link, then the Notion and Slack connectors for where research notes should land.
5. 5Run a practice interviewDo a ten-minute call with a colleague using the User interview template, then check the transcript quality and the notes before a real customer call.

What Natively does not do for product teams

• It does not create tickets in Jira, Linear or Asana. Action items have to be copied over by hand or sent through a webhook or Zapier.
• It does not record video. You get the transcript, notes and any screenshots you chose to take.
• It always separates you from the other side of the call. It can name speakers from Google Meet in Chrome (through the Companion extension) and from the Zoom and Teams desktop apps; telling apart three customers on one channel depends on the speech provider.
• It cannot take notes on a call you are not in, and there is no mobile app that records calls. In-person research works through your computer's microphone.
• Its answers about past interviews are only as good as the transcripts behind them, so treat them as pointers to evidence, not the evidence itself.