Linear at 100 Engineers: Where the Cracks Start

Linear is the rare developer tool whose adopters describe it in language usually reserved for typed languages or terminal emulators. Engineering teams who pick Linear stop talking about Linear and start talking about their work. That is the highest compliment a productivity tool can earn. It is also the trap: the loud minority of large engineering organizations that have outgrown Linear's opinions are quieter than the satisfied majority who haven't, and the gap between the two experiences is wider than the marketing acknowledges.

We tested Linear at three engineering organizations during Q1 2025: a 60-engineer scale-up, a 110-engineer mid-stage company, and a 240-engineer growth-stage company. The smaller team adored the product. The mid-stage team was satisfied with reservations. The largest team was actively considering Jira.

Why the love is real

Speed. The product is the fastest piece of project-management software in the category and it is not close. The keyboard shortcuts are coherent. The data model is consistent enough that any engineer can predict where a given piece of state lives. The cycle planning model — short, fixed-duration sprints with clear scope — is the right answer for the modal engineering team and Linear's implementation is the cleanest in the category.

Linear is the rare developer tool whose adopters stop talking about it and start talking about their work.

The integrations are the other underrated strength. The GitHub, Slack, and Figma integrations are first-rate. The API is a real API, not the documentation-shaped stub Jira shipped for years. Internal tooling on top of Linear is more practical to build than on any competitor.

Where the cracks open

Reporting at scale. Linear's reporting model is built for a single team or a small number of teams. Past 8–10 active teams, the cross-team views become harder to use, and roadmap-up views — what's the state of all 14 streams of work, summarized for a leadership review? — require external tooling or manual aggregation. We watched our 240-engineer test site spend roughly 6 hours a quarter pulling Linear data into a separate dashboard for the engineering leadership review. That is a real cost.

The opinionated workflow model is the second crack. Linear's "you do it our way" stance is a feature at small scale and a constraint at large scale. The 240-engineer team had four sub-organizations with materially different working models — the platform team, the product engineering team, the SRE team, and the embedded ML team. Each wanted a slightly different cycle cadence, status taxonomy, and prioritization model. Linear's flexibility for that level of variance is meaningfully less than Jira's, and that is structural.

The third crack is enterprise pricing. The Enterprise tier has moved upward at a pace that puts Linear within hailing distance of Jira's per-seat pricing for organizations that need SAML, advanced permissions, and audit logging. Linear is still better software at that price. It is no longer cheaper software, and the procurement conversation has changed because of it.

The honest comparison

We are bullish on Linear up to 100 engineers without reservation. From 100 to 250 engineers, Linear remains the better experience but the operational cost of working around its limits begins to show, and a reasonable engineering leader could pick either Linear or Jira and defend the choice. Past 250 engineers, the case for Jira on breadth alone becomes harder to argue against, even though the experience gap is wider in Linear's favor than the typical Jira-defender will admit.

The verdict

Linear is still the right answer for most engineering organizations. The cracks at scale are real but they are scale problems, not product problems. We would still pick Linear today for any engineering team under 100. We would think hard above 250. And we would expect the company's product roadmap over the next 18 months to address the largest single gap — multi-team reporting and roadmap-up views — because the failure to address it is the only thing keeping Linear from a clearer victory in the segment.