The Consulting Proposal Deliverable: What to Hand Over Before the Contract Is Signed

A consulting proposal deliverable is something of standalone value you give a prospective client before they have signed anything: a document, a model, an analysis, a number they did not have before. It is not the proposal. The proposal describes work you intend to do. A deliverable is a small piece of that work, already done, which the client keeps whether or not they hire you.

Almost nobody sends one. That is the opportunity.

A consulting proposal deliverable is not the proposal

Read three proposals for the same job and they will be close to indistinguishable. Same structure every time. Understanding of your requirements, proposed approach, phasing, team, timeline, commercials, references. The prose differs. The substance does not, because at proposal stage every firm is working from the same two or three conversations and the same public information.

So the client is being asked to choose between three descriptions of future work, written by people they barely know. They cannot evaluate the work, because none of it exists yet. What they can evaluate is price, brand, and how much they liked whoever was in the room.

That is a bad set of criteria for you if you are neither the cheapest nor the biggest name, which most consultants are not.

The way out is to stop competing on the description and start competing on evidence. Give them something that could only have been produced by someone who genuinely understood their business, and the comparison changes shape. Two documents about what might happen, and one piece of work that already did.

What actually counts as handing something over

Three tests. It has to be useful to them if they never hire you. It has to be specific to them rather than a template with their logo dropped in. And it has to have cost you something real, or they will read it as marketing, correctly.

The first test is the one people fail. A gap analysis concluding that the client has gaps and you are well placed to fill them is not a deliverable. It is an advert wearing a deliverable's clothes. If the document becomes worthless the moment they decline your proposal, you have not handed anything over.

Four things worth handing over

A picture of how the business actually runs. Not an org chart, which they already have, and not a flow diagram of a single process, which is too narrow to be interesting. A model of the departments, the systems, and the work moving between them. Most companies under a couple of hundred people have never seen themselves laid out that way, and the reaction in the room is remarkably consistent: somebody points at a connection and says that is wrong, and then somebody else explains why it is not.

A list of what is duplicated. Two CRMs. Customer data living in three places. The same report built twice by different teams who do not know about each other. This is cheap to produce once you have the picture, and it is always slightly embarrassing, which is why it lands.

The single points of failure, named. Not "there is key person risk in operations", which every business already knows and has decided to live with. Instead: if this person is away for two weeks, these four processes stop, and here is the reason. Naming it is uncomfortable. Uncomfortable is the point, because that is the part they will still be turning over on Thursday.

One first job, scoped, with a number on it. Not the whole engagement. The smallest piece of work that would produce a visible result, what it costs, and what it returns.

That is a great deal to produce before anyone has paid you, which is precisely why so few people do it, and also why it works when you do. Building the model has always been the part that made it impractical. abi. Clone for consultants gives you your own business plus five client maps free, with no card, so the picture, the duplicate systems and the single points of failure all fall out of one model rather than out of three weeks of unbilled evenings. Exports carry your firm's name and colours. Letting abi. interview the client's team is the paid part; building the map by hand is not.

The line between generosity and being used

There is a real risk here and it deserves saying plainly. Hand over enough and some prospects will thank you, take the document to their board, and either attempt the work themselves or pass it to somebody cheaper. It happens. Anyone claiming otherwise has not done this often enough.

The rule that keeps it manageable: hand over the diagnosis, hold the treatment.

Where the time goes, what is duplicated, what depends on one person, roughly what a fix is worth. Give all of that away. How you would rewire it, in what order, with which tools, and what to do when the third department objects in week two: that is the engagement, and it stays behind the signature.

A client who takes an accurate diagnosis and tries to self-treat quite often comes back. They come back having proved to themselves that the diagnosis was right, which is a better position than the one you started in. The prospects who take the document and disappear were mostly never going to buy. You have lost a few unbilled hours and found that out early rather than after the third meeting.

When not to do this

Two situations where handing something over is simply the wrong move.

If you are being brought in on a defined, technical, fixed-scope job, this is theatre. Someone who wants a Xero migration quoted does not want a model of their business, and a diagnostic deliverable in that context reads as an attempt to enlarge the engagement. It is usually being read correctly.

And if the client has already decided, send nothing. Late generosity looks like anxiety. When you are the preferred bidder and the conversation has moved on to start dates, a free analysis arriving unprompted makes people wonder what you know that they do not.

There is a third case, less clear cut. If you are the most expensive option by a wide margin, evidence can work against you, because a client who now understands their own problem in detail may decide it is smaller than your price. Worth knowing before you send. Although a client who reaches that conclusion in week eight of a paid engagement is a far more expensive problem than one who reaches it in the sales process.

What you are actually testing

Winning the deal is not the only thing going on here. A prospect who responds to an accurate map of their own business by arguing with it, correcting it, and dragging two more people in to look at it is a prospect who will engage with the work itself. A prospect who says thanks, very interesting, and never refers to it again has told you something useful at no charge.

That signal arrives before the contract rather than six weeks into it, which is the only point at which it is any use to you.