— DISPATCH · LIVE TEST · 05
Linear's pricing page is a precision instrument. It cuts cleanly for the buyer it was built for and slides off everyone else. We pointed a SaaS Buyer cohort at it and watched the split happen in real time.
Linear sells hard to engineers and only engineers — by design, at a cost.
Would click
0%
Scroll or leave
0%
Brand
Linear
Audience
SaaS Buyer (B2B)
To decision
0s
Synthetic users
0+
The page does not try to be everything. It speaks the language of sprints, deployments, Code Intelligence, and agent automations. That focus is the strategy — and also the filter.
When a non-engineering buyer lands here, they read the same words a PM reads but hear a different message: this is not for you. They leave fast, and the page doesn't try to stop them.
20% clicked. 80% left. Why?
Same surface. Different reads. The minority who clicked — and the majority who didn't.
Workflow-native buyer with social proof and zero budget friction.
“Managing programs means I live in Jira — 600 people migrating out of it in a month hit different. OpenAI on the customer list, free tier so the mortgage isn't a factor. Clicking Continue before I talk myself out of it.”
Sold on the feature, blocked by the Enterprise paywall on Salesforce.
“Tracking feature requests across accounts is literally my job, and this shows revenue per customer — which I've been begging for. But Salesforce is Enterprise-only, and I'd need engineering to adopt this too. Not my call.”
Adjacent function reads the page and finds none of her vocabulary.
“My queries run against datasets with thousands of rows, and this page keeps showing sprint boards and bug tracking. I need something that handles data pipeline management, not developer workflows.”
Non-engineering operator finds no language for his work.
“I spend mornings synthesizing feedback from agency partners into recommendations, and this page keeps talking about sprints and deployments. There's nothing here about competing stakeholder positions or policy cycles.”
For the right buyer, the proof is loud. Customer logos carry weight. The free tier removes budget friction at the trial stage. The revenue-per-customer signal in the feature list lands hard with anyone managing requests across named accounts. When the audience matches, the page closes.
Two failure modes surfaced. The first is audience drift: analysts, operators, and adjacent functions landed on the page, scanned for their workflow vocabulary, and found none of it. They left within a minute.
The second is the Enterprise gate. Salesforce integration — the exact hook a Customer Success buyer needs to justify adoption — is locked behind custom pricing. The buyer who would champion the tool internally can't even price it without a sales call.
This actually shows revenue data per customer, which I've been begging our product team to care about. But Salesforce is Enterprise-only, and I'd need engineering to adopt this too. That's not my call.
— VERDICT
The one fix that moves the most
Unlock the Salesforce integration one tier earlier, or surface a transparent price for it. The cohort most likely to champion Linear outside engineering — Customer Success, RevOps, account-facing PMs — is currently blocked by an opaque Enterprise quote at the exact moment they're convinced.
Audience drift is harder to solve and probably shouldn't be solved on this page. Linear's focus is its moat. But the integration paywall is friction inside the converting cohort, which is the expensive kind.
1,800+ synthetic users browsed linear.app. Decision arrived in 329 seconds.
Five and a half minutes is the window. That's what it takes a real buyer to read your pricing page, run it against their workflow, and decide whether to click. We run this loop before launch so the bleeding happens in synthetic, not in production.