PUBLISHED OCTOBER 2026 · FOUR PRICING PAGES, NOBODY IN THE LOOP

We read four pricing pages with nobody in the loop: Linear, Notion AI, Airtable and Retool. Retool shows its first paid price 1 character from the words saying what that price is per. Notion AI takes 315.

Four pricing pages, fetched and counted by code with no model in it — no buyer, no decider, nobody reading the page. Measure how far each page puts its first paid price from the nearest words saying what that price is per, and the readings separate: 1 character on Retool, 16 on Linear, 19 on Airtable, 315 on Notion AI. Counted a second way, the same pages differ in where they keep what it costs: of the 103 controls on Airtable’s pricing page, 5 open a new tab to material of Airtable’s own on a separate site. Retool’s pricing page does that on 4, out of 231 controls. Linear’s 64 controls do it on none, and Notion AI’s 74 open no new tab at all.

HOW THIS WAS READ, AND BY WHAT

Nobody was in the loop. No ghost user walked these pages, no model decided anything, and not one sentence or number here was written by one — which is why this is a reading and not a run, and why there is nothing on it about where a person got stuck.

The instrument: Each page was fetched once and watched until its own list of controls stopped changing, then counted. Nothing was signed up for and nothing on this page is a sentence anybody or anything wrote about these products: the numbers are counts of controls and character offsets, taken off each page as it arrived.
When: Both readings were taken within the same hour, and the sitting is the unit rather than the date: a pricing page is edited without notice, so a reading is a fact about the moment it was taken and nothing else.
Pages read: airtable.com/pricingretool.com/pricinglinear.app/pricingwww.notion.com/pricing

WHERE EACH ONE KEEPS WHAT IT COSTS

Counted on the pricing pages themselves.

We opened each pricing page, waited until its own list of controls stopped changing, and counted the controls that send a reader somewhere else in a new tab — recording, for each one, whether it goes to material of that company's own on a separate site or to somebody else's. These are a fact about these pages on 5 October 2026 and nothing else, and anyone can open the same pages and count them again.

Pricing page	Controls on the page	Open a new tab	…to its own material on a separate site	…to somebody else's site
Airtableairtable.com/pricing	103	18	5community.airtable.com, support.airtable.com	8
Retoolretool.com/pricing	231	10	4docs.retool.com	2
Linearlinear.app/pricing	64	6	0	4
Notion AIwww.notion.com/pricing	74	0	0	0

AND HOW FAR THE PRICE IS FROM WHAT IT IS PER

The same pricing pages, read a second way.

A price on its own is not what something costs: the same number means one thing charged by the month and another charged for a year up front. So we read the rendered text of the same pages again on 5 October 2026 and measured one distance — from the first paid price the page shows to the nearest place that page names a billing period.

Pricing page	First paid price → nearest billing period	Closest any paid price gets	Paid prices within two lines of one	Periods the page names
Retoolretool.com/pricing	1 char	1 char	2 of 13	annual
Linearlinear.app/pricing	16 chars	16 chars	2 of 2	annual
Airtableairtable.com/pricing	19 chars	1 char	4 of 11	annual + monthly
Notion AIwww.notion.com/pricing	315 chars	315 chars	0 of 5	annual + monthly

WHY WE TRUST THIS ONE

There are three ways of asking the question in that table — the first paid price, the closest paid price, and how many of a page's prices sit next to a phrase naming a period — and the tool that assembles this page refuses the whole group unless all of them single out the same page. The reading was chosen after these numbers were on screen, and a finding that depends on which reading we picked is a finding about us rather than about anybody's product. It did not have to agree, and it did:

The odd one out on every reading — Notion AI

What this is not: a claim that any of these pages fails to say what its prices are per. Each one says so, and the column on the right shows which periods each names. What is measured here is how far a reader travels between the two, on one rendering of one page — and anybody can open the same page and measure it again.

WHAT THIS PAGE LEAVES OUT

What we read and are not publishing.

What a page does when a billing-period control is pressed: The sitting behind this page carries a press reading of each of these pages, and this page publishes none of it. Our own instrument recognises a billing-period label on some of these pages and not on others, which is a limit of ours rather than anything about them, and a reading across the group is worth nothing while part of the group is beyond what we can read. The pages where it does read are already published, with their readings, on the three-product comparison.
Anything a person did: Nobody walked these pages. There is no buyer here, no model decided anything, and not one sentence on this page was written by one — so there is nothing here about where somebody got stuck, and these numbers are not evidence about what a reader would do.

THE FINDING

Notion AI is the odd one out here, and it is the odd one out on each of the ways we measured the same thing: the first paid price on its pricing page, the closest paid price on it, and how many of its paid prices sit beside words naming a billing period at all. 0 of its 5 do. That is not a verdict and there is no advice attached to it — a page can be the easiest of these to read and still keep what the price is per somewhere else.

← Everything we have published, including the runs with a buyer in them