Vertical Wedge Against a Horizontal Network
Win one high-value niche before expanding across an entrenched network
- Difficulty
- Expert
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 94%
A mature horizontal network cannot usually be displaced by building a cleaner version of the same broad product because the incumbent already contains the people users need. The viable wedge is a narrow community whose members produce richer, specialized evidence through their normal work. A challenger embeds itself in that community's workflow, captures data the incumbent lacks, and provides enough focused utility to reach local critical mass. GitHub's record of developers' work and Behance's design portfolios illustrate how vertical data can become more actionable than a generic professional profile. Only after the niche has strong retention and dense participation should the product expand into adjacent communities, carrying its established graph and differentiated data into each new market.
Origin
Extracted from Acquired's discussion of how GitHub, AngelList, and Behance could challenge parts of LinkedIn without recreating a horizontal professional network.
Core principles
- 01Do not attack a mature horizontal network head-on
- 02Choose a niche where specialized data creates superior utility
- 03Use work-generated evidence rather than self-reported profiles
- 04Reach critical mass inside one community before expanding
- 05Expand only into adjacent groups with overlapping needs
How to run it
- 1
Select the wedge
Choose a narrow community with shared workflows, concentrated distribution, and an unmet need the horizontal incumbent handles poorly.
Pro tip Favor communities where reputation directly affects hiring, purchasing, or collaboration.
Watch out A niche defined only by demographics may lack a recurring workflow.
- 2
Capture proof of work
Build around artifacts and behavioral data produced through real activity rather than asking users to maintain another generic profile.
Pro tip Make profile quality improve automatically as users work.
Watch out Self-reported fields alone rarely differentiate the challenger from the incumbent.
- 3
Own the core workflow
Provide a tool the niche repeatedly uses to create, evaluate, or exchange its work.
Pro tip Attach the network to an existing high-frequency task.
Watch out A directory without workflow utility struggles to retain users.
- 4
Reach local critical mass
Concentrate recruitment within the niche until most valuable counterparties can be found on the platform.
Pro tip Measure successful connections within the niche, not total global membership.
Watch out Premature geographic or occupational expansion dilutes density.
- 5
Expand adjacently
Move into a neighboring community that values the existing members, data, or workflow.
Pro tip Choose adjacencies where one side of the new network is already present.
Watch out Do not abandon the specialized advantage in pursuit of horizontal scale.
In the wild
Recruiters can begin with GitHub because repositories and contribution histories reveal developers' actual work. That work-generated trail can provide richer evidence than a conventional professional profile while concentrating a network inside one occupation.
→ A vertical platform earns a defensible role in developer discovery without replacing all of LinkedIn.
A platform begins with oncology trial coordinators and automatically turns protocol work, site performance, and verified credentials into professional profiles. Once most coordinators in several research centers participate, it expands to investigators and specialist recruiters.
→ The platform grows from a dense workflow network into adjacent professional markets.
Common mistakes
Launching horizontally
Trying to serve every profession immediately recreates the incumbent's product without recreating its network.
Building only better profiles
Improved presentation is insufficient unless the challenger owns differentiated data or a recurring workflow.
Expanding before density
Moving into adjacent markets before the initial niche is self-sustaining weakens utility everywhere.
Is it for you?
Best for
It is best for startups with specialized workflow data and access to a concentrated professional or industry community.
Not ideal for
It is not ideal for undifferentiated products attempting to recreate an established network for everyone at once.
From the transcript
“once they have network effects applied, you don't disrupt them by building another horizontal platform.”
“If you were going to attack LinkedIn, this is the only way to do it because it's the only way where you can actually get…”
“when recruiting developers, it's very common to start on GitHub.”
From the episode