Your About Page Is Losing You Customers — Here's How to Fix It

By Jonathan · Founder, PageGains

The About page is one of the most visited pages on any SaaS site — and one of the most wasted. Visitors land there mid-consideration, when they're trying to decide whether to trust you enough to move forward. What do they usually find? A timeline of company milestones, a grid of headshots, and a mission statement that could belong to any company on the planet. That's not trust-building. That's a missed conversion opportunity dressed up as content.

Your Visitors Aren't There to Read Your Origin Story

When someone clicks "About," they're not looking for a founding mythology. They're running a checklist: Is this company legit? Are these people who get my problem? Are they going to disappear in six months? The faster your page answers those questions, the faster they move on to a demo or a signup.

Open your page with a positioning statement that names who you serve and what outcome you produce — not what you "believe" or "strive for." Something like: "We help B2B SaaS teams cut support ticket volume by automating the top 20% of questions their customers repeat." That one sentence tells a skeptical visitor more than three paragraphs of company values ever will. Lead with the customer's world, not yours. The founding story can come later, once you've earned the scroll.

The Mission Statement Problem (And What to Write Instead)

"We're on a mission to empower businesses to achieve their full potential." That line — or something nearly identical — appears on thousands of SaaS about pages. It says nothing, signals nothing, and reassures nobody.

Replace it with a problem statement. Describe the specific, painful situation your target customer was in before your product existed. Basecamp does this well — they don't say they believe in "better work." They describe the chaos of managing projects across email threads and missed deadlines, and position themselves as the alternative. That approach works because it demonstrates that you understand the problem at a granular level. Understanding equals credibility. Credibility equals trust. Write two or three sentences that describe the world before you existed, then one sentence about what you changed. That structure does more persuasive work than any mission statement.

Founders: Show Faces, Cite Credentials, Explain Why You

Anonymity kills trust in SaaS. If prospects can't figure out who built this thing, they get nervous — especially in categories with high switching costs or data sensitivity. Put the founders front and center with real photos (not illustrated avatars), names, and relevant credentials.

But go one step further: explain why this team, specifically, is the right one to solve this problem. "Former head of customer success at a 500-person SaaS company" is interesting. "Built the support workflow at Intercom before going independent to solve the same problem for smaller teams" is compelling. The "why us" angle — what makes your founders uniquely qualified to understand and fix this specific pain — is what separates a trustworthy about page from a generic one. Two or three sentences per founder, a real headshot, and a LinkedIn link is usually enough. Don't make it a full bio. Make it a reason to believe.

Social Proof Belongs on This Page Too — Not Just Your Homepage

Most SaaS teams dump all their social proof on the homepage and leave the About page bare. That's backwards. By the time someone hits your About page, they're in evaluation mode. That's exactly when third-party validation matters most.

Add a few customer quotes here — but choose ones that speak to trust and reliability, not just feature benefits. "We've been using this for three years and it's never let us down" hits differently on an About page than it does at the top of a homepage. If you have notable customers, name them. If you've been featured in relevant industry publications, a small logo row takes five minutes to add and signals legitimacy immediately. And if you have concrete numbers — customers served, uptime percentages, retention rates — put them here. "97% of customers renew after year one" tells a visitor more about your actual quality than any testimonial.

Address the Real Trust Blockers Directly

There are questions every SaaS prospect has but rarely asks out loud: What happens to my data? What if you shut down? Are you a one-person shop that'll go dark? Your About page is the right place to answer them, preemptively.

Add a short section on company stability. Mention funding status or revenue milestones if you can (even "profitable and independent since 2021" is reassuring to buyers tired of VC-backed tools pivoting). Link to your security page or SOC 2 certification if you have one. If you're a small team, don't hide it — instead, frame it as a feature: "We're a team of 11, which means you'll talk to a real engineer when something breaks, not a tier-1 support script." Acknowledging the concern directly and reframing it is far more effective than hoping visitors won't notice.

Use the About Page as a Soft CTA Moment

Most About pages have no call to action at all. Visitors who arrive curious leave with nowhere to go. Even a low-commitment CTA at the bottom of the page — "Want to see how it works? Watch a 4-minute demo" — captures people who are warming up but not ready to start a trial.

The key is matching the CTA friction level to where visitors are in the funnel. About page visitors are mid-funnel. They're not in "sign me up right now" mode. So don't push a hard free-trial button as your only exit option. Offer a demo video, a case study, a "see how [Company Type] uses us" page. Give them a next step that continues the trust-building process rather than jumping straight to commitment. One clear, low-pressure CTA at the page bottom is enough — but it has to be there.

The Page Structure That Actually Works

Here's the sequence that works across the About pages I've audited: open with a one-sentence positioning statement, follow with a problem/origin story (100–150 words max), introduce the founding team with credentials and a "why us" angle, add customer proof specific to reliability and longevity, address trust blockers directly, and close with a soft CTA.

Notice what's not in that structure: a company timeline, a list of core values, a culture section, or an awards shelf. Those elements aren't useless — they're just low priority. If you've nailed the six elements above, add them at the bottom for context. If you haven't, don't let them crowd out the things that actually move visitors. Length matters too. Most About pages benefit from being shorter than their owners want them to be. Aim for 400–600 words of copy. Tight, specific, and scannable beats long and comprehensive every time.

Check the Page Against This Fast Audit

Before you publish any revision, run it through these five questions: Does the first sentence name who you serve or what you do in concrete terms? Does the copy describe the customer's problem before it describes your company? Is there at least one named customer or concrete third-party proof point? Does a visitor know who built this and why they're credible? And is there a next step — any next step — for someone who finishes reading?

If you can't answer yes to all five in under 30 seconds of reading, the page needs work. Run this same audit on competitor About pages while you're at it. Most will fail on questions three and five, which means clearing that bar gives you a meaningful edge with prospects who are comparison-shopping.

The Bottom Line

Your About page isn't a formality. For a meaningful slice of your visitors — the ones in active evaluation, comparing you against two or three alternatives — it's a deciding factor. A page that builds real trust converts some of those fence-sitters. A page that talks about your core values and lists your office locations doesn't.

The fixes aren't complicated. Lead with the customer's problem, not your founding story. Put real faces and specific credentials on the page. Add social proof that speaks to reliability. Address the unspoken concerns before they become objections. And give visitors somewhere to go when they're done reading.

None of this requires a redesign. Most of it is a copy problem — which means you can test a meaningfully different version in an afternoon and have data within a couple of weeks. That's a fast experiment for a page that often sits unchanged for years while quietly failing the visitors who need it most.