Should Linear stay focused on product development teams or expand into work management for the whole company?

Introduction

Linear has built its reputation by being the tool product development teams actually enjoy using: fast, keyboard-first, and opinionated about how software gets planned and shipped. In 2026 it passed $100M ARR with 40,000+ paying companies and a 177% net revenue retention rate, and much of that expansion comes from adjacent teams (design, product, support, and leadership) joining the same workspace. The question is whether Linear should push that expansion all the way into general work management for marketing, HR, finance, and operations, competing head-on with Asana, Monday.com, ClickUp, and Notion, or stay focused on the product development lifecycle, where it is now becoming the context layer for coding agents.

My position going in: the answer is not a binary "stay or expand". It is about where Linear's right to win ends. I'll clarify goals, analyze the market, set a vision and roadmap, prioritize, plan execution, define metrics, and cover risks before recommending.

Step 1

Clarify the Strategic Goals (3-4 minutes)

• What is the growth goal behind this question? I'm assuming leadership wants to keep NRR well above 150% and grow ARR from $100M+ to several hundred million without a heavy sales motion. Is the concern that seat expansion inside engineering-led customers will plateau?

Why it matters: Seat expansion favors adjacent teams at software companies; new-logo TAM favors non-software companies. Expected answer: Mostly expansion within existing customers, plus credibility in enterprise deals. Impact on approach: Points toward "adjacent teams at software companies" rather than a horizontal pivot.

• How does the agent strategy factor in? Since the March 2026 Linear Agent launch, the company has said issue tracking as we knew it is dead and that Linear is context infrastructure for agents. Is expansion meant to support that bet or compete with it for resources?

Why it matters: A few hundred people cannot build a horizontal work OS and an agent platform at once. Expected answer: Agents are the top priority; any expansion must reinforce them. Impact on approach: Expansion is only attractive where it feeds better context into agents (customer feedback, specs, requests).

• What do customers already do? Do we see non-engineering teams using Linear today, for example through Linear Asks, Customer Requests, or guests on the Business plan?

Why it matters: Organic pull is the best evidence of right to win. Expected answer: Yes. IT, People Ops, support, and design teams appear in many workspaces, mostly through Asks and Slack intake. Impact on approach: Build on existing pull rather than speculative markets.

Key assumptions: the goal is expansion revenue inside software companies, the agent bet cannot be starved, and the opinionated, craft-led brand must not be diluted.