SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
fastly.comvsintercom.com
which is stronger?
→vs←
clone time
10 weeks
contested10 weeks
intercom.com
AI-integrated customer support helpdesk
53/ 100
wedge scorefull report ↗
moat
how deep is each moat.
fastly.com · aggregate
6.5/10real moat
moat delta-1.8
intercom.com · aggregate
4.7/10shallow moat
9.0
capital-4.0 →
5.0
8.0
technical-4.0 →
4.0
3.0
network+1.0 →
4.0
7.0
switching-2.0 →
5.0
4.0
data-1.0 →
3.0
6.0
regulatory-4.0 →
2.0
—
distribution—
7.8
floor
cost + time, side by side.
monthly floorfastly.com wins
fastly.com
$1 + usage
intercom.com
$47 + usage
delta −$46intercom.com costs ~47× more per month to keep alive.
time to cloneintercom.com wins
fastly.com
∞
intercom.com
10 weeks
delta · finite vs. ∞intercom.com is buildable; fastly.com effectively isn't.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only fastly.com · 00
fastly.com is a strict subset of the shared surface.
shared · 22
serverless / edge platformintegrations
only intercom.com · 55
customer support helpdeskembeddingsin-app chatllm inferenceretrieval-augmented generation
stack
what they're built on.
shared infra and the differentiating bits.
only fastly.com · 66
AWSbandwidthCloudflare WorkersFastlyGatsbyS3
shared infra · 55
CloudflareCloudFrontPostgresSupabaseVercel
only intercom.com · 99
IntercomNext.jsOpenAICloudflare R2ResendSalesforceSentryShopifyZendesk
the verdict
ATTACK INTERCOM FIRST
same comparison surface, two different walls. give the intercom attack a month. circle back to fastly only if you genuinely need what it does that the other doesn't.
the case
shallower moat
full reportcontested · 35
→ read the fastly.com report
full reportcontested · 53
→ read the intercom.com report
← saaspocalypse · directoryhead-to-head