Writing & Delivery: Business Stories & Brand NarrativeFounding story · Customer as hero · Case study · Value proposition
BigCat's Writing
Good products don't speak for themselves. Given the same features, one person writes a spec sheet; another writes a story people remember and retell. Brand narrative isn't packaging—it's making clear why you exist, whom you help, and why they should trust you. Today, four weapons: origin, hero, proof, core.
Principle 01
The Founding Story: From "What We Do" to "Why We Do It"
The Founding Story — Start With Why
Brand · Origin
The Principle
Don't open with "Founded in year X, we specialize in Y." Start with the pain that made you unable to sit still. The heart of a founding story isn't the company—it's a specific person hitting a real problem, reaching their limit, and doing something about it.
"People don't buy what you do; they buy why you do it."
— Simon Sinek, Start With Why
Why It Works
Features can be copied; the "why" can't. Sinek's Golden Circle works inside-out—Why → How → What—yet most companies run it backward: lead with features, then advantages, motive left vague. The part of the brain that processes motive and emotion is exactly the part that drives decisions. A real origin pain sorts you into "someone like me" rather than "another vendor." Airbnb isn't a "short-term rental platform"—it's two designers who couldn't make rent putting three air mattresses in their living room.
Edit in Action
Founded in 2021, we're an AI infrastructure company dedicated to providing enterprises with high-performance, scalable LLM inference services.Three years ago, shipping every new model meant two weeks rebuilding the same inference stack. The 20th time we did it, we snapped. The system we built to stop driving ourselves crazy is the product you see today.
A company with a proven track record of delivering innovative solutions.Every launch cost us the same lost fortnight. We got tired of paying it—so we built the thing that gave the time back.
When to Use + Common Mistakes
✓ The website About page, a pitch opener, personal-brand bios, the top of a job post
✗ Writing the origin as a timeline (funding round, awards)—that's a résumé, not a story
✗ Faking or inflating the motive ("to make the world better")—the audience's radar pings in a second
✗ Making "the company" the protagonist instead of a person—an origin needs a specific human to empathize with
Key References
Simon Sinek, Start With Why · Nancy Duarte, Illuminate · Cases: Airbnb / Warby Parker origin narratives
This Week's Exercise + Question
Write your product's origin in three sentences: who, the specific pain they hit, and what they couldn't stand so they built. No "dedicated to," "specializing in," or "empowering." Question: can your "why" survive follow-up questions? If the motive is invented, readers will eventually find out—an ordinary, real pain always beats a grand, fake mission.
Principle 02
Make the Customer the Hero; You're Just the Guide
The Customer Is the Hero — StoryBrand
Brand · Positioning
The Principle
The biggest brand mistake is casting yourself as the hero. The hero is the customer; you're the guide who helps the hero. Be Yoda, not Luke. Be Gandalf, not Frodo.
"The customer is the hero, not your brand."
— Donald Miller, Building a StoryBrand
Why It Works
Everyone lives inside their own story; they wake up thinking about their own problems. When your copy is all "how great we are, how advanced our tech," the reader's subconscious asks, "what does that have to do with me?" Turn the camera onto the customer: who they want to become, where they're stuck, how you'll get them across. A guide has two marks—empathy ("I understand your situation") and authority ("I've helped many others like you"). Step back half a pace, and the customer can step in.
HeroThe CustomerHas a desire and a problem; the story turns on them
GuideYour BrandGives a plan and proof; helps them arrive
Luke is the hero, Yoda is the guide—don't steal the customer's scene
Edit in Action
Our platform features an industry-leading distributed architecture, supports 100-billion-parameter models, and serves the Fortune 500.Your team is holding back on LLMs because inference is slow and costly. We've helped dozens of teams like yours cut that cost in half. You're next.
We are the trusted partner of choice for enterprises worldwide.You need this shipped by Friday without a war room. That's the whole job we do—and we've done it for teams your size before.
✗ Every sentence subject is "we"—count your "we/our" versus "you" ratio
✗ Empathy without authority (sounds like support) or authority without empathy (sounds like a huckster)
✗ Writing the customer as a helpless victim—a guide empowers, it doesn't condescend
Key References
Donald Miller, Building a StoryBrand (the SB7 framework) · Joseph Campbell, The Hero with a Thousand Faces (the guide archetype) · Steve Jobs's product-launch narratives
This Week's Exercise + Question
Take a piece of your product copy and circle the subject of every sentence. Rewrite the ones starting with "we" to start with "you," and see if the meaning survives. Question: if you never mention your own features, how will the customer know you can help? The guide still shows a plan and proof—where's the line?
Principle 03
The Case Study: One Customer + One Number + One Arc
The Case Study — Situation, Complication, Resolution
Narrative · Proof
The Principle
A case study isn't a feature list with a logo stapled on. It's one customer's miniature hero's journey: where they were stuck (situation), what went wrong (complication), how you solved it (resolution), and the outcome (a landing with a number).
"A story's power is twofold: it provides simulation—knowledge about how to act—and inspiration—the motivation to act."
— Chip & Dan Heath, Made to Stick
Why It Works
When a prospect reads a case study, they're really simulating themselves: is this company like mine? Is their problem my problem? So the protagonist must be recognizable—industry, size, the real pain—not "a large enterprise." Conflict is the key: a story that goes only smoothly is neither believed nor remembered. End by landing on one hard number—"deployment from two weeks to two days," "cost down 47%." The number is the story's anchor; without it, the reader can't remember it or retell it to their boss.
SetupSituationA specific person and context
TurnComplicationWhat went wrong
FixResolutionHow you stepped in
PayoffResultOne hard number
No conflict, it's an ad; no number, no one remembers
Edit in Action
A well-known tech company saw significant efficiency gains and great results after adopting our product.A 40-person payments team pulled all-nighters scaling before every sale—and still went down for 20 minutes last Black Friday. With our autoscaling, this year they clocked out on time: peak held, cost down 30%.
Our solution helped the client optimize their workflow and improve outcomes.Support was drowning—4-hour reply times, angry reviews. Six weeks after switching, first-reply dropped to 18 minutes and their rating climbed from 3.2 to 4.6.
When to Use + Common Mistakes
✓ Website case studies, sales materials, white papers, conference talks
✗ "A certain company," "significant gains," "great results"—vague equals useless
✗ Result without conflict—reads like an ad, not a story
✗ Faked or unattributable numbers—an inflated ROI actually lowers trust
Key References
Chip & Dan Heath, Made to Stick (Concrete / Story) · Robert McKee, Story (the structure of conflict) · The B2B Challenge-Solution-Result template
This Week's Exercise + Question
Pick a real customer you served and write 120 words as Situation → Complication → Resolution → Result. The result must contain one concrete number. Question: if the customer won't let you use their real name or numbers, can the case still persuade? (Hint: you can anonymize industry and size, but don't lose the specificity of the number.)
Principle 04
The Value Proposition: Compress the Whole Story into One Line
The Value Proposition — The Job, Not the Feature
Positioning · Core
The Principle
Customers never want your features; they want the thing the features get done for them. A value proposition names the job they hire you to do, not the product's specs.
"People don't want to buy a quarter-inch drill. They want a quarter-inch hole."
— Theodore Levitt, Harvard Business School
Why It Works
Features are the means; the "job" (job-to-be-done) is the end. A buyer wants the drill for the hole, the hole to hang a picture, the picture for the warmth of home. The further up you ask, the closer you get to why they really pay. A value proposition compresses that job—and how you do it better than the alternative—into one line that can be remembered and repeated. Geoffrey Moore's classic template forces you to fill every slot with something concrete; if you can't, you haven't figured out your positioning yet.
Geoffrey Moore's positioning template: no slot takes an adjective—only specifics
Edit in Action
Our product is powerful, high-performance, user-friendly, and affordable.For small teams shipping LLM apps who find self-hosting too slow and costly, we're a plug-in inference layer that gets you live the same day. Unlike self-hosting, you don't need a dedicated infra team.
The all-in-one solution for all your business needs.For solo founders who dread bookkeeping, we're an accounting app that files your taxes for you. Unlike a spreadsheet, you never touch a formula.
When to Use + Common Mistakes
✓ Website hero, pitch page one, the elevator pitch, internal positioning alignment
✗ Piling up adjectives ("powerful, leading, superior")—adjectives are the cheapest claim
✗ Wanting every customer ("fits all enterprises")—no focus means no positioning
✗ Talking features instead of the job—users don't care what you have, only what you get done for them
Key References
Theodore Levitt, "the drill / the hole" · Geoffrey Moore, Crossing the Chasm (the positioning template) · Clayton Christensen, Jobs to Be Done · April Dunford, Obviously Awesome
This Week's Exercise + Question
Fill Moore's template for your product in one line; every slot must be concrete, no adjectives. Can't fill in the "key difference"? That's your real problem. Question: should a value proposition be written for "everyone"? A proposition aimed at one narrow segment usually sells better than one that pleases all—counterintuitive, so why?
Going Deeper
The founding story tells a "real pain," but once the company grows and the founder steps back, does the origin still hold?
It holds, but it has to transform. The value of an origin story isn't the founder as a person—it's the "why" it anchors. If the original pain is still the customer's pain, the story is still true. As the company grows, the protagonist migrates from "a certain founder" to "a belief this group protects together," and even onto the customer. The danger is turning the origin into myth and a cult of personality detached from today's customer reality. Ask periodically: the pain we first solved—do customers still feel it? If they do, the story is still alive.
Does "customer as hero" contradict "founder as hero" in the founding story?
No—they're different cameras for different scenes. In the origin story, the founder is the protagonist to establish "I understand this pain because I lived it"—he appears as a former customer, which is still the customer's point of view at heart. In product narrative, the camera must turn to the current customer, and the founder recedes to guide. The confusion shows up as: a homepage all about how legendary the founder is, saying nothing about what the customer gets. The rule: use the origin to earn the right to empathize, use customer narrative to drive conversion. Who plays hero depends on what you want the reader to feel right now.
Do business storytelling and "telling the truth" conflict? Does dramatizing slide toward exaggeration?
There's tension, and the line runs between "selective presentation" and "fabrication." Honest business narrative may choose which customer to feature, which number to highlight, which flat parts to skip—that's editing, not faking. You cross the line when you invent nonexistent customers, inflate unattributable numbers, or pass off a single case as universal. A self-check: if the protagonist of this case read it, would they nod or wince? The power of story comes precisely from truth—an ordinary but credible result closes better than a stunning but suspect number.
How do these four (origin / hero / case study / value prop) change across text, talk, and video?
The core is constant—whom you solve what for, and why they should trust you. What changes is the carrier. Text can be reread, so the value proposition fits the hero section and case studies can spread into detail and number tables; a talk or pitch is linear and heard once, so the origin story works best as a gripping opener, and you tell one case, one core number—more won't be remembered; video can "put a face to the customer"—a real user on camera telling their own story carries more of the guide's "authority" and "empathy" than any copy. The more immediate and un-rewindable the medium, the more you subtract: one story, one number, one line.
AI can now mass-produce marketing copy—what in business storytelling can't it replace?
AI can fluently apply StoryBrand and Moore's template and generate smooth copy—which is exactly what makes "formulaic pretty phrasing" cheap and same-y. Three things stay with humans: first, the real origin and pain—AI can't invent the specific night your team "had enough"; second, the real customer's real story—interviewing, getting permission, mining that moving detail is human work; third, judging what's worth telling—recognizing, in a pile of material, that "this customer's this moment will land hardest with that kind of buyer" takes an understanding of people and markets. AI is the skilled copywriter; the human is the one who knows which story is true and worth telling.