Garrett Camp: The Product Thinker Behind Uber and Expa's Founder Factory
Garrett Camp repeatedly started with a simple interface for a fragmented problem—web discovery, urban transport, startup creation—then built networks behind it.
View all stories about this mogul
Garrett Camp’s most valuable product ideas begin by deleting friction from the screen. StumbleUpon reduced web discovery to a button. The original ride-hailing concept reduced urban transport to a phone request and a visible car. Expa tried to reduce early company formation by giving founders a shared platform for design, recruiting, capital, and operations.
The interface looked simple because the network underneath was not. Discovery required data about taste. Ride-hailing required drivers, location, payments, safety, pricing, and city-by-city operations. A startup studio required judgment about which ideas deserved years of effort.
Camp’s career shows the power of a product abstraction—and the danger of mistaking an elegant front end for the whole business.
Chapter One: StumbleUpon Made Discovery a Product

Camp co-founded StumbleUpon in 2002 while studying in Calgary. The service helped people discover web pages based on interests and feedback. Instead of typing a query or following a known link, a user could ask to be surprised within a learned preference space.
That interaction turned browsing into a product loop: discover, react, improve the recommendation, repeat. It anticipated a central feature of later feeds—the platform chooses the next item, then learns from behavior.
eBay acquired StumbleUpon in 2007 and the founders later bought it back. The sequence taught two different lessons. An acquisition can provide capital and distribution, but ownership inside a larger company does not guarantee that a product’s rhythm fits the parent. Buying it back restored control without restoring the web environment in which it first grew.
The internet was shifting toward social feeds and mobile apps. Discovery increasingly happened inside a few large platforms. StumbleUpon’s elegant button remained useful, but distribution moved around it.
Camp’s first major product therefore contained a pattern he would revisit: make a fragmented supply legible through one lightweight action. The product must still adapt when the channel changes.
Chapter Two: The Black-Car Button Became a Network

The familiar origin story places Camp and Travis Kalanick in Paris, struggling to get a cab on a snowy night. Origin stories become cleaner with repetition, but Uber’s 2019 registration statement identifies Camp and Kalanick as co-founders and describes the company that grew from the idea.
Camp’s concept centered on a reliable premium car summoned from a phone. The user experience collapsed several uncertainties—availability, dispatch, location, payment, and trust—into a request and an estimated arrival.
The first product did not eliminate the transportation system. It reorganized access to it. Professional drivers and black-car operators supplied the early network. GPS and smartphones made vehicles visible. Stored payment removed the end-of-ride transaction.
As Uber expanded beyond premium cars, the abstraction gained power. More drivers could reduce wait times; lower wait times attracted riders; more demand improved driver utilization. That marketplace flywheel supported geographic expansion.
It also created conflicts the original button could not solve. Driver classification, local licensing, insurance, safety, surge pricing, and platform power became central. A smooth interface can make externalized complexity invisible until regulators, workers, and communities force it back into view.
Camp served as chairman for years while Kalanick became the public operating force. Their roles illustrate a recurring company tension: the product originator defines a compact experience, while the scaling operator builds an organization aggressive enough to reproduce it worldwide. Those skills can complement each other and generate governance risk when growth outpaces controls.
Chapter Three: Expa Tried to Productize Company Creation

Camp founded Expa as a platform for starting and supporting companies. Rather than operating as a conventional fund that only selects outside teams, a studio can develop ideas internally, recruit founders, supply design and engineering help, and provide seed capital.
The appeal is reusable infrastructure. Early startups repeatedly need incorporation, recruiting, brand work, prototypes, analytics, fundraising preparation, and introductions. Centralizing those capabilities can shorten the path from concept to market test.
But company creation resists assembly-line logic. The shared team may become a service bureau detached from customers. Founders can lack true ownership if an idea arrives too fully designed. A studio can also spread attention across attractive concepts that each require deep domain commitment.
Expa’s portfolio demonstrates range across mobility, property, finance, and consumer services. Range is not the same as repeatability. Uber-scale outcomes are rare because timing, regulation, capital, team chemistry, and network effects do not follow a fixed recipe.
The studio model works best when it shares expensive early capabilities while giving each company independent accountability. It should accelerate learning, not protect weak ideas from the market.
Chapter Four: What Camp’s Product Method Gets Right

Camp’s strength is reduction. He searches for one action that can represent a much larger system: stumble, request a ride, start a company. That action is memorable enough to guide product design and fundraising.
Reduction becomes dangerous when leaders ignore what the interface hides. Ride-hailing is labor and regulation as well as software. Discovery is power over attention as well as convenience. A startup studio is capital allocation and founder psychology as well as shared services.
The right product abstraction does not deny complexity. It chooses which complexity the company will absorb for the customer. Uber handled dispatch and payment so the rider did not have to. The operational burden moved into the platform.
Camp’s quieter public profile also offers a governance lesson. Business histories often assign one face to a network of founders, employees, investors, suppliers, and users. Uber’s filing preserves Camp’s co-founder role, while the company’s later controversies show why credit and responsibility must be examined across the organization.
His legacy is less a single corporate culture than a way of framing products: find a repeated frustration, make the desired outcome one obvious action, and then build the network capable of honoring that promise.
The Real Lesson
Simplicity is not the absence of complexity. It is the decision to move complexity behind the product boundary. Great founders know which burden the company can absorb; reckless ones pretend the burden disappeared.
💡 Key Insights
- ▸ The best marketplace concept often compresses a messy system into one obvious user action.
- ▸ A simple interface can conceal a difficult network of supply, regulation, payments, and safety.
- ▸ Founder studios can reuse recruiting and design systems, but product-market fit does not become repeatable on command.
- ▸ Quiet product influence can be as consequential as the operator who scales the company publicly.