Service Deck Creation Prompt

Purpose: Generate service deck copy following StoryBrand framework and Brainforge SOP Output: Markdown draft with slide-by-slide breakdown, copy, and visual suggestions Exclusions: NO pricing/investment section

Context

Service Information

Service Name: [Service name from vault]

Service Details (from gtm/agents/memory/services.md):

Who it’s for: [Target roles/audience]
Business problems addressed: [List problems]
Outcomes in 30 days: [Expected outcomes]
Scope & configuration: [What’s included]
Success metrics: [KPIs and metrics]
Timeline & plan: [Phases and duration]
Deliverables: [What client receives]

Related Case Studies (from gtm/sales/*.md):

[Client examples with metrics if available]

Interview Transcript/Notes

Paste interview transcript or notes here:

[User will paste interview transcript/notes in this section]

Extract from transcript:

Pain points (external, internal, philosophical)
Outcomes & metrics (% improvements, results, time to insight, decisions made, ROI)
Client quotes (direct quotes about pain and outcomes)
Process details (how service works, timeline, deliverables)
Success stories (specific examples, use cases)

Instructions

StoryBrand Framework Structure

Follow this flow for the service deck:

Character (The Hero/Customer) - Who is this for?
Problem (The Challenge) - What pain do they face?
Guide (Brainforge) - How we help (empathy + authority)
Plan (The Solution) - Our process/approach
Success (The Positive Outcome) - Transformation they achieve
Call-To-Action - Next step to engage

DO NOT include: Pricing/Investment section

Slide Structure (8-12 slides typical)

Slide 1: Hook/Title Slide

StoryBrand Element: Character
Content: Compelling headline that identifies the target customer and their core tension
Visual Suggestion: Hero image or illustration representing the customer/industry

Slide 2: The Problem (External)

StoryBrand Element: Problem
Content: External problem statement - “I can’t get the right information fast enough to make confident, strategic decisions”
Visual Suggestion: Problem illustration or diagram showing the challenge
Stats to Include: If available from transcript, include specific pain metrics

Slide 3: The Problem (Internal/Emotional)

StoryBrand Element: Problem
Content: Internal problem - “I feel exposed and inefficient. I know we’re behind, but I don’t know where to start — and I don’t trust what I see”
Visual Suggestion: Emotional imagery or before/after comparison
Client Quote: Use direct quote from transcript if available

Slide 4: The Guide (Empathy)

StoryBrand Element: Guide
Content: Empathy statements - “We’ve been there. We’re operators too — and we built Brainforge to solve the problems we faced ourselves”
Visual Suggestion: Team photo or authentic imagery
Authority Signals: Brief mention of credentials (90% engineers, certifications, client count)

Slide 5: The Plan (Process Overview)

StoryBrand Element: Plan
Content: 3-step process (Diagnose → Design → Deploy) or service-specific process
Visual Suggestion: Process flow diagram or timeline visualization
Timeline: Include timeframes from service details

Slide 6: The Plan (What You Get)

StoryBrand Element: Plan
Content: Deliverables and scope
Visual Suggestion: Icon grid or checklist visualization
Details: List specific deliverables from service details

Slide 7: Success (Outcomes & Metrics)

StoryBrand Element: Success
Content: Transformation outcomes with specific metrics
Stats to Include:
- % improvements
- Results (before/after)
- Time to insight
- Decisions made/enabled
- ROI data
Visual Suggestion: Bar charts, line charts, or gauge charts for metrics
Client Quote: Use outcome quote from transcript if available

Slide 8: Success (Before/After)

StoryBrand Element: Success
Content: Before/after transformation table or comparison
Visual Suggestion: Side-by-side comparison or transformation diagram
Focus: Show the shift (reactive → respected, chaos → clarity)

Slide 9: Case Study/Proof

StoryBrand Element: Guide (Authority)
Content: Specific client example with results
Stats to Include: Real metrics from case study or transcript
Visual Suggestion: Client logo, before/after metrics visualization
Details: Extract from related SOW documents or transcript

Slide 10: The Agreement (Confidence Guarantee)

StoryBrand Element: Plan
Content: Address common fears with guarantees
Visual Suggestion: Checkmark icons or guarantee badges
Format: Table format (Fear → Our Guarantee)

Slide 11: Next Steps/CTA

StoryBrand Element: Call-To-Action
Content: Direct CTA - “Book a Diagnostic Workshop” or “Schedule your strategy call”
Visual Suggestion: CTA button mockup or action-oriented imagery
Options: Provide both direct and transitional CTA options

Slide 12: Contact/Thank You

Content: Contact information and thank you message
Visual Suggestion: Contact card or team photo

Stats Requirements

Include these types of metrics throughout the deck:

% Improvements: Percentage increases/decreases (e.g., “40% reduction in time to insight”)
Results: Before/after comparisons (e.g., “45 minutes → 10 minutes per lead”)
Time to Insight: Speed metrics (e.g., “Results in weeks, not months”)
Decisions Made: Impact metrics (e.g., “Enabled 15 strategic decisions per month”)
ROI: Economic impact (e.g., “Six-figure cost savings” or “30% efficiency gain”)

Extract from:

Interview transcript (primary source)
Service details from vault
Related SOW documents
Case studies

Visual Suggestions Guidelines

For each slide, recommend appropriate visual elements:

Charts (for metrics slides)

Bar charts: For comparisons (before/after, different metrics)
Line charts: For trends over time
Gauge charts: For single metric displays (e.g., “95% accuracy”)
Pie charts: For distributions (use sparingly)

Diagrams (for process/architecture slides)

Process flows: For service steps (Diagnose → Design → Deploy)
Timeline visuals: For project phases
Architecture diagrams: For technical services
Before/after comparisons: For transformation slides

Icons (for feature/benefit slides)

Concept icons: For key ideas (speed, clarity, trust)
Feature icons: For deliverables
Benefit icons: For outcomes
Process icons: For steps

Imagery (for emotional connection)

Hero images: For title/hook slides
Problem imagery: For pain point slides
Success imagery: For outcome slides
Team photos: For guide/empathy slides
Client logos: For case study slides

Visual Placement Notes:

Suggest where visuals should go (left, right, full background, etc.)
Note visual hierarchy (what should be most prominent)
Consider color usage (brand colors, accent colors)

StoryBrand Framework Reference

Character (Target Customer):

Senior leaders at mid-market, tech-enabled U.S. companies ( $5 M -$ 100M revenue)
Sub-archetypes: The Aspiring Operator, The Evangelist
Define clearly in opening slides

Problem Statements:

External: “I can’t get the right information fast enough to make confident, strategic decisions”
Internal: “I feel exposed and inefficient. I know we’re behind, but I don’t know where to start — and I don’t trust what I see”
Philosophical: “Leaders shouldn’t miss out on the power of AI just because their house isn’t in order”
Villain: “The Illusion of Control” — systems appear data-driven, but under the hood: chaos

Guide Positioning:

Empathy: “We’ve been there. We’re operators too”
Authority: 90% engineers, no vendor kickbacks, trusted by X+ clients, certifications
Differentiation: “We build what we run”

Plan Structure:

Process Plan: Diagnose → Design → Deploy (or service-specific)
Agreement Plan: Address fears with guarantees
Extras: No fluff, no markups, no AI hype

Success Outcomes:

Individual success: Trust, clarity, alignment, control
Before/after transformation: Reactive → Respected, Chaos → Clarity
Specific outcomes: AI in production, one source of truth

CTAs:

Direct: “Book a Diagnostic Workshop”, “Schedule your strategy call”
Transitional: Case studies, checklists, educational content

Customer Quotes (use from transcript and framework):

Frustration: “I’m wasting hours every week just trying to get basic answers”
Confusion: “A complete blur and fuzzy dashboard, like a swamp”
Powerless: “I shouldn’t have to fly this company blind”
Use authentic language from interviews

Output Format

Generate markdown with this structure:

# Service Deck: [Service Name]
 
## Slide 1: [Title]
**StoryBrand Element**: [Character/Problem/Guide/etc.]
**Copy**: 
[Headline]
[Subheadline or body copy]
 
**Visual Suggestion**: 
[Type of visual]: [Description of what to show]
[Placement notes]: [Where visual should go]
[Color/style notes]: [Any specific design direction]
 
**Stats Included**: [If any metrics on this slide]
 
---
 
## Slide 2: [Title]
[Repeat structure for each slide...]
 
---
 
## Notes for Designer
 
**Overall Design Direction**:
- [Any overall design notes]
 
**Brand Guidelines**:
- Follow existing brand guidelines
- Use brand colors and fonts
- Maintain visual consistency
 
**Visual Consistency**:
- [Notes on maintaining visual style across slides]

Quality Checklist

Before finalizing, ensure:

Last Updated: 2026-01-30

Brainforge Knowledge

Explorer

service-deck-prompt