SAASPOCALYPSEcase · head-to-head
wedge comparison
subjects of investigation
atlassian.comvsloom.com
which is stronger?
clone time
10–16 weeks
contested10–16 weeks
atlassian.com
team collaboration & project management suite
36/ 100
wedge scorefull report ↗
→vs←
clone time
6 weeks
contested6 weeks
loom.com
async screen recording & video messaging
61/ 100
wedge scorefull report ↗
moat
how deep is each moat.
atlassian.com · aggregate
6.4/10real moat
moat delta-2.5
loom.com · aggregate
3.9/10shallow moat
6.0
capital-2.0 →
4.0
6.0
technical-1.0 →
5.0
7.0
network-4.0 →
3.0
7.0
switching-3.0 →
4.0
4.0
data±0
4.0
4.0
regulatory-2.0 →
2.0
9.2
distribution-4.7 →
4.5
floor
cost + time, side by side.
monthly floorloom.com wins
atlassian.com
$47
loom.com
$42 + usage
delta +$5loom.com costs less per month to keep the lights on.
time to cloneloom.com wins
atlassian.com
10–16 weeks
loom.com
6 weeks
delta −3× faster6 weeks vs. 10–16 weeks.
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only atlassian.com · 44
issue / project trackerautomationsrole-based access controlrich text editor
shared · 22
comments & mentionssocial login
only loom.com · 33
screen recordingspeech-to-textvideo transcoding
stack
what they're built on.
shared infra and the differentiating bits.
only atlassian.com · 33
LoopsReactTiptap
shared infra · 99
CloudflareCloudFrontGitHubNext.jsPostgresCloudflare R2ResendSupabaseVercel
only loom.com · 77
Cloudflare PagesElectronMuxOpenAIS3SentryTauri
the verdict
ATTACK LOOM FIRST
same comparison surface, two different walls. give the loom attack a month. circle back to atlassian only if you genuinely need what it does that the other doesn't.
the case
cheaper at the floorshallower moat
full reportcontested · 36
→ read the atlassian.com report
full reportcontested · 61
→ read the loom.com report
← saaspocalypse · directoryhead-to-head