Criticalhero
Hero repeats headline; buries outcome
The H1 'The product development system for teams and agents' repeats three times in the visible text, and the subheading 'Purpose-built for planning and building products. Designed for the AI era.' is category + buzzword, not a concrete outcome. A cold visitor cannot answer 'what will this do for me?' in 5 seconds.
FixReplace the repeated headline with a single, outcome-focused statement: 'Ship products 3x faster with AI agents handling triage, planning, and code review.' Move the product demo below the fold so the promise, not the interface, dominates the hero.
Warningcta
No clear primary CTA in hero
The static HTML shows 'Sign up,' 'Open app,' and 'Log in' in the nav, but no dedicated hero CTA button is visible. If the primary action is JS-rendered, it may be invisible to cold traffic or unclear which button converts.
FixEnsure a single, prominent 'Start free' or 'Try Linear free' button appears in the hero, above the fold, with a clear label that signals the next step (e.g., 'Start free — no card required').
Warningsocial_proof
Zero customer proof or logos
No testimonials, customer logos, case studies, or verifiable outcomes (e.g., 'Used by 5,000+ product teams') are visible. For a SaaS product, this is a trust leak at the commitment point.
FixAdd a 'Trusted by' section with 3–5 recognizable customer logos (Figma, Stripe, etc.) and a single specific testimonial near the CTA: 'Reduced issue triage time by 60%' — [Name, Company].
Warningcopy
Benefit copy lacks specifics
Sections like 'Designed for speed' and 'Reduces noise and restores momentum' are abstract. 'Restores momentum' and 'new standard' are buzzwords that don't tell a visitor what they'll actually gain.
FixRewrite with concrete metrics: 'Designed for speed: Triage issues 10x faster with AI-powered labeling and routing' or 'Reduces noise: Auto-categorize customer feedback so your team focuses on high-impact work.'
Warningclarity
Product demo dominates above the pitch
The page shows a detailed product interface (issue tracker, agent output, code diffs) early, before clearly stating what problem Linear solves or why a visitor should care. This assumes familiarity and risks losing cold traffic.
FixRestructure: lead with a 2–3 sentence outcome promise ('Ship products faster by automating triage, planning, and code review with AI agents'), then show the product in action. Use captions that tie features to outcomes, not just describe the UI.
Warningfriction
Pricing and signup friction unclear
A 'Pricing' link is in the nav, but no pricing, free trial length, or 'what happens after signup' is visible in the static HTML. Visitors may hesitate if they don't know cost or commitment upfront.
FixAdd a line near the primary CTA: 'Free forever for small teams. Upgrade anytime.' Or link to a pricing page that shows tiers and trial length before the signup form.
Minorcopy
AI agent terminology may alienate non-technical buyers
Phrases like 'AI workflows,' 'agents,' 'PRDs,' and 'MCP' assume the visitor is a technical product manager or engineer. Non-technical stakeholders (execs, ops) may not understand the value.
FixAdd a brief explainer or use a secondary headline: 'For product teams: AI agents handle repetitive work (triage, labeling, code review) so your team focuses on strategy.' This signals both technical and non-technical buyers are welcome.
Minorcopy
H1 repeats three times in visible text
The headline 'The product development system for teams and agents' appears verbatim three times in the scraped HTML, suggesting a rendering or layout issue that may confuse or annoy visitors.
FixAudit the live page to confirm this is a scrape artifact or a real rendering bug. If real, remove the duplicates and ensure the H1 appears once, prominently, in the hero.
