Nice try. The moat was never the code. Realistically you won't.

What stops a copy of Notion working?

The last 20 per cent of a block editor is where editors go to die. Selection across nested blocks, paste from Word, undo that spans a drag, IME input, collaborative cursors. The recursive data model, where a database row is itself a page containing databases, is elegant and unforgiving. Permissions and rendering both have to terminate. Real-time collaboration on a tree, with offline edits that merge sanely. Performance on a workspace with 50,000 pages, which is the only workspace that matters commercially.

Can AI copy

Notion

Documents made of blocks, where any page can also be a database.

Nice try

Verdict: Nice try
Time to copy: you won't
Category: ▧ Productivity
Source: Proprietary

The prompt

Written to be pasted straight into an agent with no editing. It describes the whole job, including the parts that will go wrong.

Build a block-based document editor. Every document is an ordered tree of typed blocks: paragraph, heading, list, toggle, code, image, table, and embed. Blocks are addressable and can be referenced from other documents. Any collection of pages can be rendered as a database with typed properties and switchable table, board and calendar views. Support real-time collaboration with operational transforms or CRDTs over the block tree, per-block permissions inherited down the hierarchy, and full-text search. Expect the selection model to take longer than everything else combined.

Open inClaude ↗Terminal agents take it from the clipboard.

What copies cleanly

A block editor. Slash commands, drag handles, nested lists. Editor frameworks make the first 80 per cent pleasant.
A table view with typed columns, filters and sorts.
The visual language: the sidebar, the emoji page icons, the wide serif headings.

Where it stops

The last 20 per cent of a block editor is where editors go to die. Selection across nested blocks, paste from Word, undo that spans a drag, IME input, collaborative cursors.
The recursive data model, where a database row is itself a page containing databases, is elegant and unforgiving. Permissions and rendering both have to terminate.
Real-time collaboration on a tree, with offline edits that merge sanely.
Performance on a workspace with 50,000 pages, which is the only workspace that matters commercially.

What actually protects them

Switching cost measured in years of a company's accumulated internal knowledge.
Templates and a creator economy that markets the product for them.
The data is a graph and graphs export badly, which is a moat whether or not it was designed as one.

Editor's note

An agent produces a convincing Notion in one session. Then you press Ctrl+Z after dragging a nested toggle and watch the document fold in half.

Somebody already did it

Go and look at the original

We would rather you formed your own opinion than took ours. They built the thing; we only measured it.

notion.so ↗