Market Entry: Choose a Wedge That Can Earn Expansion

A product can solve a real problem for a large market and still have no credible first customer.

The people with the greatest need may be difficult to reach. The easiest buyers may require integrations the team cannot support. A willing design partner may accept manual help that conceals an unrepeatable product.

Market entry fails when the addressable market is mistaken for an executable starting point.

The product decision is to choose a wedge: a narrow combination of customer, situation, route, product boundary, and service promise that can earn evidence before the company broadens.

Keep entry separate from analysis, segmentation, and launch

Market analysis describes the wider system: customers, substitutes, competitors, regulation, economics, and change.

Segmentation creates useful groups for a particular decision.

Market entry chooses which group and situation the product will serve first, through which route, with which adoption burden and deliberate exclusions.

Launch execution coordinates exposure, communication, readiness, and operations after that choice.

Market Analysis for Product Managers owns the wider diagnosis. Market Segmentation owns the grouping logic.

Entry begins when the team must commit to one reachable path rather than keep every plausible segment alive.

Write the wedge as a testable claim

“Enter the mid-market” is not a wedge. It names a revenue band, not a buying and adoption system.

Use this form:

For a defined customer in a recurring situation,
reached through a named route,
we will replace a specific current behaviour
with a bounded product and service promise.
They can reach first value after these adoption steps.
This evidence would justify another commitment.
These conditions would narrow or stop the entry.

The wedge must expose exclusions. A product cannot learn cleanly from a first market if every sale creates a different workflow, integration, policy, and service model.

An exclusion is not a claim that another segment lacks value. It protects the coherence of the entry test.

Select the beachhead through four constraints

Bill Aulet’s Disciplined Entrepreneurship presents beachhead selection as part of a structured practitioner process.

It is an authored operating method, not an empirical finding that one beachhead framework predicts venture success.

Use four questions to challenge the first segment.

Urgency

How costly, frequent, or time-sensitive is the current problem for this group?

Urgency should appear in behaviour: budget already spent, workarounds maintained, deadlines missed, risk carried, or repeated attempts to solve the problem.

Verbal enthusiasm is weak evidence when nothing changes after the conversation.

Reachability

Can the team repeatedly identify, contact, qualify, and support suitable customers through an affordable route?

Reachability includes channel access, sales cycle, procurement, geography, language, trust, and the evidence required to begin a serious evaluation.

A segment found through a founder’s personal network may be reachable once and unreachable as a market.

Adoption feasibility

Can the customer cross the full distance from interest to operation with the product, integrations, authority, skills, and service capacity currently available?

This question often eliminates an attractive segment whose need is real but whose implementation burden exceeds the entry system.

Learning value

Will evidence from this wedge reduce uncertainty about the intended product and a plausible expansion path?

A bespoke customer may produce revenue while teaching little about a shared product. A tiny segment may teach quickly but create no credible route beyond itself.

Do not collapse the four questions into a score. A high average can hide one fatal constraint.

Price the complete switching burden

The incumbent is not only another product. It is the customer’s current arrangement of tools, people, habits, data, contracts, approvals, and accepted failure.

Burnham, Frels, and Mahajan developed a consumer switching-cost typology covering procedural, financial, and relational costs.

Their 2003 study concerns consumer perceptions and intention to stay with service providers. It does not measure B2B implementation or prove how a software buyer will behave.

The categories still prompt a better entry ledger.

Procedural burden

• search and evaluation;
• security, legal, or procurement review;
• data preparation and migration;
• integration and configuration;
• training and workflow change;
• parallel operation and verification;
• exception handling and support.

Financial burden

• purchase and implementation cost;
• remaining incumbent commitment;
• lost productivity during transition;
• specialist or partner cost;
• failure and recovery exposure;
• ongoing service and operating cost.

Relational and political burden

• trusted provider relationships;
• reputation of the internal sponsor;
• changed ownership between teams;
• loss of familiar expertise;
• explanation required when the switch fails.

Add the product team’s burden as well. Record onboarding time, custom work, support, data handling, account management, compliance, and operational exceptions.

A wedge is not viable when customers reach value only because the team supplies labour the business model cannot sustain.

Let the entry motion change the product

Product-led entry needs an individual or team to discover, try, and reach value with limited assistance. Eligibility, time to value, collaboration, and upgrade boundaries become product decisions.

Sales-led entry can support a longer evaluation, but the product must survive buyer-user separation, security review, contracting, implementation, and evidence promised during the sale.

A regulated entry may require qualified review, auditability, data boundaries, documented controls, and a narrower release before value evidence is even admissible.

A marketplace must create sufficient value on both sides in one bounded context. Adding demand without suitable supply, or supply without viable demand, does not prove entry.

A services-assisted motion can be responsible when service work is explicit, priced, and designed to reveal what should become product capability.

The motion is part of the product strategy because it changes identity, permissions, onboarding, evidence, support, and economics.

Go-to-Market Strategy covers the broader route by which a selected market discovers, adopts, and receives the product’s value.

Build a proof ladder before scaling exposure

Rogers synthesises diffusion research around perceived relative advantage, compatibility, complexity, trialability, and observability.

The framework spans many innovations and contexts. It is not a predictive formula for a particular software market or channel.

Use a proof ladder that earns one commitment at a time.

Problem proof

The defined group repeatedly encounters the problem in the intended situation. Current workarounds, consequences, and decision authority are observed rather than inferred from a broad trend.

Access proof

The team can find and engage suitable prospects through a route that could continue beyond personal introductions.

Adoption proof

A customer can complete the required approvals, migration, configuration, training, and workflow change within the stated product and service boundary.

Value proof

The customer reaches the promised result, and the evidence distinguishes delivered value from implementation activity or contractual commitment.

Repeatability proof

Another suitable customer can move through a comparable path without the team quietly inventing a new product or service model.

Expansion proof

The adjacent segment shares enough need, route, product capability, and operating model that broadening is a testable extension rather than a fresh entry.

The ladder is an editorial operating model. GOV.UK’s private-to-public beta guidance is one official example of increasing exposure as service evidence and operating readiness improve.

Its public-service assessment context does not validate this commercial market-entry sequence.

Decide what evidence changes the wedge

Set triggers before a large opportunity arrives.

Narrow when urgency concentrates in one workflow, a route reaches only one subgroup, or adoption succeeds only under a tighter product boundary.

Stop when the problem does not produce changed behaviour, suitable customers remain unreachable, implementation exceeds capacity, or value depends on obligations the team will not accept.

Expand when customers reach value through a repeatable route, service burden remains inside the model, and the adjacent segment preserves the mechanism that made the wedge work.

Hold when evidence is promising but has not matured at the natural buying or usage cadence.

Do not treat one contract as repeatability. Do not treat a paid pilot as retained value. Do not treat an inbound lead as a reachable segment.

Record the competing explanation for every favourable signal.

Test a wedge without declaring a market

Consider a fictional product that helps regional food manufacturers collect supplier compliance documents. The choice is illustrative; nothing here shows that the market or wedge would succeed.

The broad market includes manufacturers, retailers, logistics providers, and certification firms. The team initially describes all of them as supply-chain compliance customers.

The wedge review finds different systems.

Retailers have strong urgency but lengthy procurement and integration. Small manufacturers are reachable but often lack a dedicated compliance owner. Regional manufacturers face recurring audits and already use manual document chasing.

The team chooses regional manufacturers preparing for recurring customer audits. It excludes live logistics monitoring and retailer-wide supplier networks.

The switching ledger exposes data migration, supplier invitations, permission setup, audit templates, and the sponsor’s risk if documents remain incomplete.

The proof ladder begins with observed document failures, then tests whether a compliance lead can invite a bounded supplier set and produce one reviewable audit pack.

Service time is recorded because manual document cleaning could make the product appear more capable than it is.

Expansion to retailers remains a hypothesis. It requires a different buying route and integration burden, so success in the wedge would not automatically justify it.

The exercise reduces the number of systems being tested at once. Commercial attractiveness would still need evidence.

Earn the right to broaden

A narrow entry is useful only when it can produce a clear decision.

Choose a segment with urgent work, a route the team can repeat, an adoption path the product can support, and evidence that matters beyond one convenient customer.

Price the customer’s switch and the company’s implementation burden. Stage proof from problem to repeatability. Define what narrows, stops, holds, or expands the commitment.

The first market is not a smaller version of the total market. It is the controlled product and operating system through which the company earns the right to make a larger claim.

Sources

• Burnham, Frels, and Mahajan: Consumer switching costs (2003 empirical consumer-services research developing procedural, financial, and relational cost categories; intention measures and consumer context do not establish B2B switching behaviour)
• Rogers: Diffusion of Innovations, 5th edition (broad research synthesis on innovation diffusion and perceived adoption attributes; not a forecast for one product, segment, or route)
• Aulet: Disciplined Entrepreneurship (first-party practitioner method that includes beachhead-market selection; not a controlled study of venture outcomes)
• GOV.UK Service Manual: How the beta phase works (official staged-exposure guidance for assessed UK public services; not a commercial market-entry model)

Read next

• Market Analysis for Product Managers
• Market Segmentation: Choose a Group for a Decision
• Go-to-Market Strategy: Design the Path to Value