Proposal assembly checklist
Assemble the pricing, the approved terms, and the proof the buyer asked for into one packet, with each missing piece named before the send.
Tools
Loopio, Salesforce CPQ, Salesforce, 6sense
Outcomes
Every proposal checked before it is sent • Missing proof named, not shipped • One owner per outstanding input • Approved terms reused from the library
Documentation
Instruction-ready detail below
A proposal goes out with no case study because the request to marketing was never sent, and the buyer notices before the sales team does. This workflow builds the packet from a checklist rather than assembling it from memory. It pulls current pricing from the quote, the approved terms and standard clauses from the response library, and the proof this buyer actually asked for, then compares what is present against what this deal requires. Each missing item is listed with one named owner and a date rather than a general reminder, so chasing happens once instead of in three threads. An answer in the library nobody has touched in a year is flagged before it gets reused, because stale proof is worse than no proof. The packet is assembled as one file with a version number and the date it was built, so the buyer and the rep are holding the same document. A human still decides which proof lands the deal, whether a case study is approvable, and what to leave out. The checklist says what is missing; the rep decides what the proposal is for.