The most dangerous sentence in business is the customer asked for it.
It sounds like the end of an argument. It sounds like humility, even. We listened, they told us, we built it. What more do you want!?
Here’s what’s wrong with it, and it’s not a small thing. Your customer did not tell you their problem. They told you their solution. And you wrote it down, and you built it, and you put it on your homepage, and you have been quietly wondering ever since why the thing you shipped exactly as requested is not selling the way it should.
Let me show you what happened, and I’m going to use a story, because the abstraction is useless without it.
The man at the gorge
A man is standing at the edge of a gorge.
You walk up and ask how you can help. He asks for a bridge. So you sell him a bridge.
That is how most businesses are run, and it is why most marketing does not work.
Because almost nothing in that request is true.
He did not set out to reach a gorge. He set out towards something. The gorge is not his destination, and it isn’t even his problem. It’s the last obstacle in a chain of obstacles, and the chain started a long time before you turned up. If you don’t know what he was walking towards, you don’t know what to sell him, because you are selling the crossing and he is buying the arrival.
He does not want a bridge. Nobody has ever wanted a bridge. He wants to be on the other side, and a bridge is simply the cheapest way he can currently imagine of getting there. Ask a person what they want, and they will hand you a mechanism, every single time, because a mechanism is much easier to say out loud than a longing.
And he does not need the other side either. The far side is only a place. What he needs is whatever made him leave home. The job. The doctor. The daughter. The version of himself who is no longer standing here. He has not mentioned this. He will not mention it unprompted. And there is a very fair chance that he could not name it if you asked him directly.
So when he asks for a bridge, what he is actually saying is closer to this:
I was going somewhere. I have been stuck here for four months. I tried once already, and it went badly, and I felt stupid. There’s a way round, but it costs me three days I haven’t got. Every morning I look at this thing and decide again not to cross. And I’m starting to wonder whether I ever will.
That’s the story. The bridge is one line of it.
Ask, want, need: the three things every business confuses
Here’s the discipline, and it’s worth more than any framework I could give you.
There are three things in play, and we habitually smash them into one. Keep them apart, and almost everything else in your marketing sorts itself out.
The ask. The solution they name. A bridge. This is the search term, the words in their head, the thing they type at eleven at night. It is the first line of your page, whether you like it or not.
The want. The far side. The thing they’d pay for. This is emotional, specific, and it is what your headline is for.
The need. Whatever made them leave home. Usually unspoken, often unnamed, and it is what your product must deliver if they are still with you in month six.
Enter at the ask. Sell to the want. Deliver on the need.
Three different jobs, three different places. Collapse them, and you get one of three specific, expensive failures, and I’ve watched businesses commit all three in the same quarter.
Three ways businesses get customer needs wrong
Failure one: you only build the bridge.
You gave him exactly what he asked for. He bought it. He crossed. And then he churned, or he went quiet, or he renewed once and not twice, and your retention team wrote something in a spreadsheet about engagement.
He didn’t need a bridge. He needed to get to the doctor. Your bridge went to the wrong side of the valley, and nobody found out until month four, because he’d asked for a bridge and you’d delivered a bridge and everybody was, technically, correct.
Failure two: you ignore the ask entirely.
You’ve read enough marketing books to know that customers don’t buy features; they buy outcomes. So your homepage is about transformation and possibility and the version of themselves they could become, and it is genuinely beautifully written, and nobody knows what you sell.
He searched for a bridge. He is standing on a page about journeys. He leaves.
Failure three, and this is the one that people who’ve read a book about Jobs-to-Be-Done commit constantly: you tell him he doesn’t really want a bridge.
You’ve spotted it. You’re pleased about it. And so you explain, with some care, that what he really needs is to interrogate the underlying assumption that crossing is the correct strategy at all.
You are completely right. He will smile, and he will walk, and he will buy a bridge from somebody less clever than you within the fortnight.
Never tell a man at a gorge that he doesn’t really want a bridge. You’ll win the exchange and lose the customer, which is the worst trade available.
Meet him at the ask. It’s not a lie, and it’s not stupidity. It’s just the only vocabulary he has for a thing he’s been standing in front of for four months.
Two examples: what a restaurant owner and a dieter actually need
Two people I’ve used elsewhere, put through the same three failure columns.
Marco runs a sixty-cover bistro and takes his bookings in a paper diary.
He asks for a booking system that stops the double bookings. He wants a relaxed Sunday morning. To come down at eleven, make a coffee, and open his phone without the flinch. He needs his head chef, Anna, to stay. Because if she goes, he’s on the pass six nights a week at his age of forty-nine, and the thing he built stops being a business and goes back to being a job.
Priya is thirty-eight, works in procurement, and has downloaded and deleted three calorie apps in four years.
She asks for a calorie counter that isn’t annoying. She wants to get in the pool on a Saturday. In a costume. In front of strangers. Not thinking about any of it. She needs to stop being the mother who says no. Her son asked twice, and she said she was tired, and now he doesn’t ask.
Now look at those and ask yourself, honestly, whether anything on your website is written for them.
Anna isn’t a feature. The pool isn’t a benefit. But they are the reason two people are going to spend money this year, and every competitor Marco and Priya are looking at is talking about table plans and macro tracking, in a room where nobody has ever mentioned the boy who stopped asking.
How to find what a customer really needs
You will not get the need by asking for it. “What do you really need?” is a question that produces either silence or nonsense, because if they could answer it they’d have solved it themselves.
You get it by asking a smaller question, three times.
What does that cost you?
Then, when they answer: and what does ‘that’ cost you?
And again.
The first answer is always the shell. Marco says he loses covers. Second pass, he says he comps tables and turns them late. Third pass, quieter, he says Anna watched him do it and didn’t say anything.
There it is. Three questions, about ninety seconds, and you have reached the thing he has been thinking about at four in the morning and has never said to a living soul.
That’s column three. That’s what you have to build. And you’ll never find it by asking what he wants, because what he wants is a bridge, and he has been telling you that from the beginning.
And then the fire
One last thing, because none of this makes him move.
He can know exactly what he wants and exactly what he needs and stand at that edge for another four months. People do. You are almost certainly doing it about something right now, and you could name it in three seconds if I asked you to.
He won’t cross because you turned up with a better bridge.
He’ll cross the day something behind him catches fire.
Your job is to know what the fire looks like, to be standing there on the day it starts, and to have already shown him where to put his feet.