Technical Storytelling

Craft narratives that make technical solutions resonate. AI builds before/after stories, hero journeys, and data-backed impact narratives that connect Salesforce to customer outcomes.

Skill Details

Install this skill

Versionv1.0.0AuthorJorge ArteagaLicenseMITSections13

Works with

Claude CodeCursorWindsurf

When This Skill Owns the TaskWorkflow

Required Context to Gather FirstWorkflow

Before crafting a story, ask for or infer:

The customer or persona — Who is the hero of this story?

The problem — What specific pain are they experiencing? (From discovery)

The stakes — What happens if the problem isn't solved?

The transformation — What does life look like after Salesforce?

Any quantified outcomes — Numbers, percentages, time saved?

Audience for the story — Technical, business, or executive?

Delivery format — Spoken talk track, written narrative, or slide content?

WorkflowWorkflow

Choose the story framework — Before/After, Hero's Journey, or Challenge/Solution/Outcome.

Establish the hero — A specific, relatable persona (not "a company," but "Sarah, VP of Sales").

Set the scene with the problem — Concrete, specific, emotionally resonant.

Raise the stakes — What is the cost of the status quo? Make it visceral.

Introduce the transformation — Salesforce enters the story as the enabler, not the hero.

Land the outcome — Specific, quantified if possible, and connected to business value.

Add the proof — A customer reference, a data point, or a relatable analogy.

Close with the invitation — Connect the story to the prospect's specific situation.

Core Frameworks

Framework 1: Before / After

The simplest and most powerful structure for SE storytelling.

Code

BEFORE (The World Without Salesforce):
  [Hero] was dealing with [specific problem].
  Every [time period], [consequence of problem].
  Their team was [emotional/practical state].

THE TRIGGER:
  Then [event happened — a missed target, a lost deal, a customer complaint].
  That's when they decided [something had to change].

AFTER (The World With Salesforce):
  With [specific Salesforce capability], [hero] now [concrete change in behavior].
  In the first [time period], [quantified result].
  Today, [broader transformation].

Example:

Before: "The sales team at Acme was managing their pipeline in spreadsheets. Every Monday morning, the VP of Sales spent 3 hours consolidating reports from 12 reps to get a single view of the forecast. It was always out of date by the time she finished."

The Trigger: "In Q3, they missed their number by 18% — a miss that came as a complete surprise. That's when they knew they had a visibility problem."

After: "Twelve weeks after going live on Sales Cloud, the Monday pipeline review went from 3 hours to 15 minutes. The forecast accuracy improved by 40% in the first quarter. And for the first time, the VP could see which reps needed coaching before a deal was lost."

Framework 2: The Hero's Journey

For longer narratives or executive storytelling. The customer is the hero; Salesforce is the guide.

Code

ORDINARY WORLD:    "Here's how [industry/company] operates today."
CALL TO ADVENTURE: "But [disruption/trend/competitive pressure] is changing everything."
CHALLENGES:        "Most companies are struggling with [specific challenges]."
THE GUIDE:         "Salesforce gives [hero] the tools and intelligence to [capability]."
TRANSFORMATION:    "[Hero] is now able to [new state] — something that wasn't possible before."
RETURN WITH BOON:  "[Result for the business, the customers, and the people]."

Framework 3: Challenge / Solution / Outcome (CSO)

Fast, tight, and evidence-based. Best for technical audiences who appreciate brevity.

Code

CHALLENGE: "[Specific technical or business problem]."
SOLUTION:  "With [specific Salesforce capability], [how it addresses the challenge]."
OUTCOME:   "[Quantified or described result] — [customer name or 'a [industry] company like yours']."

Feature-to-Outcome Translation

The most common SE storytelling failure: speaking in features, not outcomes.

The "So What" Test

After every claim, apply the "So what?" test until you reach a business outcome:

"Salesforce has Einstein AI."
→ So what?
"It gives reps next best action recommendations."
→ So what?
"Reps know exactly what to do next for every deal."
→ So what?
"They spend less time wondering and more time selling."
→ So what?
"Win rates go up 15-25% on average."
→ So what?
"For a team of 50 reps doing $200K average deal size, that's $5-8M in additional annual revenue."
→ THAT is the story.

Keep asking "So what?" until you reach a number or a feeling that makes someone lean forward.

Output FormatTemplate

Talk Track Template

MARKDOWN

# Talk Track: [Capability / Story Name]
**Audience:** [Who this is for] | **Duration:** [X] min | **Context:** [When to use this]

## Opening Hook
[1-2 sentences that grab attention — a surprising statistic, a relatable frustration, or a provocative question]

## The Story
[Before/After, Hero's Journey, or CSO — fill in the framework]

**Before:**
[The status quo — specific, concrete, emotionally resonant]

**The Stakes:**
[What happens if nothing changes — quantified if possible]

**After:**
[The transformed state — specific capability → concrete change → business outcome]

## The Proof
[Customer reference, benchmark, or analyst data that validates the story]

## The Invitation
[Connect the story to this specific prospect's situation]
"Based on what you told me about [their situation], this is exactly what I'd expect you to experience..."

## Transition
[How to move into the demo or next section]
"Let me show you what this looks like in practice..."

Anti-PatternsReference

Scoring Rubric (80 Points)Reference

Cross-Skill IntegrationReference

Task	This Skill	Defer To
Craft a "before/after" customer story	Yes	—
Build a hero journey narrative	Yes	—
Translate features into outcome language	Yes	—
Write a compelling talk track for a capability	Yes	—
Build the slide deck for the story	No	sf-se-presentation
Write the executive one-pager	No	sf-se-executive-briefing
Script the live demo with click paths	No	sf-se-demo-scripts
Feature Language (Avoid)	Outcome Language (Use)
"Salesforce has a 360-degree view of the customer"	"Your reps will never walk into a renewal blind again"
"Einstein AI provides next best action recommendations"	"Your reps spend less time guessing and more time closing"
"Agentforce can handle tier-1 service cases autonomously"	"Your customers get instant answers at 2am — without adding headcount"
"Data Cloud unifies data from multiple sources"	"You finally get one version of the truth about every customer"
"Flow Builder automates business processes"	"The work your team does manually today? The system does it for them"
"Salesforce has a 99.9% uptime SLA"	"The one thing your team can always count on is that it'll be there"
Anti-Pattern	Why It Fails	Fix
"Salesforce is the leader in CRM"	Everyone says this; it's white noise	Lead with the customer's problem, not Salesforce's ranking
Telling the customer's story back to them incorrectly	Nothing breaks rapport faster than getting their reality wrong	Use their exact words from discovery; don't paraphrase their pain
Stories with no stakes	Without stakes, there's no urgency	Ask: "What happens to the business if this problem isn't solved?"
AI/technology as the hero	Technology doesn't have emotions; people connect to people	The customer's employee, customer, or leader is the hero; Salesforce is the enabler
Using Salesforce jargon in customer stories	Terms like "Einstein," "Agentforce," "LWC" mean nothing to business buyers	Translate every capability into what the person can now do that they couldn't before
Ending on a feature	"And that's how the AI recommendation engine works" is a dead landing	Always close on an outcome: "...and that's why win rates go up"
Generic stories not tailored to the industry	Business buyers in healthcare don't connect to a manufacturing story	Always anchor the story in the prospect's industry and persona
Category	Points	Pass Criteria
Narrative Structure	20	Clear Before/After or CSO arc; stakes are explicit
Feature-to-Outcome Translation	25	No feature language without an outcome; "So What?" test passes
Specificity	20	Named persona, specific pain, quantified outcome (or credible estimate)
Proof	15	At least one reference, benchmark, or analogous example
Skill	When to Use It
sf-se-presentation	Build the slide deck that carries this narrative
sf-se-demo-scripts	Script the live demo that proves the story is real
sf-se-executive-briefing	Compress the story into a C-suite one-pager
sf-se-discovery	Use discovered pain points as the raw material for the story
sf-se-proof-of-value	Replace estimated outcomes with quantified ROI data

Technical Storytelling

When This Skill Owns the TaskWorkflow

Required Context to Gather FirstWorkflow

WorkflowWorkflow

Core Frameworks

Framework 1: Before / After

Framework 2: The Hero's Journey

Framework 3: Challenge / Solution / Outcome (CSO)

Feature-to-Outcome Translation

The "So What" Test

Output FormatTemplate

Talk Track Template

Anti-PatternsReference

Scoring Rubric (80 Points)Reference

Cross-Skill IntegrationReference

More in Storytelling & Demos

Demo Scripts

Executive Briefing

Presentation Decks