PageGoblin PageGoblin

The Hoard / B2B SaaS

linear.app landing page review.

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

Goblin's Score

7.1

Out Of 10

"Linear knows what it is and why you need it. The hero nails clarity, customer proof is solid, but Goblin spotted vague CTAs and some marketing fluff hiding real differentiators."

linear.app

/

30 Sep, 2026

Full Report

8/10

Hero clarity

Hero headline 'The product development system for teams and agents' is specific and immediate—no mystery about who this is for.

What You Got Right

  • Headline names the core audience (teams and agents) and function (product development system) in one sentence.

    • What's Wrong

  • Subheadline 'Purpose-built for planning and building products. Designed for the AI era.' uses marketing jargon—'AI era' is vague and trendy rather than concrete.
  • CTA text 'New Loops →' is cryptic; new users don't know what Loops are or why they matter yet.

    • 7/10

    CTA prominence

    Two CTAs above fold ('New Loops' links), but they're unclear and duplicate. Primary action should be a single, obvious 'Sign up' or 'Get started' button.

    What You Got Right

  • CTA is visually prominent and clickable above the fold.

    • What's Wrong

  • Two identical 'New Loops →' CTAs suggest unclear intent—which one should users click?
  • 'Loops' is jargon; users unfamiliar with Linear don't know if this is a feature, product, or onboarding step.

    • 7/10

    Value prop specificity

    Subheadline 'Purpose-built for planning and building products' describes what it does, but doesn't name the outcome or problem it solves.

    What You Got Right

  • Mentions 'AI workflows' and 'AI era'—shows Linear understands modern team needs.

    • What's Wrong

  • 'Purpose-built' is corporate filler; doesn't explain the benefit.
  • No number, metric, or concrete outcome (e.g., 'reduce cycle time by 40%' or 'resolve customer requests in hours, not days').

    • 8/10

    Trust signals

    Customer logos and testimonials from named people at real companies (OpenAI, Ramp, Opendoor) with titles appear early. Strong signal, but names could be more prominent above fold.

    What You Got Right

  • Named executives with company and title (Gabriel Peal, Staff Software Engineer at OpenAI; Nik Koblov, Head of Engineering at Ramp).
  • Logos from recognizable companies (OpenAI, Ramp, Opendoor).
  • 'Powering 40,000 product teams' is a concrete user count.

    • What's Wrong

  • Testimonials and logos are not fully visible above the fold on initial scroll—require scrolling to see them.
  • '40,000 product teams' lacks context: is that active teams, signups, or paying customers?

    • 6/10

    Copy concreteness

    Feature sections name actual capabilities (Intake, Triage, Pulse, Projects) but descriptions lean on buzzwords like 'purpose-built' and 'designed for the AI era' instead of specific outcomes.

    What You Got Right

  • Feature names are specific: Intake, Triage, AI automations, Pulse, Initiatives, Projects, Coding sessions.

    • What's Wrong

  • Descriptions like 'Automatically turn conversations and customer feedback into actionable issues' and 'Purpose-built for modern teams with AI workflows at its core' use passive voice and marketing language.
  • No numbers or concrete examples: e.g., how many minutes does triage save? How many PRs can agents review?

    • 9/10

    Social proof depth

    Three named testimonials with full title and company ('Gabriel Peal, Staff Software Engineer, OpenAI'). Goblin respects specificity. Quote quality also matches the credibility—no generic praise.

    What You Got Right

  • Three quotes from verified individuals with full titles (Staff Software Engineer, Head of Engineering).
  • Quotes are specific and credible: 'You'll probably build a better product, just because of the craft that using Linear infuses on your brain.'
  • 40,000 team user count provided.

    • 5/10

    Objection handling

    Goblin sees features described but no explicit handling of buyer fears: cost, migration effort, AI reliability, lock-in, or learning curve.

    What's Wrong

  • No pricing visible on this page (must click Pricing link in nav).
  • No mention of migration support, data portability, or switching ease.
  • AI agent reliability not addressed—no mention of accuracy, fallback to humans, or when to trust the agent.

    • 8/10

    Visual hierarchy

    Eye flow is clean: headline → UI mockup → feature sections. Typographic scale is clear, whitespace generous. No visual clutter. One small issue: CTAs blend in.

    What You Got Right

  • Large headline, compact subheadline, clear white space.
  • Feature sections alternate between text and visuals, guiding eye downward.
  • Color and type hierarchy support readability.

    • What's Wrong

  • CTA buttons ('New Loops →') use subtle styling; could be bolder to draw attention.
  • Multiple feature sections compete for attention; no clear 'start here' beyond the hero.

    • 8/10

    Mobile rendering

    Responsive design appears solid: nav collapses, layout stacks vertically, touch targets are adequate. No obvious mobile UX traps.

    What You Got Right

  • Mobile nav is present (button for menu on small screens).
  • Content stacks vertically without overflow.
  • Text sizes and spacing look readable on mobile.

    • What's Wrong

  • Without live rendering, hard to verify tap target sizes for buttons; 'New Loops' link may be too small on mobile.
  • Feature showcase images likely take full width on mobile—confirm these are optimized for slow connections.

    • 7/10

    Page speed signals

    Images stripped in preprocessing, so Goblin can't assess optimisation, but lazy loading is set on img tags, which is good. Third-party scripts removed, so no obvious bloat.

    What You Got Right

  • Lazy loading and async decoding applied to images.
  • No visible third-party tracking or ads in remaining HTML.

    • What's Wrong

  • HTML is large and deeply nested; semantic structure could be simpler.
  • High reliance on visual mockups (screenshots of the app) means large images are likely; risk of slow load on mobile.

    • 8/10

    Form and CTA friction

    Sign up link is in nav; no credit card gate mentioned. Entry is frictionless, but Goblin would like a bolder 'Get started' CTA above the fold.

    What You Got Right

  • Sign up is one click away in the top nav.
  • No mention of credit card requirement.
  • Multiple CTAs ('Open app', 'Get started', 'Contact sales', 'Download') offer choices.

    • What's Wrong

  • Primary CTA above fold ('New Loops') is unclear and buried; should say 'Start free' or 'Get started'.
  • Lack of clarity on free tier limits (no mention of seats, projects, or features included).

    • 4/10

    Pricing clarity

    No pricing on this page. Must click Pricing link in nav. For a SaaS buyer, this is friction. Goblin hates it when pricing is hidden.

    What's Wrong

  • Pricing is behind a link, not visible above fold or on the main landing page.
  • No indication of free tier, cost, or per-seat pricing.
  • Buyers can't compare value to cost without navigating away.

    • Priority Fixes

  • Move pricing to this page or make it more prominent—hiding cost is a red flag for serious buyers.
  • Replace vague 'New Loops' CTA with 'Start free' or 'Get started for free'; clarify what Loops are in a tooltip or secondary copy.
  • Add objection-handling section addressing cost, migration ease, AI reliability, and lack of lock-in to build buyer confidence.

    • Things Goblin Respected

  • Strong social proof: named executives with titles from recognizable companies (OpenAI, Ramp) and 40,000 team count.
  • Clean visual hierarchy and responsive design; feature sections guide the eye downward without clutter.
  • Feature set is concrete and specific: Intake, Triage, AI Agent, Projects, Pulse—no vague product names.