In the last post, I introduced the four page intent types that make up Purpose-Driven Messaging: Convert, Convince, Answer, and Qualify. Each one has a specific job. Each one requires a different approach. And most underperforming websites have pages trying to do all four at once, which means they're doing none of them well.
This post is about Convince: what it actually means, which pages carry it, and what goes wrong when you treat it like something it's not.
What Convince Actually Means
Convince doesn't mean sell harder.
It means the visitor isn't ready to act yet, and your job isn't to push them. It's to make the eventual yes feel inevitable.
There's an important distinction there. A Convert page is talking to someone who's already decided. They just need the friction removed. A Convince page is talking to someone who's still evaluating. They have doubts. They're comparing. They're asking themselves whether you're the right fit, whether you're credible, whether the risk of hiring you is lower than the risk of hiring someone else.
The Convince page's job is to answer those doubts. Not by listing features, not by stacking testimonials, and definitely not by asking for the action before you've done the work. By building a case. Methodically. Without it feeling like a pitch.
Which Pages Carry This Intent
Services pages. About pages. Case studies. Process pages.
Basically: any page a visitor lands on when they're trying to decide whether you're the right choice. They know what they need. They're not sure you're the one to deliver it. That's the Convince moment.
Here's where it gets interesting. Most of these pages are built as if the visitor is already sold. They list the services. They describe the deliverables. They tell you who the team is and what awards they won. Then there's a button that says "Let's Talk."
That's not a Convince page. That's a brochure.
A brochure assumes the reader already trusts you. A Convince page earns that trust before it asks for anything.
What Convince Pages Get Wrong
Three patterns show up constantly.
Leading with features instead of fit. Your services page talks about what you do: the deliverables, the timeline, the tools you use. What it doesn't address is whether you understand the problem the visitor is actually trying to solve. Features are easy to list. Fit is harder to demonstrate. Fit is what builds trust.
Credibility signals that don't connect to the doubt. Logos. Testimonials. Years in business. These aren't bad, but on their own they're inert. A testimonial that says "Rebekah was great to work with!" doesn't resolve the specific hesitation a new visitor brings to the page. What were they afraid of before they hired you? What did they find out was different? That's the testimony that does work on a Convince page.
Treating Convince like Convert. This is the big one. Someone builds a services page, realizes it's not converting, and adds a more prominent CTA. Maybe a sticky button. Maybe a pop-up. More urgency. More ask.
The page wasn't failing because the ask wasn't loud enough. It was failing because the trust wasn't there yet. Adding more friction-forward pressure to a page that hasn't done the convincing work makes things worse, not better. Visitors feel pushed before they're ready, and they leave.
The Right Messaging Approach
Convince pages need two things working together: narrative and diagnostic.
Narrative means the page tells a story the visitor recognizes. Not your brand story. Their story. The situation they're in, the problem they've been trying to solve, the failed attempt they've probably already made. When a visitor reads a page and thinks "this is exactly what I've been dealing with," trust starts to build before you've said a single thing about yourself.
Diagnostic means the page demonstrates that you understand the problem at a level that earns credibility. Not "we've helped companies like yours grow." That's noise. Specific. Mechanistic. "Here's why the approach most agencies take doesn't work, and here's what has to be true for a website to actually function." That's diagnostic. It shows you know what you're doing without having to say "trust me."
Structured together, a Convince page moves like this: here's the situation you're in, here's why the approaches you've already tried haven't worked, here's what actually needs to happen, here's why we're the right ones to do it, here's what that looks like in practice.
That sequence builds trust incrementally. By the time the page asks for anything, the visitor has already answered their own doubts.
What This Looks Like on a Services Page
A services page is the most common Convince failure, so let's make it concrete.
Most services pages are organized around what the provider offers: Service A, Service B, Service C. There's a description of each, maybe a list of what's included, and a contact button. The assumption is that the visitor knows they need these services and is just confirming you offer them.
That assumption is usually wrong.
The visitor landed on your services page with a question underneath the surface question. The surface question is "what do you do?" The real question is "can I trust you to fix what's broken, and is the risk worth it?"
A services page built for Convince intent starts differently. It starts with the problem. Not your solution. The problem. It acknowledges what the visitor has probably already tried. It names the gap between what they expected and what they got. Then it explains how you approach the work differently, and why that difference matters.
The deliverables come later. The structure comes later. The "here's what's included" section belongs in the page, just not at the top, and not as the main event. Trust has to be established before the details land.
One Page, One Job
The most important thing about Convince pages isn't the tactics. It's the discipline of not asking for the action before the case is made.
That discipline is harder than it sounds because there's always pressure to get to the CTA. Put it above the fold. Make it sticky. Don't make them scroll too far before they see it.
But a visitor who hasn't been convinced yet doesn't need to see your contact form sooner. They need to be convinced. Give the page that job. Let it do the work. The action comes when the trust is there, and when it does, it converts without resistance.
Next up: the Convert page. What it takes to get out of your own way when someone is already ready to act.
Fibonacci Design Lab builds websites for established B2B service providers using the Purpose-Driven Messaging system, starting with page intent before anything else gets decided. Learn how it works.
