# Linear. Brand File > Drop this file into any AI tool (ChatGPT, Claude, Gemini, etc.) as context at the start of a conversation. Everything the AI generates from that point on will be in your brand voice, aligned with your strategy. > > **Every claim is sourced.** This file draws on 386 Reddit posts (deduplicated by post ID across r/Linear, r/webdev, r/ProductManagement, r/SaaS, r/startups, r/programming, captured 23 May 2026 via Apify Reddit Scraper), captured copy from linear.app (homepage, pricing, about, customers, /now/ai, /next, changelog), and five AI tools (Claude, ChatGPT, Gemini, Perplexity, Grok) each answering the same three questions about Linear via OpenRouter API on 23 May 2026. Full research record at [rational-magic.com/s/linear-v1/research/](https://www.rational-magic.com/s/linear-v1/research/). --- ## Business basics **Business:** Linear (legal entity: Linear Orbit, Inc., Delaware corporation filed 22 October 2019). **Primary founders:** Karri Saarinen (Co-founder, CEO. ex-Principal Designer at Airbnb, ex-Coinbase), Tuomas Artman (Co-founder, CTO. ex-Senior Engineer at Uber), Jori Lallo (Co-founder, CPO. ex-Senior Engineer at Coinbase). **Current CEO:** Karri Saarinen (co-founder). **Founded:** 2019 in San Francisco. Exited private beta June 2020. Reported profitable by June 2021. 7 years old as a company, 6 years post-public-launch. **HQ:** Linear Orbit, Inc. at 2261 Market St STE 10632, San Francisco, CA 94114. Operationally remote-first: per linear.app/about, "Our team is distributed across North America and Europe, and we're continuing to grow internationally." **Team size:** Approximately 178 to 209. Aakash Gupta cited about 100 employees at the time of the Series C in mid-2025; rapid hiring since suggests the 200 range in 2026. **Funding:** $134.2M total across 3 disclosed rounds. Largest single round was the Series C, $82M in June 2025 at $1.25B valuation, led by Accel with Sequoia, 01A, Seven Seven Six, Designer Fund, Indie.vc, TK Ventures, Soleio, plus angel investors including Jeff Weinstein, Ilkka Paananen, and Lauren and Vlad Loktev. **Revenue (external estimate; Linear has not published official figures):** approximately $100M ARR in 2025 per getlatka.com. **Website:** [linear.app](https://linear.app). **Category:** Product development system. Issue tracking, project management, roadmaps, cycles, plus (since 2025 to 2026) an AI agent platform. **Category position:** The benchmark for modern issue tracking. The tool Jira is now compared against, not the other way around. Linear's homepage claim: *"Linear powers over 25,000 product teams. From ambitious startups to major enterprises. 2.0x Increase in filed issues. 3.3x Faster issue resolution. 28% Issues authored by agents."* These are first-party claims, not independently audited. **Pricing (current, from linear.app/pricing, captured 23 May 2026):** | Tier | Price | Key inclusions (verbatim) | |---|---|---| | Free | $0 | *"Unlimited members / 2 teams / 250 issues / Agent platform / Linear Agent (beta)"* | | Basic | $10 per user / month, billed yearly | *"All Free features + / 5 teams / Unlimited issues / Unlimited file uploads / Admin roles"* | | **Business** | $16 per user / month, billed yearly | *"All Basic features + / Unlimited teams / Private teams and guests / Triage Intelligence / Linear Agent automations (beta) / Code Intelligence (beta) / Linear Insights / Linear Asks / Zendesk and Intercom integrations"* | | Enterprise | Custom, annual billing only | *"All Business features + / Invoice/PO billing / SAML and SCIM / Granular admin controls / Enterprise-grade security / Advanced org modeling / Migration & onboarding support / Priority support / Account management"* | **Pricing-model note:** every paid tier is per-user-per-month and annual-billing-only. There is no monthly billing option above Free. **AI gating:** **Linear Agent** (public beta launched 24 March 2026) is available on **ALL plans including Free.** Per Linear's changelog: *"Agent and Skills are included on all Linear plans. Automations and Code Intelligence are available on Business and Enterprise. During beta, all features are available at no additional cost."* The Business tier ($16/user/month) gates the higher-value agent capabilities (Triage Intelligence, Linear Agent automations, Code Intelligence, Insights, Asks). **Notable acquisitions:** None publicly disclosed per tracxn.com and crunchbase.com. **Strategy date:** May 2026. > **Not stated in this file** (because not in the evidence we captured): Linear's official MRR or ARR figures (only external estimates exist), cumulative revenue, G2 or Trustpilot review data (not captured this pass), per-customer agent adoption rates, internal product roadmap. --- ## Who Linear is (positioning) Linear is a product development system. Karri Saarinen, Tuomas Artman, and Jori Lallo founded the company in San Francisco in 2019, exited private beta in June 2020, and reported profitability by June 2021 per The Pragmatic Engineer. 7 years post-founding, 6 years post-public-launch, the product is the benchmark for modern issue tracking. The tool other tools in the cohort (Jira, Asana, ClickUp, Monday.com) are now compared to, not the other way around. The May 2026 product is selling agents. The homepage hero is *"The product development system for teams and agents"* with the sub-headline *"Purpose-built for planning and building products. Designed for the AI era."* Customer logos: Vercel, Cash App, Clay, Perplexity, Cars24, Substack, Lovable, Remote, Polymarket, Boom. Headline metrics: *"25,000+ organizations · 2.0x Increase in filed issues · 3.3x Faster issue resolution · 28% Issues authored by agents."* In March 2026 Linear published "Issue Tracking is Dead" at linear.app/next and launched the Linear Agent public beta. Five named AI products now sit in the stack: Linear Asks (Nov 2025), Linear Agent (Mar 2026 public beta), Triage Intelligence (public beta), Code Intelligence (Business+ beta), Product Intelligence. **This is the right strategic bet.** Agents-doing-the-work is where software development is heading in 2026: GitHub Copilot, Cursor, Claude Code, Codex, Anthropic adding scheduling to Claude Code. Linear has the strongest production proof in the cohort. *"28% Issues authored by agents"* across the 25,000+ customer base; per qa.tech, *"within a week of Linear's integration with Cursor, over 45% of enterprise customers were assigning tasks to Cursor agents directly within Linear."* The 5/5 LLM convergence on "the prettier, faster Jira for engineering teams" describes Linear as it WAS in 2019 to 2024. The homepage describes Linear as it IS becoming in 2026. **The positioning challenge isn't whether to push agents. It's how to close two specific gaps.** First, the LLM-narrative gap. When the 5 captured LLMs (Claude, ChatGPT, Gemini, Perplexity, Grok captured 23 May 2026 via OpenRouter) are asked *"what makes Linear different from competitors?"*, **none of them name Linear Agent, the five-pillar AI stack, or the 28% / 45% production proof.** All 5 still describe Linear in the 2019 to 2024 shape: anti-Jira, opinionated, fast, beautiful. Second, the context-layer gap (see Shadow Side below). The agent-first thesis requires Linear to become the context layer; right now context lives outside Linear in Slack, GitHub-md, Google Docs, ChatGPT history. **Elevator pitch (referral version):** > Linear is the product development system for software teams and agents. Issue tracking, project management, cycles, roadmaps, plus a five-pillar AI stack (Asks, Agent, Triage Intelligence, Code Intelligence, Product Intelligence). Free for solo and small teams; $10/user for Basic; $16/user for Business (agent automations + Code Intelligence). Used by 25,000+ organizations including Vercel, OpenAI, Cash App, Perplexity, Substack. The forward bet: humans and agents share the same workspace, the same context, the same plan. **Elevator pitch (first-person, for Linear's own surfaces):** > Linear's the product development system. Built local-first, so it feels instant. Opinionated about how product teams work, because we ran product teams for a long time before we built it. And now it's built for the AI era: agents on every plan, agent automations and Code Intelligence on Business. 28% of issues across our 25,000 customers are already authored by agents. We don't pretend the context layer is finished. We're telling teams honestly: this is where humans and agents share the same workspace, and we're building the context layer that makes that work. --- ## What Linear fights against (Hidden Enemy) > *Hypothesis (Fred Loo, May 2026):* the Hidden Enemy is **the belief that issue tracking IS the work.** > > **This is internal-facing diagnostic, not brand voice.** It names the structural belief Linear needs to defeat to win the 2026 to 2030 buyer. It is not a line Linear would say out loud. The brand-voice translation lives in the antidote below and the tagline. The legacy issue-tracking category (Jira, Trello, classic Asana) was built around a structural assumption: tracking the work IS the work. Tickets exist to be groomed, sprinted, burned-down, retro'd. The tool's job is to be the system of record for that ceremony. Linear's "Issue Tracking is Dead" post in March 2026 was an explicit category-shift declaration: in an agent-native world, the bottleneck is no longer the execution of issues but the shared context that humans and agents both need to act. **Reddit corroborates the category-shift framing.** u/corenellius in r/Linear, 24 March 2026 (17 upvotes / 23 comments): *"Linear's latest post was interesting because it feels like one of the clearest statements yet that the bottleneck in software development is shifting from execution to context. Their core argument is: the handoff-era of software created a lot of workflow ceremony; agents compress planning, implementation, and review; the new bottleneck is giving agents the right context; the winning system is the one that turns context into execution."* [source: reddit.com/r/Linear/comments/1s2mf7t fetched 23 May 2026]. **Even the critical Reddit voice acknowledges the shift.** u/SteveZedFounder in r/startups, 27 March 2026 (53 upvotes / 76 comments): *"Their moat was always: (1) not Jira, and (2) genuinely better UX than Jira. Design was the moat. They won on that. Agentic AI just blew that up. If agents are doing the work and tracking their own context, who's updating tickets? The whole premise of issue tracking gets weird fast. So Linear is moving up the stack."* [source: reddit.com/r/startups/comments/1s5chlx fetched 23 May 2026]. The critique is real but it confirms the hidden enemy: in the agent era, the "issue tracking IS the work" belief is the thing that gets disrupted, not Linear. **5 of 5 captured LLMs describe Linear inside the issue-tracking-IS-the-work frame.** Every single LLM (captured 23 May 2026 via OpenRouter) names Linear as *"a faster Jira"* / *"streamlined Jira"* / *"anti-Jira"* / *"Jira killer."* Gemini: *"Often described by its users as the 'anti-Jira,' Linear's differentiation boils down to six core philosophies: speed, keyboard-centricity, opinionated design, aesthetics, developer focus, and automation."* That framing is true to Linear's 2019 to 2024 positioning. It misses Linear's 2026 move entirely. **The hidden enemy isn't Jira. It's the belief that defines the Jira category.** ### Antidote (the forward-facing positioning move. What Linear DOES about the Hidden Enemy) **Where teams and agents share the same context.** That's the tagline. 8 words. Forward-facing. The structural answer to the hidden enemy: if issue tracking ISN'T the work, then the workspace's job isn't to manage tickets. It's to be the shared context layer where humans and agents both act. The team plans, the agent drafts, the team reviews, the agent ships, the team retros, the agent improves. Same workspace. Same plan. Same context. The criticism is real: in an agent era, tracking tickets is no longer where the value lives. Linear's structural answer in 2026 isn't to walk back the issue-tracker. It's to extend the issue-tracker into the context layer that agents need to act competently. **Linear Agent is the bridge.** 28% of issues across 25,000 organizations are already authored by agents. The OpenAI case study reports 3,000 internal users. The Cursor integration moved 45% of enterprise customers into agent-assignment within a week. Production proof of the antidote, today. **Two gaps to close, not one:** 1. **The narrative gap.** The 5 captured LLMs don't yet surface the agent push as a Linear differentiator. Their training data lags Linear's homepage by months. Close it with concrete proof everywhere: - *"Here's what Linear Agent does today, in three named jobs."* - *"Here's the 28% number, with the methodology behind it."* - *"Here's the OpenAI scale story, with the named integration partners (Cursor, Vercel, Claude Code)."* - *"Here's what the agent doesn't yet do well. We'll tell you when to use a human or a specialist tool instead."* 2. **The context-layer gap (the Shadow Side. See below).** The agent-first positioning requires Linear to become the context layer. Right now context lives in Slack, docs, GitHub-md, ChatGPT history. Reddit Theme 4 is the live evidence. Close it not by building a Confluence-clone, but by making docs, specs, decisions agent-native objects inside Linear itself. --- ## Linear's honest trade-off (Shadow Side) > *Hypothesis (Fred Loo, May 2026):* the Shadow Side is **the Confluence-shaped gap. Linear won the issues battle. The team's context still lives outside Linear.** > > The "yet" matters. The Shadow Side isn't a permanent ceiling. It's the specific structural gap the agent-first positioning has created and that the next 12 months of product work need to close. Day 1 with Linear: instant. Local-first. Clean. The team migrates from Jira and 6 months later the most-quoted phrase across migration posts is *"the team actually uses it without complaining."* Issue tracking, done right, at last. Day 365 (without the context layer): the issues are tidy. The cycles are humming. The agent platform is on. But the decisions, the design rationale, the spec docs, the PRDs, the architectural debates, all still live somewhere else: a Google Doc here, a Slack thread there, a half-written GitHub README, a ChatGPT conversation no one saved. The agent the team turns on in March 2026 can act on the issue, but it can't always answer *"why did we decide to do it this way?"* because the why never made it into Linear. Day 365 (with the context layer working. The forward bet): docs live in Linear. Specs live in Linear. Decisions get logged in Linear as first-class objects, with agent-readable structure. The agent assigned the issue can read the spec, the decision-log, the prior-art PRD, all in the same workspace. The team's context and the agent's context are the same context. The Confluence-shaped gap closes not by Linear building Confluence, but by Linear extending the issue object into a richer context model that agents and humans both navigate. **Verbatim evidence (captured 23 May 2026 from r/Linear via Apify):** - *"Linear Replaced Jira, What is a linear equivalent of confluence?"* (11 upvotes / 19 comments). Top comment: *"A Linear flavored version of Confluence would be great."* [source: reddit.com/r/Linear/comments/1n1r3gm fetched 23 May 2026]. - *"Documents? Linear?"* (16 upvotes / 16 comments). Verbatim OP: *"Right now we have ongoing, some project, some company related docs at multiple places: Some in public Github repos, md / Some are inside private Github repos, md / Some in Google Docs. Is it possible or practical to move docs to linear? Any interesting suggestions of how you guys use documents at your company? We don't like Notion btw."* [source: reddit.com/r/Linear/comments/1qtsn13 fetched 23 May 2026]. - u/Hour-Two-3104 in r/Linear, 15 April 2026 (10 upvotes / 14 comments): *"a lot of context still ends up living outside the tool, decisions in Slack, explanations in docs and then Linear becomes more like a place to store tasks rather than where the actual work understanding happens, which kind of defeats the point."* [source: reddit.com/r/Linear/comments/1sm1ac0 fetched 23 May 2026]. - u/brushali in r/ProductManagement, 12 September 2025 (122 upvotes / 114 comments, the highest-engagement Linear-vs-Jira post in the capture): *"Made the switch from Jira to Linear 6 months ago for our AI product team (6 people)... The reality check: Missing advanced reporting we relied on. Integrations aren't as mature. Cost jumped 40%."* [source: reddit.com/r/ProductManagement/comments/1neyq6j fetched 23 May 2026]. **The honest acknowledgement (template, in Linear's voice. Forward, not defensive):** > *"On day 1, Linear gives your engineering team the issue tracker they've wanted since they stopped wanting Jira. Six months in, you'll notice the issues are tidy and the context still lives somewhere else. We've been building the context layer for exactly this. Docs, specs, decisions, all as agent-native objects inside Linear, so the agent assigned to your issue can read the why, not just the what. Here's where that work is today. Here's what's still in beta. Here's where the team using Linear at scale is already feeling the lift."* --- ## How Linear behaves (Personality. Derived from verified evidence) ### 1. Opinionated **What it means:** Linear has a view on how product teams should work, and the product enforces it. Cycles (not arbitrary sprints), strict hierarchy (Projects > Issues > Sub-issues), Triage mode, the Linear Method. Customisation surface is intentionally narrow. **The agent platform extends this. The agent is opinionated too, it ships inside the Linear workflow, not as a free-form chat bolt-on.** **Evidence:** 5/5 LLMs name "opinionated" or "opinionated > customizable" as a core differentiator. ChatGPT one-liner: *"Here's a good way to run product and engineering, use it."* Perplexity: *"Product philosophy (opinionated, craft-driven, not 'move fast & A/B test everything')."* Claude: *"Opinionated Workflows: less customization by design, encourages best practices rather than letting teams build complex, messy systems."* Grok: *"obsessively focused on being the best tool for high-velocity software teams"* (captured 23 May 2026 via OpenRouter). **What it's NOT:** infinitely configurable. Not Jira-coded, not enterprise-form-builder-coded. Not for teams whose first question is *"can we customise the workflow per project?"*. **In action:** lead the onboarding with *"this is how Linear thinks product development works. Try it before you ask to change it."* The agent gets the same treatment: agent skills are scoped, agent automations are workflow-shaped, agent context is structured Linear data, not free-form chat history. ### 2. Built by engineers, for engineers **What it means:** the three founders are an ex-Airbnb principal designer, an ex-Uber senior engineer, and an ex-Coinbase senior engineer. The product carries that DNA. Keyboard-first. Git-native. Speed-obsessed. Built for the people who actually write the code, not for the people who manage the people who write the code. **Evidence:** 5/5 LLMs name "built for engineering teams" / "developer-obsessed" / "built by engineers, for engineers" (captured 23 May 2026 via OpenRouter). Grok: *"The founders (former engineers at Airbnb, Coinbase, etc.) built the exact tool they wished they had."* Gemini: *"developer-obsessed"* design with GitHub/GitLab/Sentry integrations. ChatGPT (Q2): *"Engineering-led companies · Product/engineering/design teams · Teams already using GitHub/Slack/Figma."* Reddit corroborates: u/brushali's *"team actually uses it without complaining"* is the developer-side language, not the manager-side. **What it's NOT:** for non-technical teams. Not for marketing, ops, HR, sales. Linear knows this and says it: 4/5 LLMs explicitly call out who Linear is NOT for (the ChatGPT line: *"Less customization, more convention"*). **In action:** marketing copy speaks to the engineer first. Pricing speaks to the team admin who's also an engineer. Customer stories lead with engineering velocity (3.3x faster issue resolution, 2.0x increase in filed issues), not with executive dashboards. **For the agent push: lead with the developer-tooling story (Theme 3 below). Cursor, Claude Code, MCP integrations. The leading-indicator signal is sharpest here.** ### 3. Aesthetic-led **What it means:** the product is beautiful. Minimal interface. Pixel-perfect type. The visual design is itself part of the positioning. Gemini called it: *"It treats its B2B software like a high-end consumer product. The result? Developers and designers actually enjoy using it."* Grok: *"the only tool that doesn't feel like work."* **Evidence:** 5/5 LLMs name beauty / aesthetics / craftsmanship / "doesn't feel like work" as a Linear differentiator (captured 23 May 2026 via OpenRouter). The Karri Saarinen design-lead origin story (ex-Principal Designer at Airbnb) corroborates. Reddit migration posts converge on the same: the UI is the reason teams adopt and don't churn back to Jira. **What it's NOT:** enterprise-heavy, dense-with-toolbars, ribbon-style. Not Jira-coded, not Confluence-coded, not SharePoint-coded. **Also not optional.** Aesthetic restraint is part of how Linear gets adoption without org-mandate, the tool is the marketing. **In action:** keep the visual surface clean as the AI features ship. Resist the temptation to add agent UI density. The agent should feel like a quiet teammate inside the workspace, not a chatbox panel grafted on. The Linear Agent's place in the UI should be as carefully designed as a Cycles view was in 2020. ### 4. Speed-obsessed **What it means:** Linear's local-first sync engine is the technical moat. The app downloads the workspace to the local machine; every navigation, every issue creation, every status update is instant, no network round-trip. Speed isn't just a feature; it's the structural reason the product feels different. **Evidence:** 5/5 LLMs name speed as a Linear differentiator; 4/5 explicitly name the local-first or sync-engine architecture as the reason (captured 23 May 2026 via OpenRouter). Gemini: *"When you open Linear, it downloads your workspace data to your local machine. This means navigating, creating issues, and updating statuses happens instantly, with zero latency."* Perplexity: *"UX and performance (instant feel + local-first architecture)."* Reddit: u/brushali on the migration: *"UI is clean, fast, no bloat. Team actually uses it without complaining."* **What it's NOT:** *"fast enough"* as a feature claim. Speed at Linear's level is a structural property of the architecture, not a benchmark slide. Don't market it as a number; market it as a feeling. *"It feels instant because it IS instant."* **In action:** when describing what makes Linear different, lead with the sync engine, not the keyboard shortcuts. The keyboard shortcuts are the surface; the sync engine is the moat. **For the agent push: the speed expectation now extends to the agent. Agents have to feel as instant inside Linear as humans do. Latency is the difference between "the agent is a teammate" and "the agent is a slow API."** ### 5. Forward-betting **What it means:** Linear is willing to declare a category dead. "Issue Tracking is Dead" was the March 2026 post that bet the company on the agent-native frame. Linear is repositioning ahead of the LLM-internet's awareness of the move. The personality trait is the willingness to stake the brand on where the puck is going. **Evidence:** linear.app/next (Mar 2026) "Issue Tracking is Dead" post. The five-pillar AI stack shipped between Nov 2025 (Asks) and Mar 2026 (Agent public beta). Customer-side proof on the homepage: *"28% Issues authored by agents."* Reddit Theme 2: even the critical voice (u/SteveZedFounder) frames Linear as *"moving up the stack"*, that's a forward-bet acknowledgement, not a status-quo defence. **What it's NOT:** safe-positioning. Not *"we're still the better Jira, plus AI features."* Not following the cohort (Asana, ClickUp, Monday all adding AI features as cosmetic layers). Linear is betting that the category itself is changing, and that the right brand move is to declare it before the rest of the cohort catches up. **In action:** the bet has to keep landing. Every quarter the agent push should ship a forward proof: a new AI product, a new customer scale story, a new integration that compresses the human-to-agent context loop. The brand's credibility on the forward bet compounds with each shipped proof. **The audit's job is to help Linear close the LLM-narrative gap so that by Q4 2026, the answer to *"what makes Linear different?"* across the AI tools starts to include the agent layer, not just the anti-Jira frame.** --- ## How Linear sounds (Voice & Tone) ### Voice baseline > *"Engineer-direct. Plain-spoken. Opinionated. Talks like the founder who built the issue tracker because the old one was broken, and is now building the agent layer because the old issue tracker is about to be broken too. Not the marketing department selling a roadmap. The product team telling other product teams where the category is heading."* ### Tone by context | Context | Tone | |---|---| | Homepage / product pages | Lead with the structural truth (the product development system for teams and agents); back agent claims with named scale (25,000+ orgs, 28% issues authored by agents, OpenAI 3,000 users, 45% Cursor-assignment within a week). Name what's beta. | | Pricing | Direct. Shows the per-user math. Names exactly what's gated on Business ($16) vs Free, with the agent on EVERY plan. Pre-empts the *"Business to Enterprise jump"* complaint that surfaced in Reddit Theme 6. | | Founder posts (Karri Saarinen) | First-person singular. One thing built, one thing the agent is now doing that used to fall on the team, one thing the agent doesn't yet do well. Long-arc tone, *"we've been building Linear since 2019"*, earned, not aspirational. | | Replies to a buyer asking about reporting, integrations, the Business-to-Enterprise jump | Honest routing today + forward fix tomorrow. *"Advanced reporting at the depth of Jira's data lake isn't where we are today. Here's what Linear Insights does, here's what we've heard, here's what's shipping in the next two quarters."* | | Developer / agent audience (Reddit Theme 3) | Lean in. The developer-tooling explosion around the Linear Agent API, Claude Code workflows, MCP integrations IS the brand's leading-indicator signal. Speak to that audience directly: docs, examples, GitHub repos, MCP server reference. | | Customer comms (e.g. Business-tier feature lockout, like the May 2026 Releases pipeline limit) | Pre-emptive. Explain the rationale, name the upgrade path, acknowledge the friction. Don't let pricing-page reality diverge from the value at scale. | | Email / onboarding | Brief. One action per message. *"Today: import from Jira. Tomorrow: run your first cycle. Don't try to set up every workflow this week. The agent will help as you scale."* | --- ## Words Linear uses *product development, system, issue, cycle, project, roadmap, triage, agent, agentic, automation, skill, context, ship, build, plan, opinionated, fast, instant, local-first, sync, keyboard, integration, MCP, beta, scale, team, organisation, the Linear Method, the product development system* These are words that appear on Linear's live homepage / pricing / changelog / now/ai pages, or that match the dominant Reddit language across the 386-post sample. ## Words Linear never uses (banned per brand voice + Quality Gate) **Never used about competitors:** any word that alleges wrongdoing or criminality. When Reddit users use loaded language about another brand (Jira included), paraphrase the underlying complaint rather than republishing the word as a Linear-attributable claim. **Banned per brand voice:** game-changing, supercharge, level up, revolutionize, world-class, cutting-edge, disruptive, ninja, rockstar, unleash, stunning. Plus context-dependent filler: unlock / empower / amazing / incredible / passionate / thrilled / ecosystem when used as marketing-speak. Plus enterprise-overuse filler: seamless / transformative / next-generation. **Banned for this audit's audit-page-about-Linear:** *"Jira killer"* (the LLM convergence frame Linear has been trying to grow out of; don't replicate it as a Linear-side claim); *"the anti-Jira"* (same shape, sticks Linear inside the issue-tracking-IS-the-work frame it's actively repositioning against). --- ## Key messages ### Tagline (Strategic Core) > **Where teams and agents share the same context.** The tagline is the antidote to the Hidden Enemy, framed in Linear's own forward-facing voice. 8 words. It names what Linear is becoming (the shared workspace where humans and agents both act on the same plan) and what that frees the team to do (ship product, not maintain ceremony). It is a thing Linear could ship as a homepage hero tomorrow. > **A note on what this tagline is NOT.** The Hidden Enemy (the structural belief Linear needs to defeat) is *"the belief that issue tracking IS the work."* That's the internal diagnostic. It is not a tagline. The tagline is what Linear says about defeating it. Forward-facing, brand-positive, agent-and-team-paired. ### Four differentiators **1. Local-first speed. The sync engine is the technical moat.** > *Proof:* 5/5 LLMs name speed as a Linear differentiator; 4/5 name the local-first or sync-engine architecture as the structural reason (captured 23 May 2026 via OpenRouter). Gemini: *"When you open Linear, it downloads your workspace data to your local machine. This means navigating, creating issues, and updating statuses happens instantly, with zero latency."* Perplexity: *"UX and performance (instant feel + local-first architecture)."* In a market where every PM tool claims to be fast, Linear's speed is a structural property of the architecture, not a benchmark claim. **In the agent era this moat extends: agents have to feel as instant inside Linear as humans do, and the local-first sync engine is what makes that possible at 25,000-org scale.** **2. Opinionated workflow. The Linear Method.** > *Proof:* 5/5 LLMs name "opinionated" or "opinionated > customizable" as the philosophical wedge (captured 23 May 2026 via OpenRouter). ChatGPT one-liner: *"Here's a good way to run product and engineering, use it."* Claude: *"Opinionated Workflows: less customization by design, encourages best practices rather than letting teams build complex, messy systems."* Gemini: *"It is intentionally opinionated, meaning it dictates how you should work. It offers Sprints (called 'Cycles'), a strict hierarchy (Projects > Issues > Sub-issues)."* The Linear Method is the published version of the opinion. **This applies to agents too: agent skills are scoped, agent automations are workflow-shaped, the agent isn't a free-form chatbox grafted on.** **3. Built for software teams (and explicitly not for everyone).** > *Proof:* 5/5 LLMs name "built for software / product / engineering teams" as a differentiator; 4/5 explicitly call out who it's NOT for (captured 23 May 2026 via OpenRouter). Grok: *"Not-for: Enterprises that need heavy compliance/reporting · Non-technical teams · Teams that love heavy process."* Perplexity: *"narrow, deep focus on product/engineering/design, you'd be hard-pressed to use it as the only project management tool for an entire company."* This is the discipline that lets Linear stay opinionated. The narrow buyer means the product can be opinionated about how that buyer works without needing to flex for every adjacent market. **4. The agent-native context layer. Linear's forward bet on what product development becomes next.** > *Proof:* Linear's May 2026 homepage hero is *"The product development system for teams and agents"* with the sub-headline *"Purpose-built for planning and building products. Designed for the AI era"* [linear.app fetched 23 May 2026]. Homepage scale claim: *"28% Issues authored by agents"* across 25,000+ organizations [linear.app fetched 23 May 2026]. Linear Agent public beta launched 24 March 2026 [linear.app/changelog/2026-03-24-introducing-linear-agent fetched 23 May 2026]. Five-pillar AI stack: Linear Asks (Nov 2025), Linear Agent (Mar 2026), Triage Intelligence, Code Intelligence, Product Intelligence [linear.app/now/ai fetched 23 May 2026]. Cursor integration proof point: *"Within a week of Linear's integration with Cursor, over 45% of enterprise customers were assigning tasks to Cursor agents directly within Linear."* [qa.tech fetched 23 May 2026]. **The 5 captured LLMs don't yet surface this differentiator, they describe Linear as it was (anti-Jira), not as it's becoming (agent-native).** That gap is the positioning opportunity, sharper than Notion's because Linear's pivot is more recent and more thoroughly bet-the-company, with stronger production proof already shipped. ### The most contrarian observation (own it; lead with it) **Linear's biggest 2026 strategic bet, the agent platform, is invisible to 5/5 LLMs. That's the positioning opportunity, not the verdict.** > All 5 captured LLMs (Claude, ChatGPT, Gemini, Perplexity, Grok, captured 23 May 2026 via OpenRouter) describe Linear as *"the prettier, faster Jira"*. None surface Linear Agent, the five-pillar AI stack, the 28% issues-authored-by-agents proof point, or the OpenAI / Cursor scale story. The May 2026 homepage hero and the March 2026 "Issue Tracking is Dead" post have not landed in the LLM-internet's framing of Linear. > > **This is what positioning work exists for.** LLM training cutoffs lag the product by 6 to 18 months. Reddit is the leading indicator (per LLM Source-Access Asymmetry pattern) and Reddit has already moved: developers are building Claude Code, Cursor, and MCP integrations on the Linear Agent API in r/Linear today (Theme 3, 8+ developer-tooling posts in the last 3 months). The strategic recommendation: close the gap explicitly, name the agent story everywhere with concrete production proof, so the LLM-internet catches up with the agent framing intact. ### Google Business Profile / SEO meta description > *"The product development system for software teams and agents. Issue tracking, cycles, roadmaps, plus Linear Agent (public beta) on every plan. Free for solo and small teams; $10/user for Basic; $16/user for Business with agent automations and Code Intelligence."* ### Bio (X / Instagram / LinkedIn) > *"The product development system for teams and agents. Local-first. Opinionated. Built by engineers, for engineers. linear.app"* ### Email signature template (for Linear employees / Karri Saarinen) > *"Karri Saarinen · CEO · Linear · linear.app"* --- ## Linear's customers ### Audience Truth (synthesised from Reddit corpus + 5-LLM Q2 convergence) > *"My team is migrating from Jira and we want a tool that actually feels good to use. Get us shipping by next sprint, not next quarter. And give us a path through the agent question, because every engineer on the team is already using Cursor / Claude Code / Codex on their own."* The audience isn't asking *"what does Linear do?"*. They already know. They're asking *"how does Linear handle the agent question better than rolling our own?"*. The forward answer: **the agent is on every plan, and the integrations with Cursor, Claude Code, and MCP are first-class.** The team builds the system, the agent acts inside the same workspace, the context is shared. Backed by: - u/brushali in r/ProductManagement, 12 Sept 2025 (122 upvotes): *"team actually uses it without complaining"* (the universal migration-win phrase). - u/corenellius in r/Linear, 24 Mar 2026 (17 upvotes): *"the bottleneck in software development is shifting from execution to context."* - The 8+ developer-tooling posts in r/Linear over the last 3 months on Linear + Claude Code workflows, MCP servers, headless agent integrations. - ChatGPT (Q2 via OpenRouter, captured 23 May 2026): *"Engineering-led companies · Product/engineering/design teams · Teams already using GitHub/Slack/Figma."* - Grok (Q2 via OpenRouter, captured 23 May 2026): *"product teams, startups, and fast-growing companies that want to replace clunky tools like Jira with something much faster, simpler, and more enjoyable to use."* ### Jobs to be done - **Functional:** *"Give us a fast, opinionated issue tracker for the engineering team that integrates natively with GitHub, Slack, Figma, and our AI tools (Cursor, Claude Code). Don't make us configure it for three weeks before we can ship. And give us the agent layer that turns the workspace into a place where humans and agents actually share the work."* - **Emotional:** *"Make me feel like the team's tooling is finally as well-designed as the product we ship. The agent push has to keep that feeling, not break it with a chatbox that feels grafted on."* - **Social:** *"Let me show another engineering leader our Linear workspace and have them go 'oh I want this.' Same for the agent integrations. The Cursor + Linear story is the recruitment story."* ### Customer-scale anchors (from linear.app, captured 23 May 2026) > *"Linear powers over 25,000 product teams. From ambitious startups to major enterprises."* [linear.app homepage fetched 23 May 2026]. > *"28% Issues authored by agents"* (across the 25,000+ organization customer base) [linear.app homepage fetched 23 May 2026]. > *"Why OpenAI chose Linear and scaled to 3,000 users"* [linear.app/customers/openai fetched 23 May 2026]. > *"Within a week of Linear's integration with Cursor, over 45% of enterprise customers were assigning tasks to Cursor agents directly within Linear."* [qa.tech/blog/ai-builder-stack-linear-cursor-vercel-qa-tech fetched 23 May 2026]. Named customers (homepage logo strip + Series C announcement): Vercel, Cash App, Clay, Perplexity, Cars24, Substack, Lovable, Remote, Polymarket, Boom, OpenAI, Coinbase, Ramp, Scale AI. --- ## Right of reply If you're at Linear and any claim above is wrong, reply to fred@rational-magic.com. Corrections published within 48 hours. A standing right-of-reply page lives at [rational-magic.com/s/linear-v1/right-of-reply](https://www.rational-magic.com/s/linear-v1/right-of-reply/). --- *Strategy by Rational Magic · rational-magic.com · Prepared May 2026.* *Evidence: 386 Reddit posts (deduplicated across r/Linear, r/webdev, r/ProductManagement, r/SaaS, r/startups, r/programming, captured via Apify Reddit Scraper), 5 AI tools each running three standardised questions (Claude Opus 4.7, ChatGPT GPT-5.4-pro, Gemini 3.1-pro-preview, Perplexity Sonar Pro, Grok 4.20, via OpenRouter API), and captured copy from linear.app (homepage, pricing, about, customers, /now/ai, /next, changelog). Full sources and methodology at [rational-magic.com/s/linear-v1/research/](https://www.rational-magic.com/s/linear-v1/research/).*