Illustrated Example: Uber
How a business model looks when treated as a system of hypotheses instead of a static structure.
Uber is a well-known platform business operating under constant regulatory, technological and societal pressure. This makes it an ideal example to illustrate why static business model descriptions fail in the age of AI.
Uber’s Business Model as a static Business Model Canvas
Customer Segments
-
Riders (urban, on-demand mobility)
-
Drivers (independent contractors)
Value Proposition
-
Fast, convenient, on-demand transportation
-
Typically cheaper and more flexible than traditional taxis
Channels
-
Mobile app
Customer Relationships
-
Self-service via app
-
Algorithmic matching and pricing
-
Limited human support
Revenue Streams
-
Commission per ride
-
Dynamic pricing (surge pricing)
-
Ancillary services (Uber Eats, subscriptions)
Key Activities
-
Platform development and maintenance
-
Matching supply and demand
-
Pricing optimization
-
Marketing and growth
Key Resources
-
Platform & algorithms
-
Data (demand, supply, pricing)
-
Brand
-
Network of drivers
Key Partners
-
Drivers
-
Payment providers
-
Mapping / navigation services
-
Vehicle leasing partners (in some markets)
Cost Structure
-
Platform development
-
Marketing & incentives
-
Driver subsidies
-
Regulatory and legal costs
Result: A coherent, internally consistent snapshot of how Uber creates and captures value at a given point in time.
Limitations of the static approach
The Business Model Canvas is not wrong — but it is structurally blind to what matters most in Uber’s reality.
1. No concept of decay or erosion
The static approach cannot express that:
-
“Low prices” are becoming politically and economically unsustainable
-
Driver flexibility is under regulatory pressure
-
Public trust in algorithmic pricing is eroding
2. No differentiation by speed of change
-
Regulatory constraints change yearly
- Pricing logic changes weekly
-
Core platform capabilities evolve slower
3. No representation of uncertainty
Key questions are invisible:
What assumptions might fail next? Which elements are experimental vs. core? Which bets depend on autonomous driving becoming real?
4. Strategy and execution are artificially separated
For Uber:
-
Pricing decisions are strategy
-
Driver incentives are strategy
-
Algorithm design is strategy
The BMC cannot represent this coupling between design and execution.
5. No place for decision logic
Critical strategic issues are missing:
Who decides pricing rules? Which decisions are automated? Where must humans override algorithms?
Uber as a Hypothesis System
Value Hypotheses
| Hypothesis | Status | Strategic implication |
|---|---|---|
| Immediate ride availability drives demand | Stable | Core value remains intact |
| Low price is the main decision factor | Eroding | Margin pressure, political risk |
| Convenience outweighs car ownership | Stable | Long-term urban trend |
| Safety expectations are “good enough” | Eroding | Trust becomes strategic |
| Ride pooling is broadly accepted | Failed | Stop investing |
Execution Hypotheses
| Hypothesis | Status | Strategic implication |
|---|---|---|
| Drivers remain flexible partners | Eroding | Regulatory exposure |
| Algorithmic matching scales globally | Stable | Core capability |
| Incentives secure driver loyalty | Eroding | Rising cost base |
| Global rollout is easily replicable | Eroding | Localization required |
| Autonomous driving replaces drivers | Experimental | Long-horizon bet |
Decision & Control Hypotheses
| Hypothesis | Status | Strategic implication |
|---|---|---|
| Pricing can be fully automated | Eroding | Human oversight required |
| Algorithms resolve conflicts fairly | Eroding | Transparency needed |
| Centralized decision logic scales | Eroding | Local autonomy increases |
| AI decisions need no explanation | Failed | Regulatory constraint |
