If you didn't relieve a client's pain, did you create value?

I want to ask a question that sounds simple and is actually hard:

After your last engagement — your last project, your last retainer, your last piece of work — did the client’s situation get measurably better?

Not: were they happy with you? Not: did they pay the invoice? Not: did they say positive things about the work?

Better. As in: the problem they came in with is smaller, or gone, or the number that was pointing the wrong way is now pointing the right way.

Because if the answer is no, or “I’m not sure,” then the value that was created is genuinely in question.

The difference between outputs and outcomes

Most service businesses, if you ask what they delivered, will describe outputs: the report, the plan, the implementation, the hours, the module. These are real things. But outputs are not the same as outcomes.

An outcome is a change in the client’s situation. Revenue up. Cost down. Process that was broken, now working. Decision that was being made blind, now made with data. Owner who was working 60-hour weeks, now working 40. Cash that was trapped in receivables, now moving.

An output is what you made. An outcome is what changed because of it.

The distinction matters because clients — consciously or not — measure value in outcomes. A gorgeous deliverable that doesn’t move anything is, eventually, a deliverable they stop paying for. A modest-looking piece of work that demonstrably changed a number they care about is something they’ll tell people about.

Pain is the most useful unit

I’ve found that “pain” is a more honest and operational word than “need” or “goal.” Needs and goals can be aspirational. Pain is concrete and present.

Pain sounds like: “We close the books two weeks after month-end and by then nobody cares about the numbers.” Or: “We can’t tell which customers are actually profitable — we just know the big ones feel important.” Or: “The owner has to be in the building for anything to get done.”

When you understand the pain specifically enough to repeat it back in the client’s own words, you have two useful things: a clear definition of what success looks like, and a built-in measurement for whether the work worked.

The outcome of the engagement should be: that specific pain is gone, or measurably smaller. If it isn’t, you should know why, and the client should know why. “We tried X, it didn’t resolve it, here’s what we learned and what we’d do next” is a legitimate answer. “We delivered the deliverables” is not.

The uncomfortable implication

This logic has a slightly uncomfortable consequence for how engagements get structured and sold.

If value is measured in pain relieved, then taking on an engagement where the pain isn’t well-defined is a problem — not just for the client, but for you. You’ll work hard, deliver outputs, and have no real way of knowing whether you helped. The client won’t know either. And when it comes time to renew or refer, they’ll be vague, because you both were.

The discipline of asking “what pain are we solving, and how will we know when it’s gone?” before the work starts is one of the highest-leverage things a service business can do. It sets up a clear test. It keeps the work pointed at what matters. And it produces a story — “before we started, this number looked like this; now it looks like this” — that the client can actually tell.

That story is worth more than any deliverable.

How we think about this

The way I approach it: enter through the P&L, because that’s where pain eventually becomes visible. A process that’s broken shows up as a cost. A customer relationship that’s mis-priced shows up as margin. Owner-dependency shows up as a ceiling on growth.

The engagement isn’t done when the analysis is complete. It’s done when something on that P&L moved in the right direction, the client can see why, and the process that produced the wrong number has been changed so it produces a better one.

That’s the standard. It keeps the work honest — for both sides.

← All posts