95% of visitors aren't in market

A B2B website has two jobs, and most teams only build for one of them. The first job is to convert the 5% of visitors who are ready to buy today. The second is to stay useful and memorable for the 95% who aren't in market yet, because the ones who do become buyers later will remember whether your site taught them something or just pushed a demo request at them. This article covers how to route, educate, and measure future buyers across your homepage, product page, and resource hub without forcing a signup they're not ready for.

Why the website for future buyers is a maintenance problem

The 5% obsession

Most B2B sites are built around the visitor who's ready to decide: a clear CTA above the fold, a demo request in the nav, pricing one click away. That setup is fine for the buyer who already knows they have the problem and are comparing solutions. It's a dead end for everyone else.

The problem isn't the CTA. It's that the rest of the site doesn't do much for anyone who isn't already halfway to buying. Future buyers land, see messaging aimed at someone further along than they are, and leave with nothing. No framing, no proof, no reason to come back. Forrester research on B2B buying consistently shows that buyers do most of their research on their own long before they contact a vendor. If your site only speaks to the last 10% of that journey, you're invisible for the 90% before it.

What changes when you optimize for the other 95%

The job shifts from "capture intent" to "build recall." A future buyer who visits your site today and leaves without converting isn't a lost lead. They're a future lead who will remember whether your site was worth their time. The metric that matters isn't conversion rate on that visit. It's whether they come back when the project becomes real.

That means the site needs to do three things for non-buyers: orient them, give them something worth remembering, and give them a reason to return. Maybe that's a framework. Maybe it's a benchmark. Maybe it's one sharp proof point they can actually use later.

The update loop is the real operating system

A site built for future buyers isn't a one-time launch asset. Positioning changes. The product ships new capabilities. The proof points that worked six months ago may not match the audience you're attracting now.

PostHog's SEO advice for startups makes a related point: the sites that compound over time aren't the ones with the most content. They're the ones that keep updating what they have based on what's actually working. The same logic applies to future-buyer pages. If a product page isn't pulling return visits, that's a signal to revise the framing, not to publish more. Publish, measure, learn, update. That's the loop.

How to separate in-market visitors from future buyers without forcing a form fill

Segment by intent signals, not by asking people to identify themselves

You don't need a gated assessment to know where a visitor is in their journey. Behavioral signals do most of the work:

• Pricing page visits — especially repeat visits or long time on page — signal active evaluation
• Product depth browsing — someone who reads three feature pages in a single session is further along than someone who bounced off the homepage
• Return visits within a short window — a visitor who comes back within two weeks is warming up
• Content depth — reading a long-form piece to the bottom, especially a comparison or use-case piece, suggests research mode rather than casual browsing

None of these require a form. They're readable from standard analytics. Vercel Web Analytics and tools like PostHog, Heap, or Amplitude all surface these patterns at the session level.

What anonymous intent scoring can and can't tell you

Anonymous behavioral data gives you enough signal to route content and prioritize follow-up. It doesn't give you a named account or a confident "this company is buying in Q2." The useful middle ground is to treat high-intent anonymous sessions as a reason to surface more proof and a softer next step, not as a trigger for a sales sequence.

A visitor who hit the pricing page twice and read a case study is worth showing a comparison guide or a customer story. They're not worth a "let's talk" popup that assumes they're ready to buy.

Where the site should branch once intent shows up

A simple routing model works better than a complex personalization stack:

• First visit, low engagement -> homepage and product pages do the orientation job; resource hub does the education job
• Return visit, content depth -> surface proof: case studies, benchmarks, specific use-case pages
• Pricing page + return visit -> make the next step low-friction: a short demo, a trial, a comparison guide, not a 30-minute discovery call

The branch doesn't require a CDP. It can be as simple as a sticky resource module that surfaces case studies once someone has read two blog posts, or a pricing page that links to a "how teams like yours use this" page instead of just a contact form.

What your homepage should do for non-buyers

The homepage's first job is orientation

A future buyer landing on your homepage for the first time doesn't know enough to evaluate you yet. They need to understand what you do, who it's for, and why it matters before they're ready to engage with a CTA. If the homepage leads with a value proposition that only makes sense to someone who already understands the category, you've lost the non-buyer in the first paragraph.

Orientation means a plain-language description of what the product does, a clear signal of who the customer is, and enough context to know whether this is worth reading further.

Give non-buyers one reason to keep going

Once orientation lands, the homepage needs one module that earns the scroll for a non-buyer:

• A customer proof point with a specific outcome ("reduced onboarding time by 40%"), not a generic logo wall
• A use-case section that names the problem before naming the product
• A benchmark or industry stat that makes the category feel important
• A clear path into deeper content, like "how it works for [role]" or "read how [company type] uses this"

The goal isn't to convert them on this visit. It's to give them one thing they'll remember when the buying context changes.

A homepage that changes with the product stays believable

Stale homepage messaging is one of the quietest trust killers in B2B. A future buyer who visited six months ago and comes back to find the same copy while the product has shipped three major features notices the gap. It signals that the site isn't maintained, which creates doubt about whether the company itself is moving.

Treat the homepage as a living document. When the product ships a significant change, the homepage should reflect it within a sprint. When a new customer segment starts converting at higher rates, the homepage messaging should shift toward that segment. The update cadence matters.

What your product page should do for future buyers

Product pages need proof, not just feature lists

A future buyer reading a product page isn't ready to evaluate features against a requirements doc. They're trying to understand whether the product solves a real problem for someone like them. A feature list doesn't answer that question. Proof does.

Proof means a customer story with a specific before and after, a screenshot or demo that shows the product doing the job, and a quantified outcome tied to a named company or role. The future buyer is building a mental model of "could this work for us," and they need evidence from someone in a similar situation, not a capability checklist.

Show the work the product does in the user's world

The most effective product pages connect capabilities to jobs. Not "real-time analytics dashboard" but "see which steps in your onboarding flow are losing users, so you can fix the one that costs you the most activations." The capability is the same. The framing is different. One describes the product; the other describes what the product makes possible in the buyer's actual workflow.

This framing also makes the product page more durable. Capabilities change, but the jobs buyers are trying to do change more slowly. A product page built around jobs needs fewer rewrites when the product ships a new version.

A good product page makes the next visit easier

Future buyers often visit a product page multiple times before deciding. Each revision should make the page easier to read for someone coming back after a first touch, which usually means adding proof, tightening the job framing, and removing anything that requires prior knowledge to parse. Linear's thinking on building competitive products applies here: the goal isn't the most impressive first version, it's the version that holds up under repeated scrutiny.

What your resource hub should do for non-buyers

Teach the problem before you pitch the product

The resource hub is where future buyers spend the most time, and where most B2B sites waste the opportunity. A hub full of product announcements and feature walkthroughs serves existing customers, not future ones. Future buyers need content that helps them understand the category, name the problem they're experiencing, and build the internal case for why it matters.

That means the hub should include category explainers that don't assume the reader already knows why the problem is important, comparison content that helps buyers understand the tradeoffs in the space, and use-case content that connects the problem to specific roles or industries.

Build a path from curiosity to confidence

The best resource hubs create a progression. A future buyer who lands on a top-of-funnel post about the problem should be able to find a middle-of-funnel piece about how companies solve it, then a proof-heavy piece about what results look like. That path doesn't require a gated nurture sequence. It requires internal linking and content at different depths on the same topic.

The failure mode is a hub where every piece is the same depth, or all of it is too close to the product, and there's no natural next step for a reader who wants to go further.

The hub should earn return visits

A future buyer who bookmarks a resource hub piece and comes back to it when the project becomes real is a high-quality lead. They already trust the content. That trust is built by being genuinely useful over time: publishing new content when the category evolves, updating old content when the advice changes, and covering the questions buyers actually have rather than the ones that are easiest to rank for.

A hub that earns return visits is one where the reader believes they'll find something new and useful next time they check. That's a maintenance commitment, not a content volume commitment.

---

FAQ

Q: What should a B2B website do for the 95% of visitors who are not ready to buy today?

Orient them, give them something worth remembering, and give them a reason to come back. The goal isn't conversion on the first visit. It's building enough recall and trust that when the buying context changes, your site is the one they return to. That means plain-language positioning, proof that resonates with their role, and content that helps them understand the category before they're ready to evaluate vendors.

Q: Which site experiences best educate and stay memorable without pushing a demo or signup?

Resource hub content that teaches the problem before pitching the product, product pages framed around jobs rather than feature lists, and homepage modules that surface specific proof points, like customer outcomes, benchmarks, and use cases, rather than generic value propositions. The common thread is content that gives the non-buyer something they can take away and use, even if they never convert.

Q: How should we segment future buyers versus current buyers on the website?

Use behavioral signals rather than form fills. Return visits, pricing page engagement, content depth, and time on page are reliable proxies for buying intent. First-time visitors with low engagement are in orientation mode; return visitors who've read multiple pieces are in research mode; visitors who've hit the pricing page more than once are in evaluation mode. Route content accordingly. More proof and softer next steps for the middle tier, a clearer conversion path for the high-intent tier.

Q: What content should a homepage, product page, and resource hub deliver to non-buyers?

Homepage: orientation, what it does and who it's for, plus one proof point or use-case module worth remembering. Product page: customer proof with specific outcomes, job-framed capability descriptions, and a clear picture of what the product does in the buyer's world. Resource hub: category education, comparison content, and a progression from introductory to proof-heavy depth, with internal links that let the reader go further without hitting a gate.

Q: How do we measure whether non-converting visitors are becoming more likely future buyers?

Track return visit rate, content depth, and assisted conversions, meaning visits that didn't convert immediately but appear in the attribution path of a later conversion. A rising return visit rate on non-converting sessions is a leading indicator that the site is building recall. Assisted conversion rate tells you whether those future buyers eventually came back to buy.

Q: What metrics should replace or complement conversion rate for future-demand audiences?

Return visit rate, content depth per session, time on page on educational content, and pipeline influence, meaning how many closed deals touched a non-converting visit earlier in the journey. Raw form fills measure the 5% who were ready today. These metrics measure whether you're building the pipeline that will convert over the next quarter.

Conclusion

The site isn't a conversion machine with a blog attached. It's a maintenance loop for future buyers. The 95% who aren't ready today will remember whether your homepage oriented them, whether your product page gave them real proof, and whether your resource hub taught them something worth coming back for. This week, audit all three. Change one thing on the homepage for someone who doesn't know your category yet. Update one product page section to lead with a customer outcome instead of a feature. Add one internal link in the resource hub that moves a reader from curiosity to proof. Those three changes are the operating system in practice.