Linear scored 6.0/10.

The page is trying to reposition Linear from issue tracker to AI product system, but it buries the most credible proof of that shift — the Ramp customer story, where Linear’s coding agent accounts for 60% of merged PRs — inside a customer page that most homepage visitors will never reach. The homepage testimonials are enthusiastic but vague: “you will just feel it” and “just excellent” are fan quotes, not evidence that the AI-native workflow claim is real. The one testimonial that gestures at outcomes (“action biased”) doesn’t connect to the AI agent story at all. The page is making a category-level claim — “issue tracking is dead” — without showing the buyer what killed it and what replaced it. Pull the Ramp agent stat onto the homepage, above the numbered workflow sections, and let it do the work the vague pull quotes can’t.

The page opens with “The product development system for teams and agents” and immediately follows with “Purpose-built for planning and building products. Designed for the AI era.” These two sentences describe two different products — one is a human-plus-agent collaboration system, the other is a planning tool for human teams. The numbered workflow sections (1.0 Intake through 5.0 Monitor) then present a complete product ops pipeline, which is a third framing entirely. A buyer landing from a search for issue tracking software encounters three different category frames in the first scroll. The page needs to commit to one: either Linear is the system where agents do product work alongside humans (the most differentiated claim, and the one competitors can’t match today), or it’s the best-designed planning tool for fast teams (the legacy positioning). The current page tries to hold both and lands neither.

The “Issue tracking is dead” callout links to linear.app/next but sits mid-page with no context — the buyer who hasn’t already read the announcement doesn’t know what they’re clicking into or why it matters to them right now. This is the sharpest positioning move on the page, and it’s treated as a sidebar. If Linear genuinely believes the category has shifted, that claim belongs in the hero, not as a mid-scroll aside with an arrow link. Either lead with the shift and let the rest of the page prove it, or remove the callout entirely — a half-committed category declaration reads as hedging, not confidence.

The page has five workflow sections (Intake, Plan, Build, Diffs, Monitor) each with its own headline, description, and UI mockup. For a buyer who already uses Jira and is evaluating a switch, this is the right content — it maps the full replacement. But for a buyer who arrived from a “fast issue tracker” search or a word-of-mouth referral, five sequential feature sections with no single conversion surface between them is a reading assignment, not a path to signup. There is one CTA above the fold (“Sign up”) and one cluster at the bottom (“Get started / Contact sales / Open app / Download”), with nothing in between across the longest part of the page. A buyer who gets curious at section 3.0 Build has no way to act without scrolling back to the top. Add a signup surface after the Build section — that’s where the agent workflow claim peaks, and it’s the moment a buyer is most likely to want to try it.

The enterprise page at linear.app/enterprise describes Linear as “An AI product system for modern enterprises,” while the homepage calls it “The product development system for teams and agents.” These are close but not the same claim, and the difference matters: “enterprise” implies a buyer who needs governance, scale, and security; “teams and agents” implies a buyer who wants speed and AI integration. A mid-market engineering lead evaluating both pages will notice the inconsistency and read it as a brand that hasn’t decided what it is. Pick the frame that fits the homepage ICP — Series B+ product and engineering teams — and make the enterprise page a vertical of that frame, not a parallel one.