Turn Word documents into shareable PDFs.
Open tool
Use-case page
Sales proposal PDF workflows
Send sales proposals as polished PDFs: convert from Word or PowerPoint, attach case studies, compress for email, and protect pricing versions.
A proposal is often the first document a prospect forwards around their own company, to a manager, procurement, or finance. Sending a Word file invites accidental edits and broken fonts on the client’s machine; a PDF keeps the layout, pricing table, and branding exactly as you designed them. The challenge is getting from a draft built by several people to a single file that is small enough to email and controlled enough that pricing does not get altered.
What a proposal PDF usually contains
- A cover letter or executive summary addressed to the buyer
- Scope of work, timeline, and deliverables
- A pricing page or rate card
- Case studies, team bios, or a capabilities deck as appendices
- Terms and conditions, or a draft order form
Producing the client version
- Export the main document with Word to PDF. If the proposal was built as slides, use PowerPoint to PDF instead. Open the result and check that custom fonts, page breaks, and the pricing table came through.
- Attach supporting material with Merge PDF: proposal first, then case studies and terms. A Generate table of contents option helps when appendices run long, and it gives the buyer’s procurement team an easy way to find the terms.
- Run Compress PDF on the merged file. Proposals full of high-resolution photos usually get smaller at the default Level 5; keep Convert to grayscale off, because brand colors matter in a sales document.
- Open Protect PDF for the version that leaves your company. To let anyone read it but discourage changes, leave Open password empty, set an Owner password, and tick Disable document editing. Tick Disable copying text and content if you do not want the pricing pasted into a competitor comparison.
- Save the exact file you sent, with the date and client name in the file name, so follow-up calls reference the same page numbers.
Example: a services proposal with a case-study appendix
Picture an agency sending a six-page Word proposal plus a slide deck of three case studies. They convert both, merge them with the proposal first, compress the result, and protect it with an owner password and editing disabled. The prospect can open and forward the file freely, but their reader software is told not to permit edits.
Things that go wrong
- The client says the file will not open. You probably set an Open password they were never given. For broad internal forwarding, permissions without an open password are usually friendlier.
- Permissions get ignored. Owner-password restrictions are enforced by the reader application, not by the encryption itself, as the qpdf documentation explains. Treat them as a deterrent and keep your signed agreement as the real protection. Our guide to passwords versus permissions covers the difference.
- Photos look soft after compression. Lower the Compression level and accept a larger attachment, or share a link.
When to skip the PDF
If the buyer explicitly asks to redline the terms, send an editable document for that section. For e-signature platforms, upload the unprotected PDF, since an encrypted file may be refused by the signing service.
Trust center
Trust pages
How We Want PDF handles your files: privacy, security, and how long uploads are kept.
privacy
Privacy
How We Want PDF handles the files you upload, what is needed to use the tools, and which tools send content to an AI provider.
security
Security
How We Want PDF checks uploads, delivers results, limits abuse, and removes queued job files.
retention
File retention
How long We Want PDF keeps uploaded files and results, and when they are removed.