SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
loom.comvszendesk.com
which is stronger?
clone time
6 weeks
contested6 weeks
loom.com
async screen recording & video messaging
61/ 100
wedge scorefull report ↗
→vs←
clone time
10–14 weeks
contested10–14 weeks
zendesk.com
AI-powered customer support platform
53/ 100
wedge scorefull report ↗
moat
how deep is each moat.
loom.com · aggregate
3.9/10shallow moat
moat delta+0.8
zendesk.com · aggregate
4.7/10shallow moat
4.0
capital+1.0 →
5.0
5.0
technical±0
5.0
3.0
network±0
3.0
4.0
switching-1.0 →
3.0
4.0
data±0
4.0
2.0
regulatory±0
2.0
4.5
distribution+3.7 →
8.2
floor
cost + time, side by side.
monthly floorloom.com wins
loom.com
$42 + usage
zendesk.com
$47 + usage
delta −$5loom.com costs less per month to keep the lights on.
time to cloneloom.com wins
loom.com
6 weeks
zendesk.com
10–14 weeks
delta −2× faster6 weeks vs. 10–14 weeks.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only loom.com · 44
screen recordingcomments & mentionssocial loginvideo transcoding
shared · 11
speech-to-text
only zendesk.com · 33
serverless / edge platformllm inferencewebhooks
stack
what they're built on.
shared infra and the differentiating bits.
only loom.com · 88
Cloudflare PagesCloudFrontElectronGitHubMuxS3SentryTauri
shared infra · 88
CloudflareNext.jsOpenAIPostgresCloudflare R2ResendSupabaseVercel
only zendesk.com · 44
PostmarkSegmentTwilioZendesk
the verdict
ATTACK LOOM FIRST
same comparison surface, two different walls. give the loom attack a month. circle back to zendesk only if you genuinely need what it does that the other doesn't.
the case
cheaper at the floormatched moat depth
full reportcontested · 61
→ read the loom.com report
full reportcontested · 53
→ read the zendesk.com report
← saaspocalypse · directoryhead-to-head