The NotionFlow Suite

Problem

Notion is powerful but missing dozens of small, specific things — a clipper, a form builder, a deadline view. Each gap is too small to justify its own standalone product.

Idea

Build one shared architecture — auth, sync, UI shell — once. Then ship a new extension against it every week or two, so each new gap costs days instead of months.

Role

Sole builder, working alongside a small team of AI agents.

Process

Clipper shipped first and kicked off the suite, then Snapper, DailyFlow, PinFlow, FormFlow, TreeView, TemplateFlow, DeadlineFlow, StatusFlow, and RelayFlow followed — ten extensions, one architecture, ten weeks.

Outcome

Ten live Chrome extensions under one suite at notionflow.io.

Lessons

The tenth extension should always be cheaper to build than the first. If it isn't, the architecture isn't actually shared — it's just copy-pasted.