# Scaling Linear's GTM to $100M+ ARR — Cristina Cordova, COO

## Executive summary

Linear, a product initially focused on issue tracking, is undergoing a fundamental shift toward agentic workflows, driven by the rise of AI. The company has prioritized building a 'product development system' that minimizes manual intervention, evidenced by over 50% of issues now being created by agents. This transition has necessitated changes in GTM strategy, team structure (eliminating SDRs and forward deployed engineering), and pricing, moving from seat-based models to usage-based billing.

## Key takeaways

- The Death of Manual Tracking: The company has pivoted from being an 'issue tracking' tool to an 'agent orchestration' system. The core philosophy is that manual work in a system is obsolete, leading to the development of features like 'triage intelligence' to automate workflow steps (1:05:54).
- Agent-Driven Workflow: Linear launched its MCP server in 2025, and within 1.5 years, over 50% of issues are created by agents, demonstrating a massive shift in how work is managed (1:08:59).
- Strategic Team Optimization: The company operates with a 'do more with less' philosophy, having never hired SDRs and not engaging in forward deployed engineering, preferring Solutions Engineers for deep technical integration support (34:40, 42:23).
- Pricing and Business Model Evolution: Linear is transitioning from a seat-based model to usage-based pricing, particularly for AI features, which are often tied to the costs incurred by running services like coding sessions (50:06).

## Technical details

- Agentic Systems and MCP: Linear utilizes an MCP server and has built APIs to allow external agents to deeply integrate and interact with the product, enabling agents to perform tasks like assigning and delegating issues (1:08:59).
- AI Feature Implementation: AI features, such as 'triage intelligence,' are integrated directly into the product rather than relying solely on external LLMs. The company uses Frontier models for chat and offers choices between OpenAI and Anthropic models for coding sessions (50:06).
- System Usability and Integration: The product is designed to be highly usable not just for engineers, but for non-technical roles (Sales, Ops), reducing the need for complex, dedicated admin roles. Solutions Engineers focus on complex migrations (e.g., 30,000 users from a legacy tool) (1:08:59).

## Practical implications

- Companies must re-evaluate their GTM strategy, as the core product function may be rapidly changing due to AI capabilities.
- The concept of a 'moat' is shifting from proprietary features to organizational speed, team quality, and adaptability.
- Sales and support teams must evolve to manage and validate AI-generated outputs, ensuring a high-quality, human-in-the-loop experience.
- Pricing models are moving toward outcome-based and usage-based billing, requiring transparency regarding underlying service costs.

## Topics

AI, Product Management, Go-to-Market Strategy, Software Architecture, Pricing Models, Karri’s blog post “Issue tracking is dead”

Source: https://www.youtube.com/watch?v=x0VSm6IjcDQ
