Notion has built an excellent AI activation engine (five minutes from signup to a working relational database), then hidden it behind three screens of its own commercial priorities, and forgotten to show the user what it built.
A brand-new account, walked end to end on the free tier as a founder setting up a shared team workspace: the exact profile most likely to convert and most likely to leak.
Notion's AI workspace builder is genuinely very good. Answer one question about your role, press a button labelled "Build it", and roughly forty seconds later the sidebar contains Projects, Tasks, Meetings and Docs: real databases, with real relations between them, seeded with plausible starter rows. For a category whose historic failure mode is the paralysing blank page, this is a serious piece of product engineering. It resolves the oldest complaint about Notion almost entirely.
The problem is everything wrapped around it. Between the account existing and that engine starting, a new user is asked to invite their teammates, choose a paid plan, and download the desktop app: three consecutive screens, none of which serves the user, all of which serve Notion. The user has at this point seen nothing the product can do. They are being asked to recruit, to pay, and to install, on the strength of a brand promise alone.
That miss compounds at the other end. Notion's Home, the surface a returning user lands on, the thing that decides whether day two happens, is empty. Not sparse: empty. The words "Welcome home" on white space, for an account that had just had four populated databases built into it minutes earlier. Above them sits a banner announcing a sidebar redesign to a user six minutes old who has no previous sidebar to compare it to.
The rest is smaller but consistent in direction. Two of the three suggested starting points on the first screen inside the product are padlocked, gated behind the plan the user declined one screen earlier. The free plan's feature list is set in a grey that fails accessibility contrast standards. The plan comparison describes the free tier as "1000 blocks" to a person who has not yet learned what a block is.
None of this is incompetence. It reads as a funnel that has been optimised one screen at a time, each addition locally justified, with nobody accounting for the cumulative cost to the person walking through all of them in sequence. That is the most common way good activation funnels rot, and it is very fixable.
All values below were read from the live DOM during traversal: 728 CSS custom properties resolved from getComputedStyle, not sampled from screenshots or taken from documentation.
Stack: ui-sans-serif, -apple-system, system-ui, "Segoe UI Variable Display", Helvetica, Arial. No webfont is loaded for UI chrome, a deliberate performance choice that renders natively per-platform. Weights 400 / 500 / 650 / 800. Buttons run 14px / 500.
#A19E99 on white at 14px, a ratio of 2.66:1, against a WCAG AA requirement of 4.5:1. The primary blue CTA renders #F3F9FD on #2783DE at 3.72:1, also below AA. The second is systemic: that button style recurs throughout the product.Severity is assigned against one bar only: does this help a brand-new user reach a genuinely useful artefact quickly, and come back tomorrow? Where a choice appears to be a deliberate design decision rather than a defect, it is logged as a trade-off, with the caveat that intent is inferred from outside, not confirmed.
Each carries a named principle from the evaluative framework. Three matter more than the rest, R1, R2 and R13, because each governs a different moment the user decides whether Notion is worth continuing with: seeing the value, returning to it, and being pulled back to it.
#A19E99 on white at 2.66:1. The primary blue CTA renders #F3F9FD on #2783DE at 3.72:1. Both fall below the 4.5:1 AA threshold for normal text.#7D7A75 (secondary, comfortably AA at 14px). Darken the primary button to approximately #1A6DC0, or set its label to pure white and increase weight. Add an automated contrast gate to the token pipeline so semantic pairings are checked at build time.Sharpening pass. These are observations rather than separate recommendations. Where they change a priority, they are folded into the numbered set above.
Effort: S hoursβ1 day Β· M days Β· L 1β2+ weeks. Impact β ββ β β .
| # | Fix | Effort | Impact | Why now |
|---|---|---|---|---|
| R5 | Remove padlocked cards from free-tier first-run suggestions | S | β β β | Two of three first actions currently fail; config change, no new surface |
| R7 | Raise free-tier text and primary-button contrast to AA | S | β β | Compliant tokens already exist; systemic fix, one-line change |
| R8 | Rewrite "1000 blocks" and tier bullets as outcomes | S | β β | Copy-only; sits on the screen where money is decided |
| R9 | Unify the skip affordance across onboarding steps | S | β | Copy and layout only; removes a false forced-step signal |
| R12 | Move the desktop-app prompt to end of first session | S | β β | Pure sequencing; recovers a pre-value interruption |
| R2 | Suppress product-change banners for accounts < 7 days old (partial R2) | S | β | Audience rule on an existing banner system; separable from the Home rebuild |
| R15 | Collapse the sidebar below a mobile breakpoint; hide banners on narrow viewports | S | β β | Two contained CSS fixes turn an unusable screen into a survivable one |
| R13 | Remove tier-locked features from the free-user email's primary CTA | S | β β | Copy and audience targeting only; the current CTA points free users at a paid feature |
| # | Fix | Effort | Impact | Why |
|---|---|---|---|---|
| R1 | Render created databases inline at the "All set" reveal | M | β β β | The single highest-value change in the audit; inline DB previews already exist elsewhere in the product |
| R3 | Relocate the invite step to after the reveal, framed on the artefact | M | β β β | Highest-value step for a team product, currently placed where it converts worst |
| R10 | Make slash-menu "Suggested" account-age and plan aware | M | β β | Highest-attention slot in the most-used menu, currently spent on promotion |
| R11 | Replace the bottom starter bar with inline chips at the cursor | M | β β | Moves guidance 550px closer to where attention already is |
| R13 | Rebuild the first activation email around the user's own workspace, behaviourally triggered | M | β β β | The opening return touch currently points away from everything that would work |
| R14 | Bring the template gallery in-app with a role-matched opening shelf | M | β β | Stops ejecting high-intent users onto a marketing page with a logout button |
| # | Fix | Effort | Impact | Why |
|---|---|---|---|---|
| R2 | Rebuild Home around the user's own content and progress | L | β β β | The surface that decides day two currently does no retention work at all |
| R6 | Side-by-side wizard with live workspace preview and per-item progress | L | β β β | Turns the interview into co-creation; the pattern's largest documented activation lift |
| R4 | Default new signups to Free; move plan choice to first real limit | MβL | β β | Removes monetisation from the learning path; needs billing and lifecycle coordination |
Targets are framed as directional deltas rather than absolutes. An outside auditor has no access to Notion's baselines, and a specific number quoted without one would be fabrication.
See your funnel this clearly
This audit named 15 conversion leaks in Notion's activation journey, each one diagnosed, prioritised, and anchored to a behavioural principle. Sitepeep does the same for your product: every leak across your funnel, a prioritised roadmap, and the science behind each fix.