The P->M->F Loop
Product Market Fit as an iterative problem space
I’ve always been unsatisfied with the definition of product-market fit. No definitions offer a real way to operationalize the concept.
Existing definitions are binary - you have it or you don’t - or scalar - a amorphous score you increase until you cross the threshold. Or they’re emotive. Something you feel in your chest. Know-it-when-you-see-it. “When the market starts pulling you”. "When you go from pushing a boulder uphill to desperately running downhill to keep up with it.”
All of these definitions describe a state, not a mechanism. They tell you what arrival feels like but not how to navigate towards its destination.
I believe the framing is wrong.
PMF isn’t a destination. It’s a feedback loop.
P, M, F and the loop
Let’s start with three variables.
P is everything you can control. The full surface of decisions you can make about your business. The product itself, but also its positioning, pricing, marketing, sales motion, hiring, engineering, support processes. Everything.
M is the market you’re selling into. M is high-dimensional - many ICPs, many segments, many possible positions where your product can fit. Competitors occupy different optima in the same space. M may shift over time if you’re in a frontier market.
F is the fitness signal. You expose P to M and get a signal back, F(it). F is noisy, lossy, slow. It’s not just slow to arrive, but it takes cycles to decode. You have to gather signal from support tickets, sales conversations, marketing data, customer interviews and analytics. Decoding F and locking onto the signal within the noise is a learned skill. Few possess this skill.
The infrastructure you build to decode F is itself an investment in P. Part of iterating on your business is investing in your ability to hear what the market is telling you.
F is not a number; it’s a signal landscape across M - strong in some regions, weak in others. Absent where the market doesn’t exist.
M responds differently to different iterations of your P.
This creates a clear loop. P→M→F→iterate.
Adjust P, expose it to M, receive F, decode F, adjust P.
This control loop is something you can reason about and take steps to engineer.
Structurally, it’s a RL problem. You’re an agent navigating a state space against a reward signal that is noisy and delayed. You’re exploring and exploiting against that signal: when do you try new positions in P-M space and when do you commit to a region with strong F reward signal?
I find this frame compresses well. It is purposefully hand-wavy. It allows you to go arbitrarily deep on any sub-topic of P, M or F while still reducing down to three basic questions:
What actions am I taking to position P against M?
How is M responding?
How well am I decoding F and leveraging that to iterate on P?
Everything else is a subproblem of one of these three questions. You can mold these principles to whatever deeper frameworks match your specific problem space.
What the loop reveals
Iteration speed is the game
Iteration speed through the loop compounds. Every investment that makes P-iteration faster or the F-decoding clearer/cheaper is a compounding investment in the loop itself.
Before agentic development, it was expensive to set up infrastructure that increased iteration speed. Agentic dev collapses this investment cost to near-zero. You can have much more mature infrastructure for P-iteration and F-decoding in week one of your company.
This continues to scale as you setup new roles in the company. Support teams can have knowledge bases, tagging and routing from day one because the creation of those tools are the type of low-complexity knowledge work agents thrive on.
Explore vs Exploit
Startups that scale prematurely are scaling before F gives strong signal. Exploiting too early → doubling down on a P-M position that hasn’t been validated by enough signal.
The other failure mode (although a good problem to have) is staying in Explore mode too long when the signal is already crystal clear. Not many startups die from having PMF and scaling their GTM too aggressively.
In this frame, a pivot isn’t an identity crisis. It’s a large jump in P-M space when F is making it clear you’re in the wrong region.
Competitors are part of F
Most startups worry too much about the competition instead of the P→M→F loop. The loop frames this differently. In this frame, competitors are not a problem to manage. They aren’t on the board at all.
If a competitor exists and is solving problems better than you for a segment of M, that’ll simply provide a weak F signal. You don’t have strong fit with those customers because their needs are met. You have to offer something meaningfully different or better.
This is why the classic advice is to build something “10x better” than the existing solution. An order of magnitude improvement is often the only thing that will give you real signal from M when their needs are already being served.
Attend to signals that exist, quickly
First-time founders over-focus on P. They don’t attend to M, the space they’re navigating. This is why the industry pushes founders to build MVPs. An MVP is whatever helps you complete the loop.
An MVP in this loop landscape is a minimal viable P - not necessarily a product in hand. It is some subset of P that you can take to M and get an F to decode.
Second-time founders are often much more thoughtful about distribution and GTM. They spend more time in research or crafting landing pages, vaporware demos and other materials that give enough P to earn a signal from M.
Dogfooding and bootstrapping
Dogfooding - using your own product internally - gives you a shorter, faster loop. Your internal users are a subset of your M. They emit F internally for their use cases. This allows you to iterate much more quickly on P.
Bootstrapping - using your own product to build your product - is a form of double-compounding on P-iteration. You improve P, which improves all future iteration on P. This faster P-iteration gets you to your next signal faster.
Other advice that clicks
“Do things that don’t scale” → P is weak in the early game and F is its noisest. Taking actions to navigating yourself into more unique P-M positions, even if it takes a lot of curated, non-scalable effort, is worthwhile to eke out better F. You should also be spending a massive amount of time with customers, effectively manually sampling your F signal.
“Jobs to be done” → M has strong ambient signals of what they invest in today. Paying attention to those up front saves you from Exploring blindly.
Tyler, isn’t this just Lean Startup with some RL sauce on it?
Yeah sure, agile nerd. Go run a t-shirt sizing session.
Lean Startup definitely operates on the similar underlying dynamics. Build-Measure-Learn is a loop over similar variables. But Lean Startup is a methodology. In my experience, it’s a prescription of workflows and artifacts that fail contact with reality.
What I’m trying to hone this down to is raw building blocks you can stack how you like for your specific situation. So much of company building is emergent. How you run the loop might rhyme across businesses or industries, but every business is ultimately a production function of this loop that optimizes itself for its F signal.