coExploro
Teardowns

Product teardown

Notion product teardown

By coExploro · Captured · Updated

Reviewed and edited by coExploro · Independent, not affiliated · Public methodology · Corrections: support@coexploro.com

How this page was made: Drafted by four AI analysts from a capture of www.notion.so on . Checked by coExploro’s founder on .

A curated sample showing what coExploro observes about public homepages, pricing pages, feature pages, and UX signals.

Illustrative public sample. coExploro is not affiliated with Notion.

Sample output

Overall score 91/100

PM 92

UX 85

Summary Card + findings

Category
Connected workspace and docs
Captured
Published
Updated
Visit product

Summary Card

The shareable readout before the full canvas.

This public version uses the same compact card pattern as private teardowns: one score, four persona signals, and the strongest findings compressed into a card a product team can forward.

Read the methodology

Overall score

91/100

Confidence

mid

PM

92/100

UX

85/100

coExploro

Notion

teardown · captured 2026-08-08

Overall score · good
91
mid confidence
PM
92
MKT
95
UX
85
DSG
92

Top findings

  • Seventeen questions sit under the pricing table
  • The page sells a workspace, not a notes tool
  • Use-case links carry the segmentation
coexploro.com/teardowns/notionView full teardown

Findings

What the personas surfaced.

UX

Medium impact

Seventeen questions sit under the pricing table

The pricing FAQ opens with 'How does Notion AI use my data?' and only then asks 'Where can I find my invoices?' and 'What are your accepted payment methods?' Data handling comes first, ahead of the billing mechanics.

Evidence: How does Notion AI use my data? · Seen on www.notion.so/pricing, FAQ below the plan tables, first question · Captured · Indirect evidence

PM

High impact

The page sells a workspace, not a notes tool

Copy describes a place where teams and agents work together, and AI appears throughout the pricing page. The word "notes" does not lead anywhere on the captured pages.

Evidence: Where teams and agents Ship together. · Seen on www.notion.so, hero headline · Captured · Direct evidence

Marketing

Medium impact

Use-case links carry the segmentation

A grid under 'See what Notion can do' lists entries such as 'Triage product feedback', 'Resolve support tickets in Slack' and 'Respond to security alerts faster'. One horizontal product addresses several buying contexts from one homepage block.

Evidence: Triage product feedback · Seen on www.notion.so, 'See what Notion can do' link grid, first entry · Captured · Direct evidence

Design

Low impact

Five icon colours carry no shared meaning

The use-case links carry icons in five colours: blue, amber, red, green and indigo. The palette does not encode a category that the captured copy names.

FAQ

Public sample notes.

This sample covers pages that were publicly visible on . No account, private data or share link is involved. It carries observations only. The underlying run does produce recommendations, but they are written for someone deciding how to compete with the product, which is not what a public page about that product should say.

Marketing scores 95 and UX scores 85 — why the gap?

They answer different questions. Marketing weighs how convincing the page is; UX weighs how it holds up under interaction. UX scored 85 against 95 for Marketing. Its one major issue was a guess about phones: that the pricing page's feature comparison table would need sideways scrolling or break its layout there, which the desktop capture could not check.

What does Notion's pricing FAQ cover besides AI data use?

After invoices and accepted payment methods, it covers block limits, student discounts, analytics tiers, how members and paid seats are charged, plan changes, cancellation, failed payments and refunds.

Which use cases does Notion's homepage list?

The entries under 'See what Notion can do' include triage product feedback, resolve support tickets in Slack, respond to security alerts faster, automate weekly reporting, and create your own developer tools.

Next

Run the same format on a product you care about.

Start a teardown