home / skills / gtmagents / gtm-agents / call-brief-framework

call-brief-framework skill

safe

/plugins/sales-calls/skills/call-brief-framework

This skill helps structure concise call briefs with clear objectives, roles, agenda, and follow-ups for efficient customer meetings.

npx playbooks add skill gtmagents/gtm-agents --skill call-brief-framework

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.2 KB

---
name: call-brief-framework
description: Use to structure concise call briefs with objectives, agendas, and role
  assignments.
---

# Call Brief Framework Skill

## When to Use
- Preparing customer meetings that need clear objectives and roles.
- Enabling managers to inspect upcoming calls before they happen.
- Sharing quick reference docs with supporting teams (SEs, exec sponsors).

## Framework
1. **Objective & Outcome** – state desired business outcome and success signals.
2. **Stakeholders & Roles** – list attendees, personas, and internal owners.
3. **Agenda** – map timeline with talk tracks, demos, and checkpoints.
4. **Key Messages & Proof** – highlight value pillars, metrics, and references.
5. **Risks & Follow-ups** – flag sensitivities, blockers, and immediate next steps.

## Templates
- One-page call brief (objective, agenda, roles, messaging, assets).
- Manager inspection checklist.
- Follow-up log for commitments captured during the meeting.

## Tips
- Keep the brief within a single page to encourage adoption.
- Include a “call scorecard” section so managers can annotate feedback post-call.
- Pair with `persona-intel` for tailored questions and talk tracks.

---

Overview

This skill structures concise call briefs to align objectives, agendas, and role assignments for customer-facing meetings. It provides templates and a clear five-part framework to prepare teams, enable manager inspection, and capture follow-ups. Use it to make every call outcome-focused and easy to review.

How this skill works

The skill generates one-page call briefs using a five-part framework: Objective & Outcome, Stakeholders & Roles, Agenda, Key Messages & Proof, and Risks & Follow-ups. It can produce manager inspection checklists and a follow-up log to capture commitments. Outputs are compact, shareable, and designed for quick consumption by sales, SEs, and executives.

When to use it

Before customer meetings that require clear objectives and defined owner responsibilities
When managers need a quick inspection or scorecard for an upcoming call
To prepare internal teams (SEs, exec sponsors) with aligned talk tracks
When capturing commitments and actions during or immediately after a call
For recurring GTM reviews and handoffs between sales and customer success

Best practices

Keep the brief to one page to maximize adoption and readability
Start with a measurable objective and clear success signals for the call
List attendee personas and explicitly assign internal owners for key sections
Include concise proof points and metrics to back key messages
Add a short call scorecard area for managers to annotate feedback post-call
Use the follow-up log to track commitments with owners and deadlines

Example use cases

Pre-call preparation for a renewal conversation with a defined outcome and timeline
Manager review of a high-stakes demo using the inspection checklist and scorecard
Sharing a one-page brief with an SE to align demo scope and technical owners
Capturing action items and owners during an executive sponsor meeting
Standardizing briefing for discovery calls across a sales pod

FAQ

How long should the call brief be?

Aim for a single page so attendees can scan objectives, agenda, roles, and follow-ups quickly.

Can I customize the agenda and message sections?

Yes. Templates are meant to be adapted: shorten or expand talk tracks and proof points to match call complexity.