SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
amazon.comvsgoogle.com
which is stronger?
→vs←
moat
how deep is each moat.
amazon.com · aggregate
7.3/10deep moat
moat delta+1.7
google.com · aggregate
9.0/10deep moat
9.0
capital±0
9.0
6.0
technical+3.0 →
9.0
9.0
network+1.0 →
10.0
7.0
switching+1.0 →
8.0
8.0
data+2.0 →
10.0
3.0
regulatory+5.0 →
8.0
—
distribution—
—
floor
cost + time, side by side.
monthly floortie
amazon.com
$2 + usage
google.com
usage-based
monthly floor is roughly the same on both sides.
time to clonetie
amazon.com
∞
google.com
∞
neither is buildable as a clone — the fight here is the moat, not the build.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only amazon.com · 11
checkout
shared · 22
marketplacepayment rails
only google.com · 00
google.com is a strict subset of the shared surface.
stack
what they're built on.
shared infra and the differentiating bits.
only amazon.com · 77
CloudFrontPostgresReplicateResendSendGridShopifyStripe
shared infra · 00
no shared dependencies.
only google.com · 11
Rails
the verdict
ATTACK AMAZON FIRST
same comparison surface, two different walls. neither is a layup — amazon is the thinner wall. circle back to google only if you genuinely need what it does that the other doesn't.
the case
shallower moat
full reportfortress · 27
→ read the amazon.com report
full reportfortress · 10
→ read the google.com report
← saaspocalypse · directoryhead-to-head