Acquired · Amazon · Strategies
Strategies
Named moves Acquired identified in Amazon's playbook — what they did, when it crystallized, the evidence behind the claim, and where each move sits in the broader 12-pattern strategic taxonomy.
Strategic moves · grouped by era
1997-present
Day 1 operating principle — permanent first-day urgency
Every Bezos shareholder letter since 1997 has repeated 'Day 2 is stasis. Followed by irrelevance. Followed by excruciating, painful decline. Followed by death. And that is why it is always Day 1.' The principle operationalizes a consistent set of behaviors: customer obsession over competitor focus, willingness to be misunderstood, rejection of proxy goals (processes over outcomes).
- Ben:Day 2 is stasis. Followed by irrelevance. Followed by excruciating, painful decline. Followed by death. And that is why it is always Day 1.[Acquired Amazon.com, ch. The Day 1 letter]
Sacrifice short-term margin for long-term market share
Amazon repeatedly chose to price below competitors and invest in warehouses, AWS, Kindle, and Prime Video at a loss, accepting near-zero operating margins for years. Each investment widened the moat while eroding the economics of retailers, publishers, and broadcasters who could not match the price or the Prime bundle. Bezos treated Wall Street expectations as an external irrelevance.
2000-present
Third-party marketplace: let rivals sell, take the cut
Amazon opened its platform to third-party sellers starting in 2000. By 2023 ~60% of units sold on Amazon are from third parties, who pay ~15% commission plus fulfillment fees. The marketplace adds selection Amazon cannot profitably stock itself, while Amazon captures the margin without the inventory risk.
2002-present
The API mandate — internal discipline becomes external product
Bezos mandated in 2002 that all internal Amazon teams must expose their capabilities through service interfaces, and those interfaces must be designed as if they would be sold externally. The mandate was not originally about AWS — it was about forcing Amazon to build modular, interoperable systems. AWS was the externalization of what that discipline produced.
2005-present
Prime flywheel: lock in the shopper before the shopping decision
A $139/year Prime membership reverses the consumer's cost calculation: instead of asking 'should I pay shipping?' a Prime member asks 'how do I get maximum value from the membership I've already paid for?' Prime members spend ~2x non-members. The subscription also anchors Prime Video, Prime Music, and Prime Reading — making cancellation increasingly costly with each added service.
2006-present
AWS: sell the shovel — infrastructure as a product
Amazon built datacenter infrastructure at scale to run its own retail operation. It then rented that infrastructure to third parties at a margin. The model inverted the capex relationship: customers pay per use instead of building their own servers. AWS now generates ~$105B/year in revenue at ~30%+ operating margins — multiples of the retail business that funded it.
- David:AWS is the most profitable business Amazon has ever built, and they basically invented the category. The operating margin on AWS is over 30 percent.[Acquired Amazon Web Services]
Concepts this company exemplifies
Scale economies→
Cost advantages a large player has that smaller competitors structurally can't match, which then reinforce themselves.
Network effects→
Compounding advantages from more users, developers, partners, suppliers, or fans on the same system.
Vertical integration→
Owning more of the value chain than necessary, in order to capture margin or remove a dependency that could become an obstacle.
Pattern constellation
Of the 12 strategy patterns in the Acquired taxonomy, Amazon most prominently practices 6. Size = how many named strategies express that pattern.