Jun 5, 2025 · 1h 33m · in-depth
Inside Linear: Why craft and focus still win in product building | Karri Saarinen (Co-founder & CEO)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this in-depth interview, Linear co-founder and CEO Karri Saarinen shares how his journey through early design, Y Combinator, Coinbase, and Airbnb shaped Linear's contrarian philosophy on software craftsmanship, speed, and disciplined company building.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Brett holds 14.9% of the talking time here. How this is scored →
Brett as informed peer 4.4 Guest teaching 4.7 Guest disagreement 1.1 Brett pushing back 1.4
speaking balance: gold is Brett, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 21:49 Debunking the headcount-to-success correlation
Saarinen directly rejects the Silicon Valley hypergrowth orthodoxy, asserting that massive hiring is an outcome of immense business growth rather than its underlying cause.
Hardest push from Brett ▶ 1:03:45 Salesforce customizability vs product elegance challengeBrett directly challenges Saarinen's philosophy by citing massive enterprise platforms like Salesforce, asking whether extreme craft inevitably caps overall market size.
Biggest teaching moment ▶ 29:10 Why enterprise software fails individual contributorsSaarinen educates Brett on the systemic failure of enterprise tools, explaining how optimizing for procurement buyers rather than end-user ICs destroys product utility and data fidelity.
Brett holds their own ▶ 11:51 The Texas vs Massachusetts oil-drilling analogyBrett demonstrates strong venture expertise by articulating a nuanced theory on repeat founder success, contrasting individual skill with market randomness.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Brett as informed peer | Guest teaching | Guest disagreement | Brett pushing back | Why |
|---|---|---|---|---|---|---|
| Early Beginnings: Gaming, Coding, and Discovering Design | 3 | 2 | 0 | 0 | Brett opens with straightforward biographical prompts about Saarinen's childhood and early exposure to computing and aesthetics. Saarinen recounts learning commands visually on a Commodore 64 and noticing poorly designed bicycles. | |
| Identity, Practical Value, and Leaving Business School | 3 | 3 | 1 | 0 | Brett asks about Saarinen's early professional identity and educational choices. Saarinen explains his preference for creating real-world practical value over academic exercises, leading him to leave business school. | |
| Founding Kippt, Navigating Y Combinator, and Acquisition | 3 | 4 | 1 | 0 | Brett prompts for the history of Kippt and its trajectory through Y Combinator. Saarinen walks through the mechanics of bookmarking, why tagging failed at scale, and the eventual acquisition by Coinbase. | |
| Startup Lessons: Market Selection, Focus, and YC Advice | 6 | 5 | 1 | 2 | Brett provides a detailed framing on repeat founders using an oil-drilling analogy to explore luck versus accumulated skill. Saarinen agrees and details how market selection and strict buyer qualification shaped Linear. | |
| Operating Insights from Coinbase and Airbnb: Power of Small Teams | 6 | 6 | 2 | 4 | Brett challenges Saarinen's small-team philosophy by pointing out that Coinbase and Airbnb succeeded through rapid headcount growth. Saarinen reframes the point, arguing that massive hiring is a byproduct of success rather than its driver. | |
| The Genesis of Linear: Jira Frustrations and Airbnb Extension | 3 | 4 | 1 | 0 | Brett asks about the specific genesis moment for Linear. Saarinen explains building an internal Chrome extension at Airbnb to restyle Jira's interface for visual sanity and speed. | |
| Co-Founder Reunions and Formulating the Linear Problem Space | 4 | 3 | 0 | 1 | Brett clarifies the chronological sequence of the co-founders deciding to team up versus selecting the problem space. Saarinen shares how their shared Finnish background and informal discussions solidified the concept. | |
| Defining Core Pillars: Optimizing for ICs and Local-First Speed | 4 | 6 | 2 | 1 | Brett asks how much Linear benchmarked competitors versus focusing on user needs. Saarinen outlines Linear's foundational tenets: optimizing for individual contributors over buyers, local-first architecture for speed, and vertical visibility. | |
| Validating Intuition and Creating Excitement in Enterprise Tools | 5 | 5 | 1 | 2 | Brett explores how early customer conversations shifted Saarinen's mental model. Saarinen notes that research was used to hone existing founder intuition rather than slavishly build whatever users requested. | |
| Transitioning to Full-Time, Dogfooding, and the Private Beta | 4 | 4 | 0 | 1 | Brett probes the timeline from part-time exploration to quitting day jobs. Saarinen shares the rhythm of weekly bar meetings, internal dogfooding milestones, and the gating of early access via surveys. | |
| Waitlist Management, Cohort Iteration, and Roadmap Prioritization | 5 | 5 | 1 | 2 | Brett asks how the team filtered constructive feedback from users who simply were not a good fit. Saarinen emphasizes focusing strictly on highly motivated cohorts, tracking retention, and avoiding trying to boil the ocean. | |
| Opinionated Product Architecture and Multi-Product Expansion | 7 | 6 | 2 | 4 | Brett presses Saarinen on the tension between opinionated simplicity and the massive TAM achieved by flexible platforms like Salesforce. Saarinen responds that Linear expands TAM by moving upstream into planning and feedback rather than adding bespoke enterprise bloat. | |
| Contrarian Brand Strategy and Positioning for Distinction | 4 | 6 | 2 | 1 | Brett asks Saarinen to define what brand actually means in practice. Saarinen explains brand as a consistent philosophical narrative and argues that startups should adopt contrarian positioning relative to stagnant incumbents. | |
| Finnish Cultural Influence, Sustainable Scaling, and Quality First | 4 | 5 | 2 | 1 | Brett asks how Finnish cultural background shapes company strategy. Saarinen contrasts Silicon Valley's hyper-focus on rapid scaling with a measured, quality-first, sustainable operating posture. | |
| Pragmatic Evolution: Enterprise Sales and Tiered Flexibility | 5 | 5 | 1 | 2 | Brett asks about dogmas that Saarinen had to revise as the company expanded. Saarinen highlights embracing an enterprise sales team and allowing greater workflow flexibility at executive layers while keeping IC tiers opinionated. | |
| The Design Founder Scarcity and Expanding Creative Mindsets | 4 | 6 | 1 | 1 | Brett asks why design-led founders remain rare in tech compared to engineering leaders. Saarinen explains that engineers accidentally build working functional prototypes, whereas designers frequently lack holistic business context. |
Statements from this episode (31)
Saarinen: Effective design stems from an innate ability to visualize improvements
“So I think there is some innate ability to see how things can be better, and then it is, like, easier to do designs when you can do that.”
Business schools teach middle management theory rather than practical entrepreneurship
“And then like later I realized that like business schools are not really about founding companies or entrepreneurship. They're more about the middle management or the kind of the theory of like, how do you run a company, but not actually the practical aspects …”
Saarinen: Founders must think about business models and monetization early
“Made me realize that the advice on like starting a company and not thinking about the business model too much is, is not good. Like I think you should think about it a little bit. It's like, what is, what kind of business are you in? Like what, who is going to…”
Saarinen: Web bookmarking tools are not venture-scale businesses
“I still don't think it's like a venture scale type of business. It's the market is not there to support it now or probably never. It's just like, it's not a thing or it's not that interesting for that many people”
Saarinen: Developer tools are uniquely viable to monetize due to high budgets
“Software companies and engineering tools are type of products that people are willing to pay for because the engineering functions are already highly paid and software companies have, especially VC funded software companies, they have a lot of money to spend.”
Saarinen: Linear solves organizational coordination that breaks down as companies scale
“In the end, like what the problem we are solving for companies is this like organizational coordination and communication problem. And especially like the larger the company is more problems you have with that. And basically the problem is always no one ever k…”
Saarinen: Linear limits team growth to avoid culture dilution
“We've been trying to keep the teams, like the whole company quite small or not overly growing it too fast. So I think there's two problems with growing the team too fast. One is like the, it takes a lot of time and the culture gets diluted very easily.”
Saarinen: High-speed, high-output projects always come from small teams
“All the projects that I was part of, what were the projects that went really well, like where the output was really good, where the speed was really fast or executing execution speed was really fast. And it was always like projects where we had a small team wo…”
Saarinen: Companies mistakenly treat resources as headcount instead of output
“Companies don't really do it that much because I don't, I find they often think about the resources as number of people, not, not necessarily like the output of those people. So it's easy to say, like, we need to hire like a hundred more engineers, but maybe y…”
Saarinen: Startup success enables mass hiring, not the other way around
“I don't actually believe that those people are needed for the success. It's more that the company is so successful that they can hire these people. So it's like when you have the growth there, you are able to do that. That's the lesson people should take from …”
Saarinen: Users treat incumbent enterprise software like permanent building floors
“Like, I think this market is like weird where you have this incumbent and I think people just assume it's the thing. It's like, it's always been there. It's always going to be there. And so it's a little bit like the floors in the building. It's like, you don'…”
Saarinen: No project management tool properly targeted engineering to rival Jira
“Obviously there's been companies, other companies doing project management and stuff, but No one has really focused on the engineering use case that well, I think, and haven't been able to get to the scale where, where like GRI is.”
Saarinen: Productivity tools should optimize for individual contributors rather than management
“In the end, the productivity of any company comes from the ICs, like what the actual, what is actually the work output and the ICs engineers or designers or someone are building that output.
So I think if the tool should be optimized around anything, it should…”
Saarinen: Enterprise software is built for buyers instead of actual users
“What I could see a lot of tools, and this generally I think goes for enterprise tools, they are optimized around the buyer, because that's how they get bought.
You don't, the users don't go buy the tools.
The, like the actual end users don't go buy the tools.
…”
Saarinen: Individual contributors and executives align on output while middle management obstructs
“I noticed in all of the companies I worked at that actually the ICs and the high level leadership was, I think more philosophically aligned because I think CEOs and a lot of the high level leadership, they just want to see things happening.
They want to see ou…”
Linear models user needs internally rather than building direct feature requests
“It's never been, even in the beginning or later stages, it's never that like we Listen to these users and then we build what they want or what they say. We went there, like, it's more like we have that model in our heads. And then if something doesn't quite fi…”
Simple MVPs fail in project management due to high baseline user requirements
“Like, you could build a very simple version of something, but in this category, it's, like, just doesn't work because people already have, like, pretty high standards or high needs for how this kind of tool should work.”
Linear secretly required waitlist users to complete an allegedly optional onboarding survey
“The survey was kind of optional, but Actually, you wouldn't really get in without filling the survey. So the survey was kind of like required to like actually get into the service.”
Saarinen: Linear waitlist reached 10,000 emails with 10% converting
“I would say like on the waitlist, I remember that eventually we had about like 10,000 emails on it. I would say about like 10% of them converted during that year.”
Saarinen: Linear had over 1,000 DAUs at public launch
“When we launched, we had over, I think, over a thousand, thousand, like, daily actives.”
Saarinen: Product waitlists lose user interest after at most six months
“There's also like waitlist has a decay that it's people's interest doesn't last forever. So I think I would say like the realistic timeframe is probably months or maybe at max six months.”
Saarinen: Software cannot be optimal if endlessly customizable
“I don't believe that you can build the optimal tool for anything if it's very flexible and endlessly customizable.”
Saarinen: Linear will expand beyond issue tracking and project management
“We see that the linear, what we're trying to do is helping companies to build products. And it doesn't have to be limited to the issue tracking or project management. We can do other things too.”
Project management tool brands are historically non-existent or viewed negatively
“What we found that like in this market, the brands are kind of non-existent or they're bad or they're negative. So if you think about project management tools, there's anything, and no one is like that exciting. Like, it's even hard to say, like, what do this …”
Saarinen: Startups should do the opposite of incumbent competitors
“You shouldn't probably emulate. You should almost do the opposite what all the other players in your domain are doing. And maybe you can take inspiration from some other companies in other domains and do something like similar there.”
Saarinen: Pressure on Short-Term Metrics Inevitably Degrades Product Quality
“I think like what often happens to startups or any companies is like, The quality goes down because they get pressured on some, something else. They pressured on the, we need to ship this or we need to get, get these metrics up. And then the quality goes down …”
Linear rejected salespeople before enterprise customers necessitated procurement support
“Initially, we're, like, the investors were saying that, hey, you probably need some, like, salespeople. And we said no. And it's not, like, who wants to talk to salespeople? But then at some point, you start getting these customers that do want to talk to sale…”
Saarinen: Software should be structured for execution but flexible for leadership
“We could still be more opinionated on the lower levels where there's more of this volume and need for structure because there's more people and more things happening and the more flexibility you introduce, it multiplies a lot more. But once you get to the very…”
Saarinen: Engineers validate startup ideas faster than designers through working prototypes
“So there's a little more like clear, like quicker bath to some kind of validation, I would say, versus like designers, you might have this idea of something could be better. But so you design it, but you still just have designs. You don't actually have the pro…”
Product quality suffers across tech because organizations incentivize speed over craftsmanship
“Why quality doesn't happen in most companies. It's like, it's just because it's not incentivized. No one ever says you should do it. It's almost that no, we just want you to complete this task. We don't actually care how do you complete it too much. We just wa…”
Saarinen: Many product designers are too narrow-minded and ignore business context
“There's maybe that a lot of designers are too focused on their, like a little bit too narrow looking at things or narrow minded and not maybe interested enough, like what happens like around them or like around there or they're more just looking at the design …”