Pre-Engagement Discovery: The Unpaid Three Weeks Nobody Bills For

Pre-engagement discovery is the work a consultant does to understand how a client actually operates before there is a signed contract to pay for it. Interviews, a walkthrough of their systems, a look at whatever process documentation exists. It happens in every engagement, it decides whether the proposal is any good, and almost nobody charges for it.

That last part is the problem. Not because consultants are bad at pricing, but because of where discovery sits in the sale. You cannot write a credible scope without it. The client will not pay for it until they believe the scope. So it gets absorbed, quietly, into business development, and the cost hides in a line nobody examines.

What the unpaid weeks actually consist of

Strip out the meetings that are really sales meetings and the shape is consistent.

You talk to the person who bought in, usually an owner or an ops lead, and get their version of how the business runs. That version is wrong in interesting ways. Then you talk to three or four people who do the work, and you get four incompatible accounts of the same process, all of which are true from where each person sits.

Someone sends you a process document. It describes a version of the workflow that existed when it was written, which was probably before the last two tool changes. Somebody mentions in passing that they stopped using the system it references about a year ago.

You build a picture from that. Usually in a spreadsheet or a slide, occasionally in a diagramming tool. It takes a fortnight or three weeks depending on how many people you can get in front of and how quickly they reply.

And then the engagement starts and you discover the thing you missed.

Why it is worse than it looks

The direct cost is the obvious part. Two or three weeks of senior time on an opportunity that might not close, repeated across however many prospects you are working at once.

The indirect cost is bigger and less visible.

Discovery is the least repeatable thing a consulting firm does. Everything downstream can be productised to some degree: the automation build, the reporting, the change management, the handover pack. But every discovery starts from nothing, and the quality of it depends almost entirely on which individual ran it. That means it does not scale, it cannot be delegated to a junior without a drop in accuracy, and none of the pattern recognition from the last engagement carries into the next one in any usable form.

It is also the part most likely to be wrong in a way that costs you money later. A scope built on an incomplete map produces a fixed-price engagement that runs over, or a time-and-materials engagement where the client feels ambushed by the revision. Either way you pay for it in margin or in the relationship.

And there is the conversion problem. A prospect who has sat through three weeks of your questions and received a document at the end has been given a lot of your time and very little they can look at. Discovery output is usually text. Text does not sell.

The thing clients cannot see

Here is what makes discovery hard to charge for and easy to undervalue at the same time.

The client already believes they know how their business works. They have an org chart. They have a CRM. They have the version of the process that they described to you in the first meeting, and they described it with total confidence.

What they do not have is the view from outside. Nobody in a twenty-person company has ever seen the whole thing at once, because everybody's view is the view from their own desk. The finance person knows the invoicing runs late and assumes it is sales being slow with paperwork. Sales knows they send paperwork immediately and assumes finance is understaffed. Both are describing a handoff neither of them can see the whole of.

When you show them that handoff, drawn out, with the steps and the delay in it, the conversation changes. It stops being your opinion versus their assumption. It becomes a picture on a screen that everybody in the room can argue with, which is a far better position to be selling from.

The trouble is that producing that picture is precisely the expensive bit.

Shortening it without cheapening it

There is no version of this where discovery disappears. Anyone selling you that is selling you a worse engagement. But the three weeks can become a shorter number, and the output can become something more useful than a document, if you change what you are building rather than how fast you build it.

Build a model instead of a report. A structure that holds departments, roles, systems and the processes running between them can be filled in progressively, corrected in front of the client, and reused when the engagement starts. A report gets read once and filed.

Start it before the interviews rather than after. Most of the first pass is public or obvious: the departments a company of that size and sector has, the systems they almost certainly run, the standard shape of quote to cash. Put that in first as a hypothesis. Then the interviews become corrections rather than blank-page questions, which is a much faster conversation and a much better one. People are far better at telling you what is wrong with a picture than at describing a process from memory.

Make the artefact presentable. If what you produce can be put on a screen in front of the client's leadership team, discovery stops being a cost centre and becomes the pitch. This is where abi. Clone for consultants sits: it builds a working model of how a business operates, tools shown with their real logos, and you can rotate it and isolate a function while the client watches. Consultants get their own business plus five client maps free, no card. Building, editing and presenting the map costs nothing. Letting abi. interview a client's team is the paid part, because that is the part with a real cost per use.

Separate what is evidence from what is assumption. Any map you build in the first week is mostly the second. Marking which is which protects you when you quote, and it makes the coverage gaps into an argument for the next conversation rather than a hole you hope nobody notices.

The honest counterargument

A faster map is not always a better one, and speed is genuinely a risk here.

Three weeks of talking to people has a side effect that nothing replaces: you meet the people. You find out who is difficult, who is quietly running things, who will sink the project six months in because they were not consulted. None of that is in a process map, and a consultant who moves straight from a structured model to a proposal without spending real hours with the client's team is going to be surprised by something.

There are also engagements where the discovery is the value. Genuine strategic work, contested reorganisations, anything where the political read matters more than the process read. Do not compress those. Charge for them properly and take the time.

What is worth compressing is the part that is pure information gathering. Which systems, which steps, who does what, where the time goes. That work is necessary and it is not where your judgement lives, and it is the reason discovery costs so much.

The number worth knowing

Most consulting firms cannot say what pre-engagement discovery costs them, because the hours go into business development and never get split out. Before changing anything about how you do it, work out your own figure. Take the last five proposals, count the hours spent before signature, multiply by your rate, and divide by the number that closed.

The cost per won engagement is usually larger than people expect. It is also the clearest argument for doing this differently, and it is one you can only make with your own numbers rather than anybody else's.