After a discovery call or demo, prospects often ask for "something I can share with the team." It's tempting to attach the full 60-page proposal and every supporting document. But that leaves the buyer to dig for the three sections their colleagues actually need. A focused follow-up pack is a small set of PDFs, each answering a specific question from the conversation. It is easier to read, easier to forward, and less likely to cause confusion about which version is current.
Here's a practical way to build one.
Before opening any files, go back to your call notes. List the open questions and who raised them. A typical follow-up might look like this:
Next, map each question to where the answer lives. It might be in your master proposal, a security overview, an implementation guide, a pricing schedule, or a published case study. This step tells you what belongs in the pack before you start pulling pages.
Most sales documents are written to cover every possible buyer. Your follow-up only needs to cover this one. When you review candidate pages, check each against a few criteria:
Record your selections as you go, using the source file name and page ranges. For example: "Proposal_v7: pages 1–2, 14–18; Security_Overview: pages 3–6." This list becomes your extraction plan and a record of what you sent.
You have two basic options: one combined PDF or a few separate files organized by topic. Separate files are often easier for buyers to work with. The champion can forward the security pages to IT without also sending pricing to people who don't need it. Three to five files is a manageable range for most follow-ups.
Whichever format you choose, add a short index. It can be a few lines in your email or a one-page summary at the front that lists each file and what it covers.
Once you have your page list, the extraction itself should be quick. Here's a workflow that works on a Windows PC.
1. Set up a working folder. Copy the source documents into a new folder for this prospect. Work on copies, never the originals in your shared library. Confirm each source is the latest approved version before you extract anything from it.
2. Extract the pages you need. A desktop PDF splitter is useful here. One option is CoolUtils PDF Splitter for Windows. In the standard version, you add a file, choose a splitting method, set an output folder, and click Split. To pull specific pages, you enter a list of pages and ranges such as 1,2,5,7-10. If your proposal uses bookmarks for each chapter, you can split by bookmarks to separate whole sections at once. The tool can also process a folder of PDFs in a batch and combine split pages into a new document, which helps if you want pages from one source merged into a single topic file.
The tool runs offline, so your files are processed on your own computer rather than uploaded to an online service. That matters when the pages include pricing or contract terms. It also includes a renamer for output files and options to password-protect the results.
CoolUtils offers separate editions for different jobs. PDF Splitter Pro includes everything in the standard version and adds features such as splitting by specific text lines (invoice numbers, for example), generating reports, and manual splitting. These features are aimed more at high-volume document processing than at assembling a single proposal pack. PDF Splitter X is a separate server version with no graphical interface, intended for web servers and integration into other applications. The standard desktop tool also supports command-line use if you want to script a repeat task.
3. Review every output file. Open each extracted PDF and check it page by page. Confirm the pages are correct and in the right order, that no blank pages slipped in, and that charts and tables are legible. Also scan for cross-references to sections you left out.
A file called "proposal (2) final.pdf" tells the recipient almost nothing, and it gets worse after a few people forward it. Pick a naming convention and use it every time. One simple format is:
[YourCompany]_[Prospect]_[Topic]_v[Version]_[YYYY-MM-DD].pdf
For a fictional example: Northwind_AcmeCo_Pricing-Summary_v3_2026-10-22.pdf
A few rules keep this consistent:
Version confusion is one of the most common problems with sales documents. A prospect might review outdated pricing or a security page that has since been revised. A few checks before you hit send can prevent it:
A focused proposal pack won't decide a deal on its own, but it removes avoidable friction. Buyers can find what they need, forward the right pages to the right people, and trust that they're looking at the current version.