The Second Signature: Why Delivery Should Read the Proposal Before the Client Does

Every firm has a version of this scene. A proposal has been drafted late, polished by a partner and is ready to go. It describes a cadence of meetings, a named team, a set of deliverables and a fee. The client reads it as a statement of intent. Six weeks later, the delivery lead opens the file for the first time and begins to calculate what the document actually requires.

The gap between the promise and the plan is rarely a matter of bad faith. It is a matter of sequence. The people who write the proposal are usually closest to the relationship, the opportunity and the pressure to win. The people who will run the engagement are usually closest to capacity, dependency and the practical cost of keeping the promise. Bringing the second group in after the work has been won is an expensive way to discover a mismatch.

Two authors, one document

Proposals are written by optimists by necessity. A partner or business developer is trying to show the client what the firm can do. The language naturally leans towards the possible: senior oversight throughout, a responsive team, a flexible approach, regular engagement. These are not lies. They are ambitions expressed in the grammar of commitments.

Delivery leads are realists by necessity. They know which senior colleague is already committed three days a week, which client contact will need more support than the fee allows, and which deliverable always takes longer than the template suggests. Their judgement is not more virtuous than the seller's. It is simply made from a different vantage point.

The conflict is structural, not personal. That is why it cannot be solved by asking people to be more careful. It needs a step in the process.

A veto, not another committee

The remedy is not a review board. A committee would slow the proposal, blur accountability and produce a document that reflects everyone's caution and no one's judgement. The proposal would arrive later and say less.

A delivery veto is narrower. Before a proposal leaves the building, one named person who will be accountable for the work reads it and has the standing to say: not as written. That person is not there to rewrite the sales case or to second-guess the fee. They are there to test whether the firm can keep the promise at the price and pace proposed, with the people named and the capacity available.

The veto should be time-boxed and recorded. A 48-hour window is usually enough for a document of this length. If the reviewer raises no objection, the proposal proceeds and the review is noted. If they do object, the objection must be resolved in one of four ways: amend the proposal, amend the resourcing, amend the price, or decline the opportunity. Those are the only honest outcomes.

This is not a legal or risk sign-off. Those remain separate and should not be conflated with a commercial judgement about deliverability. Nor is it a post-mortem. It happens while the proposal is still a draft and while the client has not yet been given a reason to expect something the firm cannot provide.

The one-page test

A useful delivery review fits on a single page. The reviewer should be asked to complete six fields, not to write an essay.

1. Named delivery lead and first-90-day capacity. Who will run this, and how many hours do they realistically have in the first three months? Not the team as a whole. The accountable individual.

2. Three assumptions the price depends on. What must be true for the fee to work? Client availability, data quality, decision speed, access to a particular person, a stable scope. If an assumption fails, what happens to the margin?

3. The sentences we would struggle to honour. Ask the reviewer to underline the phrases they would not want to defend at a monthly review. Common examples include ongoing support, senior oversight throughout, flexible scope and a named individual who is not actually available at the volume implied.

4. What is explicitly out of scope. A proposal that lists only what is included invites the client to assume everything else is included too. The review should confirm that the boundary is written down, not merely understood.

5. Margin at risk and the change trigger. What is the estimated effort against the fee, and at what point would the firm need to renegotiate? The trigger should be a fact the delivery lead can observe, not a vague feeling that the work has grown.

6. The first thirty days. Who does what, what the client must provide, and what the firm will do if the client is late. A proposal that is silent on mobilisation tends to become a proposal that is renegotiated at mobilisation.

Reading the words we would struggle to honour

The third field is often the most revealing. Proposals accumulate language that sounds reassuring in a pitch and burdensome in a delivery plan. A phrase such as ongoing support may mean a monthly call to the client and a weekly call to the delivery lead. Senior oversight throughout may mean a partner attends every steering meeting, or it may mean the partner reads the minutes. The difference matters to the client and to the economics of the work.

The reviewer's task is not to remove every ambitious phrase. It is to make each one either defined, priced or deleted. A defined promise is a commitment the firm can plan for. A priced promise is one the client has chosen to buy. A deleted promise is one the firm has decided not to make. All three are preferable to an undefined phrase that both sides interpret differently.

What the test changes

It changes the question from can we win this to can we run this. That shift is healthy for business developers as well as delivery leads. A seller who can say the delivery team has reviewed this and is comfortable has a stronger proposal than one who is simply optimistic. A seller who is asked to amend a promise before sending it has a defensible reason to do so, rather than appearing to withdraw an offer under pressure.

The test also improves the quality of the firm's pricing conversations. When the delivery lead identifies an assumption that is doing a lot of work, the firm can choose to price the risk, qualify the assumption in the proposal or walk away. Each of those choices is better made before the client has signed than after.

Keeping the veto honest

Any review step can become a rubber stamp. The usual causes are familiar: the reviewer is too senior to read the detail, the window is too short to allow a real objection, or the firm treats a veto as a career risk rather than a commercial control.

Three habits help. First, rotate the reviewer across engagements so that the role does not become one person's private fiefdom. Second, record the outcome of every review, including the amendments accepted and the assumptions qualified. Third, review the pattern every quarter: are proposals being amended in the same places, and is the firm winning work it later struggles to deliver?

A delivery veto is not a brake on growth. It is a check that the growth is real. The proposal is a contract in prose, even before it is signed. The person who must keep it should read it while there is still time to change it.

The client's side of the signature

Clients rarely see the internal review, but they experience its absence. They see the partner who promised senior involvement and then disappears, the team that was named and then substituted, the scope that was described as fixed and then reopened. Each of those moments damages trust more than a carefully qualified proposal ever would.

The second signature is therefore not an administrative nicety. It is a client-protection measure disguised as an internal control. The firm that lets delivery read the pitch before the client does is not being cautious. It is being consistent, and consistency is what clients remember when the work becomes difficult.