Write a brand story for [BRAND] aimed at [TARGET AUDIENCE]. The audience faces this concrete situation or problem: [CUSTOMER PROBLEM]. Our offer and evidence are: [OFFER AND PROOF]. The desired action is [CALL TO ACTION]. Create a 650- to 850-word website-ready story with these labeled sections: customer tension, the old way and its cost, the insight behind the brand, how the offer helps, proof and limits, what changes for the customer, and a direct call to action. Make the customer, not the company founder, the protagonist. Describe the customer's starting condition, obstacle, choice, and desired outcome in terms that match their actual work or life. Position the brand as a capable guide: show the relevant method, product, or service, explain what it does and does not do, and connect each benefit to a supplied feature or proof point. Use only claims, customer outcomes, statistics, testimonials, or origin details included in my inputs. If the evidence is thin, write a restrained claim and flag the gap rather than creating social proof, revenue figures, awards, or dramatic transformation. Use a voice that is [BRAND VOICE]. Avoid inflated mission language, generic industry claims, and a founder biography unless it directly explains a customer-relevant insight. Give the story a specific point of view rather than a timeline of company milestones. After the story, provide a five-line message map: audience, problem, promise, proof, and action. Before answering, check that every claim can be traced to an input and that the call to action matches the audience's decision stage. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [BRAND] | Describe the company, product, and category in a few factual sentences. | Ledger Lane is bookkeeping software for independent architecture studios with two to fifteen employees. |
| [TARGET AUDIENCE] | Name the specific buyer or user and their relevant context. | Studio principals who still reconcile projects and invoices after client work. |
| [CUSTOMER PROBLEM] | Describe the concrete frustration, risk, or job the audience is trying to solve. | They cannot see project profitability until weeks after decisions are made and rely on spreadsheets built by a former employee. |
| [OFFER AND PROOF] | List the offer, features, verified outcomes, testimonials, and limits you can support. | Connects bank feeds, time entries, and invoices; shows project margins weekly; three customer quotes approved for use; no claim of replacing an accountant. |
| [CALL TO ACTION] | State the single next action you want readers to take. | Book a 20-minute workflow review. |
| [BRAND VOICE] | Describe the desired voice with a few useful traits and examples to avoid. | Calm, practical, and respectful of design work; avoid startup slang and grand promises. |
How to use
- Paste factual source notes, including approved testimonials and claims you can substantiate.
- Name one tightly defined audience instead of grouping every possible customer together.
- Check the draft for a clear customer problem, proof attached to each promise, and one action readers can take.
- Follow up with: "Rewrite the opening for a skeptical buyer who has tried spreadsheets and does not trust software claims."
Variations
Founder story
Use this when the founder's experience directly explains why the company exists.
Write a 500-word founder story for [BRAND] based only on these verified events: [FOUNDER FACTS]. Connect the origin to this customer problem: [CUSTOMER PROBLEM] and this current offer: [OFFER]. The reader is [AUDIENCE]. Include the triggering insight, the decision to act, and how that insight shapes the product today. Do not create hardship, customer outcomes, dates, or milestones not supplied. End with [CALL TO ACTION] and flag any unsupported claim. Voice: [VOICE]. Ask up to three questions only if necessary.
About page
Use this for a concise About page that explains what the company does and why it matters.
Draft an About page for [BRAND] for [AUDIENCE]. Use these facts: [FACTS]. In 350 to 500 words, explain the customer problem, the company's point of view, what it offers, how it works at a high level, and why readers should trust it. Make the customer need more prominent than company history. Include a short values list only if it is evidenced by real operating choices. End with [CTA]. Do not invent team size, mission claims, testimonials, or results. Check each claim against the provided facts.
Campaign narrative
Use this when a launch or campaign needs a focused story rather than a full brand history.
Create a campaign narrative for [CAMPAIGN] aimed at [AUDIENCE]. The audience currently faces [TENSION], and the offer is [OFFER]. Use these approved facts and proof points: [PROOF]. Produce a 300-word landing-page narrative, three headline options, and one CTA. Build urgency from a real decision, deadline, or consequence supplied in the inputs, not false scarcity. Do not promise outcomes that the proof does not support. Tone: [TONE]. Ask up to three questions only if a required input is missing.
Tips
- Treat proof as part of the story, not a footer: attach a customer quote, process detail, or verifiable outcome to the promise it supports.
- A useful brand antagonist is usually the costly old process, not a competing company or a vague statement about the industry.
- Match the call to action to trust: a new visitor may book a demo or download a guide, while a ready buyer may start a trial.
- Keep founder details only when they explain an insight your audience can use; chronology alone rarely improves positioning.
FAQ
Should a brand story be about the founder?
Usually the customer should be central. Founder context earns space when it provides a credible reason the brand understands the customer's problem.
Can AI create testimonials for a draft?
No. Use approved customer language, anonymized research notes you are allowed to use, or leave a proof gap clearly marked.
How long should a brand story be?
For a website page, 500 to 900 words is often enough. Use the reader's decision complexity, not a fixed word count, to decide what to include.