Writing for 'Everyone in SaaS' Is Why Your Landing Page Converts Nobody

By Jonathan · Founder, PageGains

Most SaaS landing pages don't have a traffic problem. They have a "this could be for anyone" problem. When your headline appeals to every possible buyer, it resonates with none of them — and visitors who don't feel immediately spoken to don't scroll, don't click, and don't convert.

The Composite Persona Trap: When You Average Out All the Signal

Here's a scenario that plays out constantly: a SaaS team builds a persona called "Marketing Manager Mike" — 35 years old, mid-size B2B company, cares about pipeline. They write their landing page for Mike. The problem? Mike is a statistical average of six different real buyer types stitched together. He doesn't actually exist.

The copy ends up generic because the persona was generic. You get headlines like "Grow your business faster" because that's what you write when you're trying to not exclude anyone.

Real personas come from actual sales calls, not spreadsheets. Pull the last 20 won deals. What job title signed the contract? What problem did they describe in their own words during the first call? What almost made them not buy? That's persona data. A job title plus a demographic age is a costume, not a profile.

The fix: anchor your page to the single highest-converting customer segment you already have. You can build additional pages for other segments later. Start with the one who actually pays and stays.

The Job Title Isn't the Persona — The Situation Is

Two people with identical job titles can be in completely different buying situations. A VP of Marketing at a 12-person startup is not the same buyer as a VP of Marketing at a 400-person company with a dedicated RevOps team — even if your CRM lumps them together.

Situation-based targeting is more predictive than demographic targeting. Instead of writing for "VP of Marketing," write for "VP of Marketing who just took over a new role and needs to show pipeline impact in 90 days." That's a person with urgency, a specific fear, and a concrete deadline.

How does this change your page? Your headline shifts from "Marketing automation for growing teams" to something like "Hit your first-quarter pipeline number without adding headcount." One is about the product category. The other is about the reader's situation. The second one makes the right visitor feel seen.

Audit your current headline: does it describe your product, or does it describe the problem your best customers were in when they first found you? Those are very different sentences, and the second one converts better.

Trying to Address Every Use Case Above the Fold Kills the Page

It's tempting to front-load every possible use case. You sell to sales teams, marketing teams, and customer success — so you put all three in the hero section. Rotating text. Tabs. A headline with three slashes in it.

What the visitor sees: a page that hasn't decided what it's for.

Above the fold is not a brochure. It's a handshake. It needs to answer one question in under five seconds: "Is this for someone like me with a problem like mine?" If the answer requires the visitor to decode a switcher widget, you've already lost them.

Pick the primary persona for that page and write the hero exclusively for them. If you genuinely need to serve multiple segments, build separate landing pages with separate traffic sources. A sales-team-focused page from a LinkedIn ad campaign targeting SDRs will outperform a "we do everything for everyone" page almost every time. This isn't a theory — it's the consistent result across segmented campaign structures at every company we've audited.

Vague Pain Points Are Just as Bad as No Pain Points

"Save time." "Streamline your workflow." "Work smarter." These show up on the majority of SaaS landing pages, and they are the verbal equivalent of beige wallpaper. They're not wrong, exactly — but they're so diluted that they don't create any emotional response.

The reason pages fall back on vague pain points is the same reason they fall back on composite personas: someone tried to make the copy inclusive rather than resonant. If you're specific about the pain, some people will self-select out. That's the point.

Here's a reframe: "Stop losing deals because your proposal sat in someone's inbox for a week" is about a specific, humiliating, costly problem. It's about a specific person. It will not resonate with someone who doesn't send proposals — and that's fine. The person who does send proposals and has watched a deal die in email limbo will feel a jolt of recognition when they read it. That jolt is what drives scroll depth, and scroll depth drives conversions.

Find the sharpest version of your best customer's pain. Say it plainly. Don't sand off the edges to make it palatable to a wider audience.

Social Proof That Doesn't Match the Visitor's Persona Does More Harm Than Good

Most teams treat social proof as a box to check. Drop in a logo bar. Add a few testimonials. Done. But mismatched social proof can actively undermine trust.

If your target persona is a startup founder and your testimonials are all from enterprise procurement managers at Fortune 500 companies, you haven't reassured your visitor — you've made them wonder if your product is even for them. Same problem in reverse: targeting enterprise buyers with testimonials from three-person startups signals that you might not be ready for their scale.

Social proof needs to mirror the persona. That means the person giving the testimonial should have the same job title, company size, or situation as the person reading the page. When a visitor sees a quote from someone who looks like them, describing a problem they recognize, it short-circuits skepticism.

Segment your testimonials the same way you'd segment your pages. For a campaign targeting e-commerce brands, surface testimonials from e-commerce brands. Pull the quote that speaks to the specific outcome that segment cares about — not a generic "great product!" endorsement, but something like "We cut customer churn by 18% in the first quarter."

Feature Lists Written for the Product Team, Not the Buyer

There's a point in almost every SaaS landing page where the copy transitions from "here's your problem" to "here's our product" — and that's where a lot of pages fall apart. The features section reads like internal documentation. It lists capabilities in the order the engineering team shipped them, not in the order that matches what the buyer actually cares about.

Features aren't inherently persuasive. Outcomes are. "Automated follow-up sequences" is a feature. "Never let a warm lead go cold because you forgot to follow up" is the outcome that feature enables. The second framing is about the buyer's world, not your product's architecture.

Go through your features section and ask: for the specific persona this page is targeting, which three features solve the problem they came here with? Lead with those. Everything else can live in a secondary section or a docs page. A tightly persona-matched features section with three outcomes beats a comprehensive feature grid every time when it comes to moving someone toward a CTA click.

The Pricing Page Persona Mismatch Nobody Talks About

Here's where the persona problem often causes invisible damage: the pricing page. A visitor arrives qualified, interested, and ready to consider buying — then they hit a pricing page that clearly wasn't designed for them.

If your primary landing page targets a solo operator but your pricing table is structured around seat counts and enterprise tiers, you've created a jarring disconnect. The visitor went from "this is for me" to "wait, is this actually for teams of 50?" That confusion doesn't always produce a bounce. Sometimes it just produces a hesitation that kills the conversion a day later when the visitor never comes back.

Your pricing page should feel like a natural extension of the persona context you set on the landing page. If you drove a startup founder to a landing page promising quick setup and no IT required, your pricing page should reinforce that: name the plan they'd be on, use language that matches their scale, and make the first paid step feel like a natural next move for someone at their stage.

Persona consistency across the funnel — not just on the hero section — is where significant conversion gains hide.

The Bottom Line

Every section of your landing page is making a bet about who's reading it. The headline, the pain points, the testimonials, the pricing structure — all of it signals "this is or isn't for you." When those signals are diluted by trying to speak to every possible buyer, the page becomes a blur. Visitors don't feel addressed; they feel processed.

The single highest-leverage thing you can do for a SaaS landing page that isn't converting is to narrow the persona it's built for. Not slightly — meaningfully. Pick the buyer segment with the clearest pain, the most recognizable job situation, and the strongest outcome you can document. Build the entire page around that person. Every line of copy should be something that person would read and think, "yeah, that's exactly it."

You can always build more pages. Traffic segmentation, dedicated campaign pages, and persona-specific routes through your site are all scalable once the first version works. But you can't convert a visitor who never felt like the page was speaking to them in the first place. Start with one person. Make them feel seen. That's what converts.