Storytelling

general
3 prompts
0 users

Prompts tagged with “Storytelling

Creating a Brand Story Using Legendary Marketer Seth Godin's Framework

<Task>Create a brand story for a product the user submits following Seth Godin’s approach to brand storytelling with four clear sections - ‘setting the scene’, ‘introducing the challenge', ‘overcoming obstacles’, and finally ‘the transformation’. <Inputs>{Product_Name}</Inputs><Instructions> <step>Setting the Scene: Create a narrative for ‘Setting the Scene’. This section should introduce the product's customer and brand and the problem space the product operates within. It should be easy to understand and jargon free. It should entice the reader to consume the entire story and learn about how the product could make their life better. Add this narrative to the variable $scene to be used later in this prompt</step> <step>Introducing the Challenge: Next you need to clearly introduce the core challenge the customer of the product has, the challenge this product will solve. Introducing the challenge the hero customer faces is crucial because it creates tension that demands resolution. This tension captures the audience's attention and keeps them engaged, as they’ll want to see how the challenge is overcome. It's also an opportunity to highlight the specific problems the product solves. Add this narrative to the variable $challenge to be used later in this prompt</step> <step> Overcoming Obstacles:Next you’ll move to the part where the story delivers on its promise, showcasing how the hero confronts and overcomes the challenge. It's a demonstration the product in action, providing concrete examples of how obstacles are surmounted. This part of the story builds credibility and illustrates the effectiveness of the product to solving the customers problem. It's also where empathy and inspiration come into play, as the audience sees the journey of overcoming obstacles as both relatable and aspirational. Add this narrative to the variable $obstacles to be used later in this prompt</step> <step>The Transformation: This is the culmination of the story, the transformation, is the payoff for the audience. It’s the evidence that change is possible, and it directly ties the journey to a positive outcome. This is where you highlight the benefits and value of the product, showing not just a change in circumstances, but a change in the hero's life or state of being. The transformation is what turns the story from a narrative into a testimonial of success, illustrating not just what your product does, but why it matters. Add this narrative to the variable $transformation to be used later in this prompt</step> <step>Present your completed brand story including the product name into a table that should be structured as follows: First Row: [Setting the Scene][Introducing the Challenge][Overcoming Obstacles][The Transformation] Second Row:[$scene][$challenge][$obstacles][$transformation] Also provide a visual storyboard to illustrate this brand story to a CEO in an easy to understand jargon free way.</step> BEGIN BRAND STORYTELLING Product Name: {$PRODUCT_NAME} </Instructions>

Claude (Opus 4.1)TextFounder+2 more
1 views

Spotlight Your Customer as a Hero in Product Storytelling

<Task>Identify the "hero" customer or user in [insert_brands] product story based on the provided product details. Focus on the customer as the main character of the brands story and identify how does your product or service fit into their epic tale?</Task> <Inputs> {$PRODUCT_DETAILS} </Inputs> <Instructions> You will be analyzing a set of product details to identify the "hero" customer or user that the brand is positioning as the central focus of their product story. The "hero" is typically the type of person or user that the product is designed to serve and benefit the most. <step>Carefully review gather the product details from the suggested following places: The products website Review websites like TrustRadius and G2 Written articles about the product online to understand the target audience, primary use cases, and key benefits for customers.</step> <step>Identify the specific type of customer or user that seems to be the main focus or emphasis of the product description. This could be based on demographic details, lifestyle characteristics, or the specific problems/needs the product is meant to address.</step> <step>Consider how this "hero" customer or user is portrayed and positioned within the product details. Look for language that highlights their importance, unique challenges, or centrality to the product experience.</step> <step>Summarize the "hero" customer or user in 1-2 sentences, explaining why they appear to be the primary focus or most important beneficiary of the product based on the information provided. Write your summary inside <answer></answer> tags.</step> <step>If you are unable to clearly identify a "hero" customer or user, state that the provided product details do not contain enough information to determine the hero of the product story.</step> BEGIN ANALYSIS {$PRODUCT_DETAILS} </Instructions>

Claude (Gemini 2.5 Pro)TextFounder+2 more
0 views

One Idea, Six Stories Framework Explorer

You are Story Architect GPT. GOAL Take ONE story idea and render it in SIX storytelling frameworks so I can test which one lands best. INPUTS - Core Idea/Scenario: - Audience (who they are, what they care about): - Goal (what I want them to think/feel/do): - Tone (pick: visionary / pragmatic / friendly / urgent / credible): - Constraint (word count target: e.g., 120–180 words per version): - Call to Action (CTA): - Facts/Proof points (bullets): - Taboo/Don’ts (words or claims to avoid): OUTPUT SPEC Return SIX labeled sections in this order. For each, include a 1-sentence hook + the structured beats from that framework, then a tight CTA line. 1) PIXAR STORY FRAMEWORK Beats: Once upon a time… / Every day… / One day… / Because of that… (x2) / Until finally… 2) GOLDEN CIRCLE (SIMON SINEK) Beats: WHY (purpose/belief) → HOW (unique approach) → WHAT (offering) → CTA 3) STORYBRAND (DONALD MILLER) Beats: Character (customer) has a Problem → meets a Guide (us) with Empathy + Authority → gets a Plan (process + success path) → Call to Action (direct + transitional) → Stakes (avoid failure) → Success (after state) 4) HERO’S JOURNEY (CONDENSED) Beats: Call to Adventure → Threshold/First Step → Trials & Allies → Ordeal → Reward → Road Back → Transformation → Return with the Elixir → CTA 5) THREE-ACT STRUCTURE Beats: Act I (Setup: context + inciting incident) → Act II (Conflict: rising stakes, obstacles, turning point) → Act III (Resolution: decision, result, takeaway) → CTA 6) ABT (AND/BUT/THEREFORE) Beats: AND (status quo + context) → BUT (tension/change) → THEREFORE (action/result) → CTA STYLE RULES - Plain English. Concrete over vague. Verbs over adjectives. - Keep claims believable; tie to the provided facts. - No platitudes; show stakes and consequences. - Make each version self-contained (can be read without the others). - Use the audience’s language. Remove filler. QUALITY BAR - Each version must be skimmable and memorable. - Each beat must be one clear sentence (two max). - Avoid duplicate wording across versions. At the end, add a 6-row table: | Framework | Best Use Case | Risk if misused | Hook to test |

Gemini (Opus 4.1)FounderText+2 more
3 views