ExperienceFrictionsImprovements
Get Started
Back to linear.app
  1. linear.app
  2. Report

Experience

How well does this page work for human visitors?

64
Needs work
CriticalNeeds workStrong
1Cognitive Clarity7.0
2Decision Clarity5.0
3Trust Signal7.0
4Motivation Strength6.0
5Comfort Level7.0
6Flow Coherence8.0
7Identity Match6.0

Cognitive Clarity

7.0
Narrative

Linear's page is well-structured at the macro level — four tiers, grouped comparison table, clean design — but the feature inheritance model and per-card billing toggles create localized cognitive friction that a developer audience will notice and find sloppy.

What's working
  • 4 plan tiers (Free, Basic, Business, Enterprise) — within the 3-4 sweet spot for pricing pages
  • Feature comparison table is well-organized with section headers: Core, AI and agent workflows, Integrations, Team management, Analytics & Reporting, Linear Asks, Security, Support
  • Dark, minimal aesthetic with consistent typography reduces visual noise — Aesthetic-Usability Effect working in Linear's favor
What's hurting
  • Billing toggle appears per-card (Basic and Business show individual toggles) rather than as a single global switch — asymmetric interactive element breaks the comparison frame
  • Feature comparison table is extremely long — 40+ rows across 8 categories — requiring significant scroll investment before reaching Security/Compliance features that enterprise evaluators need
  • 'All [tier] features +' inheritance notation in plan cards requires users to mentally reconstruct cumulative feature sets across 4 tiers without an expand/link to inherited features
Principles
Frictions
  • Per-card billing toggles (Basic, Business) instead of a single global toggle create asymmetric comparison frameMedium

Decision Clarity

5.0
Narrative

The absence of a recommended-plan badge combined with identical 'Get started' labels across all self-serve tiers means Linear forces every visitor to self-navigate a 4-tier decision without a satisficing shortcut — the highest-weighted dimension for a pricing page is the page's clearest gap.

What's working
  • The Business plan card CTA appears with slightly different visual weight (filled white button vs. outlined buttons for Free and Basic) in the screenshot — this is a weak but real visual hierarchy cue
  • Enterprise card correctly differentiates with 'Contact sales' — positive Choice Architecture separating sales-led from self-serve paths
  • 'or contact sales' secondary link below Business CTA is the only plan-specific cross-sell signal — good instinct, weak execution
What's hurting
  • No 'Most popular', 'Recommended', or equivalent badge on any plan card — confirmed from screenshot and pre-detected pattern analysis (screenshot evidence)
  • All four self-serve plan cards use identical CTA label: 'Get started' — no label differentiation to signal which tier suits which visitor
  • Link data shows alternating /signup and /settings/plans hrefs for identical 'Get started' CTA text — dual-audience routing where new users hit /signup and existing users hit /settings/plans. Both appear per plan card, not a per-plan inconsistency, but still creates potential confusion for link-inspecting developers.
  • Bottom-of-table CTAs repeat the same equal-weight options without any new decision aids — badges, summaries, or 'right for you if...' copy — compounding Decision Fatigue after 40+ rows of scrolling
Principles
Frictions
  • No recommended plan badge — all four self-serve tiers have identical visual weightHigh
  • Bottom-of-table CTAs repeat equal-weight plan options with no new decision aids after 40+ rowsHigh

Trust Signal

7.0
Narrative

Linear's trust signals are present and credible — especially the developer-brand logos and security table — but they're positioned for general credibility rather than plan-selection confidence; no testimonial or proof point appears adjacent to a plan card.

What's working
  • 'Trusted by more than 25,000 companies' stat with logo strip featuring Vercel, Cursor, OpenAI, Coinbase, Cash App, Ramp — high-credibility developer-brand logos directly relevant to the target audience
  • 'Customer stories →' link near the logo strip signals proof depth beyond surface logos — Authority Principle reinforcement
  • Security section in comparison table (SSO, SCIM, HIPAA, Audit log, IP restrictions) signals enterprise-grade credibility for compliance-minded evaluators
  • Footer links to Privacy, Terms, DPA signal legal transparency — appropriate for B2B
  • GitHub, X (Twitter), YouTube social links in footer signal active community and product investment
What's hurting
  • Logo strip positioned below plan cards and CTAs — visible but not at the highest-anxiety decision moment (plan card level)
  • No testimonials on the pricing page — homepage has 3 ('You just have to use it and you will see', 'Linear helps us be action biased', 'It has the right opinions for fast moving teams') but these don't appear at point of plan selection (Message-Match break confirmed by pre-detected pattern)
  • No payment security badge, 'no credit card required' micro-copy, or money-back guarantee near plan CTAs
Principles
Frictions
  • Testimonials present on homepage, absent on pricing page — trust signal degrades at highest-intent momentMedium

Motivation Strength

6.0
Narrative

The page tells visitors what features exist per tier but never tells them why those features matter or what outcome they'll achieve by upgrading — it's a feature inventory, not a motivation engine.

What's working
  • The price anchor ($0 Free → $10 Basic → $16 Business) creates natural value progression — Anchoring Effect working implicitly
  • '25,000 companies' trust stat is adjacent to the logo strip — provides social momentum context
What's hurting
  • Page H1 is simply 'Pricing' — no value proposition, no outcome framing, no reason to upgrade before the price is shown
  • Plan subheadings use functional descriptors: 'Free for everyone', 'Billed yearly' — no audience targeting or outcome framing per plan ('For solo devs', 'For growing teams')
  • Feature labels like 'Triage Intelligence', 'Linear Agent automations (beta)', 'Linear Asks' are internal product names — no explanation of what they do or why the visitor should care
  • Closing section headline 'Built for the future. Available today.' is aspirational brand copy with zero plan-selection utility — recency position wasted on brand narrative rather than decision reinforcement
  • No 'save X% annually' savings quantification visible on the billing toggle — the toggle exists but the incentive to switch is unstated
  • No testimonials citing specific outcomes ('We shipped 40% faster', 'Cut sprint planning from 3 hours to 30 minutes') — homepage has directional quotes but they're not on this page
Principles
Frictions
  • Feature labels like 'Linear Agent automations (beta)' and 'Triage Intelligence' are internal names with no outcome explanationHigh
  • Billing toggle defaults to 'Billed yearly' but shows no savings percentage — the incentive to accept annual is invisibleMedium
  • 'Built for the future. Available today.' closing headline wastes the recency position on brand aspirationLow

Comfort Level

7.0
Narrative

The Free tier is the strongest comfort signal on the page — but Linear leaves several low-cost reassurance opportunities untaken: no 'no credit card required' copy, no annual savings quantification, no cancellation language, and a default-ON annual billing toggle without stated exit terms.

What's working
  • Free tier ($0, no credit card implied) dramatically lowers commitment anxiety — developer audience can try the product without any financial exposure
  • 'Get started' CTA label is low-commitment phrasing — better than 'Subscribe' or 'Buy now'
  • Privacy, Terms, DPA links in footer — visible legal transparency for B2B procurement
  • Startups program link in footer — signals flexibility for early-stage companies, reducing lock-in anxiety for smaller teams
What's hurting
  • No 'no credit card required' micro-copy near any CTA — the implication is there (Free tier exists) but it's not stated explicitly, leaving room for ambiguity
  • Basic and Business show 'Billed yearly' toggles in ON position by default — per-card billing toggle default is ON, creating implicit annual commitment assumption without clearly stating the exit terms
  • Enterprise shows 'Annual billing only' — transparent about lock-in, but no indication of minimum contract size or exit terms
  • No cancellation, refund, or money-back language anywhere on the page
Principles
Frictions
  • No 'no credit card required' or 'cancel anytime' copy near self-serve CTAsLow

Flow Coherence

8.0
Narrative

The page's information architecture is sound and follows the industry-standard pricing page flow effectively — the main flow coherence issue is the comparison table losing sticky column headers during deep scrolling, which creates orientation loss for the users who need the table most.

What's working
  • Logical top-to-bottom flow: Plan cards → Trust logos → Feature comparison table → Closing CTAs — the standard pricing page information architecture
  • Feature comparison table section headers (Core, AI and agent workflows, Integrations, Team management, Analytics & Reporting, Security, Support) provide clear wayfinding through a long table
  • Closing CTA section ('Built for the future. Available today.' + 'Get started' + 'Contact sales') provides a logical decision point after the comparison table
  • Navigation is consistent and sticky — users can always find their way to other product areas or return to the top
  • No progress indicators needed (single-page decision, not a multi-step flow) — absence is appropriate here
What's hurting
  • The comparison table loses column headers (plan names) as users scroll deep — enterprise evaluators reading row 30+ of the security section have lost context for which column maps to which plan
  • Closing CTA section brand headline ('Built for the future. Available today.') interrupts the decision-completion flow — the narrative shift from feature evaluation to brand aspiration is a flow non-sequitur
Principles
Frictions
  • Comparison table loses column headers (plan names) during deep scroll — orientation loss for enterprise evaluatorsMedium

Identity Match

6.0
Narrative

Linear's pricing page speaks fluently to developers through its feature vocabulary and logo choices, but fails to signal which tier serves which team size or role — a visitor from a 3-person startup and one from a 300-person engineering org read identical copy with no routing signal for their context.

What's working
  • Logo strip features Vercel, Cursor, OpenAI, Coinbase, Ramp — high signal-to-noise for a developer/engineering tool audience. These are aspirational but identity-relevant brands for the target visitor.
  • Feature labels like 'Linear Agent (beta)', 'MCP access', 'API and webhook access', 'SCIM provisioning' are developer-native language — strong identity signal for technical evaluators
  • Footer's developer-first links (Developers, GitHub, Documentation, Changelog) signal an engineering-centric product culture
What's hurting
  • Plan cards have no audience descriptors — 'Free', 'Basic', 'Business', 'Enterprise' communicate tier but not persona. No 'For solo developers', 'For growing engineering teams', 'For companies shipping at scale'.
  • No role-specific framing: an Engineering Manager, a Head of Product, and a solo founder would all read identical copy with no signal that the product specifically understands their context
  • Navigation includes 'Startups' and 'Enterprise' routing — audience segmentation exists in the site architecture, but doesn't surface on the pricing page itself
  • 'Linear Asks', 'Triage Intelligence', 'Linear Insights' — internal product naming with no explanation creates an identity gap for visitors who haven't read the product pages. Existing Linear users will understand; first-time evaluators won't.
Principles
Frictions
  • Plan cards have no audience descriptors — 'Free', 'Basic', 'Business' signal tier not personaMedium