Flint Ross All articles
Client Relationships

After the Report Is Filed: A Ninety-Day Test of Whether Advice Travelled

Flint Ross
After the Report Is Filed: A Ninety-Day Test of Whether Advice Travelled

Photo: Internet Archive Book Images, No restrictions, via Wikimedia Commons

Clients are usually pleased with advice at the moment it is delivered. The report is clear, the partner was responsive, the workshop was well run. What the post-engagement review rarely establishes is whether anything changed afterwards — and in a professional firm, that is the only claim ultimately worth making.

The gap between delivery and effect is not a failure of the client. It is a gap in the firm's evidence. Most satisfaction instruments are built to measure the experience of the engagement, because that is what the firm controls. Implementation sits outside the engagement, in a business the firm does not run, subject to budget cycles, leadership changes and the ordinary friction of operating a company.

Why the survey cannot carry this weight

A post-engagement questionnaire measures sentiment at a single point, normally within a fortnight of the invoice. At that moment the client has read the executive summary and not yet attempted anything. Delight is cheap and, in a professional setting, socially produced: the person answering is usually the person who commissioned the work.

There is also the question of who asks. A partner enquiring whether their own recommendations were adopted is conducting a relationship conversation, not an evaluation. The answers will be warm and largely unusable.

Designing the audit

A ninety-day implementation audit is a short written return, followed by a conversation of thirty to forty minutes, run against a fixed template and recorded in the client's own words. It is not a survey and it should not become a sales call, although it will reliably generate one or two.

Ninety days is the useful interval. At thirty days there is little movement to observe; at six months the participants have forgotten why a decision was deferred and will reconstruct a tidier account. One full quarter captures the first budget round, the first executive meeting and the first occasion on which a recommendation met an obstacle.

Run it across a deliberate sample rather than the whole client base: eight to twelve engagements a year, weighted towards work where implementation was plausible, with at least a few where the firm suspects nothing happened. A sample of the willing proves little.

Three columns: taken, dropped, deferred

For each recommendation in the original report, place the item in one of three columns.

Taken — what was decided, in which forum, on what date. A decision is not the same as an intention, and the distinction is the whole point of the exercise. A board resolution, a budget line, a signed supplier contract, a changed delegation of authority: these are decisions. 'They seemed keen' is not.

Dropped — abandoned, with the reason attached. The reason matters more than the count.

Deferred — still live, with a date at which it will be reconsidered, and a named owner. A deferral without a date is a drop wearing better clothes.

The reasons tend to fall into a small number of categories, and each is a finding about the advice rather than merely about the client: cost, internal capacity, disagreement with the analysis, a competing priority, a change of circumstances, or the departure of the executive who owned the work. A firm that discovers its recommendations are routinely dropped for capacity reasons has learned something about the feasibility of its own counsel, not about its clients' discipline.

Contribution, not credit

Attribution is where professional firms most often overreach. Markets move, management teams change, and a client's results are rarely traceable to a single piece of advice. The safe construction is temporal rather than causal: following the review, the client did X, on this date, in these terms.

Resist 'as a result of our report'. Prefer 'the board took the decision in the quarter after the review'. It is less impressive and considerably more durable.

Two categories of finding are especially valuable and usually ignored. The first is adaptation: the client implemented something recognisably derived from the recommendation but materially altered. The record should show the alteration, because it is evidence of what actually works in that business. The second is productive disagreement: the client rejected the recommendation, proceeded differently, and was proved right. That belongs in the file and should reach the next client's proposal.

What the findings are for

The audit has three uses. It sharpens the next proposal, because the assumptions that failed are now visible. It exposes patterns across a portfolio that no single engagement can show. And it supplies evidence for panel reviews and tenders that survives contact with a procurement team, because it is dated, specific and attributable to the client rather than to the firm's own marketing.

Publish the aggregate internally, including the parts that are unflattering. A firm that circulates only the successes has built a reporting exercise, not an audit, and the partners will know it.

The discipline of asking

The objections are predictable. It invites a conversation about fees. It may surface that the advice was wrong. It creates work for a client who has already paid. It may generate a follow-on request the firm has no capacity to serve.

All of these are better known than unknown. The fee conversation is happening anyway, and better at ninety days than at renewal. Advice that was wrong is worth discovering while the relationship can still absorb it. And the follow-on request is a client saying, in the plainest available language, that the work mattered.

A firm that cannot describe what happened after its report was delivered is relying on the client's courtesy for its reputation. A ninety-day audit replaces courtesy with evidence, which is a better foundation for both the relationship and the next proposal.

All Articles

Related Articles

The Courtesy of Clarity: Pricing Counsel Given Before Engagement

After the Letter Lands: A Diagnostic Debrief for Departing Clients

After the Letter Lands: A Diagnostic Debrief for Departing Clients

The Curriculum of First Contact: Auditing What Ninety Days Teach a New Client

The Curriculum of First Contact: Auditing What Ninety Days Teach a New Client