Complex deals require multiple closing documents that have to work together coherently. The proposal articulates fit and solution. The mutual action plan structures the evaluation and creates shared accountability. The business case gives the economic buyer the financial justification they need to approve. When these three documents are built separately, at different stages, by potentially different people, they often contradict each other in subtle ways: different numbers, different framings, different language for the same concepts.
A full deal package approach builds all three from the same discovery data, in the same voice, with consistent framing. The champion gets one coherent story rather than three separately produced documents. The economic buyer can read the business case knowing it connects directly to the proposal they've already seen. The evaluation team can track their progress against the MAP knowing it reflects the timeline discussed in the proposal. Coherence across the closing package is one of the clearest signals of a professional, organized seller.
When to Generate the Full Deal Package#
The deal package should be generated after thorough discovery and before the formal closing phase begins. Specifically: after you've identified the champion and the economic buyer, documented success criteria from the prospect's perspective, understood the evaluation process and timeline, identified and addressed the major competitive alternatives, and confirmed that the deal is real (budget exists, the problem is high enough priority, and there's a genuine intent to decide). Building a full deal package before these conditions are met produces generic documents rather than genuinely tailored ones.
The temptation is to generate the package early to move the deal forward. Resist it. A proposal sent before the prospect fully understands the problem and sees your product as a genuine solution gets filed away without creating action. A proposal sent at the right moment, when the prospect has seen a demo, done their evaluation, and is ready to make a decision, creates the forward momentum it's designed to produce.
The Three Documents and Their Distinct Roles#
The proposal: a mirror of discovery#
The best proposals read like a sophisticated summary of everything the seller learned in discovery, organized into a decision-enabling format. The "Understanding of Your Situation" section should use the prospect's own language, reference the specific metrics they mentioned, and accurately reflect the priorities they expressed. If a prospect reads this section and thinks "yes, that's exactly right," the proposal is doing its job. If they read it and think "close, but not quite," you've either missed something in discovery or failed to capture it accurately in the document.
The proposal's job is not to sell the product, the demo did that. The proposal's job is to make the case that your product solves this prospect's specific problem in a way that's worth the investment they're about to make. The evidence for that case comes entirely from what you learned in discovery.
The mutual action plan: accountability infrastructure#
The MAP in a full deal package should reflect the actual evaluation steps the prospect has committed to, not an idealized timeline from the seller's perspective. If the IT security review typically takes three weeks at this company, the MAP should show three weeks for the IT security review. If the CFO needs two weeks of lead time to review new vendor commitments, the MAP should include a CFO review milestone two weeks before the proposed decision date.
A MAP that's coherent with the proposal creates a powerful effect: the prospect can see exactly how the timeline in the MAP leads to the solution described in the proposal within the timeframe that serves their business goals. The two documents reinforce each other.
The business case: the economic buyer's document#
While the proposal and MAP are primarily for the champion and evaluation team, the business case is specifically designed for the economic buyer who may not have been in every evaluation conversation. It needs to stand alone, readable without reference to other documents, and make the financial case clearly and specifically using the prospect's own numbers wherever possible.
The business case includes the current-state cost of the problem (calculated from what the prospect told you in discovery), the expected improvement from your solution (conservative, base, and optimistic scenarios), the investment required (your pricing, plus realistic implementation and change management costs), and the ROI calculation expressed in terms the economic buyer cares about: payback period, three-year return, and the cost of doing nothing for another year.
Building a coherent three-document deal package from discovery notes is a significant preparation investment.
River's Sales workspace generates the complete deal package, proposal, MAP, and business case, from your discovery notes and deal context, ensuring all three documents are coherent and mutually reinforcing.
Generate My Full Deal PackageHow to Introduce the Package to Your Champion#
How you introduce the deal package matters as much as the quality of the documents themselves. Don't email three documents and hope the champion knows what to do with them. Schedule a working session: "I've put together a full proposal, a mutual action plan, and a business case. I'd like to walk you through all three and make sure they accurately reflect our conversations before you take them internal. Can we schedule 45 minutes?"
In that session, cover the proposal first (confirm the "Understanding of Your Situation" section is accurate and complete), then the MAP (confirm the milestones and timeline are realistic given their internal process), then the business case (confirm the numbers and assumptions are defensible when presented to the economic buyer). This review session serves as your quality check and as champion preparation, ensuring they can represent each document accurately in internal discussions.
At the end of the session, ask explicitly: "Is there anything in these documents that you anticipate pushback on internally, and how would you address it?" The champion's answer reveals the objections you still need to address before the economic buyer sees the package.
Maintaining Document Coherence as the Deal Evolves#
Complex deals change. A new stakeholder gets added to the evaluation. The timeline shifts. A specific requirement emerges that wasn't in the original scope. When these changes happen, the full deal package needs to be updated to maintain coherence. A proposal that references a timeline different from the current MAP, or a business case built on scope that's changed since the proposal was written, creates confusion and signals disorganization.
Build a version control discipline into your deal package management: each significant update to the package produces a new version, with a clear "updated" date. When you send an updated document, send all three with a brief note: "I've updated the proposal and business case to reflect [specific change]. The MAP has also been updated to reflect the adjusted timeline we discussed." This keeps all three documents synchronized and demonstrates careful attention to the deal's evolving requirements. For teams using River's Sales workspace, deal package generation and version management are integrated with deal intelligence, so documents update automatically when deal data changes.