How to Write an About Us Page That Converts (Template + Examples)
Turn your About page from a boring biography into a trust + conversion asset — with a reusable template for startups, freelancers, and tool brands.
People don’t visit About to read your childhood story. They visit to decide: “Can I trust these people with my time / money / data?”
What a converting About page must answer
- Who you help
- What outcome you create
- Why you’re credible
- What to do next
Page template (copy this)
1) Hero promise (not “Welcome”)
“We build free AI tools so creators can write captions, bios, and outreach without paying five subscriptions.”
2) Origin in one paragraph
One problem you saw → what you built → who it’s for now. Keep it under 80 words.
3) Proof strip
- Numbers (tools, users, generations) when true
- Logos / press / notable users if you have them
- A short testimonial
4) Values as behaviors
Don’t list “integrity.” Say: “No login wall. No fake ‘pro’ upsell. You own your output.”
5) Team / face
One real photo + 2-line bio beats a stock collage.
6) CTA block
Primary: try a tool
Secondary: contact / newsletter
Examples by business type
SaaS / tools
Lead with product outcome → mission → roadmap honesty → CTA to flagship tool.
Freelancer
Lead with niche + result → process → selected work → book a call.
Local / service
Lead with service area + promise → credentials → reviews → contact.
SEO notes
- H1 includes “About” + brand or niche
- One internal link to your best product/tool page
- FAQ: “Who is behind X?” / “Is it free?”
Related guides
Frequently asked questions
How long should an About page be?
400–800 words is enough for most brands. Add depth only if trust requires it (regulated niches, high ticket).
Should founders write in first person?
Yes for early-stage and freelancer brands. Use “we” once the brand is clearly a team product.
An About page should answer the visitor’s trust questions: who is behind this, why are they qualified, how do they work, and is this company a fit? The company story matters when it helps readers evaluate those questions.
Lead with present-day relevance
-
State what the company does, who it serves, and the problem it is built to solve. Do not make visitors decode a mission statement.
-
Tell the origin as a short cause-and-decision story: what was observed, why existing options failed, and what the founders chose to build differently.
-
Translate values into operating behavior. “Transparent” becomes pricing practices, communication standards, sourcing disclosures, or published limits.
-
Add verifiable proof: team experience, customer outcomes with context, certifications, methodology, locations, or years operating.
Introduce people with purpose
Use names, roles, relevant experience, and what each person contributes. Real photos can strengthen trust when appropriate, but do not expose private details. For distributed teams, explain collaboration or coverage only if it matters to customers.
Address fit and limits
Credibility improves when a company states who it serves best and what it does not claim. Explain data handling, editorial independence, service boundaries, or product limitations where these affect trust. Link to full policies rather than turning the page into legal copy.
End with a logical path
Offer the next step that follows the reader’s likely intent: see the product, review work, meet the team, read methodology, explore careers, or contact a named function. One primary route is more useful than a row of unrelated buttons.
A practical review checklist
- The opening explains company, audience, and problem.
- The origin story supports current positioning.
- Values have observable evidence.
- People and proof are verifiable.
- The next step matches visitor intent.
Frequently asked questions
Should the About page be written in first person?
Use the voice that matches the brand and ownership. First person feels direct for founders; third person can work for larger organizations if it avoids bureaucratic distance.
How much history should it include?
Include milestones that explain credibility, direction, or customer value. A complete corporate chronology belongs elsewhere.
Should small companies mention team size?
Be honest where capacity matters, but size alone is neither proof nor a weakness. Explain the working model and response expectations.
The related About-page tool can organize source notes; replace placeholders with real people, proof, policies, and decisions.
Share this article