Help your champion explain the decision without you

The seller leaves the call feeling understood. Later, the champion opens a document in front of colleagues who were not there.

They have different questions. What would change? Who would do the work? What happens if the team waits? Which assumptions produced the promised return?

This is an illustrative scene, not a reported customer meeting. A LinkedIn post by Joe Milnes discusses the difficulty of carrying a business justification into those later conversations. It offers professional advice about a concise business case; it does not prove that a particular document causes deals to close.

Ask the champion what decision their colleagues are being asked to make. Draft that decision in their terms, then give them a note they can correct. Include the unresolved questions they would otherwise have to answer alone in the room.

Begin with the decision they need to make

Suppose a fictional operations team is considering an integration review. A seller’s opening might describe the consultancy’s expertise. The buyer’s opening needs to explain the decision: whether to spend time evaluating how two systems exchange information before committing to a larger change.

That difference affects the whole page. A review is not the same commitment as a replacement project. The note should say what is being approved now and what remains outside the decision.

Ask the champion who will read it and what those people need to understand. A finance reviewer, an engineering lead and a manager responsible for adoption may require different supporting material. A short main note can link to details without pretending every decision fits on one page.

Draft a note that invites correction

Here is an illustrative outline for that integration-review decision. Replace every assumption with the buyer’s actual information before using it.

Decision requested: Approve a bounded review of the existing exchange between the two systems. The review would inform a later decision about whether any change is justified.

Current situation: The team reports recurring exceptions that require investigation. Their frequency and causes still need to be established.

Options: Continue with the current process, investigate internally or commission a defined external review. Describe the effort and constraints of each option fairly.

Why consider it now: Use the buyer’s real timing condition. If none has been established, record that instead of inventing a deadline.

Resources and responsibilities: State the proposed fee or cost basis only when it is real. Include the customer time, access and review work required alongside the supplier’s work.

Risks and open questions: Identify access restrictions, uncertain scope and anything the buyer still needs to verify.

Next decision: Agree what the review must produce and who will evaluate its findings.

There is no return-on-investment figure in this outline because the example supplies no evidence for one. If the buyer needs a financial comparison, the next task is to find the inputs with them. Formatting a spreadsheet will not supply the missing facts.

Let the buyer supply the business assumptions

If the team wants a financial comparison, ask which inputs it can support: current effort, the cost basis it uses internally, the amount of change it considers plausible and the work required to adopt the proposal.

Label estimates as estimates. Show uncertainty and avoid assuming every saved minute becomes a cash saving. A person freed from a task may do other useful work; whether that changes a budget is a separate question for the buyer.

Do not present a seller’s model as a customer-verified business case. Keep the source and owner beside each material assumption so the internal reviewer can ask the right person.

The same applies to urgency. If the champion cannot explain why this should take priority, adding a dramatic cost-of-inaction paragraph will not establish it.

Rehearse the questions the document cannot answer

Ask the champion to explain the proposal using their own words. Listen for places where the note forces them to guess, exaggerate or defend an unfamiliar claim.

Correct those gaps. If they cannot answer who will implement the work, arrange that conversation. If the alternatives are unclear, improve the comparison. If there is no agreement on the problem, return to discovery rather than polishing the justification.

A proposal-readiness check can help distinguish a useful scoping note from a document asking for a decision the buyer is not ready to make.

RevQ describes preparing proposals from business context and conversations. When assessing that workflow, check whether the resulting draft preserves the buyer’s assumptions and unanswered questions. A polished page should not put a stronger claim into the champion’s hands than they can support.

Before the champion takes the note into the room, ask which sentence they would find hardest to defend. Check that sentence together. The answer may send you back to discovery, or simply to the person who owns a missing assumption.

About this article: AI-assisted writing and editing, informed by the linked public discussion. Illustrative examples are labelled; they are not customer case studies. Read our editorial approach.

Updated October 3, 2026