Notion Tests Asterisked Plan Names and Solid CTAs on Pricing Page

The ABWatcher blog

Notion Tests Asterisked Plan Names and Solid CTAs on Pricing Page

ABWatcher caught Notion running a same-session pricing test with asterisked plan names, eligibility footnotes, extra feature rows, and solid-blue CTAs — here's what it signals for pricing-page CRO.

Maya Patel

Senior CRO Strategist · · Updated

Notion's pricing page (notion.com/pricing) is showing two different faces to Chrome visitors on the same day — and one of them adds asterisks to "Plus" and "Enterprise."

TL;DR

  • ABWatcher flagged the divergence via same_run_variance detection at 75% analyst confidence.
  • One of seven visits (visit 5, Chrome) showed a distinct variant; the other six — including two other Chrome sessions — showed the standard page.
  • Variant adds asterisks to Plus* and Enterprise* plan names with a footnote: "Plans may not be available for every workspace."
  • Variant inserts two new feature rows: Premium support and Customer success manager.
  • Variant swaps outlined CTA buttons for solid-blue CTAs on Plus and Business tiers.
  • Because the difference appeared within Chrome (not across browsers), it points to a cookie/session-bucketed experiment rather than a rendering artifact.

What did ABWatcher actually detect on Notion's pricing page?

ABWatcher found a single Chrome session rendering a materially different pricing table than six concurrent sessions on the same page. The baseline experience — seen in the majority of visits — shows Notion's familiar Free, Plus, Business, and Enterprise tiers with unmarked plan names and outlined CTA buttons. The outlier, visit 5, added asterisks to two plan names, a disclaimer footnote about workspace eligibility, two additional feature rows, and switched the mid-funnel CTAs from outlined to solid-blue.

The detection method matters here. same_run_variance means the divergence showed up between visits captured in the same monitoring run, using the same browser engine. That rules out the most common false positive in pricing-page monitoring: a browser or OS rendering quirk masquerading as a test. When two of three Chrome visits match each other and the third doesn't, the more defensible read is a cookie- or session-bucketed A/B split, which is why our analyst confidence sits at 75% rather than lower.

Why would Notion asterisk plan names and add an eligibility footnote?

The footnote likely tests whether transparency about workspace-level plan restrictions reduces downstream support tickets and checkout abandonment. Notion's plan availability isn't uniform — enterprise-negotiated terms, legacy pricing, and regional restrictions can all affect which tiers a given workspace can actually purchase. Surfacing that ambiguity earlier, via a lightweight asterisk-and-footnote pattern rather than a modal or gate, is a low-friction way to set expectations before a prospect reaches checkout and discovers their workspace doesn't qualify.

This is a classic Confidence-Lift-Risk tradeoff. The confidence case: fewer surprised users mid-checkout, fewer support escalations, cleaner sales handoffs for Enterprise. The risk case: any asterisk or disclaimer on a pricing page introduces friction at exactly the moment a visitor is evaluating cost, and Baymard's research on checkout and pricing transparency consistently shows that unexplained caveats increase hesitation unless the footnote is immediately legible. If Notion's footnote text is too vague, it could suppress conversion on Plus and Enterprise without the offsetting trust benefit.

Does adding feature rows and solid CTAs change buying behavior?

Adding "Premium support" and "Customer success manager" rows targets plan justification, not just plan comparison. These rows don't change what's already included — they make previously implicit value explicit at the point of comparison, which is a well-worn tactic for justifying the price gap between Business and Enterprise. Pairing that with solid-blue CTAs on Plus and Business (versus outlined) is a visual-hierarchy move: solid fills typically read as higher-affordance actions, nudging attention toward the middle tiers where SaaS pricing pages generate the most revenue per acquisition.

Table stakes reminder for anyone running similar tests: CTA fill vs. outline is one of the lowest-cost, highest-frequency tests in pricing-page CRO, but its effect size is highly context-dependent. Nielsen Norman Group's guidance on visual hierarchy and button affordance notes that fill changes matter most when they create contrast against a busy layout — exactly the situation on a four-tier comparison table where every column is competing for the eye.

How does this variant compare to Notion's standard pricing page?

The table below summarizes the two experiences ABWatcher observed across seven monitored visits.

Element Standard (6 of 7 visits) Variant (visit 5, Chrome)
Plan names Plus, Enterprise (unmarked) Plus*, Enterprise*
Footnote None "Plans may not be available for every workspace"
Feature rows Standard feature set + Premium support, + Customer success manager
CTA style (Plus/Business) Outlined buttons Solid-blue buttons
Browsers observed Chrome (x2), other engines Chrome (x1)
Detection method — same_run_variance
Analyst confidence — 75%

Notion's own templates marketplace includes a CRO toolkit template built by a third-party creator — a small signal that Notion's ecosystem is generating its own conversion tooling in parallel with what the core team is testing on its own pricing surface.

What should CRO teams take from this detection?

If you run a multi-tier pricing page, treat plan-eligibility ambiguity as testable copy, not just a legal or support afterthought. Score it with a simple ICE pass: Impact is moderate (affects mostly Enterprise and edge-case Plus buyers), Confidence is medium (transparency research is directional, not universal), Ease is high (footnote and asterisk are cheap to ship). That combination — moderate impact, low cost — is exactly the profile that justifies fast-turnaround testing rather than a full roadmap slot.

This detection was logged 12 March 2026 and remains at 75% confidence pending a repeat sighting; ABWatcher will flag if the variant persists or expands to non-Chrome sessions in future runs.

Common questions

What is same_run_variance detection?

Same_run_variance is ABWatcher's method for flagging when two visits using the identical browser engine, in the same monitoring run, render different page experiences. It's a stronger signal of a genuine A/B test than cross-browser differences, which are more often rendering artifacts rather than deliberate experiment buckets.

Why does an asterisk on a plan name matter for conversion?

An asterisk paired with a footnote sets expectations about plan eligibility before a user commits to checkout. Done well, it can reduce abandoned purchases and support tickets from users who discover restrictions late. Done poorly, it adds hesitation-inducing ambiguity at the exact moment a buyer is deciding.

Is a 75% confidence detection reliable enough to act on?

Seventy-five percent confidence means the pattern is likely a genuine experiment but hasn't been confirmed by repeat sightings across multiple runs. Teams should treat it as a strong directional signal worth monitoring, not a confirmed, finalized test result to copy outright.

Should other SaaS pricing pages test solid vs. outlined CTAs?

Yes, but only with adequate traffic to detect a real effect — CTA fill changes typically produce single-digit percentage lifts, not double-digit swings. Pair the visual test with click-tracking on each tier to confirm the fill change shifts attention toward the intended plan rather than just changing aesthetics.

How often does Notion test its pricing page?

ABWatcher doesn't have a published cadence for Notion specifically, but pricing pages at high-traffic SaaS companies are typically among the most frequently tested surfaces, often cycling variants monthly or quarterly. This detection represents one observed instance, not a confirmed testing schedule.

Read next

More from the ABWatcher blog

From the glossary

Vocabulary the article uses. See all terms →

  • Shrinkage Estimator— A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
  • Flicker Test— A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
  • Pre-Experiment Bucketing Audit— A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
  • Above-Fold Exclusion Rule— A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
  • Flicker-Free Testing— A technical setup that prevents users from briefly seeing the original page before a test variant loads.
  • Orthogonal Test Design— A test structure where multiple variables are changed independently so their individual effects can be measured without interference.

See more like this

ABWatcher catches A/B tests like this across 1,000+ brands.

Watch live experiments at 1,000+ high-converting brands, complete with hypothesis and takeaway. 7 days of Pro, free, no card, then Free forever for ten watched companies.