Mark Fennell All articles
Client Trust

The First Draft of Trust: Writing a Buyer's Problem Back to Them in Their Own Terms

Mark Fennell
The First Draft of Trust: Writing a Buyer's Problem Back to Them in Their Own Terms

Most consultants are hired to solve something. Fewer are hired because they first proved they could describe it. In the early stages of a UK engagement, the buyer is not yet weighing your methodology. They are checking whether you have heard the problem accurately enough to be trusted with it. A precise problem statement is therefore less a document than a demonstration: it shows that you can listen, select, and reflect back what matters without inflating it.

The moment before the remedy

Proposals often fail not because the solution is wrong but because the problem was never pinned down. A buyer reads a generic diagnosis and concludes that the consultant has a template. A buyer reads a specific diagnosis and concludes that the consultant has been paying attention. The difference is credibility, and it is established before the first slide is opened.

This matters more in 2026 than it once did. UK buyers can compare several credible firms within a week. Many of them have been through a project that promised transformation and delivered a report. They are not looking for enthusiasm. They are looking for evidence that someone can see the shape of the difficulty without immediately reaching for a remedy.

What vague language costs

Consider two descriptions a consultant might offer after a discovery meeting. The first: 'The organisation needs to improve its customer journey and build a more data-led culture.' The second: 'Enquiries from the website are logged in a shared inbox, but no one owns the first response. The average wait is three working days, and the sales team cannot tell which enquiries came from the autumn campaign. The result is that the marketing spend cannot be defended at the next board meeting.'

The first could apply to almost any business. The second could only apply to this one. Buyers notice that difference, even when they do not name it. Vague language does not merely sound weak; it transfers risk back to the buyer, who must now work out whether the consultant has understood anything at all.

A second example makes the point sharper. 'We need to streamline operations' is a sentence that invites a proposal full of boxes and arrows. 'Invoice approval takes eleven days across three inboxes because the finance manager is the only approver for spends over five thousand pounds' is a sentence that invites a conversation about delegation, thresholds, and cover during leave. One describes a mood. The other describes a mechanism.

A routine in three parts

The discipline can be reduced to three movements: capture, compress, confirm. None of them requires new software. All of them require restraint.

Capture the buyer's words

Before the meeting, prepare a single page divided into four columns: what the buyer says, what they avoid saying, who is affected, and what has already been tried. During the meeting, write down phrases rather than interpretations. If the buyer says 'it is a bit clunky', record 'clunky'. Do not upgrade it to 'inefficient' until you have checked. The original word carries evidence; your paraphrase carries assumption.

This is not a note-taking technique for its own sake. It is a way of preventing the consultant's vocabulary from replacing the buyer's reality. In a UK context, where understatement is common, the buyer's actual words often contain the most useful information. 'We are managing' may mean that a process is held together by one person. 'It is not urgent' may mean that the budget year has not yet turned.

Compress without thinning

After the meeting, draft one paragraph of no more than 120 words. It should contain four things: the observable symptom, the group or process affected, the constraint that makes the symptom persistent, and the consequence if nothing changes. Avoid adjectives that cannot be verified. Replace 'significant' with a number or a named effect. Replace 'poor communication' with the specific handover that fails.

The paragraph is not a summary of everything discussed. It is a test of whether you can identify the load-bearing detail. If the buyer reads it and says 'yes, that is it', you have earned the right to proceed. If the buyer reads it and says 'not quite', you have earned something almost as valuable: a correction before the proposal, rather than after the invoice.

Confirm before you build

Send the paragraph to the buyer before any proposal, with a short invitation: 'Have I described this accurately? If not, which part is wrong?' This does two things. It gives the buyer a chance to correct you cheaply, and it shows that you treat their understanding as the authority. A consultant who can be corrected early is easier to trust later.

The confirmation should not be a test of the buyer's memory. It should be a shared check of the written record. Keep it short, dated, and free of sales language. The aim is not to impress; the aim is to agree.

A pre-meeting checklist for solo consultants

Before the next discovery conversation, run through a short list. It takes five minutes and prevents a great deal of later drift.

The final question is the most useful. It invites the buyer to define the edge of the problem before you have drawn it. It also signals that you expect to be held to accuracy rather than enthusiasm.

Why this earns the next conversation

The commercial effect is indirect but reliable. A precise problem statement shortens the proposal because fewer assumptions need to be hedged. It sharpens the scope because the boundary of the problem is visible. It also lowers the buyer's risk: if you can describe the problem without exaggerating it, you are less likely to oversell the remedy. In a market where UK buyers can choose between several credible firms, accuracy is a form of modesty, and modesty is a form of credibility.

None of this requires a new methodology. It requires a discipline: resist the urge to solve until you have shown that you can see. The first draft of trust is often just a problem written back in the buyer's own terms, with care.

All Articles

Related Articles

The Payment Pathway: Agreeing Invoice Mechanics Before the First Workshop

The Payment Pathway: Agreeing Invoice Mechanics Before the First Workshop

The Empty Chair at the Next Review: Preserving a UK Account After a Sponsor Changes Role

The Empty Chair at the Next Review: Preserving a UK Account After a Sponsor Changes Role

The Halfway Conversation: A Scope Check That Keeps UK Engagements Honest

The Halfway Conversation: A Scope Check That Keeps UK Engagements Honest