Reading Between the Lines: What a Consulting Proposal Isn't Telling You

There is a particular kind of document that arrives in the inboxes of UK managing directors every week: the consulting proposal. Glossy, well-structured, often beautifully typeset. It promises a transformation, lists a method with an acronym, and closes with a fee that has been calculated to the nearest pound. It is, in every sense, a sales document.

And that is precisely the problem. A proposal written to win work is fundamentally different from a document written to describe the work. The gap between the two is where most consulting disappointment is born.

The Missing Section

Ask a consultant what could go wrong on an engagement and they will usually give you a thoughtful, candid answer — over coffee, verbally, off the record. Ask them to put it in the proposal and the answer shrinks dramatically. Risks become 'potential dependencies'. Assumptions become 'a collaborative client environment'. Exclusions vanish entirely.

This is not necessarily dishonesty. It is incentives. The consultant knows that the firm down the road, submitting the same day, will look more confident on paper. Candour reads as weakness in a competitive tender. So everyone writes the brochure, and everyone signs it, and everyone discovers in month three that the assumptions mattered after all.

The result is familiar to anyone who has commissioned advisory work: the data wasn't available, the key stakeholder was on leave, the scope grew, the timeline slipped — and each surprise arrives with an accompanying variation order.

What a Honest Proposal Looks Like

The best proposals I have seen read more like a risk disclosure from an investment prospectus than a marketing brochure. They state, plainly:

• Assumptions. What the consultant is taking as given — access to systems, availability of staff, quality of existing data. If these don't hold, what happens?
• Exclusions. What is explicitly not included. Implementation? Change management? Training internal teams? If it isn't listed, don't assume it's covered.
• Dependencies. What the client must supply, and by when. Delays here are the single most common cause of blown timelines.
• Success criteria. Not vague aspirations, but measurable outcomes both parties agree define the work as complete.
• What happens if it isn't working. The exit provisions, the review points, the mechanism for an honest mid-course conversation.

None of this diminishes a strong consultant. Quite the opposite: a professional who will put their assumptions in writing is signalling confidence, not fragility.

A Buyer's Checklist

Before signing, UK clients would do well to run a simple test. Read the proposal and ask, for every confident claim: what would have to be true for this to work? Then check whether those conditions appear anywhere in the document. If they don't, ask for them to be added.

Three questions are particularly revealing. First: what would cause you to recommend stopping this project? A consultant without an answer hasn't thought hard enough. Second: what are you assuming about our organisation that I haven't told you? Third: which parts of this fee are fixed, and which could grow, and under what circumstances?

The responses — or the evasions — will tell you more about the engagement to come than any case study or testimonial ever could.

Candour as a Competitive Signal

There is a wider point here for the UK consulting market. Buyers have become steadily more sophisticated; procurement teams at mid-sized firms have seen enough engagements to recognise boilerplate when they read it. The consultants who stand out are increasingly those willing to look less polished and more truthful.

A proposal that opens by naming the three ways this project could fail, and how each would be managed, does something no amount of branding can: it earns trust before the first invoice. In a market where credibility is the entire product, that is not a weakness in the document. It is the strongest thing in it.