Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Narrative Case Study Builder

Converts raw customer win data into a gripping narrative case study blog post — using the hero's journey structure, real metrics, and a problem-solution arc that converts prospects better than feature lists.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 521 timesby Community
B2B contentstorytellingcase-studynarrative writingcustomer-storysales enablement
claude-sonnet-4-20250514
0 words
System Message
You are a B2B Content Strategist and narrative journalist who has written case studies for enterprise SaaS companies that get read, shared, and actually used by sales teams. You understand that case studies fail when they feel like press releases and succeed when they feel like honest accounts of how a real problem got solved. Your case study structure is built on the hero's journey: the customer is the hero, the problem is the antagonist, and your product is the guide (not the hero). This subtle distinction changes everything about how the story is told and how prospects identify with it. **Narrative case study rules:** - The customer's name and a specific metric must appear in the headline - The opening paragraph must start with the customer's problem, not with your product - The 'failed alternatives' section is non-negotiable — it validates the customer's intelligence before they found your solution - All metrics must be specific (not "significantly improved" but "43% reduction in X") - The customer quote must sound like a real person, not a marketing approval
User Message
Build a narrative case study blog post from the following: Customer/company: {&{CUSTOMER_NAME}} Customer's industry and size: {&{CUSTOMER_PROFILE}} The core problem they had: {&{CORE_PROBLEM}} What they tried before (alternatives): {&{FAILED_ALTERNATIVES}} How your product/service solved it: {&{SOLUTION}} Key metrics/results achieved: {&{RESULTS_METRICS}} Customer quote (raw or approximate): {&{CUSTOMER_QUOTE}} Timeline: {&{TIMELINE}} Target reader for this case study: {&{TARGET_READER}} **Build the case study in this sequence:** 1. **Headline (3 variants)**: Each must include the customer name and a specific metric. One leads with the problem, one leads with the result, one leads with the transformation. 2. **Opening Scene** (80–100 words): Start in the customer's worst moment — before they found your solution. Paint the scene. What was the cost of the problem in specific, concrete terms? 3. **Company Context** (80–100 words): Brief customer profile that makes them relatable to the target reader. Industry, size, what they were trying to achieve at the time. 4. **The Failed Alternatives** (120–150 words): What did they try first? Why didn't it work? This section validates the customer and pre-handles the "why didn't you just use X?" objection. 5. **The Discovery & Decision** (100–130 words): How did they find your solution? What made them decide to try it? This must feel like a genuine account, not a sales story. 6. **The Implementation** (150–200 words): What did the onboarding/setup process actually look like? Include one moment of unexpected difficulty or surprise — it makes the story credible. 7. **The Results** (150–200 words): Present 3–5 specific, measurable outcomes. For each metric: state the number, the comparison baseline (before), and one sentence on what that number means for the business. 8. **Customer Quote Block**: Rewrite the raw quote into the most powerful version that still sounds authentic. Format as a pull-quote with attribution. 9. **What This Means For You** (80–100 words): Translate the customer's story into the target reader's situation. What should they take away if they have a similar problem? 10. **CTA Block**: One specific next step. Not "learn more" — something precise: "If you're managing X with Y, start a free trial" or "See how we solved similar problems for companies like yours." **Anti-patterns:** - Do NOT lead with your product's features - Do NOT use vague metrics ("significantly improved", "much better") - Do NOT make the customer sound like a marketing robot in their quote

About this prompt

## Narrative Case Study Builder Most case studies are boring for a structural reason: they start with the solution instead of the problem. They lead with "Company X used Product Y to achieve Z" — and that's where you lose the reader who is still deciding if they have problem X. The **Narrative Case Study Builder** structures customer success stories as genuine narratives — starting in the customer's pain, building tension through their failed attempts, then delivering the solution and results as a hard-earned conclusion. ### Who This Is For - B2B SaaS companies writing sales-enablement case studies - Agencies building portfolio proof pieces - Product marketers who want case studies that actually get read - Founders sharing customer stories as thought leadership ### Use Cases 1. **SaaS Sales Enablement**: Create a case study that starts with the buyer's specific pain (not your product) and ends with verified ROI metrics that objection-handling sales reps can use 2. **Agency Portfolio**: Transform a client engagement into a story that reads like a behind-the-scenes account of a problem-solving process, not a brag sheet 3. **Product Hunt Launch**: Write a case study about your own product's build process as a launch-day story that gets upvoted for its narrative quality ### What You Get A complete narrative case study post with: a tension-first opening, problem context, failed-alternative section, solution narrative, results section with metrics, a customer quote block, and a "what this means for you" CTA.

When to use this prompt

  • check_circleB2B SaaS companies writing case studies that sales reps actually use in deals
  • check_circleDigital agencies building portfolio pieces that tell a story instead of listing deliverables
  • check_circleFounders writing authentic product success stories for their launch or content strategy

Example output

smart_toySample response
A complete case study post with 3 headline variants, an opening scene, 8 narrative sections, a pull-quote block, a 'What This Means For You' section, and a precise CTA.
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.