An outcome is the way your customer sees it. Not the way you see it. Not the way your team describes it internally. The way the person on the other side of the table sees it — stated so plainly that it needs no jargon, no setup, no translation.
The test is simple: can you say what you do in a way that lands as something the customer already wants, minus a cost or drag they are already aware of? The drag does not have to be fully understood by them. It can be hidden, even mysterious. But its effects have to be visible somewhere in their world. If they cannot feel the problem, you are fighting uphill before the conversation even starts.
What capability is not
A capability is the ability to do something. Faster, cheaper, smarter, more reliably — whatever the modifier is. That sounds valuable. It often is not, or at least not on its own.
Here is the clearest way I know to show the difference. Say you have built shoes that help someone walk to the bus stop faster. That sounds useful. But unless someone actually needs to get to the bus stop faster — unless speed to the bus stop is a felt problem in their life — the shoes are irrelevant. The capability is real. The outcome is absent. And absent outcomes, there is no market.
Whether something is faster, cheaper, or better is not what makes it valuable. Whether that thing itself matters is what makes it valuable.
What this means for go-to-market
This distinction matters most to people going into organisations on the sales or business development side, and equally to founders building from scratch. If you cannot state your outcome in a way that your customer immediately recognises as something they want, you do not yet have a go-to-market. You have a capability looking for a problem.
That does not mean the capability is worthless. Much of the internet is built on things someone created without a clear market — open source tools, protocols, abstractions that no one initially had a specific need for. But someone eventually built on top of them and found the outcome layer. The capability was real. The outcome just had to be discovered and attached.
The point is not to abandon what you have built. The point is to align your mode of acquisition with a market that has your thing as an actual outcome. If you go to market claiming capability, you are asking people to do the translation work themselves. Most will not bother. The ones who do are usually not the customers you wanted anyway.