Product storytelling prompts

Feature To Two-Minute Demo Story

This prompt generates a structured two-minute demo story that frames a specific product feature around a prospect's pain, a before state, a turning point, and a measurable after outcome. It's built for AEs and Sales Engineers who need to make individual features land in discovery demos, champion enablement, or executive presentations. Use it when a feature walkthrough alone isn't compelling enough and you need a narrative that connects the capability to a business result.

Business Case & ROI Development

Feature To Quantified Value For Audience

This prompt takes product features as input and generates audience-specific value statements that frame each capability in terms of the business outcomes most relevant to a given stakeholder persona. It's designed for AEs, Sales Engineers, and CSMs who need to tailor proposal content, demo talk tracks, or business case narratives to different buyer roles. Use it when you're preparing a multi-stakeholder proposal or presentation and need to speak each persona's language without rewriting your pitch from scratch.

Proposal

Post-Meeting & Event Follow-Up

Write a Post-Demo Follow-Up Email with Next Steps

This prompt produces a concise post-demo follow-up email for AEs and inside sales reps to send within 24 hours of a product demonstration. It recaps the use cases that resonated, addresses any open questions from the call, and confirms agreed next steps with a proposed date for the next meeting. Use it immediately after a demo to keep momentum and reduce the risk of the deal going dark.

Product Collaboration

Write a Lenny Rachitsky-Style PRD from Meeting Notes

This prompt generates a Product Requirements Document using Lenny Rachitsky's PRD format, pulling from meeting notes, call transcripts, or project context you provide. It is designed for sales and product teams coordinating on customer-driven feature requests or internal product initiatives. The prompt first surfaces candidate projects from your inputs, then lets you select one before writing the full PRD. Use it when translating customer discovery into a structured product brief.

Ongoing/Cross-Stage

Sales Presentation Narrative Arc Seven Stages

This prompt helps AEs and sales engineers build a presentation narrative that follows a proven seven-stage story structure — from establishing the status quo to making the case for change and positioning your solution as the resolution. It's designed for executive presentations, demo talk tracks, and formal proposal presentations where the story has to land, not just the features. Use it when you're building or rebuilding a presentation for a specific account and need a framework that creates momentum rather than just delivering information.

Demo & Presentation Follow-Up

Demo Follow-Up Rewrite Consultative Tone

This prompt rewrites an existing post-demo follow-up email to sound less transactional and more consultative — focused on the prospect's outcomes rather than product features. AEs and Sales Engineers use it immediately after a demo when the draft feels like a feature list rather than a value conversation. It's most effective when the demo uncovered specific pain points or use cases worth anchoring the follow-up around.

Draft Before-and-After Customer Mini-Stories

This prompt creates three short before-and-after customer mini-stories based on a list of buyer pain points and desired outcomes. Each story follows a consistent arc: life before the solution, what changed, and a measurable outcome. It's designed for AEs and sales engineers who need concrete narrative proof points for demos, proposals, or presentations rather than abstract feature claims. Use it when you're building demo talk tracks or proposal sections that need to show impact rather than just describe capability.

Recap Email & Next Steps

Write a Post-Discovery Recap Email from a Call Transcript

This prompt converts a discovery call transcript into a structured follow-up email that restates the buyer's situation in their own language, lists three to five agreed objectives, and outlines a proposed evaluation path without pitching product features. It's built for AEs who want to send a recap that reinforces discovery findings and advances the deal rather than just summarizing what was said. Use it within a few hours of a discovery call while the conversation is still fresh.

Discovery

Thought Leadership & Social Content

Write a LinkedIn Lesson Post from a Professional Mistake

This prompt produces a LinkedIn narrative post for AEs, SDRs, founders, and sales managers who want to share a genuine lesson from a difficult professional experience. It structures the story using a five-part narrative arc: the pivotal moment, the challenge, the action, the outcome, and the universal lesson. Use it when you have a specific real experience — a lost deal, a bad hire, a mis-timed pitch — that produced a lesson worth sharing publicly.

Ongoing/Cross-Stage

Rewrite a Demo Talk Track in Before-and-After Story

This prompt takes an existing demo talk track section and restructures it as a before-and-after story: a vivid current-state description, a turning-point moment with your solution, and an improved state grounded in specific metrics. It is designed for AEs and SEs who have completed discovery and want their demo narrative to feel personal to the buyer rather than generic. Use it when preparing a demo for a prospect where you have clear pain and a relevant customer metric to reference.

Create Data Visualization Techniques for Sales Presentations

This prompt helps AEs and Sales Engineers choose and construct the right data visualizations for sales presentations, business cases, and demo narratives. It produces practical guidance on selecting visualization formats, building infographics, heat maps, and charts that communicate clearly to a non-technical buying audience. Use it when building a data-heavy business case, preparing ROI slides, or designing a demo flow that needs to make complex data immediately legible to an economic buyer.

Build a Before-and-After Demo Narrative by Persona

This prompt helps AEs and SEs build a structured demo narrative that leads with business outcomes rather than feature walkthroughs. It takes the audience persona, the core pain, the product or capability set, the current environment, and the desired outcome, then produces a story arc, value moments, and a talk track. Use it when you're preparing for a first or second demo and want the story to land on business value, not product mechanics.

Demo & Presentation Follow-Up

Write Technical Follow-Up Email After Evaluation

Drafts a follow-up email to a technical evaluator after a demo or proof-of-concept, referencing specific technical points, offering resources, addressing integration concerns, and proposing a next technical session. AEs and Sales Engineers use this after any evaluation meeting where a technical stakeholder was present and has open questions. Use it within 24 hours of the meeting while the specifics are still actionable.

Evaluation

Create Feature-Advantage-Benefit Statements

This prompt creates Feature-Advantage-Benefit (FAB) statements for a specific solution — going from the technical capability to the competitive advantage it creates to the specific business benefit for the buyer persona. Use it to build messaging that connects product features to buyer outcomes rather than leaving the connection implicit.

Product Collaboration

Synthesize Call Notes Into a Roadmap Report

This prompt helps AEs and CSMs turn a pile of call notes and product feedback into a structured, credible report for the product team. It produces the top ten requested capabilities ranked by frequency and deal impact, plus five suggested roadmap focus areas. Use it before a quarterly product sync, ahead of a product council meeting, or when the team has weeks of unprocessed feedback sitting in call recordings and CRM notes.

Ongoing/Cross-Stage

Create Product Metaphors and Analogies for Demo Talk Tracks

This prompt generates five short metaphors or analogies — two to three sentences each — that explain how a product works or what it does in language that resonates with a specific buyer role in a specific industry. It's built for AEs and sales engineers who need simple, memorable explanations that work in a slide caption, a demo transition, or a verbal handoff. Use it when your product is technically complex and buyers consistently ask for a plain-language explanation of how it works.