Entrepreneurship KB

Powered by Agentic Workers

Case Study: Stripe — The Schlep Nobody Wanted

5 min read

Case Study: Stripe — The Schlep Nobody Wanted

Stripe is the canonical example of Schlep Blindness — thousands of developers knew online payments were broken, but almost all avoided the idea because it seemed too tedious and regulated. Two Irish brothers, ages 19 and 21, saw the opportunity everyone else filtered out.

Timeline

YearEventScale
2009Patrick (21) and John (19) Collison discuss why payments are so hardIdea stage
2010Incorporated. Enter Y Combinator. Build first prototypePrivate beta
2010-2011”Collison installation” — walk to YC companies, set them up on the spot~100 early users
2011$2M seed from Peter Thiel, Elon Musk, Sequoia, a16zGrowing fast
2012Public launch. 7 lines of code to accept paymentsThousands of developers
2014Series C, $3.5B valuationMajor platform
2019$35B valuation, largest private fintechGlobal scale
2023$50B+ valuation after fundraiseProcesses hundreds of billions/year

Mapping to Frameworks

ideation: Schlep Blindness as Moat

Paul Graham uses Stripe as the canonical example of Schlep Blindness — the unconscious tendency to avoid ideas requiring tedious, unglamorous work.

Why everyone avoided it:

  • Dealing with banks, regulations, and compliance seemed burdensome
  • Payment processing was “boring” compared to consumer apps
  • Legacy players (PayPal, Braintree) existed — the market seemed served
  • The technical and legal complexity was genuinely enormous

Why the Collisons didn’t:

  • They were developers who experienced the pain directly (organic idea)
  • They were young enough to not know how hard it “should” be
  • They applied PG’s insight: “You can only avoid competition by avoiding good ideas”

The Schlep Blindness itself became a competitive moat — by the time competitors realized the opportunity, Stripe had years of head start with developers.

do-things-that-dont-scale: The Collison Installation

PG coined “Collison installation” at YC to describe their technique: instead of asking “will you try our beta?”, the Collisons would say “give me your laptop” and integrate Stripe into the developer’s codebase right there.

This was:

  • Impossibly unscalable: One setup at a time, in person
  • Incredibly effective: Zero friction. The developer went from “maybe” to “done” in minutes
  • A learning machine: Every installation taught them about edge cases, developer needs, and API design

The name became a verb at YC: “Just Collison-install it.”

competitive-strategy: Zero to One, Not One to N

Stripe didn’t compete with PayPal on PayPal’s terms. Per Thiel’s framework, they went zero to one — creating a new category:

DimensionPayPal (2010)Stripe
Target userConsumers/merchantsDevelopers
IntegrationRedirect to PayPal page7 lines of code
PhilosophyPayment gatewayPayment infrastructure/API
MoatBrand + network effectsDeveloper ecosystem + API design

Stripe built a platform (Thiel’s monopoly characteristic #3) — developers built on Stripe, creating ecosystem lock-in that compounded over time.

product-market-fit: Developer Love

Stripe achieved PMF with a specific, narrow audience: developers at startups who needed to accept payments. The product was 10x better (Thiel’s monopoly characteristic #1) along the dimension that mattered most to developers: simplicity of integration.

The 7-line code snippet became iconic — it was the minimum-viable-product philosophy applied to enterprise infrastructure. Do one thing (accept payments) and make it absurdly simple.

fundraising: Strategic Investors as Validation

The $2M seed round reads like a startup all-star team:

  • Peter Thiel: Co-founded PayPal — knew the payments market intimately
  • Elon Musk: Also co-founded PayPal
  • Sequoia Capital: Premier VC firm
  • Andreessen Horowitz: Marc Andreessen’s firm

Getting PayPal’s founders to invest in a payments competitor was extraordinary signal — it said “the people who understand this market best believe Stripe can win.”

growth: Platform Dynamics

Stripe’s growth engine was the developer ecosystem — a platform network effect:

  1. Developers adopt Stripe → their companies use Stripe
  2. More companies on Stripe → more developers encounter it
  3. Developer community grows → better docs, more libraries, more integrations
  4. Better ecosystem → even easier to adopt → flywheel accelerates

This is network-effects at the platform level — the strongest and most durable type per a16z’s framework. Unlike commoditized supply (Uber drivers), Stripe’s integrations are deeply embedded and switching costs are enormous.

scaling: From Startup Tool to Financial Infrastructure

Stripe’s scaling journey followed Rabois’ progression but in reverse order of complexity:

  • Started with the simplest use case (accept a payment)
  • Added complexity gradually (subscriptions, marketplace payments, fraud detection)
  • Built platform products (Stripe Atlas for incorporation, Stripe Capital for lending)
  • Became financial infrastructure that companies build entire businesses on

Today Stripe processes hundreds of billions of dollars annually for millions of businesses. The “schlep nobody wanted” became one of the most valuable private companies in history.

Key Lessons

  1. Schlep Blindness is a competitive moat — the tedium that repels others IS the barrier to entry
  2. Target developers, not end users — when developers adopt your tool, their companies follow
  3. Collison-install it — remove ALL friction from adoption, even if it means doing it for them
  4. 7 lines of code — radical simplicity is a product strategy, not just a feature
  5. Strategic investors validate — Thiel and Musk investing in a PayPal competitor was the ultimate signal
  6. Zero to one, not head-on competition — don’t fight PayPal; build a new category (developer-first payments)
  7. Young founders see what veterans filter — the Collisons’ youth was an advantage, not a handicap

See Also

Sources

Graph View

Backlinks