Patrick Collison
Founder who reimagined payment infrastructure with slow-company philosophy and intellectual density
Patrick Collison co-founded Stripe with his brother John, disrupting complex web payment processes with simple seven-line code and providing financial infrastructure for millions of global developers. He is known for wide reading, intellectual density, and slow-company philosophy, refusing early sales or quick exits to build Stripe into a diversified financial tools platform. He also helped found the field of 'progress studies', focusing on mechanisms for accelerating technological advancement.
Methodologies
- Slow-Company Building Strategy - Refuse to sacrifice long-term strategy for valuation or liquidity; use time compounding to build irreplaceable infrastructure
- Developer Experience First Principle - Developer tool competitiveness lies in documentation, API design, and debugging experience—not feature count
Key decisions and timeline
- 2007 Auctomatic sold for $5M, first entrepreneurial success - A small success can provide resources and credibility for the next big bet; the key is recognizing the scale gap between the current opportunity and the next.
- 2010 Identified payment pain points, founded Stripe - The best B2B products are often those that solve real pain points developers themselves encounter when building other products.
- 2011-09 Through Y Combinator, launched Stripe public beta - Invitation-only release is an effective early adoption strategy for developer tools, since developer testimonials have extremely high credibility among similar audiences.
Beliefs and mental models
- Belief 1 - Collison believes companies that create lasting value require decades to build; compromising on speed doesn't lead to success but mediocrity; truly important infrastructure deserves to be built slowly.
- Belief 2 - Collison positions Stripe as a high-intellectual-density organization, driving decision quality by recruiting broadly knowledgeable talent, encouraging cross-domain learning, and maintaining a problem-conscious culture.
- Belief 3 - For infrastructure products built for developers, documentation, API design, and debugging experience are as important as functionality itself; excellent developer experience is the strongest marketing.
- Model 1
- Model 2
- Model 3