About Us Page Examples

Quick answer: About Us page examples are reference points for how service businesses, ecommerce stores, SaaS products, local operators, and professional services structure their About pages so a visitor can quickly understand who is behind the business, who it helps, why it exists, what it believes, what makes it credible, and what to do next. The strongest About pages share a short intro paragraph, a real story section, a values block, a team or founder section with real names and photos where consent allows, a credibility or proof strip, a process or how-we-work block where relevant, and a clear CTA back to services or contact. Onyxarro can use concept-style examples to show the thinking clearly, but they should be labelled honestly as design examples, not presented as real client results. About page performance depends on the offer, the proof, the niche, the audience, the device mix, the speed and accessibility floor, the rest of the site, the tracking, and the follow-up. For a free 48-hour read of your About page in context, see our free 48-hour website audit.

An About page is not a founder biography. It is a trust page. By the time a visitor opens it, they have already seen the homepage, weighed the services, maybe read a review, and now they want to know whether the people behind the business feel real, capable, and safe to deal with. The strongest About pages answer that question in the first scroll and then back it up underneath.

Across every niche we audit (service businesses, ecommerce stores, SaaS products, local operators, professional services, creative studios), the structure stays the same. What changes is the weight on each section. A founder-led tradie About page leads with the person, the years on the tools, the service area, and a quote button. A SaaS About page leads with the company mission, the problem the product solves, and the team behind it. A clinic About page leads with the team, the credentials, and the booking link. Same section types, different depth on each.

This article walks the elements an About page needs, then runs niche pattern blocks (founder-led, team-based, service business, ecommerce, SaaS, local, professional services) so the umbrella stays useful for whichever niche you're briefing.

The About page is the second most-read page on most small business websites after the homepage. Buyers click it for one reason: they want to know who they're dealing with before they send a message or share their card details. Every paragraph either earns that trust or quietly leaks it.

A clean About page has a specific job. It tells the visitor who is behind the business, who the business helps, why the business exists, what it believes, what makes it credible, what proof can be shown honestly, and where to go next. Done well, the visitor leaves the page more confident and more likely to convert on the next click. Done badly, the visitor leaves the site.

None of this is legal, financial, medical, tax, compliance, staffing, operational, or industry-specific advice. The article is strictly about website design patterns. Your local advertising and consumer-protection rules sit above any of this. For the broader page-flow context, see our website homepage examples pillar, our website trust signals examples pillar, and our what makes a website convert guide.

Founder-led About pages put the person before the company. They work best for studios, agencies, consultancies, independent practitioners, photographers, builders, tradies running their own crew, and solo or small-team operators where the founder is the product.

Sections that earn their place. A real founder photo, taken on the same day as the rest of the imagery, at a consistent crop. A short founder paragraph in first person that names the founder, the years in the field, the kind of work they do, and one specific thing they care about. A "why I started this" line that explains the motivation without sounding like a TED talk. A short credibility strip (years on the tools, named past employers where appropriate, real industry memberships, real client niches). A clear CTA back to services, contact, or pricing.

What to avoid. Stock photos of a man in a suit pointing at a laptop. Bios written in the third person about a one-person business. "Award-winning" with no named award. "Trusted by hundreds" with no client visible anywhere on the site. Any biography paragraph that could be lifted onto a different studio's site without a single edit.

For founder-led service operators, the About page often does more work than the homepage. The closer the buyer is to handing the business their money, the more they want to see the actual person. See our service business website examples pillar for the wider service-niche context, and our tradie examples, photographer examples, and beauty salon examples for niche-specific founder patterns.

Team-based About pages lead with the company story and the values, then introduce a small named team. They work best for clinics, law firms, accountants, larger studios, ecommerce brands with a real production team, restaurants with named chefs, and any business where the visitor wants to know they're not just dealing with one person on holiday-cover.

Sections that earn their place. A short company paragraph that names what the business does, who it does it for, and roughly how long it has been doing it. A team grid with real names, real roles, and real photos shot in a consistent style on the same day with the same crop. A short paragraph or quote for the senior or founding team members. A credibility strip (real industry memberships, real certifications, real Google rating where genuine, real client niches). A clear CTA back to services, contact, booking, or pricing.

What to avoid. Generic stock photos of "diverse office team smiling at laptop". Vague "we are a passionate team of dreamers" copy. Team grids with no names or roles, where every face is interchangeable. AI-generated faces presented as real staff (one reverse-image search and the whole page falls). Long lists of staff for a five-person business, where the grid stops feeling honest after the third unfamiliar role.

For trust-led niches (clinics, law firms, accountants, real estate), the team grid is the most important block on the About page. See our clinic examples, law firm examples, accountant examples, and real estate examples for niche team patterns.

Service business About pages prioritise the founder or owner, the service area, the kind of work the business does, and the proof of doing that work well. The visitor wants to know: do you do my job, in my area, well enough that I can stop searching.

Sections that earn their place. A short owner paragraph with a real photo. A "what we do" block that names the actual services in plain language, not jargon. A "where we work" line naming the suburbs, region, or travel radius honestly. A "how we work" or process strip explaining what a job actually looks like. A proof strip with real Google rating, real industry memberships, and named past project niches where consent allows. A clear CTA back to the quote form, contact, or pricing page.

What to avoid. About pages that read like a corporate annual report for a two-person business. Stock-photo "team in hard hats". Service lists that include every tangentially-related skill instead of the four or five things the business actually wants to be hired for. Process strips with five steps that all say "consultation".

For the deeper service-business umbrella, see our service business website examples pillar, with niche reads for tradies, builders, and roofers.

Ecommerce About pages prioritise the brand mission, the product origin, the quality standards, and the trust around shipping, returns, and customer service. The visitor wants to know whether the brand stands behind the product and whether their money is safe.

Sections that earn their place. A short brand story paragraph naming the founders or the founding team and the reason the brand exists. A product origin block (where it's made, how it's made, who makes it). A quality or standards block where claims are real and verifiable. A short photo strip showing real product, real workshop, real warehouse, or real fulfilment, not staged "brand lifestyle". A trust block linking to shipping, returns, contact, and reviews. A clear CTA back to the product range or a featured collection.

What to avoid. Vague "founded in pursuit of excellence" intros. Origin stories that read like marketing fan-fiction. "Hand-crafted in our workshop" claims for a dropshipped product. Sustainability claims with no specific source or certification. Long brand manifestos that bury the product entirely.

For the broader ecommerce umbrella, see our ecommerce website design examples.

SaaS About pages prioritise the company mission, the product problem, the team credibility, and the security or support trust signals that enterprise buyers screen for. The visitor wants to know who is building the product, why, and whether the company is still going to be there in two years.

Sections that earn their place. A short company paragraph naming what the product does and who it does it for. A "why we built it" paragraph explaining the real problem the team set out to solve. A leadership or founder strip with real names, real roles, and real photos where consent allows. A short credibility or backing block (named investors where genuine, named customer niches where consent allows, real industry memberships). A trust block linking to security, status page, support, and changelog. A clear CTA back to demo, signup, pricing, or contact.

What to avoid. Vague "we are reimagining the future of work" intros. Leadership grids of unnamed "senior team" members. Customer logo strips lifted from logos.dev without consent. Founder paragraphs that are the same sentence five times with different verbs. Any "trusted by 10,000+ teams" line that the company cannot defend in writing.

For the broader SaaS umbrella, see our SaaS website design examples.

Local business About pages prioritise local roots, the team, community involvement, location, and the service values that make the business worth crossing town for. The visitor wants to know whether the business is real, nearby, and a good fit for their local life.

Sections that earn their place. A short owner or family paragraph with a real photo of the people who actually run the place. A "where we are" block with address, hours, and a real photo of the premises. A community block naming local sponsorships, memberships, or partnerships honestly. A team grid for any customer-facing staff. A trust strip with real Google rating, real review count where genuine, and real industry memberships. A clear CTA back to booking, contact, or the menu / service list.

What to avoid. Stock-photo storefronts that look nothing like the actual premises. "Since 1973" claims without anything specific to back the year. "Family-run for three generations" with no named family members. Vague "we love our community" copy that names no local club, school, or charity. Inflated review counts.

For the broader local hospitality and retail patterns, see our restaurant examples, cafe examples, bakery examples, and florist examples.

Professional service About pages prioritise credentials, process, expertise, and careful proof. The visitor is often researching a decision with real money or real consequences attached, and the page has to make trust feel earned, not advertised.

Sections that earn their place. A short firm paragraph naming the practice area, who it serves, and roughly how long it has been operating. A partner or senior team block with real names, real roles, real qualifications, and real photos shot in a consistent style. A process block explaining what a typical matter or engagement looks like, in plain language. A credibility strip with real industry memberships, real certifications, and real industry-body listings where current. A trust strip linking to terms, privacy, and a careful proof block (named matter types where consent allows, never client identities without explicit consent). A clear CTA back to contact, booking, or pricing.

What to avoid. "Award-winning" with no named award, year, or issuer. "Decades of combined experience" used to mask a small team. Generic stock-photo gavels, columns, or stethoscopes. Process blocks that promise outcomes the practice cannot legally guarantee.

For niche-specific professional patterns, see our law firm examples, accountant examples, clinic examples, and dental examples.

The story section is the part of the About page that most businesses fluff. It should sound like a person wrote it, not a brand consultant. The strongest story sections name a specific year, a specific moment, a specific problem the founder ran into, and a specific decision that led to the business existing.

What works. First-person voice for founder-led businesses. Third-person voice for larger teams. A specific date or year. A short anchoring story (one or two sentences) rather than a sprawling autobiography. A "what changed" line tying the founding moment to what the business does now. A natural transition into services or product.

What to avoid. "Founded in pursuit of excellence" intros. Anything that starts with "In today's fast-paced world". Story sections longer than three short paragraphs. Phrases like "we don't just X, we Y" that flag a page generated by a tool rather than written by an operator. For the deeper anti-AI-slop rules, the what makes a website convert guide has the broader tone rules.

Values blocks are useful when they describe how the business actually behaves, not how it would like to be perceived. The strongest values blocks pair each value with a specific behaviour the business commits to, in plain language.

What works. Three to five values, named in short, plain phrases. A one-sentence behaviour pinned to each value, naming a concrete thing the business does or refuses to do. Values that match the rest of the site (a "fast" value matched by a real turnaround commitment elsewhere, a "honest" value matched by visible pricing). Values written in the same voice as the rest of the About page.

What to avoid. Generic "Integrity. Excellence. Innovation." stacks. Values with no matching behaviour. Eleven values on one page. Values written in a different voice from the rest of the site, lifted from a brand-guidelines slide. Anything that reads like it was generated from a "values for a small business" prompt.

The team and credibility block carries most of the trust weight on an About page. It works hardest when the photos are real, the names match the roles, and the credibility signals near them are verifiable.

What works. A consistent photo style across the team (same crop, same background, same light). Real names and real roles. Short bio lines (one or two sentences) for senior or customer-facing team members. A credibility strip near the grid: real industry memberships, real certifications, real Google rating, real named past employers or clients where consent allows. Where the team is small or solo, a single founder photo plus a single workshop or service-area photo usually does the job.

What to avoid. AI-generated faces. Stock-photo "diverse smiling team" grids. Unnamed roles. "Senior Specialist" titles that mean nothing. Credibility strips with logos that the business does not have permission to use. Memberships that have lapsed. Star ratings that include reviews from a different business.

For the broader trust-and-proof layer, see our website trust signals examples pillar.

The proof strip on an About page is shorter than the proof strip on a homepage, and it sits closer to the team grid and the CTA. The visitor uses it as a final sanity check before clicking through to contact or services.

What works. A real Google rating block with the real review count, where the count is genuine. Real named clients or client niches with explicit consent. Real industry memberships where current. Real awards with named issuer, year, and award name. Real press mentions with a link and a date. A short, real client quote with a named person, role, and business, only with consent in writing.

What to avoid. Logo strips lifted from public-logo libraries without consent. "Featured in" strips with vague "industry publications" claims. Inflated review counts. Awards with no issuer. Anonymous "client X" quotes. Anything that would not survive a buyer copying the line into Google.

About-page claims are also where consumer-protection regulators tend to look first when a complaint lands. In New Zealand, the Commerce Commission's misleading-claims guidance applies to About-page copy as much as it does to ad copy. Similar rules sit under the ACCC in Australia, the ASA + CAP codes in the UK, and the FTC's truth-in-advertising rules in the US. None of this is legal advice, just a flag that About-page claims should be defensible, not aspirational.

About pages are read by visitors who are still deciding. The CTA at the bottom of the page should match that mood. It is the wrong place for a hard "Buy now" push and the right place for an easy next step that fits the trust the page just earned.

What works. A primary CTA back to the most useful next step (services, audit, booking, quote, demo, pricing). A secondary CTA back to a softer entry (contact, FAQ, work portfolio). A short reassurance line under the buttons confirming response speed or "no call required" where true. Mobile-thumb-sized buttons.

What to avoid. Three different CTAs that all compete for the same click. "Submit" buttons. CTAs that lead to pages that 404. Pop-ups firing on an About page where the visitor is mid-read. For the deeper CTA pattern library, see our website call-to-action examples, and for the pricing-page connection see our pricing page examples.

The most common About page failures are the same on a $200 freelance site and a $40,000 agency build. Different production budgets, same buyer-trust mistakes.

Each of these is fixable in a single sprint. The shortcut is to write the About page assuming the visitor will reverse-image search every photo, Google every claim, and screenshot every quote before sending the first message. A page built for that visitor never has to be rewritten when regulators tighten the rules.

Onyxarro briefs an About page off the same checklist regardless of niche. Real story, real team, real values, real proof, real CTA. Where a real client is on the page, it is on the page with explicit consent. Where a result is named, it is named only when there is something honest to point at. Where there is no team, we do not invent one.

Onyxarro can use concept-style examples to show the thinking clearly, but they should be labelled honestly as design examples, not presented as real client results. We will happily ship a concept story section, a concept values block, a concept team grid, a concept process strip, a concept proof bar, or a concept CTA pattern for any niche on this list. Concepts are useful for showing how an About page should feel; they are not a stand-in for the real business's story, real team, or real proof.

The 48-hour delivery is a workflow choice, not a quality compromise. The structural piece (story, team grid, values, proof strip, process block, CTA) is fast once the brief is honest. Most of the time in an About page rebuild goes into the conversations needed to write a story that sounds like a person actually said it.

If you want a redesigned About-page preview against your real site, the free 48-hour website audit ships a written read plus a public preview link. You can also browse past work for examples of finished pages, or read the website homepage examples pillar for the upstream front-door pattern that feeds the About click.

A practical operator checklist for anyone briefing or sweeping an About page. Tick what's working; everything still unticked is a candidate for the next sprint.

If more than four lines stay unticked, the About page is a rebuild candidate, not a polish job. The free 48-hour audit runs this checklist on your live site and ships a written read alongside a redesigned About-page preview.

The About page pillar connects to every other conversion-trust page on the site. Pick the closest pattern or niche for the deeper read:

• Website homepage examples: cross-niche front-door pattern library.
• Website trust signals examples: cross-niche proof and credibility layer.
• Website call-to-action examples: cross-niche CTA pattern library.
• Contact page examples: cross-niche enquiry, booking, and trust patterns.
• Pricing page examples: cross-niche pricing and packaging patterns.
• Booking page examples: cross-niche appointment, consultation, quote, demo, and reservation pattern library.
• Website navigation examples: cross-niche header, footer, mobile menu, and nav CTA pattern library that carries About into every page.
• Service business website examples: cross-niche service-business umbrella.
• What makes a website convert: the upstream design-decision layer.
• Ecommerce website design examples: ecommerce brand, product, and trust patterns.
• SaaS website design examples: SaaS company, product, and credibility patterns.
• Tradie website design examples: trades founder and proof patterns.
• Accountant website design examples: accountant team and credibility patterns.
• Law firm website design examples: legal team and process patterns.
• Clinic website design examples: clinic team and booking patterns.
• Restaurant website design examples: local hospitality brand patterns.
• Photographer website design examples: creative service About patterns.
• Beauty salon website design examples: beauty team and booking patterns.