Notion — the calm review from a team that picked markdown instead

Who this is for

Teams that want a single visual workspace for docs, wikis, lightweight project tracking, and customer-facing knowledge bases — without standing up a static-site generator, a git workflow for non-engineers, or three separate SaaS tools. Notion is also genuinely useful as a public publishing surface for things you wrote in markdown elsewhere: a paid PDF mirror, a public roadmap, a hiring page. If your team is comfortable in a code editor and your "docs" already live in a git repo with ADRs and standards, the case for Notion gets thinner — that's our case, and we'll be honest about it below.

What it does well

A short list of things we recognise as genuinely good about Notion, even from the perspective of a team that has consciously not adopted it as our system of record.

• The block model is genuinely well-designed. Every paragraph, list item, image, embed, and table cell is a movable block. The drag-and-rearrange interaction is the cleanest implementation of this idea on the market, and once your team gets used to it, the cost of restructuring a document drops to roughly nothing. This matters a lot for documents that get rewritten often — strategy docs, brand bibles, customer-facing wikis.
• Public-page publishing is one click. Toggling a Notion page from private to public-on-the-web gives you a working URL on notion.site with no build step, no DNS configuration, and no hosting bill. For sharing a draft, a public roadmap, a hiring page, or a one-time digital-product mirror, this is faster than any static-site workflow.
• Databases are flexible without being a database administrator job. Notion databases are the part of the product that most non-technical teams underestimate. A Notion database is a typed, queryable collection with multiple views (table, board, calendar, timeline) — useful for tracking content pipelines, customer interview logs, sprint backlogs, or vendor lists. It will not replace Postgres, but for sub-database team-state needs, it's better than a spreadsheet.
• The API is real and documented. Notion's public API is stable enough to script content sync from a git repo into a public Notion mirror, or to push customer-support metadata back into a Notion database. The auth model (internal vs. public integrations) is straightforward. We have not built this integration, but we have read the spec and verified the surface is real, not aspirational.
• The default voice is restrained. Notion's product surfaces — onboarding, empty states, settings — are written in plain, calm language. The marketing skews enthusiastic, but the product itself is quiet, which matters when you spend hours a day inside it.

What to watch for

Three honest caveats. The first one is the reason Klem HQ does not use Notion as our system of record.

• It is not a substitute for version-controlled markdown. A Notion page does not have a meaningful diff, a commit history you can blame, a branching workflow, or a way to time-travel back to "the version of this doc that existed on the day we shipped." For strategy documents, ADRs, brand standards, and any artifact where "what did we decide on what date, and what was the version before?" matters, a markdown file under git is structurally better. Notion's page-history feature exists but is shallow and per-page; it is not a substitute for git log.
• The free-tier ceiling lands earlier than the marketing implies. Notion's homepage emphasises "free for individuals" and "free for small teams up to N people," which is true on paper. In practice, the file upload limit on the free tier (small per-file size cap), the guest collaborator limits, and the version history retention (limited on free, generous on paid) push most teams that actually use the product onto a paid plan within months. The free tier is a real trial, not a sustainable production tier.
• Lock-in shape: data is exportable, but structure is not portable. Notion exports to markdown or HTML, but the export drops the relational structure of databases, the inline page embeds, the linked-mentions graph, and the formatting fidelity. If you commit to Notion as your knowledge graph, migrating out of Notion is meaningfully expensive in human review time, even though the export button is technically there. We treat this as a real switching cost, not a hypothetical one.

How we use it at Klem HQ

This section is the most honest one in this review.

Today, Klem HQ does not actively use Notion. Our documentation, strategy, ADRs, brand standards, playbooks, and product roadmap all live as markdown files in a git repository. The decision to do it this way is deliberate, not an oversight — we wrote a convention called "standards-first" (规范先行) early in the company, and version-controlled markdown under git is the technical expression of that convention. Strategy decisions live in numbered, append-only ADR files. Brand standards live in brand/*.md. Product playbooks live in docs/playbooks/. The whole knowledge surface is searchable with grep and editable with a text editor.

Where Notion will show up at Klem HQ: the planned one-time mirror of our forthcoming paid digital product, the Indie Forge Developer Playbook (per ADR-0011 and project_klemhq_digital_products.md). The plan is: write the PDF source as markdown in the repo, publish it as the canonical paid artifact via Gumroad, and create a Notion-hosted mirror as a secondary read-only public page for buyers who prefer browser reading. Notion is the right tool for the mirror job because public-page publishing is one click and we don't want to build a custom buyer-facing portal for a single PDF. Notion will not become our system of record; it is purpose-fit for the publish-once-and-stop-touching-it case.

Why we tell you this. A review that claimed "we use Notion every day" when we don't would be the exact opposite of what a calm review section is supposed to be. If you're a team whose documentation needs are different — heavier on real-time collaboration, lighter on version-controlled history, with more non-technical writers than ours has — Notion is a genuinely good choice. The block model and public publishing are real strengths. We just made a different trade-off, for reasons that fit our specific team shape.

Pricing reality

What you'll actually pay versus what the website implies.

• Free (Personal): Unlimited blocks for one person, 7-day page-history retention, small file upload size cap, limited guest collaborators. Usable as a real personal scratchpad; tight as a team trial.
• Plus (per-user per-month, billed annually): Unlimited file uploads, 30-day page history, unlimited guests, custom websites. This is the tier most small teams that adopt Notion end up paying — the free-tier file size cap is usually what pushes them off.
• Business (per-user per-month, billed annually): SSO, longer page history, private team spaces, advanced permissions. This is the "actual company is using this" tier; price step from Plus is meaningful.
• Enterprise: SAML, audit logs, custom contract — priced on request.
• Notion AI: Add-on per user per month for AI features (writing, summarisation, Q&A across your workspace). Separate from the workspace plan price. Worth evaluating only after you've committed to Notion as a system of record — adding the AI add-on to a workspace you don't actively use is a leaking line item.
• Exact current per-user prices: Notion adjusts these periodically; verify on the pricing page at sign-up rather than trusting a number that might be stale.

The honest pricing summary: Notion's list price per seat is moderate. The team-size multiplier is where the cost lands — a 10-person team on the Plus tier crosses into hundreds of dollars per month quickly. For solo founders and small studios, Plus is reasonable; for larger teams, the all-in cost competes with Confluence and Slab and is worth comparing before committing.

Bottom line

Notion is a genuinely well-designed product that we have consciously chosen not to use as our system of record, because version-controlled markdown under git better fits how Klem HQ writes durable decisions. Where Notion will earn its place in our stack is as a publish-once mirror for a forthcoming paid PDF — a specific, narrow job it is well-suited for. If your team's shape is closer to "non-engineers collaborating on living documents" than "engineers committing immutable decision records," Notion's case is much stronger than ours. The strengths are real; the caveats are also real. Pick it for the right job, not as a default.

Affiliate disclosure: If you sign up to Notion via our referral link, Klem HQ earns a small referral fee at no additional cost to you. This review was written before the affiliate sign-up; the "we mostly do not use this" framing is editorial, and we do not adjust review content based on referral fee terms — if the program ToS conflicts with that framing, the link is dropped, not the editorial. See /legal/affiliate-disclosure for full terms.

[Affiliate link slot — BrandSite worker fills in once founder confirms Impact approval]