They Understood What I'd Built. They Still Didn't Buy.

Short answer: understanding a product and understanding its use case are two different things, and only the second one makes someone buy. If everyone who actually tries your product loves it, the leak isn't downstream — it's the step before that, getting someone to understand it well enough to try it. That's not a product problem. It's a marketing problem, and "explain it more clearly" is the wrong fix for it.

The problem I couldn't name for months

People understood what we had built. They understood the benefit. They would nod along on a call and say yes, that makes sense, that sounds useful — and then nothing would happen.

What they did not understand was the use case. And it took me an embarrassingly long time to work out that those are two completely different things.

The questions I kept getting were never "what is it?" They were:

Why should I? I get why. But what would this actually look like? How would it work? How would I set this up for my specific business?

I could go back and forth with one prospect for hours trying to explain what would actually happen once they got into the platform, and they would usually leave the call more confused than when they arrived.

Why explaining it more made it worse

Our product is general-purpose infrastructure with an AI on top. You can use it however you want. That flexibility is the whole point — and it is also exactly what made it impossible to explain.

The reason it has value is that the AI does something your brain cannot do. It looks across a space of possible collaborations and finds matches you would never have found by hand. But that creates a nasty little trap: because they could not do the calculation themselves, they could not picture the output. They had no way to imagine what the AI would come back with, because if they could imagine it, they would not have needed the AI.

So they got stuck in a loop. I would explain, they would nod, they would still be stuck, and I would explain again. Hours of my week, going nowhere.

And then, reliably, a few hours after a call, the phone would ring.

"Ah — okay. I just used the product. I just used the AI. Now I understand what you guys are doing. This is cool. Let me give you some money."

The diagnosis was in that phone call

That call is good news and bad news at the same time, and for a long time I only heard the good half.

Every single person who got onto the platform loved it. Every person who actually used the AI saw the value and stayed. Our retention was fine. Nothing downstream of "they tried it" was broken.

Which means the entire loss was happening at one step: getting someone to understand it well enough to try it. That is not a product problem. That is a marketing problem. And I am not good at marketing.

If you only take one thing from this: if the people who reach your product stay, stop touching the product.

The uncomfortable second reason this is hard

There is a second reason this is hard, and it is more uncomfortable than the first.

To be a successful business you have to be a different business. Not a better one — a different one. You have to find your own distribution channel, your own marketing message, your own product design. Otherwise you are a commodity, and commodities compete on price until nobody makes any money. This is especially true in software, where "better" has a shelf life of about a quarter.

So "explain it more clearly" was never going to be the answer. Clearer is a better version of the same message. I needed a different one.

The golden circle, and the part I kept missing

The framework I went back to is the one you have probably already heard of: Simon Sinek's Start With Why. The golden circle. You start with why, then you go to how, then you go to what.

Most companies do it in exactly the opposite order:

1. What have we built?
2. How can you use it?
3. Why is that important?

The case study Sinek uses is HP versus Apple, and it's worth walking through properly because reading it as a bullet point is not the same as hearing it.

Here is HP. You go to their site, you look at their computers, and they say: we have built this computer, with this screen, this refresh rate, this many gigabytes of RAM, this much storage, blah blah blah. Then: you can now use this to do Excel, to code, to program, to run these apps, to watch videos. Then, if they get there at all: why should you care? It is a really good computer. It could help you do a bunch of cool stuff.

Every claim is true. The spec sheet is complete and correct. And it has not given you a single reason to want one.

Here is Apple, in the same three parts, reversed.

We are building for the change makers. We're building for everyone that has a strong vision. We're building for the ones who think they are crazy enough to change the world — because those are actually the ones that end up doing it.

We want to give you the tools to do it and reach your goal, with a beautiful design that could help you reach it.

We have built personal computers that are beautifully designed and easy to use and navigate.

Same machine. Completely different message. And by the time you reach the spec sheet you already want the thing, so the specs become confirmation instead of persuasion.

That is the whole idea: start with why, then how, then what — instead of going what, how, why.

Where this left me

Knowing the order was not enough, which is the part I did not expect. We already had a why, a how and a what. Rearranging them did not fix anything, which told me something else was missing: I knew the order of the three, but not what each one was actually for.

That is the next piece, and it is the one that moved the number — the three sentences I ended up with, and what happened to our inbound the week after I rewrote the site with them. It's written up in Three sentences that make your product make sense.

Related reading:

• Three Sentences That Make Your Product Make Sense — part two: what each part of the golden circle is actually for, and the exercise that took us from zero to eight inbound meetings a week.
• Jobs to Be Done, Explained With the McDonald's Milkshake Story — the same gap, one layer earlier: understanding what job the customer hired you for.

If you're building something and the people who try it love it while the people who hear about it don't move — that's the same problem, and it's fixable.