Overview
Notion combines notes, docs, wikis and databases in one workspace. Its database engine renders the same data as tables, boards, calendars, timelines, galleries or lists, which is how one tool replaces a stack of others — at the cost of setup effort and performance limits at scale.
The database is the product, not the editor
Notion looks like a notes app and gets adopted as one, but the reason teams stay is the database engine underneath. A page is just a container; a database is a structured collection of records with properties — status, owner, date, priority, tags, relations — and the same database can be rendered six ways: table, board, calendar, timeline, gallery or list. One content calendar database becomes a calendar view for scheduling, a board grouped by status for weekly standups, and a table for bulk editing, all filtering the same records. That one idea is why Notion replaces Trello boards, Confluence wikis, Google Docs and a lightweight CRM at once: the data lives in one place, and each view is just a lens on it.
The property model is where the real power hides. Relations link records across databases, rollups aggregate them, and formulas compute on them. A client database linked to a projects database, with a formula flagging deals that have gone quiet for thirty days, is a working CRM built in an afternoon.
A concrete example: a content calendar is the most common real-world database, and it is just a list of fields:
| Property | Example value | What it does |
|---|---|---|
| Title | "Notion vs Airtable: which fits" | The record itself |
| Status | Drafting → Editing → Published | Drives the board view and filters |
| Target keyword | notion vs airtable | Feeds the editor's weekly list |
| Publish date | Aug 14 | Drives the calendar view |
| Writer | Ana | Drives the per-writer dashboard |
| URL | notion.com/blog/... | Filled at the end, surfaced in reports |
The same records then render three ways for three jobs: a calendar view shows what goes live when, a board grouped by status is the weekly standup, and a table view handles bulk edits. That is one data set, not three tools that fall out of sync — which is the entire argument for the product in a sentence.
The migration cost is the real price of entry
The subscription is cheap; the setup is not. Notion's flexibility is also its learning curve: relations and rollups are powerful and genuinely confusing to new users, and teams routinely over-structure their workspace in the first month, building ten interlocking databases where one would do. Experienced users' advice is consistently the same: start with community templates instead of a blank page, keep the structure flat, and do not migrate everything — bring over only what is actively used, because a half-migrated wiki that people cannot find things in is worse than no wiki at all. One team reported spending two weeks cleaning up a wiki that had grown organically, then getting the payoff only when new contractors stopped asking where things live.
Where it gets slow and brittle
Notion's limits show up at scale and in automation. Large databases make the app noticeably slower, and offline support is thin — the mobile app is usable, not reliable. The automation layer is the weakest spot: database automations exist (Plus and up), but power users have been hitting the same gaps for years — buttons cannot trigger automations, automations cannot filter on relational properties, and the file property cannot be used in formulas. For deep automation, teams end up routing through Zapier or Make. None of this matters for a wiki or a content pipeline; all of it matters if you intend to run serious project management on it.
What the tiers actually unlock
| Plan | Price | What changes |
|---|---|---|
| Free | $0 | Blocks and databases work; file uploads capped at 5MB, page history kept for 7 days |
| Plus | $10–12 / user / mo | 1GB uploads, 30-day history, automations, guest invites |
| Business | $15–18 / user / mo | 90-day history, SAML SSO, advanced permissions, AI usage included up to a limit |
| Enterprise | Custom | Unlimited history, audit logs, advanced security controls |
The history and upload limits are the hidden differentiators: 7 days on free means last month's version of a page is already gone, which quietly pushes document-heavy teams toward Plus. Notion AI is an add-on ($10/user/month) or a metered allowance on Business, not something the base subscription includes.
Where it fits
- Works for: startups and small teams (roughly 3–50 people) that want docs, wikis and light project tracking in one searchable place; solo operators running a business — CRM, invoicing, content pipeline and journal — without five subscriptions; any team whose pain is information scattered across tools.
- Not a fit for: engineering teams that need Jira-grade issue tracking, dependency graphs and sprint analytics; large organizations with strict permission hierarchies; teams whose work lives offline or in very large datasets, where performance becomes the bottleneck; anyone who wants automation depth out of the box, since that layer is still the weakest part of the product.