Why Notion Works as a SaaS — Lessons for a Workspace Web App

One workspace, not twelve products

Early Notion felt like a doc that could become a table. That elasticity is the magic — and it is expensive to build. Your SaaS MVP should pick one object (a brief, a deal, a lesson plan) and let people nest or tag it. Do not start with a block editor that can do everything. Start with a page that can do the job.

Sharing is a feature, not a setting

Notion spread because a page link is enough. Permissions came later and still feel simple: this page, this workspace. If your web app hides share behind an admin role, you killed the loop. For a v1, “view link” plus “edit if you’re in the workspace” is enough.

Templates teach the product

Empty Notion is a blank page. Templates are how people understand what to do. A good SaaS MVP ships two starter templates that complete the job — not a marketplace. You will learn which fields matter by watching which template people duplicate.

What to ship in a workspace SaaS MVP

Auth, orgs, one resource table, a detail page, comments or activity if the job is collaborative, and Stripe when someone else should pay. Next.js + Postgres covers this. Rich-text can be a simple editor. Real-time multiplayer can wait until two people edit the same page in anger.

• users → workspace → the job object
• One list + one detail view
• Share link on the detail page
• Two templates, not forty

We build the workspace, not the mythology

If your product is “Notion for clinics / studios / funds,” write the job in one sentence. We will tell you which Notion-isms you need in 21 days and which are a 2028 problem. Production web app, you own the GitHub.