Latent Space ↗ · 2026-11-20 07:58 · UTC+8
Scaling Linear’s GTM to $100M ARR — Cristina Cordova, COO
People Latent Space Source language: English
Linear COO Cristina Cordova discusses how the issue-tracking company reached $100 million in ARR, driven by rapid AI adoption and a shifting product strategy. More than half of all tickets on Linear are now created by AI agents, and the company has integrated with tools like Codex, Cursor, and GitHub Copilot.
Full text
← The conversationsLatent Space Podcast
Scaling Linear’s GTM to $100M ARR — Cristina Cordova, COO
>50% of tickets written by agents, the AI budgets behind $100M-in-months ARR, and selling without SDRs or FDEs
Basil Chatha
Nov 19·84 min
Listen to this conversation84 min
Read transcriptWatch on YouTube
Open video on YouTube ↗
Linear was founded to build a better issue tracker. Seven years and $134 million in funding later, its CEO Karri Saarinen published a post titled "Issue tracking is dead." In this episode, we chat with Cristina Cordova, COO of Linear, about how the company navigated that and how its go-to-market changed along the way.
Cristina spent seven and a half years at Stripe, led platform and partnerships at Notion, and was a partner at First Round before joining Linear in 2023. Linear's founders built it after living with legacy issue trackers at Coinbase, Airbnb and Uber, and it spread self-serve through startups like Vercel and Ramp.
When she joined, Linear had about 40 people and one salesperson. Since then it has shipped an MCP server, a platform for building agents into Linear, integrations with Codex, Cursor and GitHub Copilot, and its own Linear Agent. Agents created 3% of Linear's work a year ago. Now it's more than half. Linear passed $100 million in ARR this year with more than 40,000 paying customers and 177% net revenue retention, and in August employees sold $99 million in stock at a $2.5 billion valuation.
We talk about why she stopped chasing enterprise deals three weeks after joining, why Linear has never hired a single SDR, why it won't let an LLM answer support tickets on its own, and what the AI budgets behind $100M-in-months ARR mean for everyone else.
Half the work on Linear is now created by agents
Linear shipped its MCP server in May 2025, and Cristina says it was basically the first in its category. A year and a half later, more than half the issues created in Linear come from agents.
That doesn't mean Linear wants to be a database with an MCP server on top. Cristina thinks SaaS companies settling for that are making a big mistake. If the agent workflows inside your product aren't better than the ones outside it, nobody has a reason to open your app.
So she watches two lines: agent usage and app usage. If agent usage climbs and app usage doesn't, you're becoming a commodity. At Linear, both are up and to the right, because people still come back to the app to see and coordinate the work.
Jump to the MCP discussion →
"Issue tracking is dead"
When Karri published "Issue tracking is dead" in March, most of Linear's customers agreed with him. Then they asked the obvious question: so what am I buying? Linear's answer is a product development system built around agent orchestration, where humans stop doing the manual work of filing, labeling, assigning and closing issues.
Customers had been pushing it there. Most of the frontier AI labs run on Linear and wanted it to move faster. Pre-AI companies like Ramp and Coinbase were building their own internal agents and needed an API to plug them into Linear.
Cristina says Linear is lucky it's small enough to cannibalize itself. Google has a much harder problem: put an AI answer above every search result, and fewer people look at the ads.
Jump to the "issue tracking is dead" discussion →
The AI budget behind $100M in months
The thing speeding up purchases right now, Cristina says, is AI budget. Companies carved out money for AI tools that didn't exist before, and any product that fits inside it skips the usual fight for spend. At some companies that budget is very high.
It's already starting to change. Buyers are signing one-year deals and paid pilots, not three-year contracts, because nobody knows what they'll want in two years. And some overnight-$100M stories are a handful of $30 to $40 million contracts with defense companies or giant law firms. That's a very different business from Linear's 40,000 paying customers on what was, until June, entirely seat-based pricing.
When those one-year deals come up for renewal, we'll find out whose ARR was real.
Jump to the AI budget discussion →
Linear threw out its 2025 enterprise roadmap
Three weeks after joining in 2023, Cristina crossed "move upmarket to enterprise" off Linear's company goals. It had one salesperson. She went after growth-stage companies that would have to rip out an existing tool instead, the same way Stripe won new businesses long before it won switchers.
Linear finally declared an enterprise push in 2025, with a roadmap full of features for large organizations. Then agents happened. Linear built an MCP server, an agents platform with a whole new set of APIs, and integrations with Codex, Cursor and GitHub Copilot. None of it was planned, and a lot of the enterprise work never got done.
Cristina chose to race ahead anyway. Competitors waited, and enterprises started putting Linear on their shortlists.
Jump to the enterprise roadmap discussion →
No SDRs, no forward deployed engineers
Linear has never hired a single SDR. Cristina thinks the qualification call wastes the customer's time: they want a demo, not questions about their budget. AEs do their own outbound, with tooling to keep it personal.
It doesn't do forward deployed engineering either. Linear should be easy enough to adopt that nobody needs access to your systems. Solutions engineers sell alongside enterprise AEs instead, sometimes building a working ServiceNow integration overnight to show a prospect it can be done. Cristina adds that an opinionated tool gives agents cleaner data than one where every team defines "bug" differently.
Support stays in-house, and Linear won't let an LLM answer tickets on its own. AI drafts replies and a human decides what goes out. Customers sometimes assume the replies are AI because they arrive so fast. In three and a half years, Cristina has never had an escalation over a bad support experience.
Jump to the sales team discussion →
Everyone wants outcome-based pricing
Cristina would love a model like Intercom's Fin, which charges for each support conversation its AI resolves. It's harder for Linear. What is auto-triaging a bug to the right team worth when one company thinks that's the PM's job and another doesn't?
Until someone cracks that, Linear charges for what costs it money and keeps the rest free. Seats stay. Linear Agent chat is free even though it runs on frontier models. In coding sessions, users pick OpenAI or Anthropic models and harnesses, and Linear passes through the published API price plus a small markup. Loops run on AI credits.
Linear doesn't start charging for things that used to be free. New AI features launch as free betas with notice that pricing is coming, and prices start high and come down rather than the other way around.
Jump to the pricing discussion →
Why not hire 100 salespeople?
Cristina says Linear runs on about half the headcount of companies at its stage and revenue. A sales team bigger than the rest of the company would have cost it the trust engineering now has in sales.
From Stripe she brought a 40% rule: at least 40% of the company should be engineering, product, design and data. If sales wanted more people, it helped recruit engineers first. Linear has no hard rule, but one of the first things she built was a headcount spreadsheet by function, and she still watches the ratio.
Hiring is slow on purpose. Candidates do a work trial on a real problem. Hers was writing Linear's go-to-market plan for the next six to twelve months, which then became her job. At about 170 people, the only C-suite is the founders and her.
Jump to the hiring discussion →
Show notes
Linear — the product development system where Cristina is COO.
Sharing Linear's growth with the people building it — the August tender at a $2.5 billion valuation, with more than 40,000 paying customers and 177% net revenue retention.
Issue tracking is dead — Karri's March post on why Linear is building for agents.
Linear MCP server — the May 2025 launch Cristina says was basically a first for the category.
Introducing Linear Agent — the built-in agent whose chat Linear keeps free.
How we built Triage Intelligence — the feature that suggests labels and catches duplicates in incoming issues, Cristina's example of AI that doesn't need to be an agent
Coding sessions in Linear — the June launch that ended Linear's all-seat pricing, running Claude Code and Codex on AI credits.
Introducing Loops — recurring agent jobs, also billed with AI credits.
Intercom Fin pricing — $0.99 per resolved conversation, the outcome-based model Cristina wishes fit Linear.
Timestamps
0:00 Intro
0:51 Meet Cristina Cordova, COO of Linear
1:39 Why Linear hired a COO at 40 people
5:01 Her work trial: a go-to-market plan for Linear
12:11 Crossing enterprise off the company goals
20:00 Why being a database behind an MCP server isn't enough
23:39 Selling after "issue tracking is dead"
34:40 Smaller, flatter teams and no SDRs
36:14 AI-drafted support replies with humans in charge
42:23 Why Linear doesn't do forward deployed engineering
47:53 Why some AI startups hit $100M ARR so fast
50:06 Moving from seats to usage-based pricing
57:07 Trading the 2025 enterprise roadmap for agents
1:03:28 What Linear's moat is now
1:05:54 Why not hire 100 salespeople?
1:08:59 Stripe's 40% rule for engineering headcount
Transcript
Automatically transcribed from the revised edit; names and wording may contain errors.
0:00 Karri writing this blog post, like issue tracking is dead. So like how do you explain to your customers that like, hey, you know, our entire business was issue tracking before and now our CEO just wrote this blog post? The great thing about our business is that we're not like so big to like kill ourselves. Right? Yeah. Like, it's probably really hard if you're Google to, like, kill the search business. Yeah. Right? And put an AI, you know, box at the top of every search result, and maybe no one's gonna look at the ads. Right? So your entire business is upended. And, like, yes, the unit of the issue still exists, but we probably shouldn't have a world where people are, like, manually tracking work. Yeah. So, like, that's what's dead. Right? So in a lot of cases, when we were talking to various customers as this, you know, blog post came out, most of our customers were like, yeah. Tracking is dead. And by the way, like, what are you guys? What am I buying? Right? Cristina Cordova, you're the COO of Linear. Could you introduce yourself? Yeah. Yeah. So I'm Cristina. I've been at Linear for about three and a half years now. Joined as COO, and I'm still COO today. Prior to Linear, I spent time at Notion leading our platform, so the build out of our APIs, and then our partnerships and self serve growth initiatives as well. And then before that, I was at Stripe for seven and a half years. And there, I led a lot of our early partnerships and go to market, and then moved over to the product side and built out some new products for early stage companies. So I've been probably anywhere from like the product side of a company and like managing engineers all the way to, managing, you know, the business side of a company as well, which has been really fun.
1:30 So why did Linear hire a COO at, like, 40 employees? Is that, like, odd or is that pretty normal? I mean, I I generally don't believe every company needs a COO. Yeah. Right? Like, when I talk to founders and they're like, hey, like, I think I found product market fit. Like, how do we start to scale, like, the business side of the company? I am often, I feel like, cautioning against maybe hiring someone like me. So I think for every company, it's a little bit different. I think you have to really understand as, like, a founder, like, what are the things you need and what are the things you're looking for and the people that you bring on to the team. Often early on, it's just like I need someone to, like, sell something. Right? We have expanded beyond the capability of the founder CEO to sell every net new customer. Right? So there, I generally talk about, well, you should hire folks in sales. Maybe hire a sales leader to build out a team. Right? But if you're not exactly sure what you're looking for in, like, marketing or operations or other parts of the company, then it may very well not make sense to hire someone like me. You know, I think with the Linear founders, you know, they were incredibly focused on, like, design and engineering and product. And I think they had a really great, you know, kind of combination of skills between the three of them. But as we were starting to scale the business side of the company, they didn't necessarily look at, like, the next salesperson that we hired and said, I know exactly what we're looking for here, and I know whether or not sales is performing really well. Right? So if you don't look at different parts of your company and say like, okay, I know what great is, and I feel like I have a good sense of, like, how to get to great, it can sometimes be helpful to hire someone like me or, like, a functional leader, like, when it comes time to do that.
3:00 Yeah. So, like, what did the business look like at that point? Like, can you talk about, like, what revenue they were at? Or Yeah. We were probably... I wanna say, you know, we had some large customers, but no, like, public company customers. Probably no customer above, I wanna say, like, maybe 500 seats or something like that. So I would say, like, we mostly tapped out at, like, mid market. And we were probably best well known for being a great product for startups, but not necessarily a great product for other companies Yeah. At that time. You know, and I think at that point in time, we were we're doing well with like a product led growth model where most people were using our product because they signed up self serve. Mhmm. And then grew with us over time. So companies like Vercel and Ramp and many other customers like that, you know, really never talked to a human being at Linear. Signed up for the product, started using it, and then started scaling, which was great. Like, you know the product can do a lot of work on its own. But it was also start... Like, time to start selling to, you know, the company that is not even gonna put, like, a lick of data into your service without, you know, signing a contract Yeah.
4:30 And doing a pilot and surveying their team on, you know, what tool they're using before and what... You know, what tool is this and what's better. Right? So that was a very different kind of motion for the company to start scaling to larger companies. And that was, like, pretty much my objective. And we've at least 10 x ed, I think, since I joined. So... And you joined, like, four years ago? Three... Almost three and a years ago. Yeah. Oh, okay. So I think the Linear founders have talked about this. I think you have as well that, like, before you join Linear, you always do a, like, a trial period? Yes. So did you also have to do a trial period? I did. Okay. Yeah. Yeah. So, yeah. Like, what was that like? Yeah. I mean, I think my project was quite simple. It was something like, you know, come up with the go to market plan for Linear, you know, with a bounded time period, like, for the next six to twelve months or something like that. Right? And I think the good thing about that is that, you you know, that is the job. Like... Right? So you're not giving someone some, like, fictional project that's not really, like, representative of, like, what they would do when they join the company. It's like a real, project. And that would, you know, effectively be my job in joining the company. So Yeah. You know, if they didn't like the outcomes that I produced as part of that project, they probably, you know, shouldn't hire me. Yeah. So I think it was a really good way of saying, like, I have some ideas of what the company can do better, but also I wanna, like, get feedback from the people who are on the ground. Like, you know, we had a salesperson on our team. We had someone doing customer success. We had some people doing support and, you know, one or two folks doing marketing. Right? So kind of getting their perspectives on different parts of the business and, like, where I should focus and where where to prioritize.
6:00 And then making sure that, like, the company was also bought in on, like, that vision for the world, was I think really helpful for me. And then when I actually started at the company, it was almost like I have this little blueprint Yeah. For, you know, what my job should be and what I should accomplish. Can you talk about, like, what was in that plan? Think a lot of it was like brand and marketing oriented. So like, you know, things around like making Linear inevitable in a lot of ways. So, you know, either you're already on Linear or you should be like planning your move to Linear effectively. And most companies that we wanna acquire should be, you know, in, you know, one world or the other. So a lot of that was around, you know, driving the brand, building storytelling, I think increasing awareness for the company because I think we were we were well known, but I would say in like particular niches, not really outside of Yeah. Okay. So it's like, you know, we were doing marketing, but like the only marketing that we were doing was like sending out emails if we, had a change log of something new that we released. And it turns out that, like, less than 10% of users, like, subscribed to emails. So most people didn't necessarily know even just, the new features we were shipping, which was interesting. And then we would, like, send a tweet.
7:30 Okay. Like, from from the founders' accounts or, like, from the company account? And then and then, you know, the founders would reshare and, you know, they have their own, like, pretty strong, like, social presence as well. But, you know, that was like the extent of it, really. Yeah. Like, so, you know, a lot of it was just thinking about, okay, like, how are we telling a more holistic story in a better way? And then how are we actually reaching the people that we wanna be reaching? It turns out that, like, actually a lot of our users are, like, in the app, you know, day to day. Yeah. And so, like, why are we not just, like, giving them notifications about, like, what's changing within the product, like, within the place they're already at every day. Right? So, you know, just thinking about things that could be great ways to market to existing users or market to, like, net new customers that also didn't feel like off with the brand. Right? Yeah. So I spent a lot of time on that. A lot of it was also just like growing the sales team. You know, I think a lot of early stage companies, especially that are like engineering driven, like product led growth oriented are like, you know, the product should sell itself. And then everyone realizes like, well, that gets you to a certain point. Yeah. And then when you want to, like, grow faster, right, you also need to start thinking about, reaching people in different ways. And not everyone buys products self serve. And especially when you're choosing a system that's like so core to like your product development process, which we are. Yeah. A lot of companies are not going to make that decision without like building trust with human beings. And, you know, when I was doing my work trial, we had, one person on sales. Right? That was not you. So it was just like, you know, there's there's only so much you could do with, like, one person.
9:00 Right? And were they, like, an experienced salesperson? Yeah. Yeah. Yeah. Yeah. Yeah. He's actually our sales leader today. Okay. Cool. So leads our entire sales team. So he's great. But, you know, at the time, I would say this wasn't really on him. It was more on the company. It's just like, how do we actually think we wanna grow this team? Right? You can grow a sales team in lots of ways. You can have like lots of SDRs. Mhmm. We don't have any SDRs. You can have forward deployed engineers now. That's very popular. Right? We actually don't do, forward deployed engineering. We have solutions engineers, which I, you know, I think is distinct and somewhat different. But we added those later. We really... And that's part of the sales org? Yeah. Cool. We really optimized our team at the beginning for hiring AEs who had experience, like, selling technical products. Because we knew, like, if you had sold to a designer, if you had sold to an engineer before, we wouldn't necessarily have to teach you how to do that. And I think selling to someone who's like very discerning, doesn't wanna see your fancy slides, just wants to get into a demo Yeah. You know, is very different from selling to like a person in, I don't know, people ops or, you know, something else. So, looking for people with that, like, very explicit experience and then making sure that we could, like, onboard them and train them and get them, like, really competent in the product itself. Yeah. Because that's required to build trust with our customer. Right? So just figuring out, like, what's different about this company and what's going to be different about hiring or scaling, you know. And also, like, what's the way that the founders wanna do it and, like, can we do that? So support is an interesting example. When I was interviewing, the founders were very clear that, like, they did not wanna outsource support. And I've never worked at a company that didn't outsource support. So that was like...
10:30 Yeah. Thought Stripe does it internally. Right? No. They outsource. Oh, okay. Yeah. Interesting. Unless something's changed since I was there. But, you know, they have internal folks who work on support too. Yeah. But they do outsource. So, you know, I think for us, that was something that we really wanted to maintain because we really cared about, like, delivering a high quality experience, delivering a fast experience, and knowing that for a long time, we didn't have a sales team. Right? Yeah. So because we didn't have that, we knew that your first touch point, often, if you wanna talk to a human being, was going to be support. So the support better be good. Yeah. Right? And so we've still been able to figure out how to scale the team today into, like, a global team that does not outsource at all. So, you know, we'll see what the future brings. Yeah. You know, never say never on any of these things. But you know, are certain ways that we wanna do things and we probably wanna do them for like as long as possible, as long as long as it's like feasible for the business and makes sense.
12:00 Yeah. So when you first joined, like, I guess I've never been in a sales role, but like do you have to say, okay, we're starting with startups and we can't just immediately go to, like, big enterprises and start selling them? We have to, like, kinda go step by step. So, like, did you have to go, oh, we have to first get, like, medium sized businesses, and then at some point, we'll go enterprise? Like, how does that work? Yeah. Yeah. So when I joined Linear, I think we had, like, three goals, like, three company level goals. And I think one of them was, like, move up market to enterprise. And then we had, like, a company off-site three weeks after I joined. And I, like, got up in front of the whole company, which was, like, I don't know, 35, 40 people at the time. And, like, I showed the slide of the three goals, and I, like, crossed the, like, one that says we're gonna go after enterprises out. Okay. Because I was like, we have one person. We have literally one person on sales. Like, you know, you're not going upmarket to enterprise with one person. Yeah. Like, you know, so you have to think about, like, what are you capable of doing? What do you need to, like, learn in order to to get there? And then do actually have the resources to, like, accomplish that goal? Right? And, you know, I I don't think we had any of those things at that period of time. Yeah. Right? We had companies that we had primarily won because they had scaled into being like a growth stage business or like a mid market business effectively. But we hadn't done a lot of like acquiring net new, like mid market companies at that point. So I changed that goal to say like, no, we're gonna go after like companies in the growth segment. And that's gonna be our goal. And if we can win a lot of companies who are in the growth segment, who already have, like, a tool, that does in some ways what we do, and we're... We have to go in and we have to convince them to, like, rip that out and replace it with Linear, then if we're able to do that, that gives me the confidence to say that, you know, in a year or in two years, we're gonna be able to go after enterprises.
13:30 But like, I don't have confidence in that now, so why would I set that as a goal for the team? So completely agree. It's like really about setting those baby steps and making sure that, like, you're doing well with companies that you can serve today incredibly well. So that those companies, when they're doing like, you know, they're getting, like, the reference calls from the larger companies being, hey. Like, do you like Linear, and has your experience been good? They're saying, like, really positive things. And that helps us land, like, the net new customer. And, like, it worked very similarly when I was at Stripe. Like, we did not win a lot of, like, net new companies that were switching over from a competitor Yeah. For a long time. We did a great job, like, winning every net new business that was created. So, like, a startup Yeah. That's implementing payments for the first time. And then we kind of started to win companies who were switching over. And some of that stuff just takes time. It's very... Like, it's very different to sell a product where you have to rip technology out that already exists and replace it than just to sell something that's, like, nice and shiny and new on top of, like, an existing set of systems.
15:00 Yeah. So knowing that I was in, like, a very similar position in this role, it was important that, like, I just oriented the team around, like, what I felt was like a solvable problem. And then only in twenty twenty five... So that was 2023. Only in 2025 did I, you know, go up in front of a company and say like, we're going after enterprise this year. Right? Oh, wow. And that was when we started our enterprise sales segment and built out that team. Yeah. So... Okay. You guys are going like medium sized businesses. And so you are getting everyone to basically like... Because most peep... Most companies have an issue tracker. Right? Yep. Or some kind of... So you have to try to like rip them away from them. So yeah. Like how do you convince them to say, oh yeah, we're using x y z product. It works for us. But, yeah, like, you know, pitch me, basically. Yeah. And Why should I switch it? The early days, it was about being, like, significantly better Yeah. Than what the alternative solutions were. Right? I don't think you can be, like, 20% better, 30% better, and get people to switch because there's a switching cost involved. Right? So I think you have to figure out how you articulate how your product is better than what is already, like, serving the market reasonably well. Reasonably well enough to... That they have like a lot of companies that are using their product. Right? But the good thing about the space that we were entering, and I think one of the reasons why like the Linear founders chose this space were because they were all users of those legacy tools Yeah. Right, when they were working at, like, Coinbase and Airbnb and Uber. And so they knew, like, no one liked these tools.
16:30 Yeah. Right? And when they were getting rolled out, like, at their companies, they were like, oh, no. Like, you know, the fun time is going away. We have to start using these tools. Right? So, in a lot of ways, it really helped that they had this, like, knowledge and existing awareness of, like, the feeling that came with the competitors in our space Yeah. And could figure out how to build a product that got people really excited, like, to manage their work. Right? Which is presumably not something that you would expect. So a lot of the emphasis in what we built early on was in like design and UX. Right? Yeah. Make it a product that people want to be in every day and have to use. The hard part about that is that people have to like try it before they get it. Right? Yeah. Versus, like, seeing a couple slides in a sales deck and being like, okay. Like, I get it. Right? So one of the things that we did, I think, very well strategically was just having a product that anyone could start using. So, you know, a free product initially, that once you hit certain limits in terms of usage, you would have to start paying for. So a lot of people who started to use Linear for their company, actually were just playing around with it for their own purposes for free and got a sense of like how usable it was and how much easier it would be to utilize the product compared to competitors. So we started very much there. And I think that worked well for a period of time. Now our approach in terms of like how we sell Linear is very different. We're typically talking to companies about the sea change in the space that has happened over the last year and a half, two years in terms of like, you know, your entire, like, product development process has been upended. Mhmm. The way that you build products has completely changed.
18:00 And it doesn't make sense anymore to live in a world where you are... Like, you have, like, a manual way of saying, like, oh, like, I found a bug. Oh, I'm going to, like, report that bug into my issue tracker. Yeah. Oh, I'm going to label it and assign it to this other person. And then that person is going to fix it and, you know, add a status update and then close it and then, like, notify the customer. And every step in that path is, like, completely manual. That's just... It doesn't make any sense for the world that we live in now. And you talk to most companies and they're like, yes. I completely agree. And so we've really oriented the company in the last year and a half around agents and agents performing a lot of the parts of the workflow that are effectively not product development. Like everything I described in that whole chain is like, that's not you building products. And so if you can make Linear a really great tool for agentic workflows, then the individual engineer or the individual PM or designer who's using Linear can ultimately be spending more of their time building products and less time like manually moving around work in a system to prove that they are adding value to a company.
19:30 Yeah. That's really interesting because it seems like the pitch early on was the user experience. Right? And now now it seems like the the humans are not going to be interacting with the with the UI. I actually think that a lot of companies right now are feeling like it's gonna be okay to just be like a database Mhmm. And, you know, have an MCP server and, you know, give all of their data away Yeah. To agents and have the agents like interoperate with them and think that like that's going to be a great business model. And and I don't think that's going to be a great business model ultimately. Yeah. I think you have to bring the agentic workflows into your tools and you have to make them better than the tools that people would be using externally to interoperate with your system. Otherwise, there's no reason for people to go into your tool. Right? And so for us, you know, the metric that we're typically looking at and and we've seen like a lot of change here where, you know, we launched our MCP server in 2025. I think we were basically the first company in our space to do it. And now, over 50% of issues created on Linear are created by agents in just like a year and a half.
21:00 Yeah. The work is created in an entirely different way than it was before. You know? So that kind of illustrates how much has changed in a pretty short period of time. And then when we look at how many users are coming to the app and integrating or creating issues within the app itself, that's also going up significantly. Okay. Right? So sometimes people believe that like, oh, I'm just I'm just using MCP server for everything now. But like you are also going back to the app and you're interacting with it because you need to visualize things. And often, like, a chat interface isn't the best way to visualize all the work that a team is doing. It's not great for collaboration because it's typically, like, single player only. Mhmm. And so I think for us, as long as, like, you know, the MCP usage line and the app usage line are kind of going up into the right together Yeah. It proves that, you know, we have both a great UX that's great for humans and also great for agents. Right? And that's like our goal, I think, as a product, that you can be great at both of those things. And, you know, it doesn't mean that like now that agents exist, you, like, don't have to care about the interface. Mhmm. And app usage is measured by just, like, number of people using it? Because, like, I'm I'm assuming also, like, your customer base is just growing. Right? So how do you Work created
22:30 in the application. So, you know, our, like, unit of work, like, smallest unit of work is the issue. Right? So if you just look at, like, work created, like, that's like a human going into the app, like our mobile app, our desktop app, you know, our web app, all of those places, and creating work. Right? If you look at how the work is like moving through the pipeline in a way, like getting assigned to an agent, sometimes that's done manually by a human. You know, sometimes an agent does it. Mhmm. But assign... Like delegates to another agent. Right? Yeah. Often, we're now part of the workflow. Right? You can use a feature we have called loops that will, like, automatically, assign an agent to a given issue and have the agent start, like, coding against it, for so in a lot of cases, it's like an agent is doing the work, but it's a Linear agent. Yeah. Right? Which we also wanna see. Right? So we have to look at, like, multiple different factors. But it's generally like app sessions that we're looking at in terms of trying to understand activity. Yeah. So I guess that leads me to like Karri writing this blog post like issue tracking is dead. Yeah. So I'm assuming you were in the middle of selling some contracts when he wrote that. So how do you explain to your customers that like, hey, our entire business was issue tracking before and now our CEO just wrote this blog post. Yeah. Yeah. Like how do you explain that to them and how did that transition happen?
24:00 Yeah. Well, I think the great thing about our business is that we're not, like, so big to, like, kill ourselves. Right? Yeah. Like, it's probably really hard if you're Google to, like, kill the search business. Yeah. Right? And put, an AI, you know, box at the top of every search result, and maybe no one's gonna look at the ads. Right? So your entire business is upended. And so, you know, I think that's a little bit of the like innovator's dilemma challenge that a lot of tools that were, like, pre AI have, and we were certainly one of those companies that was pre AI. Yeah. And so for us, like, the great thing is that it's like, okay. You know, we see that the world is going in this direction, and you can either, like, lean into it with the plan that you build the best product for the new era Mhmm. Rather than trying to, like, hold on to an era that, like, is probably not going to exist in a few years. Right? So, you know, if the workflow that I talked about with, like, you know, this like manual intervention by humans at every step of the of the process is not going to be the work that we live in. Like, you look at Linear now and like, yes, the the unit of the issue still exists. But we probably shouldn't have a world where people are, like, manually tracking work. Yeah. So, like, that's what's dead. Right? So in a lot of cases, when we were talking to various customers as this, you know, blog post came out, Most of our customers were like, yeah. Tracking is dead. And by the way, like, what are you guys? What am I buying? Right?
25:30 And so it's much more oriented around, you know, now being like a product development system. Right? We want you to focus on building better products, and we are going to build a system that enables you to do so with very little manual work. So it's also about, you know, saying, like, we're gonna create a new category. And like, yes, we will, you know, in a lot of ways still play in the old category, but we are also driving the vast majority of our resources as a team into this new category of things like agent orchestration, managing work in a way where you don't necessarily have to be doing a lot of manual, you know, taking tasks through a system, and that you're operating far more agentically, both, like, within Linear and also outside of Linear. So I guess, like, that transition or, I guess, that blog post, were you blindsided by that? Like, Karri writing Or like he was No. No. We were all were all on the same So were you seeing like were you seeing your customers were asking for that? Or was it that you wanted to push your customers that way? I think some of our customers were asking for I mean, Linear is used by the vast majority of all the Frontier AI labs, as an example. You know, the vast majority of top AI companies already use Linear. So if you look at, like, that customer set, so, you know, this kind of, like, net new generation of, like, companies Mhmm. That started after Linear. Many of those companies were saying, you know, this is the way that we're going. Right? And we want Linear to move in that direction. Otherwise, it's not gonna be the right product for us. Right? And then at the same time, we also saw with companies that were also like pre AI. So examples of this might be companies like, Ramp or Coinbase where, you know, they existed before all of this Yeah. And decided that they were going to invest their own internal teams to build like internal agents to do work with them. Yeah. Right? And so we were like, hey, we actually need an API that enables you to create agents within Linear.
27:00 So if you're one of these companies that, you know, it's almost pre AI but on the bleeding edge of AI still, and you're creating your own like bespoke agent to help manage various different types of work or code internally and you wanna own the proprietary data that's associated with that, we wanna build the API so that you can deeply integrate Linear with those tools. Right? And like there wasn't a system or a set of APIs that any of our competitors had at the time for that. So again, just like being first to build a lot of these new ways of interacting with Linear, you know, formats of agent workflows, and then building agents directly into Linear as well. I think we're all very new for us, and some customers were asking us for them. And I would say a lot of customers weren't. But I can tell you that now a lot of them are very happy Yeah. That we have a lot of these features. Because not every company is on like the bleeding edge of the way that product development is changing.
28:30 I guess that's what I was trying to get at is like, would you... I... I'm assuming because you were trying to go more like enterprise, a lot of them were those like legacy type companies. Right? Yes. And and not the kinds of companies that are really pushing us Yeah. In this direction. Bu