Diagnose Before You Deliver: The Case for Prescriptive Marketing

There are two ways to sell professional services.

One is to present a menu. The client chooses the deliverable, the provider executes it, and everyone discovers later whether it addressed the actual problem.

The other is to diagnose before recommending. The provider asks what is happening, examines where the system is breaking and proposes a specific path with a reason behind it.

Both models can produce competent work. Only the second consistently uses the judgment a client hired an expert to provide.

What the difference costs

A menu of services puts the hardest decision on the person least equipped to make it.

A client who arrives asking for a website refresh may actually have a positioning problem, or a follow-up problem, or a target list problem. Presented with a menu, they will order the website, because that is what they came in knowing how to order. They will get a good website and the underlying issue will still be there in six months.

That is the quiet cost of a transactional posture. The work is competently delivered and the outcome does not arrive, and neither party is quite sure why.

The prescriptive alternative is not more complicated. It is one extra step at the start: diagnose before you recommend.

Diagnosis is the whole discipline

A real discovery conversation is more specific than a questionnaire.

What has been tried already, and what happened? Where does the current process break down, and who notices first? What has to be true in twelve months for this to have been worth it? Which constraints are fixed, in budget, in team, in timeline?

Those questions do two things. They surface the actual problem, which is often adjacent to the stated one. And they demonstrate competence, because clients can tell the difference between someone gathering requirements and someone thinking about their business.

This is also where honest scoping happens. Sometimes the answer is that the thing they asked for is right. Sometimes it is that they need something smaller first. Sometimes it is that the approach they are considering does not fit their shape of business, and saying so plainly is more valuable than a proposal.

Make a clear recommendation and stand behind it

Once you understand the problem, make a clear primary recommendation.

Do not default to three options at three prices simply to avoid taking a position. Recommend the path you believe is right, explain the reasoning, identify what it will require and describe what you expect to learn or see. If legitimate paths differ by risk, sequence or investment, present them clearly while still naming your recommendation.

The value is not in reducing every decision to one option. It is in ensuring the client understands which path you recommend, why you recommend it and what tradeoffs come with it.

Standing behind it also means being specific about what is not included and what could go wrong. That is not hedging. It is the part that makes the recommendation credible, and it prevents the mismatch in expectations that ends more engagements than poor work does.

What to do when the client insists

Sometimes a client hears the recommendation and wants the thing they originally asked for anyway.

That is ultimately their call, but a prescriptive posture does not require accepting work that you believe will fail or create harm. Be clear in writing about what you recommended and why. If the requested work can still create legitimate value, scope it honestly. If it cannot, declining may be the more responsible decision.

Two things follow from handling it that way. The client keeps their autonomy, which matters and which they will remember. And when the underlying issue surfaces later, the conversation is already framed, so the next engagement starts from a position of trust rather than blame.

Being prescriptive is about supplying a view, not about winning the point.

Prescribe the sequence too

The most useful prescription is often about order rather than content.

Plenty of marketing work fails because it was done in the wrong sequence. Campaigns launched before the record could support them. Personalized outreach built before anyone agreed which companies to pursue. Content produced before the positioning it was supposed to express had been settled.

A prescriptive partner says what comes first and what waits, including when that means a smaller opening engagement than the client expected. Telling someone their foundation needs two weeks before the campaign is worth running is a harder conversation and a better one.

Where the deli instinct comes from

It is worth naming why menus are so common, because it is not laziness.

A menu feels safer. It lets the client choose, which feels respectful and removes the risk of recommending the wrong thing. It is also easier to price, easier to scope, and easier to sell to someone who has not yet decided to trust you.

The problem is that safety is borrowed from the client. Every decision the menu defers is a decision they now have to make with less information than you have. When it goes wrong, it went wrong on their choice, which protects the relationship in the short term and ends it in the medium term.

Recommending carries more risk and delivers more value, which is a fair description of expertise generally.

What it earns

Prescriptive relationships can create deeper trust because the client is not required to act as their own strategist.

They came for expertise. A menu asks them to supply the expertise themselves and pay for execution. A recommendation gives them what they actually came for, which is someone who has seen this before and will say what to do.

That is what working as a partner rather than a vendor means in practice. Listen first. Diagnose the real constraint. Recommend a path and explain why it comes first.