SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
slack.comvswikipedia.org
which is stronger?
clone time
3 months
contested3 months
slack.com
team messaging & AI work platform
43/ 100
wedge scorefull report ↗
→vs←
moat
how deep is each moat.
slack.com · aggregate
5.7/10real moat
moat delta-0.1
wikipedia.org · aggregate
5.6/10real moat
5.0
capital+2.0 →
7.0
4.0
technical+1.0 →
5.0
8.0
network±0
8.0
6.0
switching±0
6.0
3.0
data+1.0 →
4.0
2.0
regulatory-1.0 →
1.0
8.4
distribution—
—
floor
cost + time, side by side.
monthly floortie
slack.com
$47
wikipedia.org
$47
monthly floor is roughly the same on both sides.
time to clonewikipedia.org wins
slack.com
3 months
wikipedia.org
8 weeks
delta −2× faster8 weeks vs. 3 months.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only slack.com · 33
serverless / edge platformapi platformcloud file storage
shared · 11
subscriptions
only wikipedia.org · 11
rich text editor
stack
what they're built on.
shared infra and the differentiating bits.
only slack.com · 44
MeilisearchNextAuthSalesforceSupabase Auth
shared infra · 77
CloudflareNext.jsPostgresCloudflare R2ResendSupabaseVercel
only wikipedia.org · 55
AlgoliaCloudflare PagesPostmarkReplicateTypesense
the verdict
TOO CLOSE TO CALL
slack and wikipedia.org land on the same moat depth, sit in the same tier, and present the same wall. either is a defensible angle of attack — the choice is taste, not difficulty.
the read
matched tiermatched wedge scoreland on the same moat depth
full reportcontested · 43
→ read the slack.com report
full reportcontested · 44
→ read the wikipedia.org report
← saaspocalypse · directoryhead-to-head