You're responding to an RFP. The prospect wants the proposal, three case studies, pricing, and terms. You email five attachments. The buyer opens one, forgets the others, and your competitor's single PDF wins.
One file beats five attachments every time.
Standard pack order
Cover with the prospect's name. Executive summary in one page. The proposal (problem, approach, deliverables, team, timeline). Relevant case studies. Pricing. Terms and conditions. Contact. Use merge PDF to combine in this order — buyers read top-down.
Personalise the cover
The cover should have the prospect's name and company prominently. Avoid generic covers — they signal mass mailing. Use annotate PDF to drop the prospect's name on a master cover template, then merge into the pack.
Curate case studies
Include only case studies relevant to the prospect's industry or problem. Three relevant case studies beat seven random ones. If you've got case studies as separate PDFs, merge the right ones into the proposal pack. The relevance signal closes deals.
Compress and send
Sales packs run heavy with case study images and logos. Compress PDF to under 10MB for easy email. Name the file with the prospect's company and date — `Proposal_AcmeCo_2026-03.pdf`. The buyer's procurement team will tag and file by name.
FAQ
Should proposals be password-protected?
For RFP responses with confidential pricing, often yes. Send the password by separate channel.
How long should a sales proposal be?
10-25 pages including supporting material. Beyond that, buyers skim or skip.
Should pricing be in the proposal or separate?
In the proposal — but late in the document, after the value proposition is established. Buyers who jump to pricing first are usually disqualifying themselves anyway.
Can I send the same proposal to multiple prospects?
Customise the cover and case study selection. The body can be 80% the same; the surface elements should be tailored.
Sales proposals win as single files. Merge in Flint and your pack opens cleanly in the buyer's inbox.