Pitch Deck Narrative Writer

A spoken pitch deck script for each slide, investor-ready narrative that builds urgency, proves traction, and closes with a clear ask.

Best For

•A founder preparing for a seed round roadshow uses it to write the actual spoken words for each slide, not bullet points, so the pitch sounds rehearsed but not robotic
•A first-time presenter nervous about the traction slide uses it to turn raw metrics into a concrete, confident narrative moment instead of a dry data recitation
•A co-founder team splitting speaking parts uses the script as a shared baseline so both founders tell the same story with the same emphasis on urgency and ask

Prompt Template

Write the narrative script for a [LENGTH, e.g., 10-slide] investor pitch deck for [COMPANY NAME]. Company context: [2-3 sentences describing what the company does, for whom, and what stage you are at]. Here are the key facts to weave in: problem we solve: [PROBLEM], our solution: [SOLUTION], market size: [TAM/SAM/SOM], traction: [KEY METRICS OR MILESTONES], business model: [HOW WE MAKE MONEY], team: [FOUNDER BACKGROUNDS], and ask: [FUNDING AMOUNT AND USE]. Write the spoken script for each slide, not bullet points, but the actual words the founder says while the slide is on screen. Each slide script should be 60–90 seconds when spoken. Make the opening memorable. Make the problem feel urgent. Make the traction slide concrete with specific numbers. Make the team slide personal and relevant to the problem. End the ask slide with a clear statement of what changes when they invest. Tone: confident, specific, and human, not corporate.

Pro Tip

Give the model your real traction numbers and specific milestones rather than describing them as 'strong growth', since the prompt is designed to make the traction slide concrete and it can only do that with actual figures to anchor on.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

Slide 3, Problem: 'Every regional logistics company we've talked to is losing money the same way: dispatchers manually routing trucks with spreadsheets built for a fleet half their current size. One customer told us they lose four hours a week just re-planning routes after a single truck breaks down. That's not a scheduling problem, that's a system that was never built to scale.' Slide 6, Traction: 'In four months we've gone from zero to 18 paying customers and $22,000 in monthly recurring revenue, growing 35% month over month.'