Tessl Raised $125M Before Launch: How Snyk Founder Guy Podjarny Is Betting on Spec-Driven Development

TL;DR: Tessl is a London-based AI-native software development company founded in early 2024 by Guy Podjarny, the founder of Snyk. It has raised $125 million — roughly $25M in seed and a $100M Series A led by Index Ventures, with boldstart, GV and Accel — at a valuation reported at $500M+ (and reported by Fortune at $750M), while the product was still in closed beta. The thesis: in an AI world, software stops being code-centric and becomes spec-centric, where a long-lived requirements document is the real asset and the code is regenerable. Podjarny's previous company, Snyk, went from $100K ARR after two years and two months — having burned $4M — to $19M ARR three years later, and does over $300M ARR today. He told both stories on The Product Market Fit Show.

What does Tessl do?

Tessl is building the platform for spec-driven development. The premise is that today's software loses its own intent:

"Today, software is defined by code. You start with some requirements, write the code, then throw those requirements away—and you repeat that cycle over and over. Eventually, the code itself becomes the only definition of what your product is. Nobody really remembers the original functional requirements." — Guy Podjarny, Tessl

Tessl's answer is to make the spec the durable artifact and let AI generate the code from it. Podjarny frames it as a progression: spec-assisted development, then spec-driven, then spec-centric software.

Where the company actually started selling, though, is more concrete than the vision — and that gap is the most instructive part of the story. Podjarny is explicit that the endgame doesn't work with today's models, so the team spent about a year finding a starting point that does. That starting point turned out to be coding agents:

"Agents do everything I described—but faster. They code faster, but they also forget faster. They create spaghetti code faster… The agent you open tomorrow has no idea what yesterday's agent did. So agents need specs." — Guy Podjarny, Tessl

Practically, Tessl integrates on top of Claude Code rather than competing with it. It gives teams a way to define how things should be built — policies, internal platforms, best practices, even commit message conventions — and stores what was built as a living "document of intent" alongside the code, capturing not just what happened but why.

At the time of the episode the main product was in closed beta, with a spec registry in open beta.

Who founded Tessl?

Tessl was founded by Guy Podjarny, a developer-turned-product-leader-turned-founder with roughly three decades in software.

• He spent his first decade in application security, at Sanctum and then Watchfire (acquired by IBM Rational).
• In 2010 he founded Blaze in Ottawa — a "web page compiler" that made sites faster — and sold it to Akamai in 2012.
• He became CTO of Akamai's web performance division, roughly half of the company's $700M-a-year business, for about three and a half years.
• He founded Snyk in July 2015 — eight days after his last day at Akamai — and led it as CEO before bringing in Peter McKay as CEO around year five.
• At the end of 2022 he took a five-to-six-month sabbatical, came back part-time to run Snyk's AI strategy in early 2023, and resigned at the beginning of 2024 to start Tessl.

His account of why he came back for another company is unusually plain:

"The last step was just admitting to myself that I'm an addict. I love building. And I wanted to do it again." — Guy Podjarny, Tessl

How much has Tessl raised?

Tessl has raised $125 million total:

• Seed — ~$25 million, from GV and boldstart.
• Series A — $100 million, led by Index Ventures, with Accel, GV and boldstart participating, announced November 2024.

Reported valuation was $500M+ at the time of the raise, with Fortune reporting $750 million.

Key stat: $125M raised before the main product left closed beta.

Podjarny doesn't defend this as a general strategy — he defends it as his:

"I don't always recommend raising that much early, but for us, it made sense. I say proudly, and publicly, that I have zero interest in building something small. We're building big." — Guy Podjarny, Tessl

He adds that practically all of that capital was still in the bank, and that the raise was about autonomy and long-term partners rather than spend. If you're weighing the same question, when to stop fundraising and product market fit with no revenue cover the trade-offs from the other end of the market.

The Snyk lesson: product-user fit is not product-buyer fit

Podjarny's most portable idea comes from Snyk's near-death stretch, and it reframes what "product market fit" even means for bottom-up companies.

Snyk was deliberately built as a developer tooling company that happened to do security — not a security company aimed at developers. The distinction drove everything: the hiring, the community, the color scheme, the guard-dog logo. It also drove a product-led growth motion that was, at the time, almost unheard of in security.

And it worked — on the usage side. Users climbed into the thousands, then tens of thousands. Then Snyk turned on billing.

"So when we launched that GitHub app, we also GA'd. I said, let the floodgates open, come pay us… It took us a moment to realize, they're not going to pay. They're just not." — Guy Podjarny, Tessl

The price was $20 a month. Nobody converted. In late 2016 Podjarny ran a preemptive round off the usage numbers, got invited to an Andreessen Horowitz partner meeting, and watched every investor walk once they saw there was no revenue behind the curtain. Ed Sim at boldstart topped up the seed with a small extension, which kept the company alive.

The diagnosis is the framework worth stealing:

"When I talk about product-market fit, I actually separate it into two things: product–user fit and product–buyer fit. I think we had cracked product–user fit, which is critical for PLG. But PLG works best when the distance between the user and the buyer is small." — Guy Podjarny, Tessl

For Snyk, the distance between the developer using it and the security leader buying it was enormous — and the team had neglected the buyer entirely. No governance, no reporting, no breadth of language coverage. A JavaScript developer doesn't care whether you support PHP; a CISO cannot run five tools across five stacks.

So Snyk spent a year building for the buyer while keeping the bottom-up motion, and paired them in what Podjarny calls a pincer movement: outbound to AppSec leaders opening with "did you know seven developers in your organization are already using and loving Snyk?"

Key stat: Snyk was at $100,000 ARR two years and two months in, having burned $4 million. Four months later: $650K. A year later: $4.5M. A year after that: $19M. Today it does over $300M ARR.

"For Snyk, it's pretty clear. It was that stretch between August and December of 2017. We started getting inbound after inbound… Suddenly, every conversation was an inbound one." — Guy Podjarny, Tessl

More on this in our guides to product market fit for developer tools and product market fit for cybersecurity.

How Snyk got its first thousands of developers

The tactical layer is worth reading if you're building bottom-up.

Snyk shipped a free CLI that required no login at first — download it, run it, find out if you're vulnerable. Podjarny then did the unglamorous work himself:

"Went to meetups, to any meetup that would take me. I'd have seven people in the audience, fifteen people in the audience. I just chased them around. That was a heavy travel year. I literally flew to give a presentation where only three people showed up." — Guy Podjarny, Tessl

Developers tried it once and stopped. The blocker was that putting a security test into the build is a gate: it breaks the build, sometimes for a vulnerability disclosed in a dependency you never touched. So Snyk built a GitHub app that engaged at the point of change — flagging a vulnerable library at pull-request time, never blocking, and opening automatic fix pull requests when new vulnerabilities were disclosed.

Those fix PRs on public open source repos created a viral loop: every one notified everybody watching the repo.

Two framing devices underpin all of it. The minimum unit of value — the smallest unit that's genuinely valuable to someone — is one developer on a desktop for dev tools, but a business unit for security governance, which is exactly why dev tools go bottom-up and security doesn't. And the care versus hard axis:

"You'll only do something if you care more than it's hard. One tool is to make someone care more—but that's slow. The other is to make it less hard." — Guy Podjarny, Tessl

That's also why Snyk started with open source dependency vulnerabilities rather than static analysis: a dependency vulnerability is a database lookup, a match. Lower difficulty, same motivation. Then the Equifax breach — 300 million records, an unpatched Java Struts vulnerability — landed squarely on the exact problem Snyk solved.

Key lessons from Guy Podjarny's playbook

1. Separate product-user fit from product-buyer fit. Loved and unpaid is a real state, not a contradiction. Measure the distance between your user and your buyer before you build a PLG motion; the bigger the gap, the more you must build for a buyer who will never open the product.

2. Pick the problem where "care" is high and "hard" is low. Snyk chose dependency scanning over static analysis on exactly this calculus.

3. Meet users at the intent moment. The build-gate failed; the pull-request notification worked. Same data, different moment, completely different adoption.

4. Anchor in the future, then find today's beachhead. Tessl's spec-centric vision doesn't work with current models — so the company shipped into the agent workflow that exists now. Podjarny's own advice: build something that in five years is more needed, not less, but take small deliberate steps to get there.

5. Build a movement, not just a product. Snyk had DevSecCon and The Secure Developer podcast; Tessl launched the AI Native Dev podcast and conference and had roughly 70,000 followers and subscribers before the product fully launched.

6. The worst outcome isn't failure — it's getting stuck. In his words: a company doing $2–3M ARR growing 30% a year, enough to survive, not enough to walk away from, and not what you signed up for.

FAQ: Tessl

Q: What is Tessl? A: Tessl is an AI-native software development company building a platform for spec-driven development, where a long-lived specification — rather than the code — defines what the software does. It integrates on top of coding agents such as Claude Code to give them guidance and persistent memory of intent.

Q: Who is the CEO of Tessl? A: Guy Podjarny, who founded Tessl in early 2024. He previously founded Snyk (2015) and Blaze (2010, acquired by Akamai), and was CTO of Akamai's web performance division.

Q: How much funding has Tessl raised? A: $125 million total — roughly $25 million in seed and a $100 million Series A announced in November 2024.

Q: Who are Tessl's investors? A: Index Ventures led the Series A, with boldstart, GV and Accel participating. boldstart and GV also backed the seed.

Q: What is Tessl's valuation? A: Reported at over $500 million at the time of the Series A, with Fortune reporting a figure of $750 million.

Q: Is Tessl related to Snyk? A: They are separate companies with the same founder. Podjarny founded Snyk in 2015 and resigned at the beginning of 2024 to start Tessl; he now advises Snyk but is no longer on its board.

Sources: Listen to the Full Founder Story

• Guy Podjarny, Founder & CEO of Tessl — founder of Snyk (over $300M ARR) and Blaze (acquired by Akamai), former Akamai CTO of web performance, now building the spec-driven development platform for AI-native software.
• Full episode: He burned $4M to hit $100K ARR — but with 1 big change, he grew to $4.5M ARR in just 12 months on The Product Market Fit Show.

Listen to the full episode at pmf.show for the complete story.

Last updated: August 2026