Who Actually Pays?

he question that rewrote a whole marketing plan, and why I still ask it first.

A few years ago, while I was based in London, I spent seven weeks consulting remotely for an education company in South Africa. The brief sounded simple: help them reach more students.

So that's where everyone started. The messaging spoke to students. The channels were the ones students lived on. The whole plan was built around what a student would want to hear.

Then came a question that sounds almost too basic to say out loud: who actually pays?

It wasn't the student.

The student was the user. The parent was the buyer. Parents weighed the cost, compared the options, worried about whether it was worth it, and made the final call. A student could be excited all day long, but if the parent wasn't convinced, nothing happened.

That one question flipped the plan. We rebuilt it around parents: what they cared about, what worried them, and what proof they needed before saying yes. Conversion went up by about a third.

The work after that question wasn't magic. The question was.

The user isn't always the buyer

Once you start looking for this gap, you see it everywhere.

The person who uses a piece of software every day is rarely the one who signs for it. The team that will live inside a new process usually isn't the one approving the budget. The customer on the phone placing an order isn't always the one deciding where the money goes.

When the user and the buyer are different people, they want different things. The user wants it to be easy, fast, maybe even fun. The buyer wants to know it's worth it, it's safe, and it won't come back to bite them. A plan that only speaks to one of them is half a plan.

Why we skip the question

We skip it because the user is the person right in front of us. They're louder, easier to reach, and more fun to design for.

We also skip it because it feels too obvious. Nobody wants to be the person in the meeting asking something "everyone already knows."

But "everyone already knows" is exactly where the biggest assumptions hide. Half the time, nobody actually checked.

How I use it now

Before I build anything, whether that's a new market, a pitch, or an AI tool for a team, I run through three questions:

  1. Who uses it?

  2. Who decides?

  3. Who pays, and what do they need to believe to say yes?

When those are three different people, you have three different jobs. Most plans only do one of them.

Building AI tools inside a company is a good example. The people using the tool every day need to love it, or it dies quietly in a folder. The people funding it need to see the hours saved and the problems solved. Build only for the first group and you get a tool nobody pays to keep. Build only for the second and you get a tool nobody opens.

Real talk

The most valuable question in the room is usually the one that feels too simple to ask.

Ask it anyway. Especially when everyone already knows the answer.

Next
Next

Does “Growth” Already Live in Your Customer List?