Diagnosis before the prescription

Most commercial consultancies show up with the solution already under their arm. They arrive with a method already built, a methodology with an English name, a two-day workshop, and they apply it almost without asking what’s actually wrong with the team in front of them. It isn’t bad faith. It’s the business model: selling the method is easier than selling the time it takes to look before prescribing.

The problem is that almost no two commercial teams fail for the same reason. One loses deals because it doesn’t qualify in time. Another loses them because the internal approval process takes so long the client goes cold. A third has salespeople who know how to sell but a CRM nobody uses, so there’s no data to steer anything with. Applying the same method to all three is like prescribing the same medicine without asking what hurts.

Diagnosing before prescribing isn’t a courtesy step. It’s the work. It means sitting with the team, reviewing the real pipeline and not the one shown in the meeting, listening for where conversations stall, and naming precisely which part has come off its axis. Only after that does it make sense to decide whether what’s missing is method, process discipline, or simply someone requiring again that what people already know how to do actually gets done.

That asks something uncomfortable of a consultant: admitting you don’t have the answer yet when you walk into the first meeting. The temptation is to show authority from minute one. But real authority isn’t arriving with the prescription ready. It’s opening the mechanism, looking closely, and saying honestly what’s needed, even when the answer is simpler or slower than the client expected.

A proper diagnosis costs time before it produces revenue. That’s why almost nobody does it well. But it’s the only way what gets built afterward outlasts the first month’s enthusiasm.