The Symptom You Recognize
Your website looks fine. You're not embarrassed to send someone to it. The logo is clean, the colors are on brand, and the homepage doesn't look like it was built in 2009.
But nothing's happening.
No inquiries. No form fills. No moments where a prospect says "I found you on your site." Just a polished digital brochure sitting quietly on the internet, costing you hosting fees and doing exactly nothing for your business.
You've probably already run the blame loop. Maybe it's the copy. It never quite sounds like you. Maybe it's the design. It feels a little generic. Maybe it's the agency that built it. Maybe it's all three.
Here's the actual diagnosis: nobody defined what each page was supposed to do before building it.
Not the site overall. Each page. That's a different question, and almost nobody asks it.
The Step That Gets Skipped
There's a gap between "we need a website" and "let's build one." It doesn't look like a gap because the process keeps moving: kickoff calls, brand questionnaires, sitemap drafts, copy briefs, design concepts. Busy. Productive. Headed somewhere.
What's missing is the moment where someone stops and asks: what is this specific page's job?
Not "what do we want visitors to do." Not "what should this section communicate." The actual job. The reason this page exists in the hierarchy of your site. What a visitor needs to think, feel, or decide by the time they leave it. Whether this page is trying to earn an immediate action, build enough trust for a future action, answer a specific question, or help the visitor figure out whether they belong here at all.
That question determines everything downstream. The messaging approach. The content structure. The calls to action. The design hierarchy. Answer it clearly and every subsequent decision has a reference point. Skip it and you're making aesthetic choices on top of a structural void.
Why It Keeps Getting Skipped
Agencies are paid to execute. Deliverables have timelines. Clients have approval processes. Slowing down to interrogate intent before a single wireframe gets drawn takes time, costs money, and tends to make everyone impatient.
So the interrogation gets skipped. Intent gets assumed, baked silently into the brief, or borrowed wholesale from whatever framework the agency uses for every client. StoryBrand for everyone. Hero-features-CTA for everyone. Whatever's trending.
The result is a site built on assumed intent, which is another way of saying a site built on guesswork that nobody had to own.
Once the framework picks the template, the content gets written to fill the template's slots. The "About" section gets written because the template has an "About" section. The "Our Process" block appears because every site in that framework has one. Whether those sections are the right tool for this specific page's actual job never comes up. Nobody asked.
This isn't a criticism of agencies. It's a structural problem. The incentives don't reward the pause. They reward the deliverable. So the pause disappears, and you end up with something that looks finished but doesn't function.
What Page Intent Actually Means
Page intent is the specific job a single page has to accomplish for a specific visitor at a specific moment. It's not a goal ("generate leads"). It's not a theme ("about our services"). It's a function.
There are four types.
Convert pages are asking for an immediate action. Contact forms, booking pages, checkout flows. The visitor is ready to move. The page's job is to make that movement frictionless and give them one final reason to follow through.
Convince pages are building trust for a future action. Services pages, about pages, case studies. The visitor isn't ready yet. The page's job is to eliminate doubt, establish credibility, and make the eventual yes feel inevitable.
Answer pages are solving a specific question. Blog posts, FAQs, resource content. The visitor arrived with something they needed to understand. The page's job is to answer clearly and position you as the source worth returning to.
Qualify pages help visitors decide whether they belong. They're doing the self-selection work so your sales conversation isn't spent figuring out fit. Done well, they attract the right clients and quietly discourage the wrong ones before anyone's wasted an hour on a discovery call.
Most underperforming websites have the same problem: pages trying to serve two or three of these intents simultaneously, serving none of them well. A homepage that's trying to convert, convince, and qualify all at once ends up doing all three badly. Visitors don't know what to do. So they leave.
Each of these intents deserves its own treatment: the messaging approach, content structure, and design decisions that make it work. We'll get into each one in detail in the posts that follow.
What Changes When You Get This Right
When intent is defined before anything else, every downstream decision becomes answerable.
Should this section lead with a case study or a process explanation? Depends on the intent. Should this CTA say "Let's talk" or "See how it works"? Depends on the intent. Should this page be long or short? Depends on the intent. How much trust does the visitor need to have before this page asks them to do something? Depends on the intent.
You stop making decisions by preference or trend or "this looked good on a site I liked." You make them against a defined purpose. That's not a small shift. It's the difference between a site that looks good and a site that does something.
It's also what makes the work scalable beyond a single person's instincts. When intent is documented, any copywriter, designer, or developer working on the site has a reference point that isn't "I think it should feel warmer" or "the client wants more color." The page has a job. Does this decision serve that job?
Where to Go From Here
This is the foundation. Intent before everything else: before copy, before design, before any framework gets applied.
In the posts ahead, we'll break down each of the four intent types in detail: what they require, what they typically get wrong, and what the right messaging approach actually looks like for each one.
If you're looking at your own site right now and can't immediately answer "what is this page's job," that's the starting point. That's the gap.
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.
