The YC S11 batch was Paul Graham's artisanal era — intimate dinners, direct access, a different quality of feedback than what most founders get. What I took from three months in that environment wasn't the tactical advice. It was a specific, usable model of what founder resilience actually looks like — and what it doesn't.
Startup Fundamentals
The operating decisions that determine whether a company survives.
Substantive content from a founder who has been through it — from default-alive modeling and hiring discipline to product-market fit diagnostics and the specific things that only come from having gotten them wrong. This is pattern recognition from building, scaling, and the scar tissue of having made the expensive mistakes.
20 articles
- What Y Combinator Actually Taught Me About Resilience
- Founder/Market Fit: A Three-Question Self-Audit Before You Raise
Investors talk about product-market fit constantly. They talk about founder-market fit much less, but they're evaluating it in every meeting. Here's the three-question framework I've developed from sitting on both sides of the table — and how to audit yourself against it honestly before you start a fundraising process.
- What YC Taught Me That Actually Applies to Building in the Nordics
Y Combinator's model was designed for a specific context: young founders, fast iteration, San Francisco network effects, three months to Demo Day. Some of what it teaches transfers perfectly to Nordic building. Some of it is actively misleading. Here's the filter I use.
- The Six Board Slides That Actually Matter
Most board decks are theater. Founders present optimistic narratives; board members ask polite questions; the meeting ends and everyone has learned approximately nothing. After being on both sides of the table, here are the six slides that make a board meeting genuinely useful — and why most founders avoid them.
- Hiring Discipline: What 68 to 24 Actually Taught Me
Cutting from 68 to 24 employees was the hardest thing I have done professionally. But the real lesson was not about downsizing — it was about the hiring decisions that made the cut inevitable.
- The Premature Scaling Trap: What You Are Actually Amplifying
Scaling is not a stage of company growth. It is a bet that your current understanding is correct. Most founders make that bet before they have run the tests that would tell them whether it is.
- Nordic Founders Fundraising in the US: What Actually Works
The US venture capital market is the deepest pool of early-stage capital in the world. Nordic founders who navigate it successfully tend to do three things differently from the ones who don't. Here's what those things are, from someone who raised $40M in the US as a Danish founder and has since helped others do the same.
- The Decade Nobody Writes About
Before Realm, before Y Combinator, before any of the founder narrative — there was over a decade at Nokia. Software configuration management, build system tooling, infrastructure for hundreds of millions of devices. The unglamorous, foundational work that I've never written about, and that I now think was the most important decade of my career.
- The Three Questions Investors Ask When the Traditional Signals Aren't There Yet
After sitting on both sides of the table — raising $40M as a founder and helping tier-one VCs evaluate early-stage deals — I've noticed that the investors who are right at the early stages aren't pattern-matching on traction. They're pattern-matching on three specific things. Here's what they are and how to test yourself against them before you pitch.
- Dilution Without Regret: What I Wish I'd Known About Cap Tables Before Raising $40M
After raising $40M across three rounds and watching the cap table evolve from a simple three-person founding team to something requiring a lawyer to interpret, here's what I actually learned about dilution, preference stacks, and the decisions that compound in ways founders don't model until it's too late.
- PMF Is Not One Number
The product-market fit conversation in most startups is binary: do you have it or not? That framing is wrong, and the wrong framing leads to wrong decisions. Product-market fit is a spectrum with specific diagnostic signals at each stage — and knowing where you are changes what you should be doing next.
- Default-Alive, For Real: The Calculation Every Founder Should Run Monthly
Paul Graham wrote about default-alive in 2015. Most founders read it and nodded. Very few actually model it. Here's the specific calculation, why it matters more than runway, and what changes when you treat it as a monthly discipline rather than a one-time analysis.
- Why Building in Denmark Is a Secret Advantage (That Most Danish Founders Don't Use)
A Danish founder who spent 13 years in Silicon Valley and came back to build in Copenhagen. What I found when I returned is not what I expected — and the advantage is larger than most Nordic founders realize, mostly because they're too close to it to see it clearly.
- The Night Seed Funding Changed Forever
I was in the room at YC S11 when Yuri Milner and Ron Conway walked in and announced that every company in the batch would receive $150,000 as an uncapped SAFE — no negotiation, no diligence. The palpable shock in the room that evening changed founder psychology overnight. Fifteen years later, it's still shaping how startups are funded.
- The Hardest Thing I've Done Professionally
We scaled Realm to 68 employees, then cut to 24 in a single round when the fundraising market tightened. What those 44 conversations taught me about the real cost of capital dependency — and the principle I've built every company around since.
- What Letting 44 Engineers Go Taught Me About Building Teams
We went from 68 engineers to 24 in a single round of cuts. It was the hardest thing I've done professionally. What came out of it permanently changed how I think about hiring, team structure, and the relationship between capital and headcount.
- Why I Started Requiring Engineers to Write Before They Coded
At Nokia, writing was how you got anything done in a large organization. At Realm, we used the same discipline differently: as a decision-making tool, not a bureaucratic process. The writing practice that actually changed how our team built.
- Product Vision Without Engineering Buy-In Is Just a Wish
In 2012, I asked our team to throw away a working codebase and start over. Getting engineers to believe in the vision as fully as I did — not just execute on it — was the hardest leadership problem I'd faced to that point. What I learned from that experience about the gap between communicating a vision and transferring it.
- The Scalability Mistake Most Startups Make Before They Have Anything to Scale
Scalability planning is one of the most misunderstood activities in early-stage software. After a decade building systems for hundreds of millions of Nokia devices and a database in 2 billion apps, here's what I've learned about when architectural decisions actually matter — and when they don't.
- What Building a Database for Two Billion Devices Taught Me About Data
Three copies of every piece of data, a custom C++ storage engine designed from scratch, and 80x performance gains that developers described as magic. What actually building at data scale revealed about the problem most engineering teams get wrong.