The diagnosis is the deliverable: how the first conversation should go

Most first calls are pitches with a discovery wrapper. Ours are not. The first call is a diagnosis, and the diagnosis itself is the deliverable. If we are not the right team afterwards, the customer keeps it.

Six themes that earn the right

A useful first call moves through six themes in order. Skip one and the recommendation lands without foundation.

• The current setup: where work starts and stops
• ICP and target accounts: who we are trying to reach
• The system of record: how clean is the foundation
• What they want to automate: where is the friction now
• Content and value-add: what does the team have to point at
• Measurement and appetite: how will we know it worked

Listen for what is not said

The most useful answers come back as silence. Nobody owns CRM hygiene. Last quarter's win cannot be repeated. Three tools were tried and quietly abandoned.

Those gaps tell you where the engine is leaking. They do not show up on a discovery deck.

The diagnosis itself is the deliverable

By the end of the conversation we should have enough to write a one-page diagnosis: what is broken, what is leveraged, where to start.

If we are the team that runs the build, the diagnosis becomes the design brief. If we are not, the customer keeps the diagnosis. Either way they are further on than they were before the call.

What a one-page diagnosis actually looks like

At the top: where they are in the engine, named. Foundation, Connected, Augmented, Intelligent, or Agentic. Honest. Not flattering. Below that: three things that are working, three things that are not, and three things that are missing entirely. Each with one specific example.

At the bottom: where to start, why, and what the first 30 days of work would do. No prices. No scope. The deliverable is the read of the situation, not the proposal.

The three things that signal a misalignment

First, the team and the leader give different answers to the same question about pipeline health. Marketing says it is fine. Sales says it is empty. Both are looking at different reports.

Second, the goal stated in the call does not match the constraint discussed an hour later. 'We need 3x pipeline' meets 'we have three SDRs and a £2K marketing budget per month'. One of those is fiction.

Third, the team has tried automation before and the leader does not know how it ended. That is a tell. The tools are still in the stack. Nobody is looking at them. We are about to be the next one in the graveyard unless we name the pattern.

Why we don't pitch on the first call

A pitch on the first call is a pitch from ignorance. We have not yet seen the engine. We do not know the team. We have nothing to recommend that is not generic.

The promise we hold is the diagnosis. If we are the right team, the diagnosis becomes the design brief and the customer pays for the build. If we are not, the customer keeps the diagnosis and finds whoever fits. Either way they end the conversation with something useful.

A diagnosis is more useful than a proposal. Earn the right to make one.