PMF is a GTM problem

Most founders treat product-market fit like a product problem. Build the right thing, nail the features, ship fast enough, and the market will respond. When it doesn't, they iterate on the product. Add a feature. Redesign the onboarding. The assumption is always the same: the product isn't good enough yet.

Sometimes that's true. But more often than not – especially pre-PMF – the product isn't the bottleneck.

What "fit" actually means

Product-market fit has three words in it, and most people fixate on the first one. But the operative word is fit. Fit between what and what?

It's the alignment between three things: who you're selling to, what you're actually offering them, and how you talk about it. The audience, the value proposition, and the message. Change any one of those and you change whether the product lands – even if the product itself stays exactly the same.

I've seen this pattern repeatedly. A founder has something genuinely useful. But they're pitching it to the wrong audience, or they're describing it in terms that don't connect, or they're leading with a feature when they should be leading with an outcome. The product works. The fit doesn't. And because they're product-minded, their instinct is to go back and build.

That instinct is wrong. What they need to iterate on is the GTM.

The iteration loop is wrong

Pre-PMF, most teams run something like: build → measure → learn → build again. The iteration variable is the product. Everything else – the positioning, the audience, the way they describe what they've built – stays roughly fixed while they tweak features. The objective is to learn what users want by shipping it (or a minimal version of it) to see if they'll use it. This commonly gets mistaken for building a v1, leading founders to polish and tweak, when the real objective is to learn.

In a GTM-led mode, the iteration loop should be: position → target → message → test → reposition. Try a different audience. Reframe the value prop. Change the message. See what sticks. The product is one input, not the whole equation. Shipping an MVP is merely a part of the test step.

This doesn't mean product doesn't matter. It means product alone is insufficient. You can have the right product for the wrong people, or the right product described in the wrong way, and it looks identical to having the wrong product. The signal is the same – no traction. But the fix is completely different.

Why founders default to building

Building feels like progress. You can see the commits, count the features, demo something new each week. GTM iteration is messier. Testing a new positioning doesn't come with the dopamine of shipping code. Talking to a different audience segment feels like starting over, and can be grueling – not satisfying like shipping a new version of your product.

But pre-PMF, the messy work is the work. The clarity you need isn't "what should the product do?" It's "who is this for, why do they care, and does the way I'm talking about it match what they need to hear?"

I've been that founder. Technical founders default to the tools they're comfortable with. Code is controllable, markets are not. So you retreat to the thing you can control and hope the market catches up. It rarely does.

The whole package

None of this is an argument against building great products. It's an argument against building in a vacuum.

Pre-PMF, every decision is connected. The audience shapes what matters in the product. The product constrains what you can credibly promise. The message determines who even gives you a chance. These aren't sequential – figure out the audience, then build, then message. They're simultaneous. You're tuning all three at once, looking for the combination that clicks.

In my experience, finding PMF quickly has less to do with how much you build and more to do with how deliberately you iterate on the whole package – the who, the what, and the message as a single system.