The Self-Translation Test: how to tell a product problem from a go-to-market problem.

Growth stalls and the room splits. Half the leadership team says the product is not ready. The other half says the sellers cannot sell. Both halves have evidence, both are describing the same quarter, and from the top a strategy that is wrong and a strategy that is not being executed look exactly the same.

There is one question that separates them, and you can answer it this afternoon with deals you have already closed.

The question

When you put your product in front of a buyer, do they translate its features into their own required capabilities and work out the impact themselves, or do they need the problem framed, the solution framed and the risk removed before they will act?

That is the whole test. It is how I define pre and post go-to-market fit: not a revenue number, not a funding stage, not headcount.

Why one question is enough

Early adopters and innovators self-translate. That is what makes them early adopters. You showed them a capability and they did the rest of the work in their own heads: what it would replace, what it would be worth, what it would cost them to put it in. They had your vision already, which is why your first customers loved you and why the pitch was never asked to do that job.

The early majority does not work that way and never will. They need the problem framed, the solution framed, and the risk taken off the table before they move.

So a company selling successfully to self-translators has product-market fit and no go-to-market fit. Nothing is wrong with the product. Nothing is wrong with the sellers. The moment you run out of self-translators, revenue stalls in a way that looks exactly like a sales problem when it is a translation problem, and every instinct in the building will tell you to hire more sellers against it.

Why a test and not a taxonomy

Adopter categories are strategy canon, and they are notoriously hard to operationalize. Nobody can look across a table and reliably place a person in a psychographic, which is why the model gets taught, admired and then left in the deck it came in.

This stops trying to operationalize the psychographics and operationalizes the behavior they produce instead. One answerable question in place of a taxonomy. You never have to classify anybody. You watch what they do with your product in front of them.

How to run it on what you already have

Take your last ten closed-won deals and ask one thing about each. Who did the translating? Did the buyer arrive able to describe, in their own words, what problem this solved for them and roughly what it was worth to solve? Or did somebody on your side have to build that for them, and if so, who, and was it always the same person?

Then run the same question across what is stuck. If the deals that closed are full of buyers who did their own translating and the deals that stalled are full of buyers who did not, you have your answer, and it is not the product.

Watch for one particular result, because it is the most common and the most misread: every closed deal translated by the founder. That is not go-to-market fit. That is one person doing the translation the pitch is supposed to do, at a rate of one conversation at a time.

What it costs to leave undiagnosed

Cycles stretch, and they stretch against runway raised on a faster plan. The only closes are to buyers who self-diagnosed, so pipeline can be neither forecast nor scaled. Every conversation runs through the founder, which caps growth at one person's calendar. The roadmap gets pulled toward whatever the last confused prospect asked for. And the next round gets priced off traction the story never produced.

Underneath all of it, the company keeps hiring against a problem that hiring does not fix.

The fix is an inversion

The problem comes first. The solution, and what it takes to put it in without getting hurt, comes second. The product comes third.

Almost every pitch at this stage runs in exactly the opposite order, and it works on the people who were going to buy anyway, which is what makes it so hard to see. The demo goes well because it is genuinely interesting. Then nothing happens, and the meeting gets logged as a good one.

One thing has to be said before any of that. If the product does not solve a problem someone will pay to have solved, messaging cannot fix it and neither can I. Establishing which of those two you are looking at is the first job here, and sometimes it is the only honest deliverable.