Gap Hypothesis Build-and-Iterate Method
Find a real-world gap, assemble elite builders, and iterate with users
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 96%
The method begins by identifying a material gap between how an industry currently works and how it could work with better technology, incentives, or workflows. Rather than requiring founders to be established domain experts, it pairs a strong hypothesis with an unusually capable technical culture. The team speaks directly with practitioners, builds an initial solution, and assumes that some features or assumptions will be wrong. Because the builders are talented, empowered, and meaningfully invested in the company, they can translate customer feedback into rapid iterations. Repeated cycles of building, showing, learning, and correcting gradually replace the original hypothesis with a product grounded in actual user needs. The output is not simply better software, but an organization able to keep learning alongside its market.
Origin
Joe Lonsdale described this method while explaining how Opto entered financial services and improved its product through sustained collaboration with registered investment advisers.
Core principles
- 01Start with a visible gap between current and possible outcomes
- 02Treat domain knowledge as learnable through close customer contact
- 03Build a team capable of responding quickly to evidence
- 04Give builders meaningful ownership
- 05Expect the initial product hypothesis to be partly wrong
How to run it
- 1
Map the gap
Describe where the industry is now, where it could be, and what prevents customers from crossing that gap. Make the contrast concrete enough to generate a testable product hypothesis.
Pro tip Look for wasted time, misaligned incentives, inaccessible information, or unnecessarily difficult workflows.
Watch out A fashionable technology without an important customer gap is not a sufficient starting point.
- 2
Form a high-velocity technical culture
Recruit proven builders who can ship quickly, communicate with users, and revise their work without defensiveness. Reinforce ownership through equity and meaningful autonomy.
Pro tip Favor people who have already built or scaled difficult products.
Watch out Talent alone is insufficient if the culture isolates engineers from customers.
- 3
Build from the hypothesis
Create an initial product that demonstrates how the gap might be closed. Treat it as a learning instrument rather than a finished answer.
Pro tip Prioritize the smallest implementation that exposes the important assumptions.
Watch out Do not confuse founder conviction with proof that every feature is useful.
- 4
Iterate with experts
Put the product in front of practitioners, identify what is wrong or unhelpful, and incorporate their feedback quickly. Continue until usage and enthusiasm demonstrate that the solution fits real workflows.
Pro tip Build with customers over time instead of collecting feedback only at launch.
Watch out Slow iteration allows incorrect assumptions to harden into expensive architecture.
In the wild
Opto began with the hypothesis that private-market access suffered from misaligned incentives, administrative friction, and poor visibility into high-quality opportunities. Its technical team worked with registered investment advisers, learned which assumptions and features were wrong, and repeatedly adapted the platform based on their feedback.
→ After several years of iteration, advisers began to adopt and value the platform more strongly.
A startup observes that regional distributors still coordinate deliveries through spreadsheets and phone calls. It recruits experienced technical operators, gives them ownership, builds a narrow scheduling prototype, and embeds with dispatchers for weekly feedback. Each iteration removes an actual bottleneck rather than adding speculative features.
→ The startup develops a workflow customers use daily and can expand from a validated operational foundation.
Common mistakes
Demanding expertise before exploration
Waiting until founders know everything about an industry prevents learning through construction and customer collaboration. The method depends on a capable culture that can learn from experts.
Building without user contact
Even intelligent teams will create features that are wrong or unhelpful. Customer feedback must influence the product continuously.
Hiring talent without ownership
A strong résumé does not automatically create an entrepreneurial culture. Builders need incentives and authority aligned with the product's success.
Is it for you?
Best for
It is best for technically ambitious teams tackling a clear but poorly served operational problem.
Not ideal for
It is not ideal when customers cannot participate in iteration or the team lacks the capacity to ship quickly.
From the transcript
“And the other thing we're looking for is like where is a gap in the world, where is something Here's where it could be, and…”
“And then and then, and then you build and you iterate with clients because no matter how smart we think, we are going to come…”
“So when you approach a new space, it's not about being an expert in this space. It's about having a really amazing culture that talks…”
From the episode
AI Innovations with Joe Lonsdale
Joe Lonsdale