Skip to content

Discovery

You're Asking the Wrong Questions

Petri Lehmuskoski ·

Most early-stage founders are optimizing for the wrong things.

Not because they're bad founders. Because the ecosystem taught them the wrong questions. The startup press celebrates fundraising as progress, valuation as achievement, and headcount as signal. So founders walk into critical decisions asking: When do I raise? How big should my round be? Which VC should I approach?

These are the wrong questions. And answering them before you've answered the right ones is how you burn runway solving problems you invented.

Here are the questions that actually matter, and what most founders get wrong about each.

1. "When Should I Raise?" Is the Wrong Question

The right question is: Do I need to raise at all?

This sounds provocative. It isn't. Across the Nordics, 82–88% of technology companies that exit successfully never raised a single euro of venture capital. That's not an anomaly. That's the dominant exit path, and almost nobody talks about it openly, because the ecosystem profits from the opposite belief.

Raising is a tool. It's not a milestone. It's not validation. It's a commitment to a specific, demanding growth trajectory, one that requires outlier outcomes to justify the dilution and the pressure that comes with it.

Before you pitch anyone, answer this first: What problem does capital solve right now that customer revenue can't? If the answer is "we'd grow faster," that's not a reason to raise. That's impatience dressed as strategy.

If the answer is "we need to hire before revenue can support it", ask why. If you need six engineers before your first paying customer, something is wrong with the model, not the fundraising timeline.

Raise when capital genuinely unlocks a step the business can't take otherwise. Not because you're out of ideas for the pitch deck.

2. "How Much Runway Do I Need?" Is Still the Wrong Question

The question isn't how much runway you have. It's what you'll learn before the money runs out.

Twelve months of runway spent validating the wrong customer segment is twelve months of very expensive confusion. Six months of runway with a clear experiment (one segment, one pricing point, one workflow) is a business.

Gorilla Capital's camel model (https://gorillacapital.fi/camel-model) is built on a simple logic: survival is a prerequisite for success. Camels survive because they force discipline before scale. The constraint isn't the enemy. The constraint is the teacher.

At the pre-seed stage, 18 months of runway is a number people repeat because it sounds responsible. It's only responsible if those 18 months are structured around learning that increases the probability of the business working. If you're burning cash on overhead and optionality, 18 months is just slow death with better branding.

Concrete benchmark: if you can't reach a meaningful customer signal (not love, not interest, actual workflow change and willingness to pay) within six months of focused effort, the hypothesis is wrong. Don't raise more money to test the same broken hypothesis longer.

3. What Actually Matters at Pre-Seed

Not what you think.

Founders believe pre-seed investors are evaluating vision, market size, and team credentials. Some are. The ones making decisions based on probability aren't.

What actually matters at pre-seed:

Problem specificity. Can you describe the pain in the customer's language, not yours? Can you name three companies where this costs real money today?

Evidence of urgency. Not interest. Not "the market is ready." Someone who moved their workflow or wrote a cheque.

Founder learning rate. How much have you changed your hypothesis in the last 90 days, and why?

Vision is cheap. The ability to update a hypothesis when reality contradicts it is rare. That's what early-stage investors who know what they're doing are actually buying.

If your pitch hasn't changed since you wrote the first version six months ago, that's a warning sign, not a sign of consistency.

4. "Do I Have Product-Market Fit?" Is Mostly Being Misused

Founders use PMF as a finish line. It's not. It's a checkpoint, and most founders declare it too early because it feels good to stop testing.

Real PMF leaves fingerprints:

  • Customers come back without being chased.
  • Retention is stable, not just acceptable.
  • Someone would be genuinely upset if your product disappeared tomorrow, not mildly inconvenienced.

The honest version of PMF testing isn't asking customers if they love the product. It's watching what they actually do. Superhuman didn't find their core insight by asking "do you like the app?" They found it by asking what users would miss most. The answer wasn't speed. It was anxiety reduction.

Most founders never reach that level of honest inquiry. They declare PMF because three customers renewed. Three customers is a hypothesis confirmed. It's not a business.

And the dangerous variant: Problem-Solution Fit declared too early (https://gorillacapital.fi/problem-solution-fit). Founders mistake demo enthusiasm for economic pain. People love demos. People pay to remove pain. These are different populations and different conversations.

5. "How Do I Avoid Premature Scaling?"

You avoid it by actually believing the order matters.

The sequence isn't a suggestion: Problem-Solution Fit → Product-Market Fit → Scaling Fit. Skipping steps doesn't make you bold. It makes you expensive. The most common variant I see is founders hiring a sales team before the funnel converts predictably. Now you have SDRs selling something that doesn't yet sell, and burning 40% of your MRR on a sales experiment that could have cost you one founder's time.

The test for whether you're ready to scale a function: can you write down, in plain language, the three steps that produce a repeatable customer? If you can't write it down, a new hire can't follow it. If they can't follow it, you're scaling noise.

Repeatability is the strategy. Scale is the reward for repeatability. Not the other way around.

6. "What Metrics Should I Track?"

Track the ones you can move this week. Not the ones that look good in a board update.

MRR tells you what already happened. It's a receipt. Pipeline conversion rate, activation rate, and 30-day retention tell you what's coming. Those are the metrics that let you intervene before the problem compounds.

Most founders track lagging indicators religiously and then act surprised when the business deteriorates. The sign that churn was rising was in the 30-day retention data three months ago. It was in the support ticket volume six weeks ago. It was in the activation rate the week after onboarding.

One practical rule: for every lagging metric in your weekly review, there should be one leading indicator you can actually move this month. If you can't name the leading indicators for your business, you don't have metrics. You have a dashboard.

7. "Should I Hire?"

The question you actually need to ask is: Are we at the stage where this hire reduces founder burden or adds to it?

Early teams must be hands-on, customer-close, and able to ship. Later-stage skills are not just irrelevant early on. They're actively harmful. A VP of Sales at €200K ARR doesn't close deals faster. They add process to a stage that needs speed and customer contact.

The right early hire is someone who can do the job, not title the job. If you're hiring to signal maturity to investors, you're spending runway on optics. That's not a hire. That's marketing to the wrong audience.

The Real Question Underneath All of Them

There's one question most founders never ask explicitly, but it drives everything:

Am I building for survival or for the story?

The unicorn story is compelling. Raise big, grow fast, change the world. The ecosystem rewards the story with attention, with introductions, with press. But the story doesn't pay the bills. Customers do.

Camel startups (https://gorillacapital.fi/camel-model) aren't small ambitions with conservative tactics. They're high-probability strategies for founders who want to actually get somewhere. Capital-efficient. Customer-driven. Built to survive long enough to earn the right to scale.

A camel can cross a desert that kills a racehorse. That's not a metaphor about being slow. It's a metaphor about who's still moving when the conditions turn.

Right now, conditions are not easy. Capital is expensive. Acquirers are cautious. The narrative economy has been repriced. What that means for founders is simple:

The questions that help you survive this are worth more than the ones that help you pitch.

Key Takeaways

1. Raising is a tool, not a milestone. Raise when capital unlocks a specific step, not because the round validates the idea.

2. Runway is only valuable if it's structured. Define the experiment before you burn the cash, not after.

3. PMF is proven by behavior, not by surveys. Customers who stay and pay without being chased. Nothing else counts.

4. Repeatability before scale. If you can't write down three steps that produce a consistent customer, you're not ready to scale anything.

5. Track leading indicators. Lagging metrics tell you what broke. Leading indicators tell you when to fix it.

More scars than trophies, and most of those scars came from asking the right questions too late.

Petri Lehmuskoski is Founding Partner at Gorilla Capital (https://gorillacapital.fi), an early-stage investor focused on capital-efficient "camel" startups in the Nordics and Baltics.

Get a free chapter

Disagree with something here, or want it covered from another angle? Send a short note.

Send feedback

The Proof Stack