The problem: multiple documents, multiple signature emails
Your sales team creates a proposal (Opportunity -> Quote), a 60-page contract, and a 4-page statement of work kept as a separate template. They send these as separate emails or separate signature requests. Signers get confused about which version to sign, legal misses a clause in the right document, and your signed files end up scattered across the Opportunity, the Contract record and personal inboxes.
That breaks reporting, delays revenue, and wastes time chasing signatures. If your team sends 120 proposals a month and each deal takes an extra four-day signature chase because signers open the wrong file, that adds up quickly. Bundling lets you send everything together in one signature run so signers see one package and you get one final PDF filed where it belongs.
What bundling does and why it matters
Bundling in Savvy DocuGen means you select multiple templates (Word or PDF) and merge them into one signature run through Circularo. The signer gets a single package. Circularo places signatures using anchor tags so positions hold even if pagination changes. When the envelope is signed, the combined PDF is written back to the originating record.
Key practical benefits:
- Single package reduces signer confusion and accelerates signatures.
- One signed file per record makes reporting and audit trails straightforward.
- Anchor tags survive repagination, so signature fields don’t move when a clause grows or shrinks.
How to set up document bundles in Salesforce
This is written for a sales ops team managing Opportunity-to-contract. Pick one person to own templates and one to own automation; both roles matter.
1) Build the templates
Create each document as a Word or PDF template that DocuGen can fill from Opportunity, Quote, Account, Contact, or child objects (DocuGen can traverse up to five parent lookups and include repeating child rows for line items).
Put signature anchor tags in each template where needed. Example anchor tags might look like this in your Word file:
[[SIGNER1_NAME]]
[[SIGNER1_SIGNATURE]]
[[SIGNER2_SIGNATURE]]
Those anchors survive repagination so a longer SOW doesn't push the signature block onto the wrong page.
2) Define who signs and how
Decide signer order and authentication. Savvy DocuGen supports the per-signer emailed one-time code and can also require a per-signer password read from that signer's Salesforce record. For example, you could store a password on Contact.SignaturePassword__c (or a similar field) and DocuGen will use it for signer verification.
3) Create the bundle and test on Opportunity
When you send, select the proposal, the contract template, and the SOW template and DocuGen merges them into one envelope. You can trigger this manually with a button on Opportunity or automate it on stage change, a field update, or when a related file is uploaded.
4) File the outcome cleanly
When the envelope completes, the signed PDF is written back to the same record (for example, the Opportunity or Contract). If your combined file exceeds 25 MB you must use Salesforce Files because Notes & Attachments is capped at 25 MB; DocuGen supports both and will put the finalized document where you prefer per-template settings.
Common bundle scenarios and how to template them
Here are three real-world scenarios you’ll recognise and how bundling fixes them.
Proposal + SOW + Signature Page (one mailing)
Template the proposal with QuoteLineItem repeating rows so prices and discounts flow in. Put the SOW as a separate template with its own repeating block for deliverables. Add a thin final signature page template with anchor tags for each signer. Send all three as a bundle so procurement and legal see the whole context when they sign.
Renewals with standard T&Cs plus a custom amendment
For renewals you might have a common T&Cs template and a one-page amendment that varies per customer. Merge both into one bundle so the customer signs the updated package once rather than twice. This reduces signature touchpoints when you have many renewals to process each month.
Large agreement split for readability but signed together
Sometimes legal wants the main agreement and a separate technical appendix. Keep them as separate templates so subject matter experts edit only their section, but bundle them so the appendix is always attached and signed with the main contract.
Practical tips and gotchas
- Anchor tags are your friend. Use clear, unique anchors for each signer and test with longer and shorter versions of documents to confirm placement stays correct.
- Keep signer identity fields on Contact or User records current if you use per-signer passwords or read other signer data from Salesforce.
- Watch file size. DocuGen supports documents up to 40 MB; use Files for anything over Salesforce Notes & Attachments limits.
- No managed package means no install – DocuGen connects through an authorised connection and works the same in sandbox as production, making testing straightforward.
Bundling is the simplest fix for messy signature workflows: one envelope, one final PDF, and one place to look for the signed agreement. It reduces signer confusion and gives you a clean audit trail tied to the originating Opportunity or Contract record.
Savvy DocuGen merges templates into one signature run, keeps anchor tags during repagination, supports signer verification, and writes the signed file back to the record. Try Savvy DocuGen in your sandbox to bundle a proposal, T&Cs and SOW and see how much faster the signatures arrive.
Read next