Service Asset Creator Prompts

Purpose: Prompts for creating service decks, one-pagers, and landing pages Agent: service-asset-creator agent Location: gtm/agents/.claude/agents/service-asset-creator.md


Overview

This directory contains prompts for generating three types of service marketing assets:

  1. Service Decks - Presentation decks (8-12 slides) following StoryBrand framework
  2. One-Pagers - Single-page service summaries with visual storytelling focus
  3. Landing Pages - Web pages with lead capture forms and FAQ sections

All prompts integrate:

  • Interview transcripts/notes (user-provided)
  • Vault knowledge (services, StoryBrand framework, case studies)
  • Visual suggestions for designer collaboration
  • StoryBrand framework compliance

Quick Start

1. Choose Asset Type

Decide which asset you need:

  • Service Deck: For presentations, pitches, sales materials
  • One-Pager: For quick summaries, handouts, email attachments
  • Landing Page: For web pages with lead capture

2. Gather Interview Transcript

Collect interview transcript or notes from service interviews. Include:

  • Pain points discussed
  • Outcomes and metrics mentioned
  • Client quotes
  • Process details
  • Success stories

3. Use the Appropriate Prompt

Open the relevant prompt file:

  • service-deck-prompt.md - For service decks
  • one-pager-prompt.md - For one-pagers
  • landing-page-prompt.md - For landing pages

4. Fill in the Prompt

  1. Service Information: The agent will pull from vault, but you can specify the service name
  2. Interview Transcript: Paste your transcript in the designated section
  3. Run the Prompt: Use with the service-asset-creator agent

5. Review Output

The agent will generate:

  • Copy-only markdown draft
  • Visual suggestions for each section
  • StoryBrand-compliant structure
  • Stats and metrics extracted from transcript

Interview Transcript Formatting

What to Include

Required Information:

  • Pain points (what problems does this solve?)
  • Outcomes (what results do clients see?)
  • Metrics (specific numbers, % improvements, time savings)
  • Client quotes (direct quotes about pain and outcomes)
  • Process details (how the service works)
  • Success stories (specific client examples)

Optional but Helpful:

  • Common objections/questions (for FAQ sections)
  • Industry context
  • Use cases
  • Timeline details
  • Team involvement

Formatting Tips

Best Format:

  • Plain text or markdown
  • Include speaker names if multiple people
  • Preserve quotes exactly as spoken
  • Include context around metrics

Example Format:

Interview with [Service Lead] - [Date]

[Speaker 1]: [What they said about the problem...]

[Speaker 2]: [What they said about outcomes...]
"We saw a 40% reduction in time to insight" - [Client Name]

[Speaker 1]: [Process details...]

What NOT to Include:

  • Internal pricing discussions (not used in assets)
  • Confidential client information (unless approved)
  • Off-topic conversations

Using the Prompts

With Claude Desktop (Agent)

  1. Open Claude Desktop
  2. Select Agent: Choose service-asset-creator agent
  3. Open Prompt File: Copy the relevant prompt template
  4. Fill in Sections:
    • Service name (if not auto-detected)
    • Interview transcript (paste in designated section)
  5. Run: Send the filled prompt to the agent
  6. Review Output: Check markdown draft and visual suggestions

With Cursor/VS Code

  1. Open Prompt File: Navigate to gtm/agents/prompts/service-asset-prompts/
  2. Copy Template: Copy the relevant prompt
  3. Fill in Sections: Add service info and transcript
  4. Use with AI: Paste into AI chat with context about the agent
  5. Review Output: Check generated markdown

Output Interpretation

Markdown Structure

Each prompt generates markdown with:

For Service Decks:

## Slide 1: [Title]
**Copy**: [Headline and body]
**Visual Suggestion**: [Recommendation]
**StoryBrand Element**: [Framework element]

For One-Pagers:

## Top Section: Visual Storytelling
**Headline**: [Headline]
**Key Stats**: [Metrics]
**Visual Suggestion**: [Primary visual]

For Landing Pages:

## Hero Section
**Headline**: [Headline]
**CTA**: [Call-to-action]
**Visual Suggestions**: [Recommendations]

Visual Suggestions

Each section includes visual suggestions:

  • Type: Chart, diagram, icon, imagery
  • Description: What to show
  • Placement: Where it should go
  • Purpose: What story it tells

Designer Handoff:

  • Copy is ready for designer
  • Visual suggestions guide design
  • Designer implements visuals based on suggestions

StoryBrand Elements

Each section notes which StoryBrand element it represents:

  • Character: Target customer
  • Problem: Pain points
  • Guide: Brainforge positioning
  • Plan: Process/solution
  • Success: Outcomes
  • CTA: Call-to-action

Asset-Specific Guidelines

Service Decks

Structure: 8-12 slides following StoryBrand flow Stats: % improvements, results, time to insight, decisions, ROI Exclusions: NO pricing/investment section Visuals: Charts, diagrams, icons, imagery for each slide

Use When:

  • Presenting service to prospects
  • Sales pitch materials
  • Internal service documentation
  • Partner presentations

One-Pagers

Structure: Condensed, scannable format Focus: Top section tells story with visuals and stats Sections: Headline, value prop, benefits, audience, deliverables, CTA + plan Visuals: Top section dominated by visuals and stats

Use When:

  • Quick service summaries
  • Email attachments
  • Handouts at events
  • Initial service introductions
  • Follow-up materials

Landing Pages

Structure: Web page with lead capture Reference: Follows sample page structure Sections: Hero, problem/solution, preview, features, social proof, process, FAQ, final CTA Visuals: Hero visuals, trust signals, social proof elements

Use When:

  • Web pages for service offerings
  • Lead generation pages
  • Service-specific landing pages
  • Download/offer pages

Quality Checklist

Before using generated assets, verify:

All Assets

  • StoryBrand framework is followed
  • Interview transcript information is incorporated
  • Vault knowledge is integrated
  • Visual suggestions are provided
  • Copy is clear and compelling
  • Stats/metrics are included where relevant

Service Decks

  • NO pricing/investment section
  • All required stats are included
  • Slide-by-slide structure is clear
  • Visual suggestions for each slide

One-Pagers

  • Top section tells story with visuals and stats
  • All sections are condensed
  • Visual storytelling focus is clear
  • Scannable format

Landing Pages

  • FAQ section is included
  • Lead capture form/CTA is clear
  • Social proof is included
  • Structure follows sample pages

Troubleshooting

Missing Information

If transcript is incomplete:

  • Agent will note missing information
  • Use vault knowledge to fill gaps
  • Mark sections that need additional research

If service details are missing:

  • Agent will reference gtm/agents/memory/services.md
  • Note if service needs to be documented first

Output Quality

If copy is too generic:

  • Ensure transcript has specific details
  • Check that StoryBrand framework is being applied
  • Verify vault knowledge is being referenced

If visuals are unclear:

  • Review visual suggestion guidelines in prompt
  • Provide more context about brand guidelines
  • Specify visual style preferences

StoryBrand Compliance

If framework isn’t followed:

  • Check that prompt is being used correctly
  • Verify StoryBrand framework file is accessible
  • Review framework reference section in prompt

File Structure

gtm/agents/prompts/service-asset-prompts/
├── README.md (this file)
├── service-deck-prompt.md
├── one-pager-prompt.md
└── landing-page-prompt.md

  • Agent Definition: gtm/agents/.claude/agents/service-asset-creator.md
  • Service Details: gtm/agents/memory/services.md
  • StoryBrand Framework: gtm/content/storybrand-framework.md
  • Case Studies: gtm/sales/*.md (SOW documents)

Updates & Maintenance

When to Update Prompts:

  • StoryBrand framework changes
  • New service types added
  • Visual guidelines updated
  • Output format changes

Version Control:

  • Prompts are versioned in git
  • Update “Last Updated” date when modifying
  • Document changes in commit messages

Support

Questions?

  • Review agent definition file for capabilities
  • Check StoryBrand framework for messaging guidance
  • Review sample landing pages for structure reference

Improvements?

  • Update prompts based on feedback
  • Add new visual suggestion guidelines
  • Enhance transcript extraction instructions

Last Updated: 2026-01-30 Maintained By: GTM Team