Write Your About / Founder Story Page
The About page is the most-skipped piece of trust-building content on every founder website. The version that exists is usually three paragraphs of generic "we believe in X" written in a hurry the night before launch. The version that converts is a deliberate, founder-led story — specific, memorable, and tied to why this particular product exists.
Done well, the About page does work nothing else can: it pre-empts the buyer's "who are these people?" question with an answer they remember, makes the founder a credibility asset rather than an unnamed corporate voice, and produces sentences that get quoted back to you years later.
This is the playbook to write it in 4 hours and have it earn its keep for the life of the company.
Why Most About Pages Fail
Three patterns produce the typical bad outcome:
- Vague mission language. "We believe everyone deserves access to [thing]" — the same sentence on 10,000 websites. It signals that the founder couldn't think of anything specific to say.
- Resume-list founder bios. "Sarah was previously at Google and Stanford" — fine for a LinkedIn page; not what an evaluating buyer needs to feel trust.
- No actual story. Pages that describe what the company does without explaining why this specific company exists are missing the entire point of an About page.
The buyer reading your About page already saw your homepage. They know what the product does. The About page exists to answer different questions: who built this, why does it exist, why should I trust it, what makes it different from the 50 other tools in this category?
This guide pairs with Customer Discovery Interviews (the customer-language you collected belongs in the founder story too), Define Your Brand Voice (the About page is the longest piece of brand-voice writing you'll do), Craft Your Value Proposition (the founder story should reinforce the value prop without restating it), and Building in Public (the About page distills the broader founder narrative).
What an About Page Is Actually For
The honest framing: an About page exists to answer four buyer questions in order:
- Who built this? Real names, real faces, real backgrounds.
- Why did they build it? A specific origin story, not a marketing tagline.
- Why should I trust them with my money / data / workflow? Credibility signals that don't read as bragging.
- What's the team's character? Tone, values, what they're like to work with.
Pages that answer all four well convert curious visitors into trial signups, calmer support relationships, easier sales calls, and warmer press coverage. Pages that answer none of these waste the visitor's attention.
1. Decide the Page's Job
The About page does different work depending on what stage your company is in. Pick the primary job before writing.
For my company at [stage / customer count / team size], decide which job the About page primarily does:
**Job A: Founder credibility for early-stage**
- "Why should I trust this 1-person company with my data?"
- Lead with: founder story, specific expertise, why-I-built-this moment
- Best for: 0-100 customers, indie hacker, AI SaaS
**Job B: Team and culture for mid-stage**
- "Who's behind this growing company?"
- Lead with: team grid, company values in action, customer stories
- Best for: 100-1,000 customers, 3-15 person team
**Job C: Mission-driven for category-defining**
- "What does this company stand for at industry scale?"
- Lead with: mission, founding story, why-we-exist manifesto
- Best for: products with category-defining ambitions, B2B that sells to mission-aligned customers
**Job D: Compliance + credibility for enterprise**
- "Is this company a serious vendor we can buy from?"
- Lead with: certifications, named investors, leadership bios with relevant experience
- Best for: products selling into enterprise procurement (alongside [Data Trust](../../../VibeWeek/6-grow/data-trust-chat.md) artifacts)
For my product:
- Recommend ONE primary job
- Identify the secondary job (a good About page does one main thing well + supports a secondary)
- Output: the About-page primary job locked in
Default for indie SaaS at <100 customers: Job A (Founder credibility). Default at 100-1,000: Job B (Team and culture). Default for enterprise-courting B2B: Job D (Compliance + credibility).
The single most-violated rule: About pages that try to do all four jobs do none well. Pick one primary job; the page becomes coherent.
2. Write the Origin Story
The origin story is the heart of every About page. It answers "why did this exist?" with specificity. The version that lands has these components.
Draft my origin story (~200-400 words on the About page).
Components, in order:
1. **The specific moment** — a real moment, in time, that started this. NOT "we noticed a problem in the industry"; YES "In March 2024, I was running [a specific thing] and hit [a specific wall]."
- Make it datable
- Make it concrete
- Make it personal
2. **What was at stake** — what made this worth solving? Why couldn't I just live with it?
- Concrete cost (time / money / opportunity)
- Why existing solutions didn't work for me
- What I tried before building
3. **The pivot point** — the moment I decided to build this
- Often a "I'll just build it myself" moment
- Sometimes a "I noticed others had the same problem" moment
- The specific decision that turned a problem into a project
4. **The early version** — what I built first, who I built it for
- Helpful: name a specific early customer (with permission) or anonymized "an indie hacker building [thing]"
- Numbers help: "It started as a 200-line script for me; today it serves [N] customers"
5. **The thread to today** — how does the original problem map to what the product does now?
- The product has grown; the underlying problem hasn't changed
- This connects the story to today's value prop
Anti-patterns:
- "I always wanted to start a company" — the story is not about wanting to be a founder; it's about wanting to solve this thing
- "We saw a $X billion market opportunity" — investor pitch, not founder story
- Generic origin words like "passionate," "revolutionary," "game-changing" — drain credibility
- Skipping the specific moment — a story without a hook isn't a story
For my product:
- Generate 3 candidate openings, each with a different specific moment as the hook
- Pick the strongest (the one that's most specific, most memorable, most tied to today's product)
- Output the full 200-400 word origin story draft
The "specific moment" rule is the difference between a story you remember and one you skim. "We noticed teams struggle with X" is forgettable. "I was on hold with [specific company] for 47 minutes when I realized I was paying $200/month for software whose only job was to do this exact thing" is a story.
3. Write the Founder Bio Section
After the origin story, the founder bio. This is where most pages fail by listing credentials instead of building credibility.
Draft the founder bio section (~150-300 words per founder).
Components, in order:
1. **The 1-line hook** — what makes this founder qualified specifically to build THIS product?
- "Sarah spent 8 years building [adjacent thing] and got tired of [exact problem]" beats "Sarah is the founder and CEO"
- Tie to the origin story; make it feel inevitable
2. **The relevant expertise** — 2-3 specific credentials that matter for THIS product
- Specific roles, specific outcomes, specific domain depth
- Not "passionate about X"; "shipped Y at Z"
- For technical products: technical credibility (built X used by Y); for B2B: customer-discovery credibility (sold to or worked with the buyer)
3. **The team color** — 2-3 sentences of personality
- What they're like to work with
- What they care about
- Optional: what they do when not building (humanizing detail, not life story)
4. **The connection** — how to reach them (LinkedIn, X, email)
- Real link, not a contact form
- Founder accessibility is itself a credibility signal
Critical anti-patterns:
- Resume-style bullet lists — kills warmth, reads as marketing
- Stock-photo headshots — readers can tell. Real photos, even imperfect ones, convert better than corporate ones
- Inflating titles — "Visionary CEO" / "Chief Storyteller" reads as overcompensating; "Founder" or actual roles work
- Using "the founder" or "the CEO" instead of named "I" / "Sarah" — distance for no reason
- Hiding the founder's name (yes, this happens) — kills trust
For each founder on the team:
- Write the 1-line hook tying their background to the product
- Write 2-3 specific credentials that matter for buyers
- Write 2-3 sentences of personality
- Add direct contact links
Output: the founder bio section ready to publish.
The "real photo" rule is concrete and consequential. Stock-photo team pages rank dead last in trust signals; AI-generated headshots are increasingly detectable and trust-eroding; real photos with real names convert measurably better, even when the photos aren't professional.
4. Add the Trust Signals (Without Bragging)
Buyers reading the About page want trust evidence. The version that lands is specific, current, and not list-shaped.
Add trust signals to the About page WITHOUT making it sound like a brag-list.
Patterns that work:
1. **Customer count + customer logos** (if you have permission)
- "Trusted by 1,200 teams including [Customer A], [Customer B], [Customer C]"
- Real logos from real customers (per [Customer Reference Program](../4-convert/customer-references.md))
- Specific numbers > vague claims
2. **Funding and investors** (if relevant and you have any)
- Backed by named investors that mean something to your buyer
- Skip if your investors are unknown to your buyer (it's noise)
- "Bootstrapped to profitability" is also a credibility signal — don't be ashamed of it
3. **Press coverage** (if real)
- "Covered by [reputable publication]" — link to the actual coverage
- Skip random aggregator sites; only press that adds credibility
4. **Compliance and security** (per [Data Trust](../../../VibeWeek/6-grow/data-trust-chat.md))
- SOC 2 status, compliance posture, privacy practices
- Link to /trust or /security for the deeper artifacts
5. **Team size honesty**
- "A team of 4" is a credibility signal for indie products
- Hiding the small team makes you look like you're hiding something
- Buyers buying from small teams know they're small; pretending otherwise is the credibility-loss
Patterns that don't work (and look like bragging):
- "We've been featured in 15+ publications" — vague brag
- Stock badges from random review sites (G2 Niche Leader, etc.) — looks padded
- Made-up customer numbers
- "Years of combined experience" — meaningless math
For my product:
- Identify which trust signals I genuinely have access to
- Skip the categories where I'd be padding
- Output the trust-signals section in 2-3 paragraphs maximum
The "honest small team" pattern is the move that disarms buyer skepticism. Founders try to look bigger than they are; smart buyers prefer to know they're working with a 4-person team. Owning the team size builds more trust than hiding it.
5. Write the "What We Believe" Section
Mission statements are usually awful. The version that works is specific opinions, not generic platitudes.
Write the "What We Believe" section as 3-5 specific opinions, not generic mission language.
The structure: each belief is a sentence the buyer can agree or disagree with. Real opinions have stakes — generic mission statements don't.
Examples that work:
- "We believe most [product category] software is over-priced for what it does."
- "We believe the right unit of pricing for AI products is [specific metric], not seats."
- "We believe SaaS quality has gotten worse as products have gotten more 'enterprise-ready.'"
Examples that don't:
- "We believe in empowering teams to do their best work" — generic
- "We're passionate about customer success" — every company says this
- "We believe in transparency and innovation" — meaningless platitude
The right opinions:
- Are specific to your category (not generic to "tech")
- Take a position the audience can agree or disagree with
- Tie to product decisions you've made (the beliefs aren't decoration; they show up in the product)
- 3-5 max — too many waters down the message
For my product:
- Brainstorm 8-10 genuine opinions I hold about my category
- Filter to the 3-5 that:
- Are most specific to my product positioning
- Are most opinionated (would create real disagreement somewhere)
- Are most reflected in my actual product decisions
Output: my 3-5 "What We Believe" statements + 1-2 sentences explaining each
The "buyer can disagree" test is the discipline that filters generic mission language. If your stated belief is something everyone agrees with, it adds nothing; if it's something some buyers will disagree with, it filters in the right buyers and creates genuine differentiation.
6. Decide What NOT to Put on the Page
About pages get bloated. The discipline is what to cut.
Audit my About page draft and cut what doesn't earn its place.
Things to consider cutting:
**Pricing recap** — has its own page; doesn't belong here
**Feature lists** — homepage's job, not About's job
**Roadmap details** — belongs in /roadmap or /changelog
**Customer testimonials** — fine in small doses; if you have many, give them their own /customers page
**Generic "join us" hiring callout if you're not actively hiring** — distracts; cut
**Stock images of teams in offices that aren't your team** — kills credibility; cut
**Long values lists** — you have 3-5 beliefs (Section 5); more than that becomes noise
**Press release-style language** — "[Company] today announced..." — wrong genre for About page
**Investors who don't mean anything to your buyer** — noise; cut unless they add credibility
**Awards from sites you've never heard of** — looks like padding; cut
**FAQ section** — has its own page; don't bloat About
**Product demo videos** — homepage / pricing / docs; not About
The discipline: every section on the About page should answer one of the four questions from "What an About Page Is Actually For" — who built this, why, why trust them, what's their character. Anything else gets cut.
For my page:
- Audit each section against the four questions
- Cut anything that fails the test
- Aim for an About page that's 800-1,500 words total — readable in 3-5 minutes
Output: the trimmed page outline + the cut list (sections I considered and removed, with rationale)
The 800-1,500 word target is what gets read. About pages over 2,000 words get skimmed; over 3,000 get bounced. The visitor came to evaluate quickly, not to read your memoir.
7. Test Before You Ship
Before publishing, run three quick tests.
Run these three pre-publish tests on my About page draft.
**Test 1: The 30-second skim**
- Show the page to a friend who doesn't know your product
- Ask: "After 30 seconds, what do you remember?"
- Healthy: they remember 1-2 specific things (the founder's name, a specific moment from the origin story, a belief you stated)
- Unhealthy: they remember vague impressions ("seemed nice," "tech company")
- If unhealthy: the specifics aren't sharp enough; rewrite with more concrete details
**Test 2: The buyer-substitute test**
- Show to someone in your buyer audience (or close enough)
- Ask: "Would this make you trust this company?"
- Listen for what they specifically remembered or doubted
- Common gaps: the credentials don't feel relevant to THIS product; the team feels too small for the scope; the origin story feels manufactured
**Test 3: The competitor-comparison test**
- Open About pages of your top 3 competitors
- Ask honestly: which About page would I pick this company over?
- The winner is usually the most specific, most personal, most opinionated
- If competitors all blend together, lean harder on what's specific to your team
Iterate based on results. Most About pages need 3-5 rewrites before they earn their place.
After publish:
- Track: where on the site does About page traffic come from? (Google? Footer link? Linked from a sales call?)
- Track: what's the next page they visit? (Pricing? Sign-up? Bounce?)
- Optimize: if About → Bounce is high, the page isn't producing trust; if About → Pricing is high, you've earned the trust transition
The friend-who-doesn't-know-the-product test is the most-skipped. Founders feel close to the material and lose sight of how it reads cold. A 30-second skim with a real outsider produces immediate concrete feedback.
Common Failure Modes
"My About page is mostly about my product, not the company." Lost the genre. Section 6 cut list — feature lists go to homepage; About is about who, not what.
"Generic mission statements that could be on any tech company's site." Section 5 — replace with 3-5 specific opinions buyers can disagree with.
"Too long; people aren't reading it." Section 6 — trim to 800-1,500 words.
"My About page has no founder photo or name." Worst-of-the-worst. Distance for no reason. Add the name and the real photo today.
"My About page hasn't been updated in 18 months." It's a living document — when the team grows, when the company evolves, when the story compounds, refresh. Set a quarterly check.
"Nobody comes to the About page." Probably true; that's fine. The About page does its work in moments — when a buyer is on the fence, when a journalist is researching, when a candidate is evaluating. It doesn't need traffic; it needs to be there when needed.
"My About page reads like a press release." Wrong voice. Read it out loud — does it sound like you talking? If not, rewrite in first person.
Common Patterns That Work
A non-exhaustive list of About-page patterns from companies that have nailed them:
- Stripe: founder-led, mission-clear, technical credibility implied through product detail rather than stated
- Basecamp / 37signals: opinionated belief statements about how software should work; the page IS the brand voice
- Linear: design-first; the page itself demonstrates the obsession
- Notion: founder origin tied to specific use cases; lots of specific names and roles
- Vercel: technical credibility through product; team is named and visible
- Substack: mission framed as a specific belief about media
What none of them do:
- Vague mission language
- Stock photos
- Bragging without specifics
- Resume-list bios
Cross-references
- Pre-work: Customer Discovery Interviews for the verbatim language; Define Your Brand Voice for tone consistency
- Adjacent positioning artifacts: Craft Your Value Proposition, Define Your ICP, Write Your Landing Page Copy
- Trust artifacts that pair with the About page: Data Trust playbook (VibeWeek), Customer Reference Program
- Founder content that compounds the About page's effect: Building in Public, Founder Newsletter, Podcast Guesting