Turn a QBR Recording into CRM Updates and Follow Ups with a Claude Skill

‍

Here's the honest state of partner reviews. Introw's QBR and meeting prep playbook estimates that partner managers spend 2 to 4 hours preparing each QBR, and that most programs only reach 20 to 30% real QBR coverage across their partner base. So when a QBR does happen, it's expensive. You'd hope it produces something.

Now picture the end of your last QBR meeting. The partner agreed to push into healthcare. You promised a pitch deck by the 15th. Their sales lead mentioned that a competitor offered better margins. Then the call ended, and the notes stayed in your head.

Three weeks later, the partner emails to ask what was decided. Sound familiar?

The meeting itself was fine. The follow up never happened. This guide covers what a good QBR meeting follow up looks like, the Claude skill that does it for you, the full SKILL.md you can copy, how to install and run it, and how you stay in control of every update it makes.

What is a QBR meeting, and why the follow up matters most

A quarterly business review (QBR) is a structured meeting, usually once a quarter, where you and a partner or customer review performance, goals, pipeline and priorities for the next quarter. If you've ever asked "what is a QBR" in a new job, that's the short answer: a regular, data based check in that keeps both sides aligned on what's working, what isn't, and what happens next.

In partner programs, the QBR meeting is where the relationship gets steered: pipeline, goals, training, engagement, commissions and next steps. That last part is where most QBRs quietly fail. The prep gets all the attention: the slide deck, the QBR template, the data pull. The follow up gets whatever time is left, which is usually none.

Here's what slips without it:

• Decisions age into ambiguity: "we agreed to expand into healthcare" becomes "I think we talked about healthcare?" within a month.
• Commitments slip: the deck you promised, the intro the partner promised, the certification their team was going to finish. Nobody wrote it down with a date, so nobody did it.
• Risks get buried: a frustrated comment about margins or a slow deal desk is a churn signal. If it lives only in a recording nobody rewatches, leadership hears about it too late.
• The CRM drifts from reality: deals discussed in the meeting moved, slipped or died, but the CRM still shows last quarter's picture.

A partner who gets a clear recap the same day trusts you more. Good channel partner management depends on that trust, and the follow up is where you earn it.

What a good QBR follow up includes

Whether you write it by hand or let a skill draft it, a strong follow up after a QBR meeting has two outputs: updates in your systems, and a meeting follow up email for the people in the room. Here's what it covers:

• Meeting action items as tasks: every concrete next step gets a named owner and a due date. "TBD" owners are how things get dropped.
• Decisions as comments on the partner record: so anyone who opens the partner next quarter can see what was agreed.
• CRM updates for deals discussed: stage changes, new values, slipped close dates and new opportunities.
• Goal changes flagged, not quietly applied: goals affect commissions and tier eligibility, so they need a deliberate update.
• Risks escalated: churn signals, legal concerns and security questions go to channel leadership the same day.
• A recap email: what we agreed, what we'll do, what you'll do and what's next, written so the partner can forward it to their team.

Keep it short. One page of decisions and action items beats a transcript summary nobody reads. If you use a mutual action plan with your partners, the QBR follow up is the moment to update it, and Introw's mutual action plan template is a good starting point if you don't have one yet.

The skill to use: QBR Recording to Portal Updates and Follow Up

QBR Recording to Portal Updates and Follow Up is a vendor side skill from Introw's free Claude skill library. It takes the recording or transcript of a QBR, MBR or partner business review and turns it into structured updates in Introw and your CRM through Introw's MCP server, plus a polished recap email for attendees.

It's the post meeting companion to the QBR Prep skill. Prep builds the meeting, this one closes the loop after it. It fires on phrases like "process this QBR transcript", "follow up from the partner meeting", "send the QBR recap" or "update Introw from the meeting".

How the skill works, step by step

The skill runs seven steps. Knowing what happens behind the scenes makes it easier to trust what comes back.

Step 1: Pull the signal out of the transcript

The skill reads the whole transcript and looks for nine kinds of signal: decisions, commitments from both sides, action items, blockers and risks, goal updates, pipeline changes, tier or program asks (like MDF or certification support), sentiment moments and the date of the next touchpoint.

For every item, it keeps the source quote and timestamp, so when a partner says six weeks later "we never agreed to that," you can point to the exact moment.

Step 2: Check what's already in Introw

Before it writes anything, the skill pulls the partner record, open tasks, open deals and current goals, so it doesn't duplicate a task or contradict what's already there.

Step 3: Stage the writes

Instead of writing straight away, the skill builds a write plan. Action items become tasks with an owner, due date and a note linking back to the transcript. Decisions and standout moments become comments on the partner record. Deals that moved become CRM updates, and new ones become deal registrations. Goal changes, tier or MDF requests and risk signals become flagged comments plus a task for the right person, and the next QBR date becomes a calendar task.

Step 4: Show you the plan

You see every task, comment, CRM change (before and after), goal flag and risk before anything happens, and you approve, edit or reject each one. Nothing executes until you say so.

Step 5: Write what you approved

Approved tasks, comments and CRM updates go into Introw and sync to your CRM, along with a full QBR summary on the partner record. Goal changes are never written directly. They become a task for whoever owns goals.

Step 6: Draft the recap email

Next comes the meeting follow up email. The subject follows a simple pattern, like "Recap and next steps, Northwind x Acme QBR, Nov 12". The body covers what we agreed, what we'll do, what you'll do and what's next, plus links to the tasks created and any decks shared.

The tone is warm but specific. Anything discussed but not decided is marked "to revisit next quarter".

Step 7: Send it, or hand it to you

By default, you review the draft and send it from your own inbox. If you've connected Gmail or Outlook and allowed it, the skill can send it for you. Either way, the sent email is saved on the partner record.

Get the skill: the full SKILL.md

Here's the complete skill file. Copy it as is, or adjust the extraction categories and email structure to match how your team runs reviews.

---
name: vendor-qbr-recording-to-portal-followup
description: Use after a QBR / MBR / partner business review meeting when a PDM, CAM, or Channel Chief wants to turn the meeting recording or transcript into structured portal updates (tasks created, comments added, CRM objects updated, goals adjusted) and a polished follow-up email to attendees. Trigger phrases include "process this QBR transcript", "follow up from the partner meeting", "QBR portal update", "convert this transcript to tasks", "post-QBR action items", "send the QBR recap", "update Introw from the meeting".
---

# QBR Recording → Portal Updates + Follow-Up (Vendor)

**Audience**: Vendor, uses **claude.ai Introw** MCP + transcript MCP (Otter, Fathom, Gong, Read.ai, Granola, or a transcript pasted into the conversation).
**Use case**: 12, QBRs / Meeting Prep (post-meeting companion to `vendor-qbr-prep`).

## When to use this skill

Use after a QBR / MBR / partner business review meeting when a PDM, CAM, or Channel Chief wants to turn the meeting recording or transcript into structured portal updates (tasks created, comments added, CRM objects updated, goals adjusted) and a polished follow-up email to attendees.

**Sample prompts that fire this skill:**
- "process this QBR transcript"
- "follow up from the partner meeting"
- "QBR portal update"
- "convert this transcript to tasks"
- "post-QBR action items"
- "send the QBR recap"
- "update Introw from the meeting"

## Why this matters
Most QBRs end with good intentions and zero follow-through. The PDM types up notes (sometimes), promises to update the portal "later," drafts an email (eventually), and three weeks later the partner is asking what was decided. The decisions made in the meeting age into ambiguity; commitments slip; the next QBR rehashes the same ground.

This skill closes the loop: meeting transcript → structured portal updates → attendee email, same day, automatically, with no PDM tax. It's the post-meeting half of the QBR motion that `vendor-qbr-prep` started. Pair the two and the QBR becomes an actual operating ritual instead of a slide deck.

## Inputs to gather first
- **Source**: meeting transcript (pasted text, transcript MCP reference, or a recording the user has already transcribed elsewhere).
- **Partner identity** + portal/CRM record.
- **Attendees** (pulled from transcript or supplied): needed for the follow-up email.
- **Meeting type**: QBR (default), MBR, WBR, ad-hoc strategic review.
- **Action authorization**: write to portal directly, or surface drafts for PDM approval first?

## Process

### Step 1: Extract structured signal from the transcript
Mine the transcript for:

- **Decisions made**: specific yes/no calls. ("We agreed to expand into healthcare in Q3.")
- **Commitments**: who promised what by when. Vendor commitments AND partner commitments.
- **Action items**: concrete tasks with owners.
- **Blockers / risks raised**: partner flagged something that needs attention.
- **Goal updates**: any commitments to revise or set new goals.
- **Pipeline changes**: deals discussed (new, in-flight, slipped, killed).
- **Tier / program asks**: partner asking for tier promotion, MDF, certification support.
- **Sentiment signals**: any major positive (advocacy moment) or negative (frustration, churn risk).
- **Next QBR / next-touch date.**

For each extraction, capture the source quote (with timestamp if available): the audit trail.

### Step 2: Pull current state for context
Before writing anything, pull current state to avoid duplicating or contradicting existing data:
- `Introw:search_partners`: partner record.
- `Introw:search_tasks`: open tasks already assigned (don't double-create).
- `Introw:search_crm_objects`: open deals that may need updating.
- `Introw:get_goals`: current goals before any revisions.

### Step 3: Stage the writes (preview, don't execute yet)
Build a write plan, not a write. For each extracted item, prepare the corresponding portal action:

| Extracted | Portal action |
|---|---|
| Action item with owner + due date | `Introw:add_task` (with title, owner, due date, partner association, why-note linked to transcript timestamp) |
| Commitment, decision, or sentiment-worthy moment | `Introw:add_comment` on the partner record |
| Deal stage change / value update / new deal mentioned | `Introw:update_crm_object` (or `Introw:share_lead_or_register_deal` if new) |
| Goal revised or new goal committed | Comment + flag for human update (goal write-back may need approval) |
| Tier / MDF ask raised | Comment + task to relevant approver |
| Risk / churn signal | Comment with flag + task to PDM for follow-up |
| Next QBR date | Calendar task with the date |

### Step 4: Surface the write plan
Show the user:
- **Tasks to create**: title, owner, due date, why.
- **Comments to add**: content + which record.
- **CRM updates**: what's changing, before/after.
- **Goals affected**: flagged for separate confirmation (goals carry economic weight).
- **Risks flagged**: anything that warrants escalation.

User approves, edits, or rejects per item. **Default mode: surface; auto-execute only when explicitly authorized.**

### Step 5: Execute approved writes
- `Introw:add_task` for each approved task.
- `Introw:add_comment` for each comment, including the QBR summary as a comprehensive comment on the partner record (so the next QBR has the full thread).
- `Introw:update_crm_object` for each approved CRM update.
- For goal changes: capture as a comment + create a task for the goals-owner to confirm and apply (don't auto-write goal targets).

### Step 6: Draft the follow-up email
Generate an email to the meeting attendees with this structure:

- **Subject**: "Recap & next steps, [Partner] x [Vendor] [QBR / MBR / Review], [Date]"
- **Opening**: thank-you + 1-line meeting purpose recap.
- **What we agreed** (decisions, bulleted, concrete).
- **What we'll do** (vendor-side action items with owners + dates).
- **What you'll do** (partner-side action items with owners + dates).
- **What's next** (next-touch date, what'll be reviewed).
- **Attachments / links**: portal task IDs created, any decks shared, the recording (if attendee policy allows).

Tone: warm but specific. No hedging. The email should be the source of truth the partner can forward to their team. If something was discussed but not decided, say "to revisit next [touchpoint]", don't fudge.

### Step 7: Send (or stage for send)
- **Default**: surface the drafted email for PDM review and send via the PDM's regular email tool.
- If a Gmail/Outlook MCP is connected and the user authorizes auto-send: send directly.
- Capture the sent email body via `Introw:add_comment` on the partner record so the email is part of the audit trail.

## Output format
- **Extraction summary**: what was identified in the transcript, with source quotes.
- **Portal write plan**: tasks, comments, CRM updates, goal flags, risk flags. Each approved/rejected by the user.
- **Confirmation log**: for each executed write, the IDs created/updated.
- **Follow-up email draft**: copy-pasteable or sendable.
- **Open items requiring human follow-through**: anything ambiguous or sensitive flagged for the PDM.

## Guardrails & PRM best practice
- **Don't fabricate.** If the transcript is ambiguous on owner or date, ask the PDM rather than guess. Wrong owners and dates create more friction than no tasks.
- **Preserve nuance.** Some QBR moments aren't decisions, they're explorations. Don't capture an exploratory mention as a commitment. The bar: was there explicit agreement?
- **Sensitive content stays out of broad audiences.** If the meeting included confidential pricing discussion, churn-risk admissions, or competitor intel, scrub those from the follow-up email, capture in vendor-internal comments only.
- **Owners must be named.** "TBD" owners create dropped balls. Every task needs a name.
- **Don't update goals without authorization.** Goal targets carry economic weight (commission impact, tier eligibility). Goal changes get flagged for explicit confirmation, never auto-written.
- **Source quotes on every extraction.** The audit trail is the source quote + timestamp. When the partner disputes an action item six weeks later ("we never agreed to that"), the timestamp resolves it.
- **Don't auto-execute on first run.** First time the user runs this skill: preview everything. After the user has trusted the extraction quality on 2 to 3 meetings, auto-execution mode can be enabled for low-risk writes (tasks, comments): never goal writes or tier moves.
- **Email tone is editable.** The drafted email is a starting point. The PDM's relationship voice matters; encourage edits. If the partner has a long history of formal English, don't ship a casual draft.
- **Privacy of recordings.** Some partners don't consent to recording, and some jurisdictions have specific rules. Confirm consent context before processing.
- **Escalate risks immediately.** Churn signals, legal flags, security issues, surface to channel leadership the same day, don't bury them in the digest.
- **Cross-skill handoff.** New deals identified → `partner-register-deal` flow or `vendor-pipeline-partner-influence-scout`. Coaching needs surfaced → `vendor-deal-coach-from-similar-wins`. Goal revisions → vendor goals-owner. Tier asks → `vendor-tier-promotion-batch-review` for next cycle. Pairs naturally with `vendor-qbr-prep`: prep generates the meeting, this skill closes the loop after.

How to install and run the skill

You've got two ways to use it, depending on where you work.

Option 1: Claude Code

Create a folder called vendor-qbr-recording-to-portal-followup inside .claude/skills/ in your repo, and save the file above as SKILL.md inside it. Claude Code picks it up automatically and runs it whenever your prompt matches one of the trigger phrases in the description.

Option 2: Claude (or any MCP client) with the Introw connector

You don't need to be technical for this one. Connect Claude to Introw once, and you can paste a transcript or connect your call recorder, then run the same play in plain language. Introw is listed in Claude's connector directory, so it's one click and a sign in, with no server URL to paste. Here's how connecting looks:

‍

The step by step version lives in the Connect Claude guide, and the Claude integration page covers what else you can do once you're connected.

Prompts to try

Once the skill is installed or Claude is connected, try any of these:

• "Process this QBR transcript for Northwind." Paste the transcript underneath and get the full extraction and write plan.
• "Convert this transcript to tasks, but don't create anything yet." Gives you the write plan to review first.
• "Follow up from the partner meeting with BrightPath. Attendees were Priya, Tom and me." Adds the right people to the recap email.
• "Pull the Fathom recording from this morning's QBR and update Introw from the meeting." Works directly from your call recorder if it's connected.
• "Send the QBR recap, and keep the pricing discussion out of the email." Drafts the attendee email with sensitive points kept internal.

What you'll get back

A typical run returns five things:

• Extraction summary: every item the skill found, each with its source quote.
• Portal write plan: tasks, comments, CRM updates and flags, each waiting for your approval.
• Confirmation log: the IDs of everything created or updated.
• Recap email draft: ready to edit and send.
• Open items: anything ambiguous or sensitive that needs a human decision.

Here's an illustrative slice of a write plan after a QBR with a reseller:

Notice the margin comment. It's escalated internally and kept out of the recap email the partner's team will read.

Staying in control: what Claude can and can't do

A skill that writes to your CRM after a partner meeting only works if you trust it. These controls are built in:

• You approve the writes: the skill waits for your go ahead on every task, comment and CRM update unless you explicitly allow otherwise.
• It works as you: Claude connects to Introw over OAuth, so it can only see and change what you can.
• It doesn't guess: if the transcript is unclear about who owns something or when it's due, it asks you instead of inventing an answer.
• It never writes goals or tier moves: goal targets affect commissions and tier eligibility, so they're always flagged for a person to confirm.
• It keeps sensitive things internal: confidential pricing, churn admissions and competitor intel stay out of the recap email and go into internal comments only.
• It earns trust gradually: the first run is preview only. After two or three meetings, you can let it create low risk tasks and comments on its own.

Prefer to do this in the Introw app?

The skill is the fast route from a meeting to a set of tasks. If you'd rather create a one off task for a partner yourself, with an assignee, due date and visibility, and show it right in the partner portal, here's how that works in Introw:

‍

Partner tasks show up in the partner portal, so partners see what's on them the moment the recap lands. For lighter, more frequent meetings between QBRs, Introw's weekly partner meeting template keeps the same structure.

Pair it with other Claude skills

This skill handles the follow up. A few others fit naturally around it:

• QBR Preparation: the companion skill that assembles pipeline, goals, activity, engagement, commissions and an agenda before the QBR meeting. Prep builds the meeting, this skill closes it.
• Pipeline Partner Influence Scout: when a new deal comes up in the meeting, it helps you find where partner influence can move other open deals too.
• Deal Coach from Similar Wins: when the QBR reveals a stuck deal, it coaches the partner using patterns from your past wins.

Partners can prep too, with the partner side Pre QBR Self Prep skill. You'll find all of these in Introw's skill library, and our overview of Claude skills for partner teams shows how they fit together.

Run your partner QBRs from Claude with Introw

Introw is a CRM first partner relationship management platform, which means it builds on top of your existing HubSpot or Salesforce setup rather than replacing it. It's also headless by design: the partner portal is one surface, but you can run the same program in plain language from Claude, ChatGPT, Slack or Teams through Introw's MCP server, with every action written back to your CRM.

That's what makes this skill useful. Tasks, comments, deals and goals all live in one place, so the CRM updates from your QBR land where your sales team already works. Partner management in Introw keeps the full record of every partner, partner performance shows whether the commitments from the QBR turn into pipeline, and deal registration handles the new opportunities that come out of the meeting. For the wider picture on reviewing partners, see our guide to channel partner performance management.

Turn your next QBR meeting into follow ups your partners can actually act on. Connect Claude or book a demo.