Notion lists Free at $0, Plus at $10 per member per month, Business at $20, and Enterprise by quote on its current public pricing page. Total cost depends on members versus guests, workspace design, AI entitlement, permissions, migration, administration, integrations, records needs, and the plan actually offered at checkout.
Official public sources checked 15 September 2026. Prices below are USD list-price references, not a quote. Country, currency, tax, reseller, promotion, contract, legacy subscription, quantity, and renewal date can change the payable amount.
Published plan-price snapshot
| Plan | Billing basis | Published rate | What to verify |
|---|---|---|---|
| Free | Public list | $0 | Published collaboration and usage limits apply |
| Plus | Public list | $10 | Per member per month |
| Business | Public list | $20 | Per member per month |
| Enterprise | Contract | Custom | Contact sales |
A price row answers only the starting arithmetic. Before approval, preserve the dated vendor page or quote, record the currency and billing term, and identify every population that will be charged. If the vendor page and order form differ, the signed order form and governing contract control the purchase.
How Notion billing changes total cost
- Notion pricing is workspace-based and generally distinguishes members from guests. Workspace boundaries and guest permissions can materially change both governance and billable count.
- AI packaging and availability can change; verify whether the quoted plan includes the intended AI functions, usage, and data controls.
- File uploads, page history, teamspaces, permissions, SAML, audit, domain, security, analytics, and support needs can change the plan decision.
- Migration from documents, wikis, databases, and project tools requires structural mapping, permissions, validation, owner assignment, and an archive decision.
Illustrative annual license baselines
The examples use the second paid public plan shown above where available. They are reproducible arithmetic, not a forecast or recommendation.
| Population | Assumption | Annual baseline | Excluded |
|---|---|---|---|
| 25 paid users | Business · Public list | $6,000/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
| 100 paid users | Business · Public list | $24,000/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
| 250 paid users | Business · Public list | $60,000/year | License baseline only; excludes tax, add-ons, implementation, migration, support, internal labor, and discounts. |
Cost drivers the quote must expose
- Paid members, guests, teamspaces, multiple workspaces, and permission architecture
- Plus, Business, or Enterprise controls for history, identity, audit, security, and administration
- AI entitlement and limits, integrations, automation, storage, and support
- Content/database migration, cleanup, governance, training, and ongoing administration
- Duplicate knowledge/project tools, annual commitment, expansion, renewal, and export
Build base, expected, and stress cases. A useful model separates recurring licenses and consumption from one-time vendor services, internal implementation effort, dependent tools, and exit work. Record unknown values as a range with an owner and decision deadline rather than silently entering zero.
Questions to put in writing
- Which collaborators need member access rather than guest access, and why?
- Will separate workspaces create duplicate paid membership or governance gaps?
- Which AI functions and limits are included in the actual offer?
- Which permission, audit, identity, retention, and export requirements force Business or Enterprise?
- How will databases, relations, files, permissions, owners, and archived content migrate and later export?
Renewal and exit checks
Record the initial term, renewal term, auto-renewal status, notice deadline and delivery method, protected pricing, uplift rule, minimum quantity, reduction window, reassignment rights, usage true-up, data-export method, post-termination access, deletion schedule, and retained-data exceptions. Test the export before the renewal decision if the product will hold business-critical records.
Official sources used
PR97 summarizes public vendor information for comparison. It has not inspected your tenant, order form, reseller proposal, or negotiated contract. Recheck the linked official source and written quote on the day of decision.
Normalize the quote in one worksheet
Capture plan, billable unit, allowances, services, internal cost, renewal, and exit assumptions beside their evidence.
Notion approval record
The approval should state which operating roles require this service, why the selected edition is necessary, and which evidence proves the mandatory workflow. For Notion, record the exact quote, plan, billable population, included allowance, add-on, service scope, implementation owner, and first renewal deadline beside the decision.
Commercial facts to reconcile
- Notion pricing is workspace-based and generally distinguishes members from guests. Workspace boundaries and guest permissions can materially change both governance and billable count.
- AI packaging and availability can change; verify whether the quoted plan includes the intended AI functions, usage, and data controls.
- File uploads, page history, teamspaces, permissions, SAML, audit, domain, security, analytics, and support needs can change the plan decision.
- Paid members, guests, teamspaces, multiple workspaces, and permission architecture
- Plus, Business, or Enterprise controls for history, identity, audit, security, and administration
- AI entitlement and limits, integrations, automation, storage, and support
- Content/database migration, cleanup, governance, training, and ongoing administration
Reviewer questions
- Which collaborators need member access rather than guest access, and why?
- Will separate workspaces create duplicate paid membership or governance gaps?
- Which AI functions and limits are included in the actual offer?
After launch, compare the first invoice with provisioned access and expected usage. Review adoption by required role and workflow at 30, 60, and 90 days. Before notice is due, test a current export and decide whether to retain, resize, renegotiate, replace, or cancel. Keep this evidence with the order form so future reviewers can reproduce both the cost and the reason for the purchase.