playbooks

home / skills / gtmagents / gtm-agents / storytelling

storytelling skill

/plugins/content-marketing/skills/storytelling

This skill helps you craft cohesive narratives that map product value to customer pain, guiding campaigns and pitches from setup to CTA.

npx playbooks add skill gtmagents/gtm-agents --skill storytelling

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

Files (1)
SKILL.md
1.4 KB
---
name: storytelling
description: Use when crafting narratives that connect product value to customer pain through clear setup-conflict-resolution arcs.
---

# Storytelling Skill

## When to Use
- Need cohesive narrative for campaigns, product launches, or decks.
- Translating technical capabilities into relatable customer stories.
- Coaching spokespeople or SDRs on better pitch storytelling.

## Framework
1. **Audience & Conflict** – identify who the hero is (customer persona) and what obstacle they face.
2. **Story Arc (SCAR)** – Situation → Complication → Action → Resolution.
3. **Characterization** – give personas motives, stakes, and quotes.
4. **Sensory Detail** – use vivid language, specific metrics, and concrete examples.
5. **Moral/CTA** – tie resolution back to product value and explicit next step.

## Templates
- Narrative outline (hook, scene, rising tension, turn, resolution, CTA).
- Pitch script template:
```
"Most {persona}s today face {pain}. When {trigger}, {impact}. We worked with {customer} to {action}, leading to {result}."
```
- Story inventory tracker to log customer, industry, proof points.

## Tips
- Record customer interviews to capture natural phrasing for quotes.
- Swap metaphors/analogies per persona so stories feel tailored.
- Reinforce numbers with vivid imagery (e.g., "saved hours = extra sprints delivered").
- Align every story with the current positioning doc to avoid mixed messages.

---

Overview

This skill helps craft narratives that connect product value to real customer pain using clear setup-conflict-resolution arcs. It provides a repeatable framework, templates, and practical tips to turn technical capabilities into persuasive, persona-driven stories. Use it to shape campaigns, pitches, and spokespeople coaching with measurable outcomes.

How this skill works

Start by identifying the hero (customer persona) and their primary obstacle, then map the arc using Situation → Complication → Action → Resolution (SCAR). Characterize the persona with motives, stakes, and a natural quote, then add sensory details and concrete metrics to make the story vivid. End each story with a moral or explicit CTA that ties the resolution back to product value.

When to use it

  • Preparing campaign narratives for product launches or feature announcements
  • Translating technical capabilities into customer-centered value stories
  • Writing pitch decks, sales scripts, or case study outlines
  • Coaching SDRs and spokespeople on concise, compelling pitches
  • Creating content that needs clear emotional and business impact

Best practices

  • Start with Audience & Conflict: define the hero and the obstacle before drafting
  • Follow SCAR: Situation, Complication, Action, Resolution for every story
  • Use real quotes and metrics from interviews to increase credibility
  • Tailor metaphors and sensory detail to each persona for resonance
  • Always conclude with a clear moral or next-step CTA aligned to positioning

Example use cases

  • Launch email sequence that opens with a customer’s complication and closes with a measurable result
  • Sales pitch script that embeds a short customer anecdote, quote, and outcome
  • Case study outline that maps customer situation to the product action and ROI
  • SDR role-play training using persona motives, stakes, and sample lines
  • Content brief for a blog or video that follows the SCAR narrative arc

FAQ

How long should a customer story be?

Keep core stories to one concise arc—about 3–5 short paragraphs or a 60–90 second pitch—then expand with supporting data as needed.

What if I don’t have customer quotes?

Use anonymized specifics (metrics, workflows, outcomes) and plan quick interviews to capture natural phrasing for future stories.