Skip to main content

Build a founder-story landing page

Use a founder-story page when the founder’s experience, point of view, or reason for building the product is genuinely part of why a customer should believe in it. The story is not a biography. Its job is to make the product’s point of view understandable and credible.

When to use it

A founder-led page is especially useful when:
  • the product was created after a meaningful firsthand problem
  • the category has a trust gap
  • formulation, sourcing, design, or product philosophy needs explanation
  • founder credibility is already important in ads or creator content
  • the brand competes on a clear belief about how the problem should be solved
Do not force the format when the founder story has little connection to the customer’s purchase decision.

Step 1: collect the real founder material

Use first-party, approved source material where possible:
  • founder interview or transcript
  • approved founder letter
  • brand origin brief
  • product-development story
  • founder video transcript
  • exact approved quotes
Then extract:
If you cannot fill these in with real source material, gather more context before generating the story.

Step 2: make the customer the reason the story matters

A strong founder page often follows:
  1. Customer-facing hook — the problem or belief.
  2. Founder connection — why this became personal or important.
  3. The gap — what was unsatisfying about existing approaches.
  4. The principle — what the founder believed should be different.
  5. The product — how that principle shaped the product.
  6. Proof — evidence the product deserves trust.
  7. Purchase decision — what the customer can do now.
The founder can be the narrator without becoming the subject of every section.

Copy-ready Jurni prompt

Step 3: use exact quotes carefully

If the founder said something especially useful, preserve it as an actual quote. Do not ask AI to make a paraphrase look like a direct quote. Label source material clearly:

Step 4: connect product details to the principle

The strongest founder pages show how a belief affected the product. For example:
  • “We wanted fewer steps” → product format or routine design
  • “We couldn’t find X without Y” → approved formulation choice
  • “We wanted people to know exactly what they were buying” → sourcing/transparency detail
Do not create a principle after the fact to make every feature sound meaningful.

Step 5: keep the story visually human

Useful assets can include:
  • founder image
  • product-development imagery
  • handwritten or archival material the brand owns
  • product closeups
  • simple founder quote treatment
Avoid filling the page with generic stock imagery that breaks the authenticity of the story.

Step 6: introduce proof beyond the founder

The founder can explain why the product exists. Customers still need reasons to believe the product works for their decision. Use approved customer proof, reviews, product evidence, or other trust signals where appropriate. The founder’s confidence alone is not independent proof.

Step 7: review for biography drift

What good looks like

The visitor should leave with a clearer understanding of the brand’s point of view and how that point of view shaped the product. The story should feel difficult for another brand to copy because it is grounded in real people, decisions, and product truth.

Common mistakes

Opening with “Meet our founder.” Lead with the customer tension unless the founder is already the traffic hook. Invented founder voice. AI can shape structure and transitions; it should not manufacture personal history or quotes. Founder as the only proof. Add relevant customer or product evidence. Too much chronology. Dates and milestones matter only if they support the buying story. No clear conversion transition. The story should eventually make product evaluation easier.

What to test next

  • customer-problem opening versus founder-first opening
  • founder video/quote near hero versus later
  • shorter founder section embedded in a PDP versus full founder-story page
  • product introduced earlier versus after the core story insight

Next playbooks