Linear の GTM を ARR 1億ドル規模へ — COO Cristina Cordova が語る営業・価格・組織づくり
Scaling Linear’s GTM to $100M ARR — Cristina Cordova, COO
Linear の GTM を ARR 1億ドル規模へ — COO Cristina Cordova が語る営業・価格・組織づくり
Latent Space: The AI Engineer Podcast
要約
Linear の COO Cristina Cordova が、入社からの約3年半で進めた Go-to-Market の拡大を振り返った回。トライアル雇用、SDR を置かない営業組織、段階的なエンタープライズ進出、CEO のブログ「Issue tracking is dead」とエージェント戦略への転換、使用量課金の考え方まで幅広く語っている。Stripe や Notion、VC での経験が今の運営にどう生きているかも述べている。
この回のポイント
- ●Cordova は、入社時に Linear の営業担当が1人しかいなかったため、社内目標の「エンタープライズ進出」を一旦消し、まず成長期企業の獲得に絞ったと述べている。エンタープライズ向けの組織を作ったのは2025年。
- ●Linear 上で作成される issue の50%超がエージェント経由になったという。MCP サーバーの利用とアプリ利用がともに伸びていることを、人にもエージェントにも使いやすい証拠だと位置づけている。
- ●「Issue tracking is dead」は、手作業でのトラッキングが終わるという意味で、顧客も概ね賛同したという。Linear は自らを製品開発システムと再定義し、エージェントオーケストレーションなどの新カテゴリへ資源を集中している。
- ●SDR を置かず、AE が自らアウトバウンドを行う方針。サポートも外注せず、AI は返信の下書きに使い、品質確認は人が行う。人員は事業の成長に比例して増やさずに済むよう工夫している。
- ●課金は座席課金が基本で、新機能はベータ期間中は無料にし、コスト実態を見てから課金する。コーディングセッションは API 実費に少し上乗せし、Loops などには AI クレジット制を使う。
- ●6か月を超えるロードマップは持たず、速さと品質のバランスを取りながら、チームそのものが競争優位になると語っている。
章立て
導入と COO 採用の背景
Linear に COO が入った経緯や、創業者が営業の良し悪しを判断しきれなかったことを説明。入社時は中堅企業止まりで、PLG が中心だった。
トライアル雇用と初期の GTM
入社前の実務トライアルで GTM 計画を作成した。ブランドやマーケティングの強化、営業組織とサポート方針を整理した。
段階的なアップマーケット戦略
1人しか営業がいない状態でエンタープライズを目標にせず、成長期企業に絞った。切り替え型の販売は時間がかかるという Stripe での経験も共有。
エージェント時代の売り方
UX 重視の初期から、エージェント中心のワークフローへ。MCP 経由の issue が50%超となり、「Issue tracking is dead」の狙いも説明。
機能の学習・営業・SDR 不在の組織
顧客の画面共有から学ぶ姿勢、Triage Intelligence、営業認定、SDR を置かない理由、CX での AI 活用方針などを述べる。
商談の長さと使用量課金
導入決定の速さは企業ごとに異なり、AI 予算が意思決定を後押ししている。使用量課金とベータ無料の運用方針を説明。
2025年の計画変更と moat
計画外のエージェント基盤構築を優先し、速度の時代に moat をどう考えるかを語る。
採用哲学と Stripe・VC の経験
少人数で段階的に拡大する哲学、Stripe から学んだ職種比率、Notion と VC を経た経験、C-suite が少ない理由を話す。
解説記事
Latent Space のこの回では、プロジェクト管理ツール Linear の COO、Cristina Cordova が登場した。Stripe と Notion を経て Linear に入社して約3年半。従業員40人の頃に営業・マーケティング・運用の拡大を担った彼女が、GTM の進め方、CEO の「Issue tracking is dead」というブログの真意、価格設計や組織づくりを語っている。
小さく始めたアップマーケット
Cordova によると、入社当時の Linear はスタートアップ向けの良い製品として知られ、顧客は Ramp など自社で導入して成長した企業が中心だった。500席を超える顧客はほぼなく、営業担当は1人だった。入社直後の全社合宿で、社内目標にあった「エンタープライズ進出」を線で消し、成長期企業の獲得に切り替えたという。リソースも実績もないまま大きな目標を掲げるべきではない、という考えだ。参照顧客が増えれば次の顧客を獲得しやすくなる。実際にエンタープライズ営業を本格始動したのは2025年である。
なお、入社前には実際の仕事と同じ内容のトライアルとして GTM 計画を作成した。これが入社後の設計図になったと述べている。
「Issue tracking is dead」の意味
初期の Linear は UX とデザインの良さで選ばれ、無料で試せる点が普及を助けた。現在は、バグ報告から担当割り当て、ステータス更新、顧客通知までを手作業で行う流れはもう成り立たないと顧客に説明しているという。Linear で作られる issue の50%超がエージェント経由で、MCP サーバーの利用とアプリ利用がともに伸びていると語る。チャットだけでは可視化や共同作業に向かないため、人向けの UI とエージェント向けの機能を両立させることが目標だという。
Cordova は、データベースと MCP サーバーだけを提供して外部エージェントに任せる戦略は長期的なビジネスモデルにならないという見方を示した。ブログについては、手作業での追跡が終わるという意味であり、顧客の多くは賛同したと述べている。Google の検索の例を挙げ、Linear は事業が大きすぎないので自己変革しやすいとも話した。また、2025年は計画外にエージェント基盤や Codex・Cursor・GitHub Copilot との連携に注力し、予定していたエンタープライズ機能の一部は未達になったが、結果的に新たな大企業の候補入りにつながったという。
営業・サポート・AI の使い方
Linear は SDR を置かず、AE が自らアウトバウンドを行う。理由は、初回の資格確認の電話が顧客にとって有益でないためだという。フォワードデプロイドエンジニアではなくソリューションエンジニアを置き、移行や API 連携の質問に答えたり、一晩でデモ用の連携を作ったりする。
サポートは外注せず、AI は返信の下書きに使うだけで、確認は人が行う。AI だけで回答する運用はブランドを損なうという考えだ。採用はこれまでより遅くなったが、事業の成長に比例して増やさずに済むようにしているとも述べた。インタビュー録音の整理には AI を使うが、記事は人が書く。こうして使いどころを選ぶ姿勢が語られた。
価格設計と商談サイクル
導入決定の速さは企業次第で、CEO のトップダウンで1か月で決まる例もあれば、2年以上かかった例もある。最近は AI 予算に収まる場合に意思決定が速くなっているという。Linear は長らく座席課金だったが、現在は一部機能が使用量課金になっている。座席課金は残し、新機能はベータ期間中は無料で試してもらい、コストの実態を見てから課金を決める。Linear エージェントのチャットは無料で、コーディングセッションは API 実費に少し上乗せし、Loops には AI クレジット制を使う。最初は高めに設定して後から下げる方針だとも話した。
採用哲学と過去の経験から
Linear は少人数で段階的に営業組織を拡大する方針で、大量採用は合わないと説明する。Stripe では、エンジニア・プロダクト・デザイン・データが全体の40%を下回らないという目安があったと紹介し、同様の人員構成の比率を自分も見ていると語った。また、Stripe では外部の優秀な人材を求めすぎ、社内の人材の成長を信じ切れなかったという反省も述べている。
VC 経験については、投資家の見方を理解でき、取締役会や資金調達で役立つと語った。ただし自分は実行が好きで、事業を作る仕事のほうが向いているという。ロードマップは最長6か月で、速さと品質のバランスを取り、チームを競争優位と捉えている。
まとめ
日本の読者にとって注目点は三つある。第一に、プロダクト主導の成長から営業主導へ移る際に、最初から大きな市場を狙わず、実績が作れる範囲に絞った点。第二に、既存製品のカテゴリを自ら再定義し、AI エージェント時代に合わせて資源を集中させた点。第三に、AI を導入しながらも、顧客体験の重要な部分は人が担うという線引きである。いずれも、SaaS の営業組織や価格設計を考える際の具体的な参考になる。
文字起こし(英語・自動生成)
Kari 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? It's probably really hard if you're Google to like kill the search business, right? And put an AI, you know, box at the top of every search result and maybe no one's going to 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. 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. Christina Cordova, you're the CEO of Linear. Could you introduce yourself? Yeah, yeah. So I'm Christina. 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-server 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. So why did Linear hire a COO at like 40 employees? Is that like odd or is that pretty normal? I mean, I generally don't believe every company needs a COO, 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 or 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, 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, hmm, 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. Yeah, so, like, what did the business look like at that point? Like, can you talk about, like, what revenue they were at? Yeah, we were probably, I want to say, you know, we had some large customers but no, like, public company customers. probably no customer above, I want to 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 at that time. You know, and I think at that point in time, we were doing well with like a product-led growth model where most people were using our product because they signed up self-serve.
And then grew with us over time. So companies like Rusell 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 like time to start selling to, you know, the company that is not even going to put like a lick of data into your service without, you know, signing a contract 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 10x, I think, since I joined. And you joined like four years ago? Almost three and a half years ago. Oh, okay. So I think the Linear founders have talked about this. I think you have as well, that before you joined Linear, you always do a trial period?
Yes. So did you also have to do a trial period? I did. Okay. So yeah, 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 12 months or something like that. Right. And I think the good thing about that is that, you know, that is the job. 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, 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. 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 want to, 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 to prioritize 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 had this little blueprint for, you know, what my job should be and what I should accomplish. Can you talk about like, well, isn't that plan? I 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 want to 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 that.
Yeah. 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 like had a change log of something new that we released. And it turns out that like less than 10 percent of users like subscribed to emails. So most people didn't necessarily know even just like the new features we were shipping, which was interesting. And then we would like send a tweet. OK. Like from the founders account? Like from the company account. 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, OK, like how are we telling a more holistic story in a better way? And then how are we actually reaching the people that we want to be reaching? It turns out that like actually a lot of our users are like in the app, you know, day to day. 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? 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 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, 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 like one person on sales.
Right. So it was just like, you know, there's there's only so much you could do with like one person. And were they like an experienced salesperson? Yeah. Yeah. Yeah. Yeah, he's actually our sales leader today. So he 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 want to grow this team, right? You can grow a sales team in lots of ways. You can have, like, lots of SDRs. 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 think is distinct and somewhat different. But we added those later. And that's part of the sales work? Yeah. Cool. We really optimized our team at the beginning for hiring AEs who had experience selling technical products. Because we knew 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 very discerning, doesn't want to see your fancy slides, just wants to get into a demo, 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 want to 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 want to outsource support. And I've never worked at a company that didn't outsource support. So that was, like, okay. Wait, I thought Spike does it internally, right? No, they outsource. Oh, okay. 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 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 want to talk to a human being, was going to be support. So the support better be good. Yeah. great. 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, you know, never say never on any of these things. But, you know, there are certain ways that we want to do things and we probably want to do them for like as long as possible, as long as it's like feasible for the business and make sense. 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 kind of 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 offsite 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 going to go after enterprises out. Because I was like, we have one person, literally one person on sales. Like, you know, you're not going up market to enterprise with one person. 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 get there? And then you actually have the resources to, like, accomplish that goal, right? And, you know, I don't think we had any of those things at that period of time, 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 going to go after, like, companies in the growth segment, and that's going to 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 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 going to be able to go after enterprises. But, like, I don't have confidence in that now, so why would I set that as a goal for me? 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 like, 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 works very similarly when I was at Stripe. We did not win a lot of net new companies that were switching over from a competitor for a long time. We did a great job winning every net new business that was created, so a startup 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 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 nice and shiny and new on top of an existing set of systems. So knowing that I was in a very similar position in this role, it was important that I just oriented the team around what I felt was a solvable problem. and then only in 2025, 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 companies have an issue tracker, right? Yeah, or some kind of tool. And so you have to try to, like, let them away from them. So, yeah, like how do you convince them to say, oh, yeah, we're using XYZ product. It works for us. But, yeah, like, you know, pitch me, basically. Yeah. In the early days, it was about being like significantly better than what the alternative solutions were. Right. I don't think you can be like 20 percent better, 30 percent 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 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. Right. When they were working at like Coinbase and Airbnb and Uber. And so they knew like no one liked these tools. And when they were getting rolled out, like at their companies, they were like, 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 helps 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. Versus like seeing a couple of slides in a sales deck and being like, OK, 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 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 your entire product development process has been upended.
The way that you build products has completely changed. 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 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 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 It's 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, 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. Yeah, that's really interesting because it seems like the pitch early on was the user experience, right? Now it seems like the humans are not going to be interacting with the UI. I actually think that a lot of companies right now are feeling like it's going to be okay to just be like a database and, you know, have an MCP server and, you know, give all of their data away to agents and have the agents like interoperate with them and think that like that's going to be a great business model. And I don't think that's going to be a great business model, ultimately. 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 no reason for people to go into your tool Right And so for us you know the metric that we typically looking at and we 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. Half 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. Right. So sometimes people believe that like, oh, I'm just I'm just using the MTC 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. 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 and to the right together, It proves that 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. And app usage is measured by just like number of people using it. Because like I'm assuming also like your customer base is just growing, right? So how do you work created the application? So, you know, our like unit of work, like the smallest unit of work issue. Right. So if you just look at like we're created, like that's like a human going into the app, like our mobile app or 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 when a site 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 example. So in a lot of cases, it's like an agent is doing the work, but it's a linear agent. Right. Which we also want to 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 Kari writing this blog post like issue tracking is dead. So I'm assuming you were in the middle of like selling some contracts when he wrote that. 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?
Yeah. Yeah. Like, how do you explain that to them? And, like, how did that transition happen? Yeah. Well, I think, like, the great thing about our business is that we're not, like, so big to, like, kill ourselves. Right? Yeah. 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 going to 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 innovators 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. And so for us, like the great thing is that it's like, OK, 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 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, it's 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 unit of the issue still exists, but we probably shouldn't have a world where people are, like, manually tracking work. 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? 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 going to 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, I guess that blog post, were you blindsided by that? Like Kari writing that? No, no, we were all We were all on the same page. So 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 this. 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 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 going to 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 and decided that they were going to invest their own internal teams to build like internal agents to do work with them. Right. And so we were like, hey, we actually need an API that enables you to create agents within linear. 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 want to own the proprietary data that's associated with that, we want to 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. Um, but I can tell you that now a lot of them are very happy that we have a lot of these features. Um, because not every company is on like the bleeding edge of the way that product development is changing. I guess that's what I was trying to get at. I was like, would you, I'm assuming because you were trying to go more like enterprise, a lot of them were those like legacy type companies, right? Yes. Yes. And, and not the kinds of companies that are, um, really pushing us 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.
And if you feel like your underlying tool set hasn't really changed, hasn't really evolved in this new world, then you should probably think about changing your tool set. Yeah. So 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 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 how you're going to learn from them versus purely just how you're going to teach them, right?
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, you know, nobody wants to like groom their backlog, right? Like, what a task that feels so outdated, right? And so, you know, we built a feature called triage intelligence, which effectively enables anything that comes into your triage workflow, bug reports, feature requests, et cetera, 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, 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. 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, ooh, like as like as, you know, someone who's not an engineer, like, ooh, I'm going to 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. Right. And so now increasingly we're getting rolled out across like 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 roadmap or like be an input into what's on the product roadmap 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 as like a system or a tool and our salespeople, you know, have learned that just in being at the company, we do a lot, as you can imagine, in linear. So you need to know how to use it just to be at the company generally. And then again, 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 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 up GitHub and have like a demo GitHub workspace and a demo linear workspace and make sure that they all work together. That can be a little bit more complex. 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 want to 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 are, like, now accessible to everyone. And an engineer on our team just has to, like, review that change and, 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. Yeah, yeah. Like, with anything. So are you, 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. Yeah. And maybe like are you seeing like customer team compositions are changing because of maybe like how they're using linear or just like agentic development like in general? Yeah. I mean, I think one of the things that people are talking about a lot today is effectively how teams are changing in that they're remaining smaller, flatter, et cetera. 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. 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 comes from a belief that, like, a salesperson should be able to, like, write an outbound email. Like, I don't see why. 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 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, like, you know, the rep is just being like, how big are you? And, like, how much money do you think you 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. Yeah. Right? Like, why am I wasting 30 minutes of my time on this call just to get to a person who can give you 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 other companies. 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 that write into us? Do you not see that, like, having LLMs write stuff to customers, like, produce swap? Yes. Like, AI swap? Definitely. How do you fix that? Yeah. I mean, the CX team, like, our humans are the quality check on that, right? So we do not have AI send math, like, a lot of companies, and other companies can do this, and that's totally fine, right? No shame to other people. But a lot of other companies will say, hey, like 100 percent of questions that come into our support team are going to be like answered by an LLM first.
Yeah. And only if that customer writes back angrily. Right. Will a human come in and be like, oh, sorry about that. Like, let me give you a real answer. Right. We just don't believe in that model. Right. So I would much rather have AI, like, draft an answer to this 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, like, three sentences. And instead I have, like, three paragraphs of, you know, a reply that ultimately is, like, 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. And we just, you know, our team's really fast. 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. That's kind of 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 writing in for the first time. And it gets them really, you know, feeling confident 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, 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. Yeah. So you, did you mention like downsizing the customer experience team? So. Not downsizing, but I don't think we've ramped it. As much as we would have. As we would have without it. Right. So I think some of these tools are very helpful for enabling us to, like, not always have to grow teams linearly with, like, how fast the business is growing. Yeah. Right? And, you know, I think on, like, other parts of the business, like, marketing 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. So, you know, we've been like we'll 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. Yeah. At least until they get better. I was pretty good at writing, I've noticed. Yeah. Anyway. How does like how do sales engineers fit into your team? Yeah. Yeah. Yeah. So we have what we call solutions engineers, effectively 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 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, right? Or how would I perform a migration of 30,000 people from like a legacy tool to Lydia, 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 they 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 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. And 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? Yeah. So sometimes 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. 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 a 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, like, a champion in a company and they're saying like linear is amazing but I can't convince like this other
person can you help me right um you know the IT person or the procurement person or you know someone else who's often not in the tool day-to-day 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 I 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 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, like, I don't know, someone who has decision-making authority? Yeah. Like the champions. 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 they're like, we're moving the 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 assuming? I mean, we had that happen at a 1,000-person company. 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 a 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, for your business. But, you know, then we'll see, like, companies. We had one company that probably took two years, two and a half years or something.
Like, and it wasn't that they were in the sales pipeline the whole time. 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. Somebody else gets using the company. Yeah. And then a different person comes in, like, nine months later, and is like, I think we can convince the CTO now. Right. And it just takes a really long time to finally get them to approve and make the decision. Sometimes it's budget. It's like, oh, we've already set the budget for this year. And if this is going to require more spend, well, that's going to be a 2028 decision. Some companies operate like that. Are you saying that they're now operating a lot faster because of the way things are changing so fast now or not really still? Maybe these more legacy companies. Yeah, I don't think they operate any faster, honestly, at least with decisions like this. I would say for a lot of these companies, 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, 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. It's starting to change for companies. But in a lot of ways, if you 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 magically found budget that didn't previously exist before. Yeah. Okay, so you think, like, a lot of this, like, AI companies are, you know, getting to $100 million of revenue within, like, three months. That's because of this, basically. It's, like, a lot of companies that previously didn't have budget for, like, experimenting with new tools are just kind of like, oh, my God, are companies going to 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 going to stop.
Like they're experimenting right now and then, you know, they're going to figure out what actually works, what doesn't. 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 going to 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? um 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 in that three-year period of time unless you have like step-ups built in 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 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 very concentrated in the customers.
Okay. 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 100 million overnight. Right. And then, you know, you see companies where you sell to like the defense industry or you sell to like gigantic law firms or, you know, something like that. And, you know, you sign a few deals that are like 30 to 40 million dollars in AR. And then, OK, great. We got to 100 million in AR. 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 would say like a lot of companies that are in the fast world 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, which was like, oh, if AI responds to your support ticket, like, you know, that costs a dollar. And you're like, is every support ticket that gets replied to like worth a dollar? Like, OK, great. Like, right. So you're pricing on like the outcome that you drive. Right. I think a lot harder for other types of businesses to be like, OK, so what is automatically triaging this bug to the right team worth? Yeah. Right. Maybe to every company, that's a little different. Maybe you believe, oh, that's the PM's job. Like they should be like, you know, triaging bugs to the 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 group app 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 so I would love for there to be a world where like there's some kind of like outcome based model that stands 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. And in some cases, those costs can be 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? Right now we're using Frontier. Okay. Even for the chat? Even for the chat. Okay, okay. Yeah, yeah, yeah. And, you know, TBD with a few holes there. And then beyond that, when you have a coding session in linear, you can choose between, like, right now, OpenAI or Anthropics 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 publish rate. And we charge, like, a little bit on top of that. And that's it. So making it very clear and transparent for most users. And then for products like Loops, we have an AI credits model as well for that feature. So 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. How do you go about going to your customer and saying, hey, previously you guys were doing seat-based pricing and now we're going to do this?
Yeah. I mean, I think it helps that the seat-based pricing isn't going away. So you're still paying for the core service, and we are not charging for things that were previously otherwise free. So it's very different, I think, when you go to a customer and you're like, yeah, so what was free is now paid and usage-based. So these are 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 can run a very inexpensive one, right? So charging based purely off of, like, you know, $1 per query, like, wouldn't make sense 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 and what the best pricing model is. So typically what we'll do is we'll have, like, 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. Like, feel free to use it. See if you get value out of it. Give us feedback. And then 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. and now I'm going to 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, like, 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 an expensive product to serve to you. But we are going to try and, like, 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, 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. Yeah. So you mentioned earlier that like when you came in, you had this like six, 12 month, like go to market plan. Did you basically follow that go to market plan like to a T 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 agent speakers? Yeah. I think I probably did. I mean, I haven't looked at it in a while, 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 12 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 market products over time. So we think a lot of those things we've like adopted into like new motions and ways of doing things for the team. And, you know, we certainly went from like no sales team almost to it being a very large percentage of the company now. So, you know, I think a lot of those things have like ultimately, you know, shipped 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 2020, 2025? Yeah. Like the agent speakers came out. 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 roadmap. 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 upmarket. And that was also 2025 was the year where we said we were going after enterprise, right? And then we saw everything that was happening in the space and we're like, ooh, we've got to build an MTP server.
Oh, we've got to build an agent's platform with a whole new set of APIs so anyone can build an agent into linear. Ooh, we've got to 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. Meaning, like, there were, like, certain customers you were trying to go after? 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 want to be like behind all of this new stuff or do we want to be like really racing ahead of where we think we should be? And I think we chose to say like, no, we're going to 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.
Right. It wasn't going to 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 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 fine. Like, that'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. I guess like JVT 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. And so in that world, 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. 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.
And then I think similarly with like all of the agentic development and the way that things have changed, like 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 want to see 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. Yeah. Who knows how things are going to change. Right. And I think that really helps to say, okay, we're going to create a story for like how the world is right now. And we can expect that that story is going to 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 got to just like move and change. And, you know, it's all going to be OK. 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 going to 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 2025 where normally like in linear business summer slows down because your customers go on vacation and they don buy things They don enter into like new procurement processes Right And and so I was expecting like what it was like in 2024 to be like it was in 2025 And I was like, this is not this is not that 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, we're just going to get up on, like, a stream and, like, launch something right now with, like, a week's notice, 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. It doesn't really matter. So just, like, all of those rules, 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 I'm like great team. I would say speed, maybe, would you say? In a way. I mean, I think it's hard because I think we care so much about quality.
We are often the company that will delay a launch to get to a certain level of quality. So we are not the fastest, but it also means we're not the sloppiest in a way. So we're in a fine line, basically. Right. But compared to legacy companies, yeah, we're fast. 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 racing at $10 billion. Yeah. Right. Like, so everything can change. Yeah. 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 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? Like it doesn't make any sense. Right. Anyway, earlier you also mentioned that like you guys were kind of 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, 100 salespeople and just go straight for those? It just wouldn't be the linear philosophy or way of doing things, 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. So, you know, I think at the beginning, I think, and this was true when I was a 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, who are these people, these car salesmen coming in to sell our product? I never thought about it that way. We don't think about it that way. Linear, but that was maybe the impression of salespeople, maybe of tech in the 2012s. And I view it very differently because I do believe that sales has a lot of power to help inflect a business that requires human interaction and persuasion. And 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. 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 we 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 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 like 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? I mean, I spent seven and a half years at Stripe.
And certainly there are things I take inspiration from. I'll give an example 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, 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 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, et cetera. And so we basically were like, okay, that's the watermark. It was just like an arbitrary number? It was 40%. Let's go 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, right? And I think, like, yes, it's an arbitrary number, but I think it's important for you to understand, like, how you want your company to be constructed, right?
Like, there are a lot of companies, like, in Uber that are, like, heavy on operations 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 of 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 watch that number. I, like, created a headcount spreadsheet. It 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, 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. 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, want to do things the same way, but also, you know, for example, don't want to answer support or, you know, want to 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 want to do in a new way that I haven't seen anyone else do. Yeah, I was going to ask that next. Like, were there like certain things that you specifically did not want to bring over from like Stripe Renation? 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 140, $160 billion 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. And it's like, oh, I'm at Google. I helped increase revenue by, you know, $20 billion. Exactly. What do you really do? Right. 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 a year later, you're able to track 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 that 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.
Stripe's been having a lot of boomerangs. People left the company because maybe they weren't on the rise in the way that they wanted to be and then came back and are doing amazingly well. And I think sometimes I would like to look back on my time at Lanier and say, like, the right people were, like, promoted and excelled. And we didn't hire about them unless the company needed to, right? Unless we needed to get to 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 teams. 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 1,000 people and also a great founder at, like, 50 people. And so I just fundamentally believe that people can grow and scale and that you should reward that over time. And different parts of the company, I'm like, I don't know if they always believe that. 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 like 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. You know, and that's not true for every other company. So, OK, you were a 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 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 like, I don't really like, uh, I had a platform and partnership. Um, and I was like, I'm not really excited about this job anymore. Like I was having more fun doing all that other stuff that I wasn't really hired to do, but it's just like, it's company building. Right. Um, and at the time I was just like, 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 and different spaces. And, you know, I think for me, it's very different being an investor than, like, coming into a company and actually doing the work. 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? 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, 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 um but you know for a startup it works really well yeah and so that worked for me are 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 to, 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 be the other investors could? What would be like 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 kind of 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, 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, 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 thinking about building a sales team, you know, from zero? And
Well, I can tell you about building it from one, you know, and, you know, because they know me, like, 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 was an investor. Like, I have a sense of, like, what they're thinking and what data they want to 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, again, like helpful to the company in a lot of ways.
Yeah, I guess you're COO, so you have to like interface with investors a lot. Yeah, yeah, yeah. And, you know, we work with some great investors and, you know, are very helpful and have referred people. But, you know, in a lot of situations, like closed mouths don't get fed. So if you don't ask for things, they're not going to give them to you. 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 operated this way as 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 has this title or something similar. and I would say at the beginning a lot of it is just you know my role is kind of a catch-all 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 170 people. In a lot of ways, we want to remain pretty flat rather than like adding a lot of layers when we are still pretty small. 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 wanted to talk about? No, no, this was a great conversation. I feel like we went into a lot of different areas of a business. So thanks. You had great questions. Yeah, thank you.
番組の概要欄(原文)
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." ( https://linear.app/next ) In this episode, we chat with Cristina Cordova ( htt...
出典・この記事について
- 番組
- Latent Space: The AI Engineer Podcast(Latent.Space)
- 元の回
- Scaling Linear’s GTM to $100M ARR — Cristina Cordova, COO
- 配信日
- 要約作成日
- 公式サイト
- www.latent.space/podcast
この要約・解説記事は、元の音声を文字起こしした内容をもとに AI(Claude)が日本語で作成したものです。 固有名詞や数値に誤りを含む場合があるため、正確な内容は元の音声でご確認ください。制作方法について
関連エピソード

エージェンティック・ステート:AIエージェントで政府を作り変える
ChinaTalk

AIエージェント2万体を計画していますか?Capital Oneからの警告|Abhijit Bose
Eye On A.I.

OpenAIの新モデルAstraは評判が散々、でもGemini 4 Neonは意外と良い?
AI For Humans: Weekly AI News, Tools & Trends

SPS 26:部品を超えて――AIと電気トポロジー設計(Murrelektronik)
Industrial AI Podcast

AI史上最も重要な10日間
The AI Daily Brief: Artificial Intelligence News and Analysis

ソフトウェアファクトリーの台頭:個人の生産性をどう組織の成果に変えるか
Software Engineering Daily