Get meeting outcomes

Copy the prompt. Paste it into your Tana chat. Create this meeting outcome from any of your meetings.

Product and engineering

  • Pain point

    A problem a customer raised, in their own words, tied to the account it came from.

  • JTBD

    The real job behind the request, mapped to the flow it sits in.

  • Insight

    A research finding backed by evidence quotes and a confidence level.

  • Behavior observation

    Capture a real user behavior or segment pattern the moment research surfaces it.

  • Decision

    Capture what you decided, why, and what you ruled out.

  • Coding-agent prompt

    A ready-to-run engineering prompt with task, context, and acceptance criteria.

  • Product feedback

    Feedback from the call, sorted into a change request and pointed at the right product area.

  • Root cause

    The real cause behind an incident, with the evidence that proves it.

  • Progress update

    Done, next, and blocked, captured the moment the meeting ends.

  • Goal

    The outcome a customer wants and the timeframe they want it by.

  • Blocker

    Name what's stalling the work, who owns it, and what it holds up.

  • Suggested ticket

    A drafted bug or task, ready for GitHub, Linear, or Jira.

  • Risk

    Capture a threat to an objective with its likelihood, impact, and mitigation plan.

  • Usability finding

    One usability problem, captured with the task, the friction, and severity.

  • Lesson learned

    A lesson from the retro, paired with the action that prevents the repeat.

  • Action item

    Every commitment from a meeting, with an owner, a due date, and the source it came from.

  • Open question

    Every unresolved question captured, with a name attached to it.

  • Feature request

    Capture who asked for what, the use case behind it, and the product area it touches.

  • Competitor mention

    A competitor the prospect named, with the context and how they felt about it.

Founders and leadership

  • Insight

    A research finding backed by evidence quotes and a confidence level.

  • JTBD

    The real job behind the request, mapped to the flow it sits in.

  • Behavior observation

    Capture a real user behavior or segment pattern the moment research surfaces it.

  • Stakeholder

    Every person in the deal, with their role, influence, and where they stand.

  • Blocker

    Name what's stalling the work, who owns it, and what it holds up.

  • Pain point

    A problem a customer raised, in their own words, tied to the account it came from.

  • Deal qualification

    Every deal scored on your framework, with the gaps you still need to close flagged.

  • Action item

    Every commitment from a meeting, with an owner, a due date, and the source it came from.

  • Decision

    Capture what you decided, why, and what you ruled out.

  • Competitor mention

    A competitor the prospect named, with the context and how they felt about it.

  • Usability finding

    One usability problem, captured with the task, the friction, and severity.

  • Root cause

    The real cause behind an incident, with the evidence that proves it.

  • Objection

    An objection captured word for word, plus how the rep handled it.

  • Feature request

    Capture who asked for what, the use case behind it, and the product area it touches.

  • Risk

    Capture a threat to an objective with its likelihood, impact, and mitigation plan.

  • Lesson learned

    A lesson from the retro, paired with the action that prevents the repeat.

  • Coding-agent prompt

    A ready-to-run engineering prompt with task, context, and acceptance criteria.

  • Churn / expansion signal

    Catch the accounts pulling away and the ones ready to grow, with the quotes that prove it.

  • Open question

    Every unresolved question captured, with a name attached to it.

  • Buying signal

    A sign a prospect intends to buy, rated for strength and tied to the deal.

  • Progress update

    Done, next, and blocked, captured the moment the meeting ends.

Consultants and clients

  • Goal

    The outcome a customer wants and the timeframe they want it by.

  • Lesson learned

    A lesson from the retro, paired with the action that prevents the repeat.

  • Blocker

    Name what's stalling the work, who owns it, and what it holds up.

  • Product feedback

    Feedback from the call, sorted into a change request and pointed at the right product area.

  • Progress update

    Done, next, and blocked, captured the moment the meeting ends.

  • JTBD

    The real job behind the request, mapped to the flow it sits in.

  • Action item

    Every commitment from a meeting, with an owner, a due date, and the source it came from.

  • Open question

    Every unresolved question captured, with a name attached to it.

  • Decision

    Capture what you decided, why, and what you ruled out.

  • Usability finding

    One usability problem, captured with the task, the friction, and severity.

  • Insight

    A research finding backed by evidence quotes and a confidence level.

Sales and GTM

  • Product feedback

    Feedback from the call, sorted into a change request and pointed at the right product area.

  • Deal qualification

    Every deal scored on your framework, with the gaps you still need to close flagged.

  • Action item

    Every commitment from a meeting, with an owner, a due date, and the source it came from.

  • Risk

    Capture a threat to an objective with its likelihood, impact, and mitigation plan.

  • Stakeholder

    Every person in the deal, with their role, influence, and where they stand.

  • Goal

    The outcome a customer wants and the timeframe they want it by.

  • Pain point

    A problem a customer raised, in their own words, tied to the account it came from.

  • Feature request

    Capture who asked for what, the use case behind it, and the product area it touches.

  • Behavior observation

    Capture a real user behavior or segment pattern the moment research surfaces it.

  • Churn / expansion signal

    Catch the accounts pulling away and the ones ready to grow, with the quotes that prove it.

  • Objection

    An objection captured word for word, plus how the rep handled it.

  • Competitor mention

    A competitor the prospect named, with the context and how they felt about it.

  • Buying signal

    A sign a prospect intends to buy, rated for strength and tied to the deal.

Can’t find the outcome you need?

Describe what you want in plain language. We’ll turn it into a setup you can paste straight into your Tana chat, or add it to your selection alongside the rest.

Get meeting outcomes - useful work, not transcripts