wedge
wedge
The narrow, specific problem you solve first to get a door open before you sell anything bigger.
IN PLAIN LANGUAGE
A wedge is the narrow problem you solve first, deliberately narrow, so you can get in the door before anyone trusts you with the bigger thing you actually want to build. It is not your vision statement. It is the annoying, specific task that gets you a paying customer this month.
Amazon's wedge was books. Bezos did not open with 'everything store.' Books were easy to catalog, cheap to ship, and did not need to be touched before buying. That narrow wedge got Amazon warehouses, logistics data, and customer trust that it later spent on electronics, then everything else.
Stripe's wedge was seven lines of code to accept a credit card. Not billing, not fraud detection, not marketplaces. Just the one excruciating step every developer hated. That got Stripe inside thousands of codebases before it expanded into the platform it is now.
The common founder mistake is picking a wedge that is actually the whole business in miniature, so it takes six months to build and still does not clearly beat the alternative. A real wedge should be buildable in weeks and obviously, painfully better at the one thing it does. If your wedge takes a full product team a quarter, it is not a wedge, it is the company.
The second mistake is falling in love with the wedge and never leaving it. Slack's wedge was internal chat for a gaming company that failed. The company that stuck rigidly to its wedge would have shut down. The wedge is a door, not a destination.
A scheduling startup for dental offices could try to build a full practice management suite on day one. Instead it builds only a no show reminder tool that cuts missed appointments by 30 percent, sells that in two weeks per clinic, then upsells billing software once it has the relationship.
Most wedges fail not because they were wrong but because thefounders never let go of them once something bigger became obvious.
QUESTIONS
- How do I know if my idea is a wedge or a whole company?
- If it takes longer than six to eight weeks to build a usable version, it is probably a whole company disguised as a wedge. Cut it down until it fits in a sprint.
- Can a wedge be too small to matter?
- Yes, if it solves a problem nobody will pay for even once. A good wedge is narrow in scope but sits on top of a real, recurring pain, not a one time annoyance.
- When should I expand past the wedge?
- Once you have proof the wedge customers trust you enough to buy something adjacent, usually shown by them asking you for it unprompted. That request is your signal, not a roadmap meeting.
RELATED TERMS
Building your product so the incumbent's own business model stops it from copying you.
The actual field you compete in: who else is there, what they give away free, and which gaps nobody has bothered to close.
The thing you have that nobody else has, the single question no automated market scan can ever answer for you.
Reading about moats is cheap. Testing one takes six stages.