miro.com
the door is switching cost: boards are just JSON blobs of shapes and stickies — there's no proprietary data format locking teams in, and the free-tier ceiling is low enough to push users toward alternatives.
where the walls are.
no regulatory wall — SOC 2 doesn't count.
their distribution is fortress-grade — they own their brand SERP end-to-end.
why this scoremedium confidenceMiro's capital moat is moderate. Enterprise sales motion, compliance certifications (SOC 2, ISO 27001), and a large...
Miro's capital moat is moderate. Enterprise sales motion, compliance certifications (SOC 2, ISO 27001), and a large customer success/implementation org create real friction for enterprise deals. However, the core infrastructure is standard cloud SaaS — no proprietary hardware, no inventory, no payments risk, no regulated capital requirements. An indie builder targeting SMB or a single vertical avoids most of this spend entirely.
- Starter plan at $8/user/mo suggests a self-serve SMB motion that requires no enterprise implementation overhead to compete against at the low end.
- Estimated competing infra cost is only $47/mo — Vercel + Supabase + R2 — confirming no proprietary infra barrier.
- Enterprise Miro deployments involve SSO, admin controls, and compliance reviews, but these are table-stakes SaaS features, not capital-intensive moats.
why this scorehigh confidenceThe real-time sync engine (CRDT/OT) and large-board performance are the only genuine technical moats. Miro has years...
The real-time sync engine (CRDT/OT) and large-board performance are the only genuine technical moats. Miro has years of viewport culling, delta sync, and selective re-render work that a v1 cannot replicate. However, the report explicitly notes that tldraw and Yjs commoditize the canvas and CRDT layers respectively — the hard part is wiring them together without data loss and achieving performance at scale (1000+ objects, 20+ users). This is a 'hard but solvable' problem, not a fortress.
- Report rates CRDT/OT sync as 'hard' and large-board performance as 'nightmare' — acknowledging real engineering depth.
- tldraw and Yjs are cited as pragmatic off-the-shelf solutions, meaning the primitives are commoditized even if integration is non-trivial.
- Miro's years of perf work (viewport culling, delta sync) are explicitly called out as an advantage an indie v1 cannot match on day one.
why this scoremedium confidenceMiro has a meaningful but not fortress-level network effect. The app/template marketplace and partner ecosystem...
Miro has a meaningful but not fortress-level network effect. The app/template marketplace and partner ecosystem (Atlassian, Slack, Figma integrations) create some multi-sided value. Sharing boards with external guests creates mild viral loops. However, boards are not inherently social objects — most usage is within a single team, not across organizations. There is no liquidity-dependent marketplace or social graph that collapses without scale.
- Miro has a public template marketplace and an app ecosystem (integrations with Jira, Confluence, Figma, etc.) that adds ecosystem stickiness.
- Guest sharing and board links create outbound viral loops, but these are weak — recipients don't need a Miro account to view.
- No evidence of a two-sided marketplace with liquidity risk or a social graph that would collapse if users left.
why this scorehigh confidenceThe wedge thesis is correct: boards are JSON blobs of shapes and stickies. The report explicitly states there is no...
The wedge thesis is correct: boards are JSON blobs of shapes and stickies. The report explicitly states there is no proprietary data format. Switching cost comes from accumulated boards, embedded workflows (Jira links, Confluence embeds), and team habit — not from data that is technically impossible to migrate. Enterprise teams with hundreds of boards and trained facilitators have real inertia, but this is workflow lock-in, not technical lock-in.
- Wedge thesis directly states: 'boards are just JSON blobs of shapes and stickies — there's no proprietary data format locking teams in.'
- Miro supports board export (PDF, image), further reducing migration pain for individual boards.
- Switching cost is primarily social/habitual (trained facilitators, embedded Confluence/Jira links) rather than data-structural.
why this scoremedium confidenceMiro has behavioral data on how teams use whiteboards (template usage, collaboration patterns, feature adoption) but...
Miro has behavioral data on how teams use whiteboards (template usage, collaboration patterns, feature adoption) but there is no evidence this data is used to train proprietary models or power a feedback flywheel that competitors cannot replicate. Board content is user-generated and not a proprietary corpus. No fraud/risk model data. No evidence of a non-exportable accumulated dataset that is the product.
- Board content is user-generated JSON — not a proprietary corpus owned by Miro.
- No evidence Miro uses behavioral data to train AI models that improve the core product in a compounding way.
- Miro has launched AI features (sticky clustering, summarization) but these appear to use general-purpose LLMs, not proprietary trained models.
why this scorehigh confidenceMiro operates in the general productivity/collaboration space. There are no regulated duties — no HIPAA, no FINRA, no...
Miro operates in the general productivity/collaboration space. There are no regulated duties — no HIPAA, no FINRA, no KYC/AML, no money transmission, no clinical data obligations. SOC 2 and ISO 27001 certifications are present but these are table-stakes enterprise sales requirements, not regulatory moats. An indie builder targeting SMB or a non-regulated vertical faces zero regulatory barrier.
- Miro is a whiteboard/collaboration tool — no financial, healthcare, or clinical data obligations by default.
- SOC 2 compliance is noted implicitly (enterprise sales motion) but SOC 2 alone is explicitly excluded from moat scoring per rubric.
- No evidence of HIPAA BAAs, FINRA registration, PCI obligations, or any licensed regulated activity.
the blunt take.
“Miro is a $17.5B whiteboard. The core product — infinite canvas, sticky notes, connectors, real-time cursors — is a well-understood engineering problem. The moat is brand inertia and integrations, not technical depth.”
The wedge is vertical focus: Miro tries to be everything to everyone (agile, design, workshops, diagramming). A contender that owns one workflow deeply — say, async retrospectives for remote teams, or lightweight architecture diagramming — can win a niche before Miro notices. The canvas itself is not the hard part; the real-time sync engine is.