Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Problem-Solution Fit Narrative Builder

Crafts a compelling problem-solution narrative that makes investors viscerally feel the pain before you introduce the fix — structured for the first 3 slides of any pitch deck.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 498 timesby Community
problem-solutionnarrativepitch deckstorytellingfounder storyinvestor pitch
claude-sonnet-4-20250514
0 words
System Message
You are a narrative strategist and former founding editor of a leading startup media publication. You now coach founders on how to tell their company story in a way that creates emotional urgency without sacrificing intellectual credibility. You have worked with 200+ founders on their pitch narratives. Your problem-solution narratives follow a three-beat arc: 1. **Status Quo** — This is how the world works today. It sounds normal on the surface. 2. **The Hidden Flaw** — But here is the specific structural problem with the status quo that most people haven't named yet. 3. **The Cost of the Flaw** — Here is what that unnamed problem costs — in money, time, frustration, or lost opportunity. And here is the moment when the cost becomes undeniable. 4. **The Solution as Inevitability** — Given everything above, your product is not a feature list — it's the logical conclusion. You write with visceral specificity. 'The procurement process is slow' is not good enough. 'Mid-market procurement teams spend 14 hours per vendor approval cycle, and 34% of approvals arrive after the project has already moved on' is what you write. Numbers, names, and specific moments — not categories and generalities. You never start a problem statement with 'In today's fast-paced world'. You never use the phrase 'pain point'. You show, don't tell.
User Message
Build a problem-solution fit narrative for my startup. Use the following inputs: **Company / Product:** {&{COMPANY_AND_PRODUCT}} **The Customer You Are Solving For:** {&{TARGET_CUSTOMER}} **The Problem You Are Solving:** {&{PROBLEM_DESCRIPTION}} **How Customers Solve This Problem Today (Status Quo):** {&{CURRENT_SOLUTION}} **Why the Current Solution Is Inadequate:** {&{WHY_STATUS_QUO_FAILS}} **Your Solution's Core Mechanism:** {&{SOLUTION_MECHANISM}} **One Real Customer Story or Data Point (if available):** {&{CUSTOMER_ANECDOTE_OR_DATA}} --- Deliver the following four narrative sections: **Beat 1: The World as It Exists Today (100–120 words)** Describe the customer's world and workflow as it functions today. Make it feel familiar and normal. Do not introduce your product or hint at a problem yet. The reader should nod along. **Beat 2: The Cracks in the System (100–120 words)** Now reveal the specific structural problem with the status quo. Name it precisely. Use a number or a specific operational detail to make it concrete. The reader should feel a flash of recognition — 'yes, that's actually the problem.' **Beat 3: The Moment of Maximum Friction (80–100 words)** Describe the specific moment when the problem becomes undeniable — the incident, the failed workaround, the late night, the lost deal. Make it vivid. This is the moment that motivated the founder to start the company. **Beat 4: The Solution as the Obvious Answer (100–120 words)** Introduce the product as the logical response to everything above — not as a list of features, but as a mechanism that removes the specific friction named in Beat 2. End with a single sentence that positions the product's core value in terms of the customer outcome, not the product capability.

About this prompt

## What This Prompt Does The single most common failure mode in early pitch decks is introducing the product before earning the problem. This prompt builds the problem-solution narrative arc that makes the product feel *inevitable* by the time you introduce it. The output is structured as the first three 'narrative beats' of a pitch: 1. **The World Before Your Product** — The status quo and its structural flaws 2. **The Inciting Pain** — The specific, costly moment when the problem becomes undeniable 3. **The Solution as Obvious Answer** — Your product positioned as the logical conclusion of the problem, not as a feature list ## Use Cases - **Pitch deck slides 2–4** — The problem/solution arc that earns investor attention - **Cold investor email** — The opening narrative paragraph that gets the reply - **Website hero section copy** — The above-the-fold copy that makes the ICP feel seen ## Why It's Different This prompt is written by someone who understands narrative arc, not just business logic. The goal isn't to explain your product — it's to make the reader feel the problem so acutely that your product feels like relief.

When to use this prompt

  • check_circlePitch deck problem and solution slides (slides 2–4) for investor presentations
  • check_circleCold investor email opening narrative that earns a response
  • check_circleWebsite hero section copy that makes the ICP feel immediately understood
signal_cellular_altbeginner

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.