PageGoblin PageGoblin

The Hoard / B2B SaaS

linear.app landing page review.

Goblin scored linear.app 6.3/10 across twelve conversion dimensions on 30 Sep, 2026.

Goblin's Score

6.3

Out Of 10

"Linear knows exactly what it is and mostly shows it well, but the hero leans too hard on product complexity and misses some trust-building opportunities above the fold."

linear.app

/

30 Sep, 2026

Full Report

6/10

Hero clarity

The headline 'The product development system for teams and agents' is clear enough, but the subline 'Purpose-built for planning and building products. Designed for the AI era' still uses marketing abstractions instead of concrete outcomes.

What You Got Right

  • Headline directly names the product category and audience (teams and agents)

    • What's Wrong

  • Subheadline relies on vague phrases like 'Purpose-built' and 'Designed for the AI era' without naming a specific benefit
  • Hero CTA reads 'New Loops →' which is feature jargon; visitors don't know what they're getting into yet

    • 7/10

    CTA prominence

    Two CTAs above fold ('New Loops →'), both styled identically and pointing to the same vague action. The buttons exist and are visible, but the label tells you nothing.

    What You Got Right

  • CTAs are visually prominent and easy to spot in the hero area

    • What's Wrong

  • 'New Loops →' is feature jargon—a visitor on the home page doesn't know what a Loop is
  • Both CTAs are duplicated and identical, creating no clear hierarchy (Get Started or Learn More would be clearer)

    • 5/10

    Value prop specificity

    The value prop is scattered across the page but never arrives at a concrete outcome. 'Purpose-built for modern teams with AI workflows at its core' tells you the philosophy, not the value.

    What's Wrong

  • No number, no metric, no time savings. 'Sets a new standard' is marketing air
  • Sections list features (Intake, Planning, AI) but never quantify the benefit—no 'reduce triage time by 80%' or 'ship 3x faster'

    • 8/10

    Trust signals

    Logos and named customers (OpenAI, Ramp, Opendoor) show up mid-page with direct quotes. The '40,000 product teams' stat is solid, but both should be above fold.

    What You Got Right

  • Three named customers with titles and company names visible in testimonials (Gabriel Peal at OpenAI, Nik Koblov at Ramp)
  • 'Over 40,000 product teams' is a strong user count stat

    • What's Wrong

  • Testimonials and customer logos appear only after multiple scrolls—not visible above fold
  • No security badge, uptime guarantee, or compliance mention visible early (GDPR, SOC 2, etc.)

    • 6/10

    Copy concreteness

    The page shows real Linear UI with actual issues, but the marketing copy around it is still vague. 'Reduce noise and restores momentum' is poetic, not specific.

    What You Got Right

  • The UI screenshots show real workflow details: issue IDs (DRV-8852), status labels (In Progress), assignees—concrete artifacts

    • What's Wrong

  • Feature descriptions like 'Powered by agents: Designed for workflows shared by humans and agents' lack specifics—which workflows? What does the agent actually do?
  • 'Reduces noise' and 'restores momentum' are abstract; should say 'stops duplicate bug reports' or 'auto-assigns to the right team'

    • 8/10

    Social proof depth

    Three named customers with direct titles and quotes are solid, but no case study depth—just a sentence. Goblin respects the specificity of names, not the lack of context.

    What You Got Right

  • Gabriel Peal (Staff Software Engineer, OpenAI), Nik Koblov (Head of Engineering, Ramp), Kaz Nejatian (Opendoor) with titles and company
  • Quotes are specific to a benefit ('Our speed is intense and Linear helps us be action biased')

    • What's Wrong

  • Only testimonial quotes—no case studies, no numbers. No 'Ramp cut triage time by X%'
  • No user count or NPS benchmark visible early (40,000 teams is mentioned later but not prominently)

    • 4/10

    Objection handling

    The page doesn't address any buyer fears: cost, migration, lock-in, or what happens if you don't use AI. These are silent.

    What's Wrong

  • No pricing visible anywhere on the homepage (only a Pricing link in nav)
  • No migration narrative—teams using Jira/GitHub Projects don't see a 'Here's how we move your data' section
  • No security/privacy section addressing data protection or API access

    • 8/10

    Visual hierarchy

    The page has a clear visual hierarchy: hero at top, features in sections, UI mockups anchoring each section. The eye moves predictably and the layout rewards scrolling.

    What You Got Right

  • Large hero headline, clear section headings (Intake and integrations, Planning and monitoring, AI and automations), UI visuals as anchors

    • What's Wrong

  • Feature sections (Intake, Planning, Build) blur together visually—no visual break or color to distinguish them
  • Too many expandable buttons ('Features') within each section—creates cognitive load

    • 7/10

    Mobile rendering

    The page is responsive and the layout stacks cleanly on mobile, but the UI mockups (which are critical to the story) become tiny on small screens.

    What You Got Right

  • Navigation collapses to hamburger, main sections stack vertically, hero text scales well

    • What's Wrong

  • Large UI screenshots don't scale well to mobile—detail gets lost and the visual story becomes unclear
  • Feature descriptions rely on sidebars and columns that become hard to scan on phone

    • 7/10

    Page speed signals

    Images use lazy loading and async decoding, which is good. No render-blocking scripts are visible in the preprocessed HTML, but multiple high-res images suggest this could be heavy.

    What You Got Right

  • Images use lazy loading='lazy' and decoding='async'
  • No <script> tags in the body (preprocessed, but signals clean JS strategy)

    • What's Wrong

  • Many 1920x1080 images at full resolution—likely to compress these for web
  • Without seeing CSS and JS file sizes, hard to assess total page weight

    • 8/10

    Form and CTA friction

    CTAs point to Sign up and Contact sales links—no forms on the page itself. Signup is likely a low-friction email or OAuth flow, but Goblin can't see the destination.

    What You Got Right

  • Sign up link is visible in nav and repeated at bottom ('Get started' button)
  • No email gate or credit card requirement visible on the homepage

    • What's Wrong

  • CTAs point away—no form or demo embedded on the page
  • No 'Try free' or 'Schedule a demo' button with inline booking

    • 2/10

    Pricing clarity

    Pricing is completely hidden behind a nav link. No mention of free tier, starting price, or per-seat cost anywhere on the homepage. This is a red flag for B2B SaaS.

    What's Wrong

  • No pricing visible on the homepage at all—only a 'Pricing' link in the nav
  • No mention of free trial, free tier, or starting price (e.g., 'From $10/month')

    • Priority Fixes

  • Move pricing above the fold or add 'Free forever for small teams' to the hero to remove friction
  • Replace vague subheadlines ('Purpose-built,' 'Designed for the AI era') with a concrete outcome: 'Ship product features 3x faster with AI-powered triage and review'
  • Add a single, clear primary CTA ('Start free' or 'Get started') instead of duplicate 'New Loops →' buttons that assume user knowledge

    • Things Goblin Respected

  • Named customers with titles and honest quotes (Gabriel Peal, OpenAI; Nik Koblov, Ramp) signal real adoption
  • UI screenshots embedded in each feature section ground the abstract marketing copy in real product detail
  • Visual hierarchy and responsive layout guide the eye smoothly from hero through features without jarring jumps