How Linear Built a $400M Issue Tracker on a $35k Marketing Budget

Linear is the fastest-growing, most beloved issue tracker in the world. $400M valuation. More cash in the bank than they ever raised. A cult following among engineers. Total lifetime marketing spend: $35,000.

How?

1. The founders did their homework

Karri Saarinen, Jori Lallo, and Tuomas Artman didn't just wake up one day and decide to build Linear.

Saarinen and Lallo had already founded a YC startup, sold it to Coinbase, and taken early roles there. Saarinen then led design at Airbnb. Artman ran engineering at Uber. As Artman put it, they "consciously took jobs in Silicon Valley to prepare for their next startup."

That preparation paid off immediately:

• 10,000 people signed up for the closed beta waitlist, pulled largely from the founders' Twitter followings.

• Early beta users included teams from Cohere, Runway, and Ramp.

• Sequoia wrote a $4.2M seed check because, in the partner's words, "people she trusts in her Twitter network were hyped about Linear."

The path to a great startup rarely starts at the startup. It starts years earlier: learning from the best, building reputation, stacking network.

Takeaway: Founder pedigree is an unfair advantage. Build yours before you need it.

2. They picked a fight worth picking

At Airbnb, Saarinen noticed what every engineer already knows: everyone hates Jira. So he built a Chrome extension to simplify it, and the Airbnb product team went nuts for it.

Signal received. People want a better issue tracker. Specifically, engineers at small fast-moving teams.

So Linear built exactly that. Not for PMs. Not for enterprise. For developers at startups. In the first two years, Saarinen says, they focused on getting product-market fit in the early-stage startup segment. The goal was to become the default pick for startups. They hit it.

When bigger companies showed up, Linear's response was honest: this isn't great for you yet, but we'll keep working on it. They earned the right to expand by winning a segment first.

Takeaway: Don't try to be good for everyone. Find an underserved niche that the big flexible incumbents can't serve well, and build something opinionated for them. (This is roughly how we've been thinking about Lore too: generic documentation tools work for no one in particular, so we built specifically for engineering teams and the operational knowledge that actually lives in their Slack threads and terminals.)

3. They tested in public for a year

Linear didn't spring fully formed from the sea foam. The timeline was methodical:

1. Validate the idea (at Airbnb, with the Chrome extension)

2. Incubate the concept

3. Build a waitlist, open a private beta

4. Run closed beta for a full year, onboarding waitlist users slowly

5. Launch publicly with 1,000+ customers and raving reviews already in the bag

People call Linear a design-driven company because of the polish. The real reason is more boring: they put their product in front of real users early and kept it there. They still ship every new feature to beta before launching officially.

Takeaway: Resist the urge to polish in a cave. Ship ugly, get feedback, iterate. Early users will tell you which features they actually care about and which ones you're wasting your time on.

4. The product sold itself

Linear is collaborative software. One engineer starts using it, invites their team, which invites other teams, which spreads across the company. Network effects. Bottom-up adoption. Same pattern as Figma and Loom.

That's why $35k of marketing was enough. When the product is good and it spreads naturally inside companies, you don't need a huge ad budget.

Takeaway: Be honest about whether your product has product-led potential. Collaborative tools that get better with every new user? Probably yes. Nerdy single-player B2B SaaS? Probably no. Don't force a growth model that doesn't match the shape of what you're building.

5. They stood for something

Here's the part that's harder to copy.

Linear took a strong opinion on how software should get built. They're openly against the Silicon Valley orthodoxy of "fail fast," obsessive A/B testing, rigid OKRs, and interchangeable teams. Linear believes in craft, taste, flexible goals, and empowered individual contributors.

Engineers who agree with that don't just use Linear. They identify with it. It becomes the obvious choice because it reflects how they already think about their work.

Same soft power Stripe and Apple have. It's not the logo or the color palette. It's the worldview.

Takeaway: Your brand is what you stand for. Pick a real position and say it out loud.

6. The naming was a mess

"Linear" is a brutal SEO name. Google it and you get linear algebra. The company's brand guidelines insist it be used as a single word, no "Linear app," competing directly with 4,000 years of mathematics.

I don't think they're going to win that fight. But they're stubborn about it, and so far it hasn't mattered much.

Takeaway: Even founders with Airbnb, Uber, and Coinbase on their resumes mess up. That's fine. Most mistakes are survivable if the rest of the thing is working.

What this actually means if you're building something

Strip the Linear story down and you get a pretty clean template:

1. Earn your network before you need it.

2. Pick a segment small enough that you can actually win it.

3. Get the product in front of real users as early as humanly possible.

4. Match your growth model to your product shape.

5. Have an actual opinion about the world.

6. Accept that some things will be suboptimal and ship anyway.

None of this is new. Almost every great company does most of it. The hard part isn't knowing the playbook. It's having the patience to run it for five years before anyone notices.