Part 3 of a series on the ZERO to 1 stage. Part 1: Why Fractional GTM Beats Hiring a VP of Sales at Pre-Seed. Part 2: The First 90 Days of a Fractional GTM Engagement.
From the outside, these two problems look identical. Deals stall. Prospects go quiet. The pipeline that looked promising in the deck review meeting somehow never turns into signed contracts. The founder starts wondering whether the whole thing is a GTM problem or a product problem, and that’s usually where the diagnosis goes wrong, because the two get treated as one question when they’re actually two completely separate ones with two completely different fixes.
Get this diagnosis wrong and you waste real time. Treat a PMF problem like a GTM problem and you’ll spend months tightening a pitch for a product the market was never going to buy. Treat a GTM problem like a PMF problem and you’ll panic, pivot, or shelve something that actually works, just because nobody had built the infrastructure to sell it properly yet.
The question that actually matters: have you closed anything?
Not “has anyone said they loved it.” Not “did a prospect get excited on a call.” Actually closed. Money changed hands, or a real contract got signed, even once, even for one customer, even at a discount you’re a little embarrassed about.
If the answer is yes, even a small yes, that’s real signal. It means someone with the problem, with budget, and with the authority to buy, looked at what you built and decided it was worth paying for. That’s PMF evidence, even if it’s thin. The problem at that point almost certainly isn’t the product. It’s that you haven’t yet built a repeatable way to find more people like that first buyer and walk them through the same path.
If the answer is no, genuinely zero, after real effort, that’s a different conversation, and it’s worth having honestly instead of assuming the fix is “hire someone better at closing.”
The consistency test
When deals stall, listen for whether the objection is the same one, over and over, from unrelated prospects, or whether it’s scattered.
A product-market fit problem tends to sound consistent: prospects like the idea but the actual thing doesn’t do the one thing they need, or it does it but not well enough to switch from whatever they’re using, or the pain you’re solving for isn’t actually painful enough for anyone to prioritize budget for it this year. You hear versions of the same “no” from people who have never spoken to each other.
A go-to-market problem tends to sound scattered and logistical: timing is off, budget cycle doesn’t align, the champion you were talking to left the company, procurement is slow, the person who said yes wasn’t actually the decision-maker. These are real obstacles, but they’re process obstacles, not product objections. Nobody is telling you the thing doesn’t work. They’re telling you buying it right now is hard for reasons that have nothing to do with its quality.
What existing customers actually do matters more than what prospects say
If you have even a couple of paying customers, watch how they use the thing. Are they opening it constantly, pulling it into how they actually work, asking for more from it, mentioning it unprompted to other people in their network? Or is usage quietly dying after the first few weeks while they stay a customer out of inertia or because cancelling feels like a hassle?
Real engagement from a small base is a stronger PMF signal than a large number of polite “this is interesting” conversations that never convert. Founders sometimes discount the first because the numbers are small, and get excited about the second because the numbers feel bigger. It’s usually backwards.
Real engagement from a small base is a stronger PMF signal than a large number of polite conversations that never convert. It’s usually backwards from what founders want to believe.
The trap in both directions
The first trap is concluding “no PMF” after a handful of early no’s when the actual problem is that nobody had a tested ICP, a tested message, or a mapped buying process yet, which is exactly what the first 90 days of real GTM work is supposed to produce. Without that foundation, a “no” doesn’t tell you much of anything. It might mean the product is wrong. It might mean you pitched the wrong person, in the wrong language, at the wrong point in their budget cycle. You can’t tell those apart without the basic infrastructure in place first.
The second trap is the opposite: assuming that because a few things are broken in the sales process, everything must be fine on the product side, and refusing to look hard at genuinely consistent negative signal because it’s less comfortable than blaming execution.
How to actually run the test
Don’t try to answer this question from a standing start. Build the minimum GTM infrastructure first: real ICP, tested message, a small number of genuinely qualified conversations with the right buyer, not just whoever answered an email. Once you’re talking to the right people with a message that’s already been refined, the “no” you get back is finally telling you something real about the product, instead of telling you something about a broken pitch or a mistargeted list.
That’s the only point at which this diagnosis is trustworthy. Everything before that is noise dressed up as signal.
Next in this series: the specific point where founder-led sales should hand off to a real, full-time sales hire, and how to structure that transition without losing the deals already in motion.