Consulting Practices and the Key Areas of Engagement

Most organisations buy consulting badly. Not because consultants deceive them, though some do, but because the buyer rarely knows what category of help they are purchasing. A managing director who would never sign a construction contract without knowing whether he is buying design, supervision, or turnkey delivery will happily sign a consulting agreement that specifies none of these distinctions.

This post sets out the categories plainly. It reflects how we structure our own practice, but the taxonomy is general, and any organisation negotiating with any firm can use it.

The four engagements that actually exist

Strip away the branding and consulting engagements reduce to four types.

Diagnostic work. Someone examines your organisation, your programme, or your market, and tells you what is true. Baseline studies, process audits, feasibility assessments, organisational reviews. The output is knowledge, and the test of quality is whether the findings survive contact with people who know the ground. A diagnostic that only confirms what the commissioning officer already believed was either unnecessary or dishonest.

Design work. Someone converts an intent into an implementable architecture: a restructuring plan, a monitoring framework, a digital transformation roadmap, a market entry strategy. Design is where most consulting money is spent and where most disappointment originates, because a design is only as good as the implementation assumptions beneath it. Ask any designer one question: who, by name or by post, will run this after you leave?

Implementation support. The consultant stays for the doing. Project management units embedded in government departments are the most visible Indian form, and they exist for a reason: the gap between a sanctioned scheme and a functioning one is where public money quietly dies. This work is unglamorous and long. It is also, in our experience, where consulting earns its keep most defensibly, because the results are observable and dated.

Advisory retainers. Standing access to judgement. A board that wants a sceptical outsider before major decisions, a promoter navigating succession, a secretary who wants policy options stress-tested before they reach the minister. Retainers are valuable when the adviser is genuinely independent and worthless when the adviser has learned what the client likes to hear. Rotate them.

Where the lines blur, and why buyers should care

Firms prefer engagements that begin as diagnostics and mature into multi-year implementation contracts. Sometimes that progression is right; the diagnostic surfaces work that genuinely needs doing. Sometimes it is a business model wearing the costume of a finding. The defence is structural, not moral. Separate the purchase decisions. Let the diagnostic conclude, sit with it for a month, and then decide, competitively if possible, who implements.

Indian buyers face a further complication: procurement rules built for goods. A quality-and-cost-based selection that weights cost at seventy percent will reliably deliver the firm that staffed the bid with names and will staff the project with juniors. Appraisal committees know this. The fix is within their power, and it consists of weighting demonstrated prior delivery, insisting on named key personnel with penalties for substitution, and interviewing the actual team leader before award. Twenty minutes of conversation reveals more than forty pages of firm credentials.

For family-run mid-market firms, the difficulty runs the other way. There is no procurement cell, no appraisal committee, and the decision rests on trust. Trust is a fine basis for choosing an adviser and a poor basis for scoping one. Even a two-page engagement letter that states the type of work, the deliverable, the timeline, and what the consultant will not do prevents most of the disputes we have seen.

A short word on scope

Every failed engagement we have been asked to review shared one feature: the scope document could have described five different projects. "Support the organisation in strengthening its systems" is not a scope. It is an invitation to mutual disappointment. Good scope is falsifiable. By March, the inventory system reconciles daily; by June, the district dashboards report without manual collation. If a sentence in the scope cannot fail, delete it.

Organisations that internalise these distinctions negotiate better, pay less, and get more. The consulting industry will not teach them, because ambiguity is profitable. Buyers must teach themselves, and the lesson fits on one page: know which of the four things you are buying, contract for that thing, and measure delivery against it.

If you are scoping an engagement and want a second pair of eyes on the terms before you sign, our team reviews such documents as a matter of course. Details are at /services.