Market structure

To build a go-to-market, you first need to see the market itself. Not as a monolithic block of “demand,” but as a negotiated space where supply meets demand, incumbents extract rent, and openings appear when the system breaks down. Market structure is the skeleton underneath all motion.

What controls your market: the diagnostic matrix

Before anything else, answer this sequence. Your answers determine what your GTM must overcome.

Supply concentration. How many sellers can reach the buyer? One, few, or many. Concentrated markets give the incumbent access control. Fragmented markets push control elsewhere: distribution, switching costs, or information asymmetry.

Distribution gatekeeping. Direct access to the buyer, or through an intermediary? Pharma companies cannot sell directly to hospitals; they work through wholesalers. SaaS companies can sell directly via the web. Distribution structure predicts your sales motion.

Switching costs. What does a buyer give up to leave? Retraining (Epic in hospitals), workflow integration (Excel macros), locked data (Salesforce), contracts (cloud infrastructure). High switching costs protect incumbents. Low switching costs mean you compete on product alone.

Information asymmetry. Who knows more: incumbent or buyer? Insurance companies know risk better than customers. Diagnostic labs know test accuracy better than patients. Asymmetry favors the incumbent. New entrants win by reducing it: transparency, data visibility, or signals incumbents ignore.

Ecosystem lock-in. Does buyer value depend on complementary products? Excel locks users in. Salesforce depends on integration. SAP depends on customizations. Ecosystem lock-in compounds switching costs. Breaking it requires building the alternative system, not just a better part.

Regulation. Does the incumbent benefit from regulatory moats? Banking regulations protect incumbents. Healthcare regulations lock in Epic. New regulation can destroy a moat (open banking). New entrants exploit regulatory blind spots until regulation catches up.

A market typically has two to three primary control points. Identify which ones protect your incumbent. Your opening will exploit the one they cannot defend without destroying their core business.

The same product, radically different market structures

A diagnostic test illustrates this perfectly. Hospital-owned labs and independent diagnostic labs sell the same test to the same patient population. Identical product. Opposite structures.

Hospital-owned labs. The hospital owns supply, controls ordering (through physician integration), handles billing directly, and captures all margin. A patient cannot choose another lab; their doctor’s order goes to the hospital’s lab. This is near-total vertical integration. The structure is monopolistic within the hospital. An independent lab entering this market must convince the hospital’s physicians to send their samples outside. This requires either changing the hospital’s economics (cheaper testing) or solving a need the hospital’s lab ignores (turnaround time for critical tests, specialized testing the hospital doesn’t offer). Most new labs cannot overcome this because hospital economics are defensive: the hospital’s lab is a cost center, not a profit center. Improving it is not the hospital’s priority.

Independent diagnostics labs. These labs compete for orders from physicians, who remain free to choose. The market is fragmented. There is no distribution gatekeeping (the physician is the buyer). Switching costs are low (the physician can send to Quest one month and LabCorp the next). Information asymmetry is low (price and turnaround are transparent). The structure is nearly perfect competition. Independent labs compete on price, turnaround, and convenience. Margins are thin. Innovation is slow because there is no structural protection for it.

Same test. One market has nearly total vertical integration and defensive incumbents. The other is fragmented and competitive. The GTM for a new lab looks completely different in each structure.

In the hospital market, you must solve a problem the hospital cannot solve internally (specialized testing, integration with rare workflows) or reshape the hospital’s economics (centralize lab costs across many hospitals). The direct-sales motion works only if you have unique value.

In the independent market, you must compete on operational excellence: fastest turnaround, lowest cost, easiest ordering. You are not breaking through a structural moat. You are out-executing competitors in a competitive structure. The GTM is distribution, sales force, and margins.

This is why market structure, not product, determines your GTM. The same innovation works brilliantly in one structure and dies silently in another.

What each control point means for your GTM

Supply concentration predicts your competitor. If concentrated, your GTM avoids competing head-to-head or serves buyers the incumbent ignores.

Distribution gatekeeping predicts your sales motion. If gatekeepers exist, you work through them or build downstream relationships. Stripe won by eliminating API friction processors ignored because bank relationships made developer experience irrelevant. This is the pattern: use the control point they cannot defend.

Switching costs predict penetration speed. Low switching costs mean product superiority and word-of-mouth work. High switching costs require cheaper switching (migration tools, training) or justifying the cost (savings exceed switching costs). You cannot ignore switching costs in your GTM.

Information asymmetry predicts where you gain advantage. Incumbents with asymmetric information can be disrupted by transparency. Insurtech companies win not by better underwriting, but by reducing asymmetry: transparency to customers or focus on segments where asymmetry is lower (self-employed know their own risk).

Ecosystem lock-in predicts whether you compete on part of the system or the whole. If ecosystem lock-in exists (Excel), competing on a single product is futile. You need the whole alternative system. Google Docs succeeded not because each piece was better, but because the whole system served new workflows with zero switching costs. Key insight: you are not competing with Microsoft Office. You are offering a different structural arrangement (cloud-first, always-on sync) for workflows where the incumbent’s moat does not exist.

Regulation predicts whether timing is your constraint. If the incumbent’s moat is regulatory, regulatory shift destroys it overnight. If your opening depends on regulation that hasn’t happened, your GTM must account for timing risk. Fintech companies operating in gray areas move fast until regulation clarifies and incumbents lobby it in their favor.

The founder mistake: structural opening vs product problem

The most common founder error is confusing a structural opening with a product opportunity. It looks like this:

The founder sees an incumbent with a legacy product. They assume the incumbent is succeeding because the product is good, not because structure protects it. The founder builds a better product and launches. Six months in, the better product is not gaining traction. The founder concludes the GTM is wrong. They hire a sales team. Still no traction. They pivot the product. Still nothing.

The problem was not the product. It was that there was no structural opening to exploit. The incumbent was protected by switching costs, distribution control, or ecosystem lock-in that no product improvement could overcome.

To test whether you have found a true structural opening, do this:

Interview 10 buyers in the incumbent’s customer base who have seriously considered switching. Do not ask them what they want in a product. Ask them what would have to be true for them to switch. If all 10 give the same answer (faster onboarding, lower price, easier integration), you have found a structural opening that multiple buyers recognize and are willing to pay for. If all 10 give different answers (one wants better reporting, another wants faster API, a third wants different pricing), you have not found a structural opening. You have found 10 different product problems. Your product cannot solve all of them. You will win the small number of buyers with the specific problem you solve best, but you will not break through the structural barrier.

The difference: structural openings converge. Product problems diverge.

A structural opening is an incentive misalignment that affects entire segments of the market simultaneously. A product problem is a feature gap that affects individual buyers.

Why incumbents leave room at the edges

Incumbents defend the core business and the margin. The edges are abandoned not because they are unprofitable, but because defending them would cannibalize the core.

Epic software powers hospitals. Very small clinics cannot afford it and lack infrastructure to run it. Epic has no incentive to serve them. Doing so would cannibalize hospital pricing. Margin protection.

Salesforce dominates enterprise CRM. It is expensive. Small businesses chafe. Salesforce could build a cheap alternative, but would train customers to expect lower pricing and threaten land-and-expand economics. Risk aversion.

Banks do not innovate in small business lending. Margin per relationship is low. Banks maximize return by ignoring unprofitable segments. Fintech companies exist because banks leave this undefended.

Regulation and organizational inertia also leave room. Stripe moved faster than payment processors because processors were constrained by bank relationships and legacy infrastructure. Stripe had neither. The opening is not the incumbent’s weakness. The opening is their rational refusal to defend everywhere at once.

How new entrants actually break through

The mistake is thinking you win by out-executing the incumbent at their own game. You do not. You win by changing the game.

Stripe did not out-execute payment processors. It changed the distribution channel from bank relationships to developer APIs. Processors left this undefended because developers were invisible in their sales model. Stripe changed the structural arrangement so that developers, not banks, controlled which payment processor got integration. The market structure shifted, and incumbents could not follow without destroying their core business.

Google Docs did not beat Microsoft Office by building a better Office. It changed the structural arrangement from licensed software to always-on cloud-native SaaS. It served new workflows (collaborative real-time editing) where switching costs to Office were zero. New workflows meant new entrants, which meant no installed base to migrate. Google did not have to break Office’s lock-in on existing workflows. It built for workflows where lock-in did not exist.

QuickBooks did not win by out-executing bank accounting systems. Banks did not care about accounting because it was not a profit center. QuickBooks won by serving a customer segment (small business) that banks ignored and by bundling accounting with business banking and payroll services. The structural arrangement was different: an integrated platform built around the small business’ actual workflow, not an accounting module in a larger banking platform.

The pattern: you win not by breaking the incumbent’s moat directly, but by exploiting the fact that the incumbent cannot defend everywhere at once. You differentiate the control point itself, not the product. Stripe differentiated distribution (developer-first, not bank-first). Google differentiated switching costs (zero, because it was cloud-native and new workflows had no legacy attachment). QuickBooks differentiated incentive structure (accounting is the core business, not a sidecar).

This requires a second insight: identify what the incumbent cannot change without destroying themselves. Then build for what they cannot serve.

Salesforce cannot build a cheap CRM without destroying enterprise pricing. Oracle cannot build an unbundled suite without destroying lock-in economics. Banks cannot serve small business lending without building a separate organization, because serving it within the legacy bank would destroy credit quality and margins.

When you have identified what the incumbent cannot do, build directly for that need. You are not competing in the incumbent’s market. You are creating a new market they cannot enter without self-destruction.

The false positive: product problem vs structural opening

A false positive: founder talks to three customers complaining about incumbent’s lack of API documentation. Founder concludes: “Structural opening.” Builds API-first alternative. Launches. Three developers adopt it. Runs out of money.

The problem: one complaint is not structural. A structural opening is a market configuration the incumbent cannot serve. A documentation complaint is a product problem. If the incumbent added documentation, it would disappear.

The test: ask 10 buyers in your target segment whether the incumbent could solve their problem by fixing the thing you identified (better documentation, lower price, turnaround). If 8+ say yes, you have a product problem. If 3 or fewer say yes, you have something structural: the problem runs deeper.

Structural openings are robust to incumbent response. Product problems are not.

Timeline for breaking through

If the opening is distribution gatekeeping with direct downstream access, timeline is 18-36 months. You teach new buyers to depend on you.

If the opening is switching costs and you reduce friction (migration, training, integration), timeline is 12-24 months per segment. You can reduce pain but not eliminate it.

If the opening is incentive misalignment (incumbent ignores your segment), timeline is 6-18 months. The incumbent is not competing. You face weak competition.

If the opening is regulation and you await clarity, timeline is unknown. Hedge by building in environments where you can operate now.

If the opening is technology shift and the incumbent cannot adopt the new architecture, timeline is 24-48 months. Scale requires market education.

The worst case: thinking you have a structural opening when you are solving a product problem. Timeline: infinite. You build a great product for an underserved segment but never scale beyond it.

Structural insight tells you where; the job tells you why

Understanding market structure tells you where the customer is and why the incumbent is not serving them. Understanding the customer’s job tells you why they buy at all.

These are two different problems, and they require different GTM motions. Structure tells you whether you have an opening. The job tells you whether the opening is worth anything.

A market can have a structural opening but no job worth solving. Consider the market for floppy disk drives in 2010. There were surely structural misalignments (incumbent manufacturers phasing out production, distributors consolidating, buyers finding it hard to buy). But there was no job worth solving. The technology was obsolete.

Conversely, a market can have a compelling job with no structural opening. A founder might see patients struggling with chronic disease management and want to build a telehealth platform. The job is real. But if every major healthcare system is already building their own telehealth, and switching costs are high, the structural opening is closed. You can still build, but you will be competing in a crowded field with every entrant claiming to solve the same job.

The full picture requires both. Structure tells you whether you can build a defensible moat. The job tells you whether any customer will care. Build where structure and job overlap.

This is why your next step is understanding the jobs your customers are actually trying to do.