From Client Conversation to Approved Proposal — and What Happens Next

Most consulting firms do not have a proposal-writing problem. They have a context-transfer problem.

The firms we speak to are staffed with people who write well. Given a clear brief, a manager can produce a strong proposal. The difficulty is that a clear brief rarely exists. What exists is a conversation that happened in someone's head, a set of documents in different systems, and a chain of handoffs where a little more of the original meaning is lost at each step.

This article walks that chain and marks where context leaks out.

The client conversation

The engagement effectively begins here. In sixty minutes a client describes their objectives, and — more importantly — everything around those objectives: which previous attempt failed and why, which internal function will resist, which capability they already have and do not want questioned, what the real deadline is behind the stated one, which budget line this will come from.

Some of this is stated. Much of it is implied. And some of the most consequential material is a commitment made in passing by whoever ran the meeting: we could probably include a diagnostic phase, we've done this in your sector, we can start before the summer.

What survives the meeting is a fraction of what happened in it. The notes capture objectives. They rarely capture nuance, constraints, or implicit commitments — the things that later determine whether the proposal is credible.

The proposal handoff

Now someone who was not in the conversation must write the proposal.

They begin by reconstructing. They read the notes, ask the partner questions, search for a comparable prior proposal, and infer the rest. Every inference is a small bet. Some are correct. Some are wrong in ways that will not surface until review, or worse, until the client reads it and recognises that the firm did not quite hear them.

This is the most expensive handoff in the commercial workflow, and it is almost always conducted informally. The context that determines proposal quality is transferred by memory and conversation, from the person with the least available time.

The review bottleneck

The partner then reviews the draft. But they are not only reviewing the proposal — they are reviewing the underlying interpretation. Two questions are being answered at once: is this document good? and did the team actually understand the client?

The second question is the slow one. Answering it means re-deriving the original context and comparing it against what the team inferred. That is why proposal review consumes so much senior time: the reviewer is reconstructing the same context the writer had to reconstruct, in order to check the reconstruction. This is also why packaging context with the review does more for cycle time than shortening the document.

The approval gap

Then the proposal is approved. Ask what that means concretely and the answer is usually unsatisfying.

Approval typically refers to a file, an email, or a moment — the version I looked at Thursday, the one attached to that thread, Marc said yes on the call. It rarely refers to an exact, identifiable artifact whose contents are governed and whose subsequent changes are tracked.

The gap shows up later. Someone edits the scope section after approval to fix a typo and adjusts a deliverable while they are in there. A pricing assumption is updated. The version sent to the client is not quite the version that was approved, and nobody can say precisely where they diverged. In a business whose product is a promise, that is a real exposure.

What happens after the proposal

The proposal is signed and the context resets again.

Someone writes the SOW, largely reproducing the approved scope in different words. Someone builds the project plan, re-deriving the phasing from the proposal narrative. The delivery team assembles kickoff materials, restating the objectives and approach that were already articulated twice. Each of these documents is a manual re-expression of decisions already made, and each introduces the possibility of drift between what was sold and what is delivered.

When the scope changes mid-engagement — as it does — the divergence compounds, because the proposal, the SOW and the plan are now three unconnected files that no longer agree.

A connected workflow

The alternative is not a better template. It is treating the commercial workflow as one connected chain in which context and artifacts persist:

Conversation → Validated context → Engagement architecture → Proposal artifact → Exact approval → Connected deliverables

Each link is load-bearing:

• Validated context means the interpretation of the client conversation is captured, explicit and confirmed by someone who was there — not reconstructed by inference.
• Engagement architecture means scope, phasing and approach are structured decisions with owners, not prose to be re-derived later.
• Proposal artifact means a persistent object with a status, a version history and traceable sources — not a file that multiplies across drives and inboxes.
• Exact approval means approval attaches to a specific version, and changes after that point are visible as changes.
• Connected deliverables means the SOW, plan and delivery materials draw on the approved artifact rather than restating it from memory.

Nothing in that chain removes judgement. It removes reconstruction — and reconstruction is where both the time and the errors are.

Where to begin

The long-term opportunity is a connected consulting lifecycle: one chain where the reasoning that won the work carries into what the firm delivers. That is a large ambition and a poor place to start.

The practical place to begin is the proposal. It is where senior attention is already concentrated, where context loss is most visible, and where the cost of a bad handoff is easiest to see. Get the proposal workflow connected — context preserved, artifacts persistent, approval exact — and the downstream links become extensions of something that already works rather than a second transformation. It is also the honest answer to the observation that a strong AI draft is not a proposal workflow.

Solon is currently in beta; firms with an active proposal can request beta access.

Explore the proposal workflow.