Skip to content
Live
Latent Space· Basil Chatha·· 54 minutes ago

Scaling Linear’s GTM to $100M ARR — Cristina Cordova, COO

Scaling Linear’s GTM to $100M ARR — Cristina Cordova, COO

Article

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

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. But now those are the companies that are reaching out to us and saying like, hey, a lot of the way that we're doing things has changed and the systems that we use to build products should be changing just as rapidly as like the landscape of coding agents as an example. Mhmm. And if you feel like your underlying toolset hasn't really changed, hasn't really evolved in this new world, then you should probably think about changing your toolset. Right? When you start like building these new features, how do you teach your customers how to use those features? How did you guys do that? Yes. Yes. So... Yeah. One, I would say, you know, again, we really emphasize with, you know, functions like sales and customer success that they understand the product very deeply. And we really try to get our sales and success teams to like share learnings with each other. So, you know, a lot of our calls are recorded with Gong as an example. And often, our own customers will be like, you know, screen sharing their workflows with us. And then we get to take that as like a learning to say, you know, here's how this company is doing it. Really interesting. Maybe I can take that to like another customer. Right? So there's both the, like, learning from your customers, which... I mean, when you have customers who are builders, you should always think about, like, how you're going to learn from them versus purely just how you're going to teach them. Right?

30:00 It's nice to have, like, AI Labs as customers. Exactly. Exactly. And then you're taking those learnings and you're saying, how do I package this up for a user that is maybe not at that point yet? Right? And then, you know, for example, we had customers who were like, oh, yeah. Like, wouldn't it be great if, you know, there was like an agent that existed that would like triage everything for me? Because like, no. Nobody wants to like groom their backlog. Right? Like, what a task that feels so outdated. Right? And so, you know, we built a a feature called triage intelligence, which effectively enables, anything that comes into your triage workflow, bug reports, feature requests, etcetera, to be, like, automatically labeled, assigned, put on the right team's queue. And like, you, as a human, do not have to do anything for that to take place. Right? So it's like, you don't need to, like, build an agent for this. We can just do it for you. Yeah. Right? So not everything necessarily needs to be an agent. It can just be part of the product. Right? So it's both taught us, you know, certainly how to teach the next customer, like, how to do things better. But it's also helped us incorporate that into the product itself.

31:30 Yeah. And then it becomes far more, you know, easy for a person on our team to sell. So how does that work if... Like, how do you teach salespeople how to use, like, engineering tools? Oh, well, the great thing about Linear is that, like, anyone can use it. Like, you know, if I think about, like, GitHub issues or something, when I go into GitHub, I'm like, oh. Like Yep. As, as, you know, someone who's not an engineer, like, oh, I'm gonna mess something up. Like, I don't belong here. Right? But I think the great thing about what we do is that that's not true. Like, we try to create a product that's, like, incredibly usable and, like, well designed, not just for engineers, but really for anyone. Mhmm. Right? And so now increasingly, we're getting rolled out across, like, you know, wall to wall within organizations. So, you know, teams like sales and ops and, like, anyone who wants to, like, know what's on the product road map or, like, be an input into what's on the product road map is using our product. And it's very usable for them too. Right? So I think that makes things far easier just because it's just... It's not scary Yeah. As, like, a system or a tool. And our salespeople, you know, have learned that. It just... In being at the company, we do a lot, as you can imagine, in Linear. So Yeah. You need to know how to use it just to be at the company generally. And then again, a a lot of it is in great, like, training of your people. And I think we've invested a lot in enablement. You effectively have to go through, like, various coursework effectively in order to be certified to even sell Linear Yeah. And get on a call solo with the customer. So we really require that, like, our sales reps understand a lot about the product. And, you know, maybe the most, like, complex engineering workflow would probably be, like, our code reviews product and or, like, our GitHub integration. Like, those can be somewhat complicated often because you have to set GitHub and and have like a demo GitHub workspace and Yeah. A demo Linear workspace to make sure that they all work together. That can be a little bit more complex.

33:00 But, you know, most of that is, you know, in relying on another tool and an integration workflow with it. But I think the great thing is like now we have like salespeople on our team shipping like copy edits to the website. And we have marketers on my team who are, you know, deciding like, oh, we wanna change like how we store this data so that we have like a better sense of like what this revenue operation system does. And, you know, things like that Yeah. Are like now accessible to everyone. And an engineer on our team just has to like review that change and Yeah. You know, approve it. And I think it's also making, like, just Linear the product and what we do far more accessible to them too. But, yeah, it takes time

34:30 Yeah. Yeah. Like with anything. So are your... Like like, is your team composition changing? Because now you're having, like, different teams, like, push copy updates to the website that maybe normally wouldn't have done that. And maybe, like, are you seeing, like, customer team compositions are changing because of maybe, like, how they're using Linear or just, like Yeah. Just agentic development, like, in general? Yeah. I mean, I think one of the things that people are talking about a lot today are... Is effectively how teams are changing in that they're remaining smaller, flatter, etcetera. I feel like I've been a lot of companies that, like, aim to work that way for a period of time, and then they just like grow out of it. And Yeah. And it changes. I think luckily, like, as a lot of these developments in our space were happening, like, Linear was already operating that way and I think has continued to operate that way. A lot of which, you know, can be due to AI. But I think as an example, you know, other teams do this differently. I think we've never had SDRs as an example. And I think that that comes from a belief that like a salesperson should be able to like write an outbound email. Like, I don't see why. Like... So what do SDRs normally do? Typically, they're, like, either doing outbound to new prospective customers and trying to get them in the pipeline or they're qualifying those customers as they come in. So they'll do, like, the first call. But unfortunately, that first call is very, like, not useful to the customer because, You're the second is just being like, so how big are you? And, like How much money do think might be able to pay us? Right? And again, like, our customer would hate to be on that call. They're like, why are you asking me questions? You are supposed to give me a demo.

36:00 Yeah. Right? Like, why am I wasting thirty minutes of my time on this call just to get to a person who can give me a demo? Right? So, you know, we don't have that function because I don't think it works well for our customers. But also because you can create systems and tooling and automations that make it easier for an AE to do outbound to a customer. Right? That feels like custom and useful. Right? And is able to like ultimately get to some point of engagement. Right? So, you know, that's one maybe difference between us and and other companies. I think we've I think we've also opted to think about areas of the business where we can have like fewer employees. Right? And what can you optimize with like tooling? So our customer experience team is like a great example. So, you know, what are the tools that we can use to automatically draft replies to customers Yeah. That write into us. Do you not see that like having LLMs write stuff to customers like produce slop? Like Yes. Like AI slop? Like, how do you how do you fix that? Yeah. I mean, the CX team, like, humans are the quality check I see. On that. Right? So we do not have AI send mass. Like, they... Like, a lot of companies. And other companies can do this, and and that's totally fine. Right? No no shame to other people. But a lot of other companies will say, hey, like, a 100% of questions that come into our support team are going to be, like, answered by an LLM first.

37:30 Yeah. And only if that customer writes back angrily, right, will a human come in and be like, oh, sorry about that. Yeah. Like, let me give you a real answer. Right? And we just don't believe in that model. Right? So I would much rather have AI like draft an answer, to the specific question based on the knowledge that, you know, it has coming in. And then a human can decide like, is that a good answer or not? But very often it's like, gosh, this would have taken, three sentences. And instead, I have, like, three paragraphs of, you know, a reply that ultimately is, not the most helpful. Right? And we get so much feedback on support where people were like... Are almost like either was this AI because your response was so fast. Yeah. And we just... You know, our our team's really fast. Yeah. So people think it's AI because it came to them so quickly. And then the second being like, wow. This is like the first good interaction I've had with like a support team in a long time. And that's kinda sad, you know, for like other tools and products out there. But, you know, for us, it's one of the things that like we give a lot of kudos to our team for that because it like sets a brand impression. Sometimes early in a customer's life cycle and sometimes, you know, they've been with us for years and are riding in for the first time and it gets them really, you know, feeling confident they they made the right decision. Right? So I think you can use these tools. They're tools. I don't believe in, like, blindly using these tools in a way that makes your... Like like, compromises your brand Yeah. And ultimately makes your team feel like it's... Like like almost less useful or less knowledgeable Yeah. Because it's relying on a tool to have all the knowledge that, like, a human should have.

39:00 Yeah. So you... Did you mention, like, downsizing the customer experience team? So... Not downsizing. But I I don't think we've ramped it as as we would have without Right? So I think some of these tools are are very helpful for enabling us to, like, not always have to grow teams linearly with, like Yeah. How how fast the business is growing. Yeah. Right? And, you know, I think on, like, other parts of the business, like like marketing and and other areas where it's like, oh, okay. We can do interviews with customers for customer stories. And, you know, we can have an AI tool, like, transcribe this interview, pull out like some of the most compelling pieces, but like we still have a human write the story. Right? Yeah. So just deciding like where you're going to decide to use it, like we don't like the way that a lot of AI writing feels. Yeah. So, you know, we've been like... Well, like, use it to help us, you know, find the interesting parts of, like, two hours that we spent with a customer. Yeah. But in a lot of ways for it to feel like how we want Linear to feel, which is like, you know, custom and handcrafted. Like, you know, we shouldn't use those tools for certain kinds of things.

40:30 Yeah. At least until they get better. So... Astra is pretty good at writing, I've noticed recently. Yeah. But anyway Yeah. Yeah. How does... Like, how does sales engineers fit into your team... Into the sales team? Yeah. Yeah. So we have what we call solutions engineers Oh, sorry. That are effectively the the same thing. They are kind of like partners to our enterprise account execs and probably like the upper end of our growth segment. And so they're spending a lot of time with sales as a customer has like really deep workflow questions. Or they're thinking about, you know, hey, I integrate with like this tool over here with it like a very custom API integration. How would I move that to Linear? Right? So you're asking someone who has like a deeper technical question. Yeah. Right? Or how would I perform a migration of 30,000 people from, like, in a legacy tool to Linear? Yeah. Right? And so, you know, a solutions engineer can come in with a technical mindset. Like, all of, you know, these folks can And the person build they're talking to is an engineer presumably? Yes. Yes. Almost always. And so, you know, that person has very detailed questions. And sometimes the people on our team are building like full end to end demos of like, oh, you wanted to see how we would integrate with ServiceNow? Like, I actually built this ServiceNow integration overnight. And like, let me show it to you. So it also makes a lot of these like transitions that customers are going through like, you know, very easy because they start to see like, wow. Like, it is possible to do these things like very quickly. Like migrating isn't that hard. Right? Because like, you know, this engineer just built this like, you know, quick importer, you know, in a day. Right?

42:00 Yeah. So sometimes we're we're helping customers along in the journey. We're typically not, like, going into their systems with access to their systems in a forward deployed engineering type of way, to, like, implement Linear. And I think a lot of that is like a philosophical belief. Like, we believe Linear should be easy enough for someone to integrate. Yeah. And, you know, we have competitors that have, you know, admins where their entire job is just managing that tool. And they are dedicated tool people within companies. Yeah. And, again, I think that works fine for products that are like almost infinitely customizable. Yeah. Right? But Linear is not that. Right? We tend to be far more of a purpose built tool. So we have, you know, pretty clear ways of doing things within Linear, but I also think that makes things far easier for agents to understand. Right? A lot of people are coming to Linear from other tools where, like, you know, bug as a label for this one team means something, and for another team means something else. And you can do that because bunch of different teams can work in, like, completely different ways, but it means that, like, the data is very difficult to discern. And so, you know, we're finding that with our system, it's just far easier for, like, agents to read and understand and work with as a result of some of these things. So I think the combination of, like, having that and then having, like, a technical counterpart to a salesperson... And often, like, our salespeople are working with people who are, like, you know, we have, a champion in the company, and they're saying, like, Linear is amazing, but I can't convince, like, this other person.

43:30 Can you help me? Right? You know, the IT person or the procurement person or, you know, someone else who's often not in the tool day to day. Yeah. Right? So maybe doesn't understand the challenges. And our salespeople are basically like advocates for that person and are like, okay. What can I do to help you sell internally? Right? And, you know, engineers are often not used to being like, need to sell other people within my company about this tool. Right? So that's like a learned skill that we can often help with. And and we find our salespeople are in, you know, kind of interesting positions, helping advocate for Linear through other people. Just curious, like, how long does it... Like, do you have a rule of thumb for how long it takes for, like, a case like that to, you know, get that customer to actually buy? Like, when, you know, they have to go to, I don't know, someone who has decision making authority? Yeah. Like the champion. Sorry.

45:00 Yeah. Sure. I mean, I think sometimes a decision can start from like one person. We've seen this. And then they get the buy in of the CEO, and the CEO just makes a top down decision. And it's like, we're moving a Linear over the weekend. Like, get used to it or get out. You know? And it's very, like, you know, dictatorial around, like, the decision that's being made. And those decisions can happen, like, in a month. Right? And those are, like, smaller companies I'm If you get... I mean, that... We had that happen, though, at a 1,000 person So, you know, again, it's just like if you have a CEO who is like, you know, I'm less of that type of person. Like, if I think my team should use a tool, I'll be like, why don't you all evaluate it and decide for yourselves? Right? Other companies work in very different ways. Right? So, you know, you have to think about, like, the politics of given organization, and every organization is inherently political in some shape or form. And then, you know, how do you ultimately, like, work this decision into a favorable way, you know Yeah. For your business. But, you know, then we'll see, like, companies. We we had one company that probably took two years, two and a half years or something. Like... And and it wasn't that they were in the sales pipeline the whole time. Yeah. It was like, they came in, oh, we couldn't convince the CTO. Like, and then they, you know, come in again, like, nine months later. Starts using me in the company. Yeah. Yeah. And then a different person comes in, like, nine months later, and it's like, I think we can convince the CTO now. Right? And then, you know, and it and it just takes, like, a really long time to finally get them to, like, approve and, like, make the decision. Sometimes it's budget. It's like, oh, we've already set the budget for this year. And if this is gonna require more spend, well, that's gonna be a 2028 Yeah. Decision. Right? Some companies operate like that.

46:30 Are you saying that like they're now operating like a lot faster because of the way like things are changing so fast now or not really still? Maybe like these more legacy companies? Yeah. I don't think they operate any faster, honestly. At least with decisions like this. Yeah. I would say for a lot of these companies, the things that... The thing that's helping them move faster is that like AI tools have effectively been like unblocked. Right? So if they believe that... The engineering team in particular believes that like this tool is going to make them better and it fits in like the AI budget. Yeah. For some companies, you know, that is maybe not infinite, but it is very high. Yeah. Whatever that budget is. And it was like, you know, add on budget that kind of had to come out of nowhere. Right? I think that's going to change. Yeah. It's starting to change for companies. But in a lot of ways, you if can like fit your company into that AI budget, then you are unlocking kind of budget that previously didn't exist. Right? And so that makes it far easier, I think, for companies to make a decision because like, oh, there is budget. We found... We've magically found budget that didn't previously exist before. Yeah. Know? Okay. So you think like a lot of this like AI companies are, you know, getting to a $100,000,000 of revenue within like three months? That's because of this basically. It's a lot of companies that previously didn't have budget for like experimenting with new tools. They're just kinda like, oh my god, our company's gonna die if we don't try any of these tools. So like, let's just experiment. And then, you know, at some point maybe a year from now, two years from now, that's gonna stop. Like they're experimenting right now and then, you know, they're gonna figure out what actually works, what doesn't.

48:00 I think I think a lot of companies are experimenting. And, you know, you're signing like one year deals maybe with companies or you're signing like pilot agreements with companies that have costs associated with them still. But you're not signing like a three year deal with a company because you're like, I don't know if I'm gonna like this. Yeah. You know, in two years, like, things are changing so rapidly. Is it normal for a company to sign a three year deal? If you're trusted Yeah. Like, we we sometimes sign very long term deals for that reason. It has trade offs. Right? Like, we can't move up our prices Oh, yeah. In that three year period of time unless you have, like, step ups built in to the agreement. But you know that you have that committed revenue. Right? So, you know, like... And for the business, the same is true. They feel like maybe they're getting a discount Yeah. For, you know, three years that they wouldn't have otherwise been getting. But but I would say like to the example you you had, I mean, I think a lot of those businesses are are very concentrated in the customers that we have. Right? So it's very different, I think, to be like a business like Linear that is, you know, 40,000 paying customers. Right? And like, historically, up until June was like an entirely seat based business. Right? Much harder to, like, grow revenue to, like, from zero to a 100 Yeah. Million overnight. Right?

49:30 And then, you know, you see companies where, I don't know, you sell to, the defense industry or you sell to, like, gigantic law firms or, you know, something like that. Yeah. And, you know, you sign a few deals that are, like, 30 to $40,000,000 in ARR. And then, okay. Great. We got to a 100,000,000 ARR. Yeah. Right? So, you know, certain kinds of businesses do have, like, more of that profile. So you're usage based now? We have some features that are usage based in terms of how we charge for them. Yeah. So how do you how do you convince your customers that that's that's a good idea to go from, like, seat based to usage based? Yeah. Is that hard to convince them? Yeah. I mean, I I would say, like, a lot of companies that are in, you know, the SaaS world Yeah. Are are certainly moving to usage based pricing. I think everyone would love for there to be like... Almost like the Intercom Fin model that existed for a long period of time where... Which was like, oh, if AI responds to your support ticket, like, you know, that costs a dollar. Yeah. And and you're like, is every support ticket that gets replied to, like, worth a dollar? Yeah. Like, okay. Great. Like, right? So you're you're pricing on, like, the outcome that you drive. Right? Think I it's a lot harder for other types of businesses to be like, okay. So what is automatically triaging this bug to the right team worth?

51:00 Yeah. Right? Maybe to every company, that's a little different. Maybe you believe, oh, that's the PM's job. Like, they they should be, like, you know, triaging bugs into the right queue, right, to the right person. And, you know, maybe another company says, well, I'd want my PM to spend their time talking to customers and, you know, building the product roadmap and doing other things instead. So I think there can sometimes be a debate in functions that are not very clearly outcome oriented, how you charge for usage based pricing. Mhmm. So I would love for there to be a world where, like, there's some kind of, like, outcome based model that makes sense for our world. I don't know that there is. So, you know, for now, we're mostly charging, you know, based off of like costs that we incur to run our services. Mhmm. And in some cases, those costs can be, you know, pretty high. Yeah. If you're running like a coding session in Linear or if you're doing things like, you know, run through my entire backlog and tell me what I should work on next. You know? You could have a very large backlog of a lot of things. Right? So, you know, those kinds of even just like chat questions to the agent can be like more expensive. We've decided to make certain things free. So like, you know, Linear agent chat conversations free, and we think we can continue to drive down the costs for that over time. You guys are using like open source models for that?

52:30 Right now, we're using Frontier. Okay. Even for the chat. Even for the chat. Okay. Okay. Yeah. Yeah. And, you know, TBD what the future holds there. And then beyond that, when you have a coding session in Linear, you can choose between like right now, OpenAI or Anthropic, models and harnesses. And the user ultimately gets to decide there and we charge basically by saying, like, here's what we were charged from the API. Here's the published rate and we charge like a little bit on top of that. Mhmm. And that's it. So making it very clear and transparent Yeah. For most users. And then for products like Loops, we have an AI credits model as well for that feature. So, you know, for everything else, it's a little different. The vast majority of our AI features are just like baked into Linear and you don't have to pay extra for them. So... How do you, like, how do you go about going to your customer and saying, hey, previously you guys were doing seat based pricing and now we're gonna do this? Yeah. I mean, I think it helps that, like, the seat based pricing isn't going away. Right? Like, so you're still paying for the core service, and we are not charging for things that were previously otherwise free. Oh, I see. Right? So it's it's very different, I think, when you go to a customer and you're like, So, like, what was free is now paid and usage based. Are, like, new features, basically. Yeah. Exactly. So sometimes we'll have a feature that's in a beta period, and we don't exactly know what it's going to cost or how to charge for it with usage based pricing because like, you know, you can, for example, run a very expensive Linear agent query and you could run a very inexpensive one. Right?

54:00 Yeah. So charging based purely off of like, you know, $1 per per query, like, wouldn't make sense in in that world. Right? So sometimes you just need to let customers, like, play with a new product to determine, like, what it's going to cost Mhmm. And what the best pricing model is. So typically, what we'll do is we'll have, a feature that's in beta, and we'll say, hey, this is an AI feature in beta. You know, we expect that we will charge for this in the future. But right now, it's free. Mhmm. Like, feel free to use it. See if you get value out of it. Give us feedback. And then we're... When we're ready to charge for it, we will let you know and give you notice. And I think that's worked generally, like, pretty well for us so far. And, you know, just trying to make sure that we're very clear with our customers. Sometimes, you know, we can have a six month beta period and then five months later, you're like, oh, I totally forgot that this was free. And in beta, I'm gonna be charged for it, and I'm disappointed. Right? It's hard... You know, there's nothing we could have done other than, you know, I don't know, warning banners in our product like, you are using a free feature that will soon be paid. There's only so much you can do about that. But I think just trying to, like, be open and honest with your customers that, we don't know what the business model is for this. Yeah. Like, we know we're going to charge for it because it's expense... It's an expensive product to serve to you. But we are going to try and, be as transparent as possible. And, you know, we hope you trust us. Right? And hopefully, like, every time one of these things happens, you are building more trust over time. I'll also say we tend to bias towards making things like more expensive at the start and then decreasing costs rather than like making things really cheap and then being like, oops. Like, actually, we can't solve... Like, serve this product for that cheap. Right? So just being like conservative in that way and where we are, like, able to lower cost for customers so that we get more adoption, we will.

55:30 Yeah. So you mentioned earlier that, like, when you came in, you had this, like, six, twelve month, like, go to market plan. Did you basically follow that go to market plan, like, to a tee, or did you have to change it along the way? And then how did that change back in 2025 when you guys started building the new agents features? Yeah. Yeah. I think I probably did every... I mean, I haven't looked at it in a while. Yeah. But I think I probably did everything, you know, for the most part, at least certainly at this point. Maybe I didn't do it all in the six to twelve month period that I thought I would. But a lot of it was like team building, hiring, you know, starting to think about launches, like product launches in a much more robust way. Like, you don't just, like, ship something and, like, move on to the next feature. You have to, like, continuously educate and and market products over time. So we think a lot of those things we've, like, adopted into, like, new make motions and ways of doing things for the team. And, you know, we certainly... And we went from, like, no sales team almost to to it being a very large percentage of the company now. So so, you know, I think a lot of those things have, like, ultimately, you know, shipped and and gotten out the door. And what was the second part of your question? It was like, how did you have to change that go to market strategy back in twenty twenty twenty twenty five when, like, the agents features came out?

57:00 Yeah. I think a lot of it was just, you know, sometimes, I think from a go to market perspective, you have a you have a long term road map. Right? And, you know, a lot of those things at the time were like enterprise features and other things to kind of help us go up market. And that was also... 2025 was a year where we said we were going after enterprise. Right? And then we saw everything that was happening in this space, and we're like, oh, we've gotta build an MCP server. Oh, we've gotta build an agent's platform with a whole new set of APIs. So anyone can build an agent into Linear. Oh, we've gotta build partnerships with like Codex and Cursor, and GitHub Copilot. So all of these agents are in Linear. And we did all of those things, but none of those things were planned. Like, we did not know we were going to do any of those things at the beginning of 2025. So that doesn't mean we did all of that and everything else that we planned for. It meant that, like, a bunch of the enterprise stuff that we planned for, you know, didn't get done. Yeah. So Meaning, like, there were, like, certain customers you were trying to go after? Or Like certain features that we wanted to build for, you know, workspaces that were of a certain size that would, like, you know, help us scale to like larger and larger organizations. And, you know, again, a lot of those things didn't get done. But I looked at it and I said, well, do we wanna be like behind all of this new stuff or do we wanna be like really racing ahead of where we think we should be? I think we chose to say like, no. We're gonna race ahead. And I think I also believed that if we did that and we did it well, that it would also win us new enterprise customers, just not in the way that we thought we would win them.

58:30 Yeah. Right? It wasn't gonna be about, you know, building, like, sub teams and multilayer, like, work streams, like roadmaps that work across multiple different teams, which you might want if you're a large organization. Right? No. It was more about, you know, building these things that make Linear work really well with agents. And, you know, because we built that and and our competitors, you know, waited a long time to do the same thing, I think we got ahead in a way that we wouldn't have otherwise. And a lot of enterprises put Linear on the list to be considered that wouldn't have otherwise. If you could go back to when you first started at Linear, knowing what you know now, like, what what would you tell yourself? Or what do you wish you knew? I feel like I probably go back and be like, you know, calm down. It'll all be fun. Like, it's probably what I would say. And what I mean by that, what that's, like, really alluding to is when I joined Linear in 2023, the startup market was not doing well. Right? Had all these dbt just came out. You had all these companies, yeah, in, like, 2021 and 2022 that raised these, like, gigantic funding rounds and were doing really well, you know, as we were kind of coming out of COVID. And then in 2023, like, it was the great, like, startup culling. Like, companies couldn't really get funded. A lot of companies were, like, cutting costs, like dramatically, trying to consolidate spend. So in in that world, it, you know, it was like much harder to grow, especially when in 2023, we were focused on startups. And then like growth stage companies a little bit. Right? So, you know, I think in a lot of ways, sometimes you enter into a space in like a market that's hard.

1:00:00 Right? Luckily, it was hard for everybody else too. So, you know, it wasn't like, you know, it was, you know, disproportionate in a way. But, you know, it did, like, affect the business. And, you know, you're trying to figure out ways to grow without that natural growth where you would have otherwise gotten. Mhmm. And then I think similarly with, like, all of the agentic development and the way that things have changed. Like, you you have to have a similar approach of saying, like, like trust in, like, engineering and product and design to build the products that they would wanna see Yeah. In the world. And we will build a business model around whatever that is. Yeah. Right? And it's not our job to exactly predict the future. And I think now we like, you know, we have a product roadmap that goes out max like six months because, you know, who knows how things are going to change. Right? And I think that really helps to say, okay. We're gonna create a story for, like, how the world is right now.

1:01:30 And we can expect that that story is gonna last for, like, six months from like a marketing perspective. And then it's probably going to evolve and change. And we shouldn't be afraid of being like, oh, no. We had this billboard that was like supposed to go up that had this other message, and maybe that message isn't right anymore. And it's like, yeah. You gotta just like move and change. And, you know, it's all gonna be okay. Right? But, like, you just don't have the same time to like plan a message, plan a strategy, like execute it perfectly as you used to, like, in the old world. So I think this new world, like, ultimately rewards speed and operating in a very different way. So, like, stay close to your customers. Focus would be like what I would go back. Do you think this is like a temporary moment in time, or this is just the way that it's going to be now? Like, things are just gonna continue changing, like, super, super fast. Yeah. I think it's the way that it's going to be. Yeah. I mean, I said this about the summer of twenty twenty five, where normally, like, in Linear's business, summer slows down because your customers go on vacation. Yeah. They don't buy things. They don't enter into, like, new procurement processes. Right? And and so I was expecting, like, what it was like in 2024 to be like it wasn't 2025. And I was like, this is not Yeah. This is not that. We are we are going full throttle. It used to be that companies, like, wouldn't launch products or, like, have conferences in the summer or, like, do any of these things. And now it's like, no. I'm... We're just gonna get up on, like, a stream and, like, launch something right now with, like, a week's notice.

1:03:00 Yeah. Right? And it used to matter that you, like, shouldn't launch on Fridays and shouldn't launch on Mondays. Now, who cares? You can launch on Saturday. Doesn't really matter. So just like all of those rules, I I would say, like, have gone out the window because there's so much launching and so much happening. And I don't see that changing for a while until there's like a consolidation moment in AI. Yeah. Also, like, everyone always talks about what's your moat? What's your moat like as a business? What would you say maybe the moat of Linear was like when you first started out and maybe like what it is now? Probably great design, great UX. Yeah. I would say now that it actually probably was, like, great team. And now it... I'm like, great team. Yeah. I would say speed maybe, would you say? Yeah. In a way. Just I mean, I think in a in a... It's hard because I think for a... Like, we care so much about quality. Yeah. We are often the company that will, like, delay a launch to get to, like, a certain level of quality. So we are not the flat... Fastest, but it also means we're not, like, the sloppiest Yeah. In a way. So we're hitting that fine line, basically. Right. But, like, compared to, like, legacy companies. Like, yeah, we're fast. Right? But, like, you know, it's all a spectrum. Yeah. Right? So I think in a lot of ways, like, for who we're competing against, you know, there's, like, the right trade off between, like, quality and speed. And for every company, that's different. Right? Yeah. I think we're higher, like, on the quality end, but still try to be fast and, like, cut scope, like, where it makes sense. Yeah. But I think, like, I think a lot of the moats in business, like, have kind of, like, crumbled away. Yeah. And the reality is that you just need to have a team that, like, has a really good sense, a really good pulse of like what's coming, what's changing, and you are investing in your team and your people to be able to figure it out. Yeah. Because, you know, yesterday, this model is the best. Tomorrow, this other model is the best. Like, a company you hadn't heard of, like, two months ago is now raising at $10,000,000,000. Yeah. Right. Like, so everything can change. Yeah.

1:04:30 Which means, like, we should all be very paranoid in a lot of ways because like, you know, the business that you had is not necessarily going to be, you know, the business that you have in the future. But I think what people are investing in is like a team and a way of doing things that is the future no matter what the future holds. Yeah. I I always find that question to startups is like dumb. It's like you're a startup because you're trying to beat incumbents. Like they have maybe a moat, like looking back, but if you like you don't have a moat when you just start a business. Right? It doesn't make any sense. Right. Anyway, earlier you also mentioned that like you guys were kinda like going stepwise where you were, you know, selling the startups and then you were like, oh, we can't just immediately go sell to, like, giant enterprises. We only had, like, one salesperson. Why not then just hire, you know, a 100 salespeople and just go straight for those?

1:06:00 It just... It wouldn't be the Linear philosophy or way of doing things. Yeah. Right? I think we've always operated with the, like, do more with less. Like, we would be a company with, like like, if you look at most companies that are stage and revenue, they have teams that are almost double the size in terms of headcount. And I think we are able to do a lot more with less. That also means that we can be a lot more nimble than other companies because you're not moving this, like, gigantic ship whenever you need to change direction. But I don't think we would have done well with, like, having a sales team that was bigger than, like, the entire company. You know? So, you know, I think at the beginning, I think... And this was true when I was at Stripe too. Like, there was this impression of salespeople that I think for a lot of tech companies can be pretty negative. Right? It's like, oh, like, who are these people? These, like, car salesman Yeah. Coming in to, like, sell our product. I never thought about it that way. We don't think about it that way at Linear, but that was like maybe the impression of salespeople maybe of like, you know, tech in the twenty twelves. You know? I view it very differently because I do believe that like sales has a lot of power to help inflect a business that requires human interaction Yeah. And persuasion. And I I would say that, like, for us, you know, doing it small and steady built the kind of trust that was required in different parts of the organization.

1:07:30 So like engineering really trusts sales. Like when our sales team is like having trouble in a particular segment and, you know, gets on calls with, like, PMs on our team and things like that. Like, there's a lot of trust in that salesperson really understanding the need of the customer, what they're asking for, sometimes even helping solution when necessary. I don't think he would have done that. Like, we would have been able to do that particularly well by hiring a ton of people really quickly. And again, a lot of startups take that approach, but I think they have probably more of like a hire fast, fire fast Yeah. Type of mentality. And I think with hiring, you know, we do work trials. Like, what signal does that send to you? That signal sends to you. Like, we like to, take our time and really understand if someone's a good fit. We want to get them into the, problem scope that Linear operates in and test to see, like, that their great experience somewhere else is going to translate well into our company. You know? So I think it's like a philosophy difference and, you know, every company does things differently. And I would say a lot of the great companies, you know, in the world do things their own way for a reason. Yeah. Do you guys take inspiration from any other companies?

1:09:00 I mean, I I spent seven and a half years at Stripe. And certainly, there are things I take inspiration from. I'll give an example. What... Because we were talking about hiring. You know, at a certain point, we were hiring, like, business people at Stripe faster than we were hiring, like, engineers and product folks and designers. And, you know, the founders were like, this has to come to a stop. Right? And it's like, well, you know, what kind of, you know, ratio would you like? Right? So you then take a step back and you're like, yeah. What what do we want this company to be? If we want this company to be like an engineering and product driven company, probably at least like 40% of the company should be like engineering product design, data, etcetera. And so we basically were like, okay. That's the, like, watermark. And, like, we can't It was just like an arbitrary number. Like It was 40%. 40%. And it was like, we can't go under that number. So if sales wants to hire more people, have sales help us hire engineers so that sales can then hire more people. I see. Right? And I think, like, yes, it's an arbitrary number, but I think it's important for you to understand, like, how do you want your company to be constructed? Right? Like, there are a lot of companies like... And Uber that are, like, heavy on operations, but that's because they're moving like humans and things. Right? We're a very different kind of company. We're like a software business. Right? And for us, we don't necessarily have to have, like, an operations component of the business that is, like, that huge because we're not dealing with those kinds situations. So like understand your business really well, understand what you want to be, and then figure out what model makes sense for you. So like, we don't have like that hard and fast rule at Linear of like 40%, but like I I watch that number. I like created a headcount spreadsheet. Was, like, one of the first things I did. Like, put everyone into their categories of, like, what function they're in, like, calculated the percentage, and, like, you know, I watch it.

1:10:30 And I'm, like, we really need to, like, step up our game on, like, engineering recruiting. It is always going to be harder to hire engineers than it's going to be to hire salespeople. Yeah. And so, like, what are we going to do to like make that easier for us? So a lot of it is just like the philosophy and what you want to be. And knowing that I've been at companies that like, you know, wanna do things the same way, but also, you know, for example, don't wanna outsource support or, you know, wanna treat different aspects of the product in a different way. And I think that's the challenge. There are a lot of things that like I get to bring with me from like my previous experience. And then at the same time, there are a lot of things that I wanna do in a new way that I haven't seen anyone else do. Yeah. I was gonna ask that next. Like, were there like certain things that you specifically did not wanna bring over from like Stripe or Notion? Maybe one example. I think I think Stripe did so well as a company that I think in a lot of ways when, you know, you're a 140, $160,000,000,000 company and you're like on that rise, sometimes you believe you can always hire better than what you have today. So you have a leader in a given function that's doing well. And sometimes your first reaction to that could be like, well, it's because the business is doing well, not because that person necessarily is that great. Yeah.

1:12:00 And it's It's like, oh, I'm at Google. I helped increase revenue by, you know, $20,000,000,000. Exactly. But what did you really do? Right? And and so sometimes it goes really well. Is it, you know, because of that person or is it because the business was going really well? And then if the company is doing so well that you can attract really high quality talent. Right? So someone like two levels above that person, and then a year later, you're able to attract a person who's two levels above that person. And... Right? You're kind of always going to be seeking, like, someone better than who you haven't seen because you can. And I think, like, for a lot of companies, like, being able to say, like like, I've said this to our founders. I'm like, we can get someone better. Like, we're a good company. Company that people want to work for and then are excited about. Like, we don't have to settle. Right? And I think that's, like, great. And then at the same time, sometimes you also have to, like, really recognize, like, the great people that you have. And I think for Stripe, it took a longer time to, like, come around to that. Like, Stripe's been having a lot of, like, boomerangs. Like, you know, people left the company because maybe they, you know, weren't on the rise, you know, in the way that they wanted to be. And then, you know, came back and are doing like amazingly well. And I think sometimes I would like to look back on my time at Linear and say like the right people were, like, promoted and excelled. And we didn't hire above them unless the company needed to. Right? Unless we needed to get to that a different stage. We needed something that that person didn't have. And not just because, like, we weren't willing to let them try to, like, be better than they are, to, like, scale at that next stage. Because, you know, in running startups, this is true of founders. Like, you don't... Like, almost no founder who has a lot of success has, like, done it exactly before. Right? And that's probably going to be true of a lot of the early team. Like, they're leaders at the company, but they've never scaled a support team to like 200 people or 500 people or whatever. That doesn't mean that they can't. Right? Just like it doesn't mean that that founder can't be a great founder at a thousand people and also a great founder at like 50 people. Mhmm. And so, like, I just fundamentally believe that like people can grow and scale, and that you should like reward that over time.

1:13:30 And, you know, I have some time... Like different parts of of the company, like, I'm like, I don't know if they always believe that. I I think... And I think a lot has changed since then, for what it's worth. But maybe that's one thing. On support, that would be the other thing. I think it's incredibly difficult to scale support to that degree. And I think that we emphasize a higher level of quality than I've seen in vast majority of support organizations I've operated in. And so it's something that we care about. We're willing to pay more for it. And we believe it's like the right thing to do by our customers. And I love that I've literally never in three and a half years gotten an escalation because someone had a poor experience with our support team. So that's like a company that like I see and I love to be part of. Yeah. Know, and that's not true for every other company I've worked for.

1:15:00 So, okay, you were at Stripe, then you went to Notion for a little bit, and then you became an investor. Yes. Why did you make that transition to becoming an investor? Yeah. When I was at Notion, I enjoyed my job, but the parts that I enjoyed were almost the parts that I wasn't really hired to do. So I I joined around maybe 40 people or so, and we were, you know, we were scaling. We didn't have like a single recruiter. We didn't have a head of people. We didn't have anyone working on growth. So, you know, what did I do? I, like, raised my hand and was like, I'll help hire our head of people. Like, I'll help hire our first recruiter. I'll find our first product manager and, like, hire them. And I did all of those things, and then I kind of, like, hired my way out of, like, jobs that I had. Right? And then got to a point where I was like, wait. I'm, like, back at the job. I was, like, actually hired to do. Yeah. Like, I don't really Which was what? Like, head of platform and partnerships. Okay. And I was like, I'm not really excited about this job anymore. Like, I was having more fun doing all that other stuff Yeah. That I wasn't really hired to do. But it's just like, it's company building. Mhmm. Right?

1:16:30 And at the time, I was just like, I I I think I need a new role at like a different company. And I don't know what that role exactly looks like. Right? And so I thought that venture might be a great way to kind of get the breadth that I was looking for, really, by spending time with, like, a bunch of different kinds of companies in different spaces. And, you know, I think for me, it's it's it's very different being an investor than, like, coming into a company and actually doing the work. Mhmm. It's really, like, different to, like, advise a company like, oh, you should go spend more time with your customers. And you, you know, should think about this business model or, you know And you were doing early stage? Or Early stage. Yeah. And a lot of the early stage stuff is like you're investing like pre product market fit. And like, I don't know anything about your market. Like, you sell to like, I don't know, procurement leaders or like construction workers or like like, you know, you have to be in that to really understand. And I actually felt like I was more helpful when companies had that product market fit. If I think about every single company I've ever joined, it like just was finding like product market fit, and then I joined. And then I can be a lot more helpful and like build out the business. But, you know, I think for pre product market fit, a lot of it's just like investing in the right people and like getting out of the way. Yeah. And being supportive and helpful with intros and things like that. But what I... Like, I actually really love execution. Yeah. Being inside a company and, like, helping get stuff done. And I think I'm kind of known as a person who will, like, run through walls to get things done even, you know, if that might rub people the wrong way in certain larger organizations. But, you know, for a startup, it works really well. Yeah. And so that's Are worked for

1:18:00 there certain things that you noticed, like being an operator made you a better investor at? And then also vice versa, like what did you learn from being an investor that made you better at, you know, your current role at Yeah. At Linear? I think I was speaking from, like, a place of, like, knowledge and truth. And I think a lot of investors have, like, never worked at a startup before. And there's nothing wrong with that. You can be an amazing... They're amazing investors who've never worked at a startup before, and it doesn't matter. Like, you invest in the right people. And, again, let them do their thing. And, you know, as long as you invest in the right people, that strategy works. Right? But, you know, I think also doing VC is sales. Like, you are selling money. And every other investor, like, has money to sell too. Right? So you're kind of selling the same product in some ways, but you are trying to sell yourself. Right? And, like, you are trying to differentiate yourself as a product beyond the money to that founder. And I found it much easier as someone who had, like, been operating at some great companies to be able to go to a founder and say, like, I can credibly help your business. Yeah. What would maybe other investors could.

1:19:30 What would be, like, the the pitch for an investor who's never worked at a company? It'd be, like, oh, I have a lot of intros. I've already invested in a lot of like really cool companies. Is that like kinda their selling point? I think a lot of it is like sometimes like pattern matching. Right? Like I've been on the boards of these great companies and I've seen success from zero to, you know, a 100 or whatever. It may have been several times over. And, you know, maybe I can tell you when it's time to do x or when it's time to do y because I've pattern matched my way here. I, you know, in a lot of cases, you work with certain investors and they have, like, a very large Rolodex. They know lots of great people at great companies and Yeah. You know, can introduce you to people who are more knowledgeable than they are in certain areas. So, you know, often investors will come to me and be like, can you help this founder who's team up building a sales team Yeah. You know, from zero? And, well, I can tell you about building it from one. You know? And, you know, because they know me, you know, that's like an access point that helps the founder. Right? So I think for every investor, it's like it's like something different. But, you know, what I take back now as, like, an investor, you know, going back into working at a company is, like, just having more of that understanding when I'm, like, in a board meeting, you know, of, like, what are the investors thinking? Like, oh, right. I I was an investor. Like, I I have a sense of, like, what they're thinking and what data they wanna see and what are the metrics that they care about. And if we're thinking about raising, like, a new round, like, what are my expectations for their help? If we need more customers, what are my expectations for, like, their introductions? And I have a better sense of, like, what I should be getting out of that person as an investor or board member or something like that. And I think that's, yeah, again, like helpful to the company in a lot of ways.

1:21:00 Yeah. I guess you're COO, so you have to, like, interface with investors a lot. Yeah. Yeah. Yeah. And, you know, we we work with some great investors and, you know, are very helpful and have referred people. But, know, in a lot of situations, like, closed mouths don't get fed. So if you don't ask for things, they're not gonna give them to you. Yeah. So... So Linear doesn't have any other c suite other than the founders in you? Yes. Why is that? It's a good question. I mean, I think, again, we we operated this way at Stripe for a very long time. So again, I take a bias towards it. But I think it's been true actually, for a lot of companies. Like, you might have, like, one executive who's, like, hired in on the business side who who has this title or something similar. And I would say at the beginning, a a lot of it is just, you know, my role is kind of a catchall for like a really small company for like lots of different functions and things over time. But I expect that to change. I don't think that's going to be like the way it is forever. You know, if we build out like the right team, you know, the right leadership in the right places, like people will earn that level of title. And I think for us right now, because we still feel so small, like we're about a 170 people, in a lot of ways, wanna remain pretty flat rather than, like, adding a lot of layers when we are still pretty small.

1:22:30 Yeah. And, I think that's been helpful for us so far. But that doesn't mean that we haven't, like, promoted people and given people more responsibility, more ownership, more scope. But we tend to focus on things like, you know, head of titles for, like, wide areas of ownership. Yeah. Yeah. I mean, that's all I had. Is there, like, any... Anything else that, you know, you wanted to talk about? No. No. This was a great conversation. I feel like we went into a lot of different different areas Cool. Of of of a business. So thanks. You had great questions. Yeah. Thank you.

Thanks for reading

Source: Latent Space · latent.space