A prospect lands on your homepage, spends eighteen seconds there, and leaves. Your page analytics say this scenario happened forty-seven times today. You’ve rewritten the copy twice. Hired someone to punch up the headlines. Every word is defensible. But those eighteen seconds keep ending the same way: exit, no demo request, no call-back booked, nothing.

The problem isn’t the clarity of your message. It’s the mismatch between what your homepage is explaining and what visitors need to understand.

---

The Conversion Problem Hiding in Plain Sight

Watch what happens in those eighteen seconds from the visitor’s perspective.

They Googled “support team can’t keep up” because their team lead is drowning and customers are angry. The search results land them on your homepage. The headline reads: “AI-Powered Customer Support Automation Platform.” The subhead explains your omnichannel routing and intelligent ticket categorization.

Nothing on the screen answers the question they came with: “How do I stop my team from drowning?”

Your homepage is explaining vendor differentiation – why your routing is smarter, how your automation works, what makes your approach different. Meanwhile, they’re trying to figure out if the chaos they’re dealing with can even be fixed. The jobs don’t match.

Eighteen seconds have ticked by, and they’re gone.

When Stages Don’t Match, Conversions Break

This mismatch happens because prospects move through stages of understanding between them realising they need help… and being ready to evaluate solutions. The early stages are when they’re naming the problem and searching for symptom relief. Later stages are when they’re comparing vendors and understanding technical differences. But your homepage speaks to the later stages, and most of your traffic arrives in the earlier ones.

This is the breaking point.

What determines what stage someone’s in? The situation they’re coming from. Someone who just lost a deal because they don’t have single sign-on (SSO) is in a different place than someone who’s spent three weeks researching identity management platforms.

Different situations create different jobs that need doing.

The first person needs to understand if adding SSO is possible. The second person needs to know why your SSO implementation is better than competitors.

This is what jobs-to-be-done research maps: people hire products to make progress out of specific situations, and the situation determines what job needs doing. When your homepage does one job (explaining vendor differentiation) but visitors need a different job done (understanding if their problem has a name) the conversion breaks.

Why Homepages Don’t Convert, Even When the Copy Is Clear

That job – the one visitors’ need doing when they land on your homepage – changes as they move from problem to solution.

This progression isn’t random. People don’t wake up one morning deciding to buy customer support software or identity management platforms. Something breaks first. Then they start searching. The searching follows a pattern that’s predictable enough that it has a name: the jobs-to-be-done journey.

Here’s how that journey maps to what someone’s searching for and what job they need done at each point.

The Four Stages from Problem to Purchase

Stage	What They’re Experiencing	What They Search For	Job They Need Done	Question They’re Asking
Stage 1: Problem Aware	Something’s broken, team is struggling, customers are complaining	Symptom language: “support team overwhelmed,” “too many tickets,” “customers waiting too long”	Validate the problem is real and shared by others	“Is this fixable or just how it is?”
Stage 2: Solution Aware	Problem has a pattern, others deal with this too, maybe solutions exist	Learning language: “how to handle support volume,” “scaling customer support,” “support team can’t keep up”	Understand if solutions exist and what they’re called	“What do other people do about this?”
Stage 3: Category Aware	Solutions exist in a category, need to understand options	Category language: “customer support automation,” “helpdesk software,” “support ticketing systems”	Learn what the category does and which type fits	“What kind of solution do I need?”
Stage 4: Vendor Evaluation	Ready to compare specific tools and make a buying decision	Vendor language: “Zendesk vs Intercom,” “[Product] pricing,” “[Product] reviews”	Evaluate which vendor solves it best	“Why this vendor over alternatives?”

 

The same pattern holds across different products and problems.

Someone whose API keeps timing out doesn’t search for “API observability platform.” They search “API randomly failing” or “request timeouts in production.” Someone losing customers because onboarding is confusing doesn’t Google “user onboarding automation tools.” They search “users don’t understand how to use product” or “high drop-off after signup.”

The search language used, reveals the stage – symptom searches mean Stage 1, category searches mean Stage 3 or 4.

Jobs-to-be-done research shows this happens because people hire solutions to make progress in specific situations. The situation – API failing, users confused, deployment breaking – creates the initial job. That job evolves as understanding grows, but it starts with the struggle, not the solution category.

Where Stage Distribution Actually Varies

However, not everyone enters their search (or your site) at Stage 1. Where your traffic lands, depends on three factors: buyer sophistication, your company’s maturity, and how established your market category is.

1. Buyer sophistication shifts entry points

A Series B CTO who’s previously implemented authentication systems doesn’t Google “how to add SSO.” They search “CIAM platform comparison” or “Auth0 alternatives.” Because they’ve already done the work of understanding the category, they enter at Stage 3 or 4.

Contrast this to a first-time founder building their first SaaS product – they enter at Stage 1 because they’re encountering these problems for the first time.

2. Seller maturity changes traffic composition

Early-stage companies get more Stage 1-2 traffic because they’re found through symptom searches and word-of-mouth from other founders dealing with similar struggles.

Later-stage companies with category presence and brand awareness attract more Stage 3-4 traffic because people searching category terms find them in the results.

3. Market maturity determines category awareness

In established categories – CRM, project management, analytics – more buyers enter at Stage 3 because the category is well-known.

In newer or emerging categories – embedded Integration Platform as a Service (iPaaS), API observability, AI agent platforms – more buyers enter at Stage 1-2 because they don’t yet know these categories exist.

Gartner research on B2B buyer journeys has shown, that these three factors significantly impact stage distribution.

A developer tools company, selling to enterprise CTOs in a mature market, might see 60% of traffic at Stage 3-4.

Whereas an early-stage startup, creating a new category for technical founders, might see 70% at Stage 1-2.

The stages exist for both, but the distribution is completely different.

Why Most Homepages Misjudge Where Their Traffic Is

Similarly, the conversion problem isn’t that every homepage speaks to the wrong stage. It’s that most technical founders misjudge which stages their traffic comes from – and build messaging for the wrong distribution.

This misjudgement happens because everyone giving you feedback on your homepage is sophisticated. Your co-founder, early customers, design partners, and investors are all Stage 4+ in your category. When they say your homepage is clear, they mean it – for them – because they already understand the category language.

But they’re not representative of your inbound traffic.

The question isn’t whether your homepage is clear to sophisticated buyers. It’s whether it matches where your traffic enters – and whether you know where that stage should be.

Three factors determine your expected stage distribution:

1. Your company stage

Early-stage, bootstrap, or pre-Series A companies typically get more Stage 1-2 traffic. You’re found through symptom searches, founder communities, word-of-mouth from people dealing with similar struggles. Later-stage companies with category presence and significant marketing spend attract more Stage 3-4 traffic through brand searches and category terms.

2. Your target buyer

First-time founders, solo developers, or teams encountering a problem for the first time enter at Stage 1-2. They’re learning the problem exists and has a name. Experienced CTOs, enterprise buyers, or repeat buyers in your category enter at Stage 3-4. They’ve seen this problem before and know what to search for.

3. Your market maturity

Established categories with widespread awareness (CRM, analytics, helpdesk) pull more Stage 3-4 traffic because buyers know these categories exist. Emerging or newly created categories (embedded iPaaS, API observability, agentic workflows) get more Stage 1-2 traffic because buyers don’t yet know the category language.

In short:

An early-stage company creating a new category for first-time founders should expect 70% Stage 1-2 traffic.

A Series B company in an established category selling to enterprise should expect 60% Stage 3-4 traffic.

Same four stages, completely different distributions.

Most technical founders assume their traffic is more sophisticated than it is.

You remember the sophisticated early customers who found you and validated the product. You forget about the hundred visitors who bounced because they landed at Stage 1 and your homepage spoke Stage 4. This misjudgement skews toward overestimating your sophistication – which means homepages end up optimised for the smaller, later-stage segment while missing the larger, earlier-stage pool.

Before you can fix where and who your homepage speaks to, you need to know where your traffic should be entering, based on who you are, who you’re selling to, and how established your category is.

The Two Ways Homepage Messaging Mismatches Your Actual Audience

If your homepage isn’t converting, it usually means one of two things: you’re speaking to buyers more sophisticated than the ones finding you, or you’re speaking to buyers less sophisticated than the ones you’re trying to attract.

Both kill conversions. Just in different ways.

Here are two fictional examples that show how the mismatch happens in both directions.

Example 1: Built for Stage 4, Getting Stage 1 Traffic

The Company:

DevFlow is an 8-person, bootstrap-funded developer tool that helps engineering teams track technical debt. They’re 18 months old, creating a new category (in this world, technical debt tracking isn’t as established as project management or code review tools), and are selling to first-time engineering managers at Series A startups – people managing a team for the first time and struggling with accumulated code problems.

Who They Should Expect:

Based on their company stage (early, bootstrap), market maturity (emerging category), and target buyer (first-time managers), they should expect 70-80% of traffic at Stage 1-2. Their buyers are encountering this problem for the first time, don’t know “technical debt tracking” is a category, and are Googling symptoms: “codebase getting messy,” “refactoring taking too long,” “old code slowing us down.”

What Their Homepage Says:

Headline: “Enterprise Technical Debt Intelligence Platform”

Subhead: “ML-powered tech debt analysis and automated refactoring recommendations”

First section: Explains their proprietary debt scoring algorithm, compares their approach to “manual debt tracking spreadsheets,” and lists integrations with GitHub, GitLab, Bitbucket.

The Mismatch:

Their homepage speaks to someone who already knows technical debt tracking is a thing, understands they need a platform for it, and is evaluating vendors. Stage 4 language is being used: “enterprise platform,” “quantify and prioritize,” “ML-powered analysis.”

But their actual traffic – first-time engineering managers Googling “codebase getting messy” – land on the page and see words that don’t yet mean anything to them. They don’t know “technical debt” is the term for what they’re experiencing. They don’t know platforms exist to track it. They’re at “something is wrong, and I don’t know what to call it.” However, their current homepage is miles ahead, at “here’s why our debt quantification approach is better than alternatives.”

The Result:

Stage 1-2 traffic (their majority) bounces because they can’t recognise their problem in the language that’s being used. The small amount of Stage 4 traffic that does convert, tends to be sophisticated enterprise buyers – exactly the opposite of their bootstrap pricing and first-time manager target audience. They’re attracting the wrong sliver while losing the right-fit majority.

Example 2: Built for Stage 1, Trying to Attract Stage 4

The Company:

SupportHQ is a customer support platform that’s been around for 6 years. They started by serving solo founders and small teams with simple ticketing. They’re now Series B, trying to move upmarket into mid-market and enterprise accounts. They need deals that close at $50K+ instead of $500/month. Their target buyer has shifted from solo founders figuring out support for the first time to experienced support directors comparing enterprise platforms.

Who They Want to Attract:

Based on their growth goals (move upmarket, raise Series C), they should be attracting Stage 3-4 traffic: experienced buyers who know the support platform category, understand enterprise requirements, and are evaluating vendors. These buyers Google: “enterprise helpdesk comparison,” “Zendesk alternatives for mid-market,” “support platform with advanced routing.”

What Their Homepage Says:

Headline: “Customer Support Doesn’t Have to Be Overwhelming”

Subhead: “Simple support ticketing for small teams just getting started”

First section: Walks through the experience of getting your first support email, not knowing how to organise responses, and feeling overwhelmed. It emphasises “simple setup,” “no complicated features,” and “affordable for startups.”

The Mismatch:

Their current homepage speaks to Stage 1 buyers – solo founders encountering support challenges for the first time, who aren’t sure what tools exist, they’re Googling symptom language like “how to organise customer emails.” This messaging worked beautifully when that was their audience.

But now, they’re trying to attract experienced support directors at companies with 50+ person support teams. These buyers land on the homepage, see “simple for small teams just getting started,” and immediately assume SupportHQ can’t handle their scale. The language signals the wrong level of buyer sophistication.

The Result:

They keep attracting Stage 1 traffic – solo founders, early startups, small teams. These buyers convert easily because the message matches perfectly. But they’re $500/month deals that churn when they outgrow the “simple” positioning.

Meanwhile, the Stage 4 enterprise buyers they’re trying to attract, take one look at “doesn’t have to be overwhelming” and assume this product isn’t built for their complexity. The homepage is optimsed for the audience they’re trying to move away from, not the audience they’re trying to reach.

The Pattern in Both Directions

DevFlow’s homepage speaks too late in the journey for their actual traffic. SupportHQ’s homepage speaks too early for the traffic they want to attract.

Neither homepage has unclear copy. The words are well-written.

The problem is strategic: the message doesn’t match the sophistication level of the target audience, based on what the company is trying to accomplish.

Before you can fix where your homepage speaks, you need to answer: based on your company stage, your market maturity, and who you’re deliberately trying to reach – where should your traffic be entering? Then: does your current homepage match that, or is it speaking to a different stage entirely?

The mismatch is the conversion killer. Not the quality of your writing.

What Matching Your Message to Your Audience Looks Like

The difference between a homepage that converts and one that doesn’t, often comes down to one question: who are you building for right now, and does your messaging match their stage?

Let’s use DevFlow again, the technical debt tracking tool from the previous example, and show how their homepage should progressively change as their company matures, and their target audience shifts. Same product. Same core value. Three completely different homepage messages, based on target buyer sophistication.

Version 1: DevFlow at Launch (Targeting Stage 1)

Company Context:

• • 8 months old, bootstrap funded, 6-person team
  • Creating new category (technical debt tracking isn’t established yet)
  • Target buyer: First-time engineering managers at Series A startups (10–30-person eng teams)
  • Expected traffic: 75% Stage 1, 20% Stage 2, 5% Stage 3-4

Their Reality:

Most traffic comes from Google searches like “codebase getting messy,” “refactoring taking forever,” “old code slowing down development.” These managers are encountering technical debt problems for the first time. They don’t know “technical debt tracking” is a category. They’re just frustrated that their team is moving slower, and they don’t know why.

Hero Section:

Headline: Engineering Is Shipping Slower and You Don’t Know Why

Subhead: Features that took days now take weeks. Your codebase is fighting back.

Key Messaging Themes Down-Page:

• • The Situation They Recognise:

Simple features now require touching five different files. Bugs pop up in unexpected places. “This should be easy” takes three days instead of three hours.

• • What This Is:

Introduces the concept of technical debt – accumulated cost of past shortcuts and code that never got refactored. It names what they’re experiencing.

• • The Transformation:

From guessing what’s wrong to seeing exactly which parts of the codebase are slowing the team down. Strategic refactoring instead of random cleanup.

• • How It Works:

Connect GitHub ? See where debt is concentrated ? Prioritise what blocks progress ? Focus refactoring on what matters.

Why This Works for Stage 1:

• • The headline speaks directly to the symptom they’re Googling – “engineering shipping slower” – not to a solution category they don’t know exists yet.
  • The subhead validates their specific experience.
  • Down-page messaging educates them about technical debt without assuming they know the term.
  • The job being done: to help them understand if this frustrating pattern they’re experiencing is fixable and has a name. Only after they see themselves in the problem, does the solution get introduced.

Two years later, DevFlow has grown.

Version 2: DevFlow at 2.5 Years (Targeting Stage 3)

Company Context:

• • Series A funded, 25-person team, established product-market fit
  • Category has gained some recognition (technical debt tracking is becoming known)
  • Target buyer: Engineering leaders at Series B companies (50–150-person eng teams) who know they need technical debt tooling
  • Expected traffic: 25% Stage 1-2, 60% Stage 3, 15% Stage 4

Their Reality:

Most traffic comes from searches like “technical debt tracking tools,” “measure technical debt,” “codebase health monitoring.” These are engineering leaders who’ve encountered the problem before, know the category exists, and are trying to understand what solutions do and which type fits their needs.

Hero Section:

Headline: Technical Debt Tracking That Shows You What to Fix First

Subhead: See where your debt blocks velocity. Make data-driven refactoring decisions.

Key Messaging Themes Down-Page:

• • Category Education:

What technical debt tracking does – identifies, quantifies, and prioritises the parts of your codebase slowing you down. Objective data instead of gut feel.

• • The Effectiveness Principle:

Not all debt matters equally. Explains why impact-based tracking (complexity + change frequency) matters more than just complexity scoring.

• • How DevFlow’s Approach Works:

Analyses Git history to find hotspots, measures complexity in those areas, ranks debt by actual impact on shipping speed.

• • Who This Is For:

Engineering teams 30-200 developers, shipping daily, scaling fast enough that technical debt compounds quickly.

Why This Works for Stage 3:

• • The headline uses category language – “technical debt tracking” – because they’re actively searching for it.
  • The subhead speaks to the job they’re trying to accomplish: figure out what kind of debt tracking approach makes sense.
  • Down-page messaging educates them about what makes debt tracking effective (not all approaches are equal) and differentiates DevFlow’s methodology.
  • The job being done: to help them understand the category landscape and where DevFlow fits. They’re past “is this fixable?” and are at “what solution approach do I need?”

Another two years pass. DevFlow reaches Series B.

Version 3: DevFlow at Series B (Targeting Stage 4)

Company Context:

• • Series B funded, 80-person company, moving upmarket
  • Category is established (multiple competitors, analysts cover the space)
  • Target buyer: VP Engineering or CTO at mid-market to enterprise companies (200-1000 eng teams)
  • Expected traffic: 10% Stage 1-2, 25% Stage 3, 65% Stage 4

Their Reality:

Most traffic comes from searches like “technical debt platform comparison,” “DevFlow vs [Competitor],” “enterprise technical debt management.” These are senior engineering leaders who’ve been researching the category for weeks, have shortlisted 3-4 vendors, and are evaluating which platform best fits their organisational needs.

Hero Section:

Headline: The Technical Debt Platform Built for Engineering Organisations at Scale

Subhead: Impact-based prioritisation across hundreds of repos. Strategic technical investment decisions.

Key Messaging Themes Down-Page:

• • Immediate Differentiation:

Impact-based prioritisation vs. complexity-only scoring. Explains why their approach surfaces the debt that matters, not just the most complex code.

• • Organisational Scale Features:

Multi-repo visibility, portfolio view across teams, cross-team refactoring coordination, budget planning for technical debt allocation.

• • Enterprise Requirements Checklist:

SOC 2 Type II, SSO/SAML, RBAC, integrations with Jira/Linear/Asana, API for custom reporting.

• • Social Proof at Scale:

Customer logos with results – “Reduced feature lead time by 35%,” “Identified $2M in velocity savings,” specific numbers from companies at similar scale.

Why This Works for Stage 4:

• • The headline immediately positions against the category – “built for scale” – and the subhead differentiates from competitors in the first sentence. They’re comparing vendors, so leading with “impact-based” versus alternatives speaks directly to the evaluation they’re doing.
  • Down-page messaging addresses enterprise buying criteria upfront (security, integrations, scale) because that’s part of the vendor evaluation checklist. Social proof comes from similarly scaled companies with specific results.
  • The job being done: to help them decide if DevFlow is the right vendor choice versus the 2-3 other platforms they’re evaluating.

The Through-Line Across All Three Versions

Same product. Same core value proposition: help engineering teams identify and prioritise technical debt that’s blocking velocity. But they have three different homepages, at different times during their progressive growth, based on who DevFlow is trying to reach at each stage of their company maturity.

Version 1 meets Stage 1 buyers at the symptom.

It speaks to the frustration of shipping slower, validates their experience, educates them about what’s causing it, and shows the path out.

Version 2 meets Stage 3 buyers who know the category exists.

It explains what makes technical debt tracking effective, differentiates their methodology, and helps them understand if this approach fits their needs.

Version 3 meets Stage 4 buyers’ mid-evaluation.

It leads with differentiation, proves capability at enterprise scale, addresses buying criteria, and demonstrates their track record.

The conversion happens when your message matches where your actual target buyers are – not where you wish they were – and not where your most sophisticated early customers were, but where the buyers you’re built for right now enter the journey.

These three diagnostic questions show you where that occurs.

The Three Questions That Show You Where Your Traffic Is

You can’t fix your homepage messaging until you know where your traffic enters the journey. Most technical founders guess – and guess wrong. And as mentioned, this misjudgement usually skews toward assuming they’re more sophisticated than the brand/market/buyer reality.

Here are three questions that surface where your traffic is, not where you think it should be.

Question 1: What Search Terms Are Bringing People to Your Homepage?

Look at your Google Search Console data or your analytics platform. Pull the data on the actual search queries that land people on your homepage. Don’t look at what you optimised for – look at what’s driving traffic.

Separate the queries into buckets:

• Symptom searches (Stage 1):

“support team can’t keep up,” “codebase getting messy,” “deployments failing,” “users leaving app”

• Learning searches (Stage 2):

“how to scale customer support,” “what is technical debt,” “deployment automation options”

• Category searches (Stage 3):

“customer support automation tools,” “technical debt tracking software,” “infrastructure orchestration platforms”

• Vendor searches (Stage 4):

“[Your product] vs [Competitor],” “[Your product] pricing,” “[Your product] reviews”

What percentage of your traffic comes from each bucket? If 60% of your queries are symptom language and your homepage leads with category language, you’ve found the mismatch.

Search terms don’t lie. They show you exactly where people are, when they decide to look for help. Your homepage needs to speak to the language they’re using, not the language you wish they were using.

Question 2: What Do First-Call Sales Conversations Sound Like?

Go back through recordings or notes from your first sales calls with prospects – the initial conversation before they’ve learned your product language or gotten deep into evaluation mode.

Listen for how they describe their problem before you start explaining your solution. Write down their exact phrases:

• “We’re drowning in tickets and don’t know which ones matter”
• “Features that should be simple are taking forever”
• “We lost a deal because we don’t have SSO”
• “Deployments keep breaking and we can’t figure out why”

This is Stage 1-2 language – the job they’re trying to get done when they first reach out. If your homepage doesn’t use any of these phrases, you’re not speaking to the moment that pushed them to search for help.

Also listen for what they don’t say. If prospects aren’t using category terms in first calls – if they’re not saying “we need a CIAM solution” or “we’re evaluating iPaaS platforms” – that tells you they’re not at Stage 3-4 yet. Your homepage shouldn’t assume they are.

Question 3: Where Are Your Best Customers When They First Find You?

Look at your top 10-20 customers – the ones who are successful, stay long-term, and represent your ideal customer profile. Go back to how they found you. Not how they found you in the mechanical sense (organic search, referral, ad), but where they were in their journey.

Ask yourself or check your records:

• Were they searching for your product category, or searching for symptom relief?

If they Googled your category name, they were Stage 3+. If they Googled their problem, they were Stage 1-2.

• Did they know they needed your type of solution, or did you have to educate them about it?

If education was required, they entered early-stage.

• How long between their first touch and their first conversation?

If they reached out immediately after landing on your site, your homepage spoke to their stage. If they came back multiple times over weeks, they were doing the work of moving through stages on their own.

The pattern across your best customers shows you where your actual target buyers tend to enter. If most of your ideal customers were Stage 1-2 when they found you, but your homepage speaks to Stage 4, you’re creating friction for the people most likely to become great customers.

What These Questions Reveal

These three questions give you evidence about where your traffic is, not assumptions about where it should be. When search terms, first-call language, and best customer entry points all tell the same story – Stage 1-2 traffic finding a Stage 4 homepage, or Stage 4 traffic finding a Stage 1 homepage – you’ve found your conversion problem.

The fix for this, isn’t better copywriting. It’s matching your message to the job your actual traffic needs done when they land on your page.

The Job Your Homepage Needs to Do

When your homepage doesn’t convert, it isn’t necessarily a copywriting problem. It’s likely a jobs mismatch.

Prospects land on your homepage, and they’re trying to progress out of a specific situation or get a specific job done – like someone whose support team is drowning, has a different job to get done than someone comparing enterprise platforms.

Different stages = different jobs = different questions.

Remember, the homepage that’s perfectly clear to you and your co-founder, isn’t necessarily clear to the Stage 1 traffic searching for symptom relief. Match your message to the right stage – the job needing to be done when they land – and it’s more likely your homepage converts.

But… keep speaking to the wrong stage, and those eighteen seconds keep ending the same way: tab closed.