The problem
You have several documents that must be signed together: a 60-page master services agreement, a 4-page statement of work, and a 1-page signature cover. Sending them separately creates versioning headaches and lengthens the signature cycle. You want one signature run from Opportunity or Contract so signers see all pages in context, and the signed PDF should land back on the same Salesforce record.
If you’re a Salesforce admin, you need a click-based setup you can test in sandbox and hand to sales reps with minimal training.
How Savvy DocGen handles bundles (quick facts)
- It merges several Word or PDF templates into a single signature run (a bundle).
- Signed PDF is written back to the same record, using Salesforce Files or Notes & Attachments per template settings.
- Signature positions use anchor tags so placement survives repagination.
- Documents up to 40 MB are supported; Notes & Attachments has a 25 MB cap in Salesforce.
- No managed package to install. Connection is authorised, and sandboxes behave the same as production.
Plan before you build
Decide three things up front:
- Which templates belong in the bundle and their order. Order matters because signers will see the merged PDF as a single document.
- Where the signed file should be stored: Files (recommended for big or multiple docs) or Notes & Attachments (only for very small docs due to the 25 MB cap).
- How the bundle is triggered: a quick action/button, an Opportunity stage change, a field change, or when a new file is attached.
Step-by-step: set up a bundle for the Opportunity or Contract object
1. Prepare your templates
Create Word or PDF templates for each document (MSA, SOW, cover). Add anchor tags where signatures, initials or dates must appear. Use field names that match your Salesforce fields for merge data. Keep each template under reasonable size; the whole bundle must stay below 40 MB to avoid upload problems.
2. Create a bundle template
In Savvy DocGen you define a bundle by selecting the templates and their order. Name it clearly, for example "Opportunity - MSA + SOW + Cover" and associate it with the Opportunity or Contract object so it’s available from the record page.
3. Decide storage and signer mapping
Choose whether the generated and signed PDF will be saved to Files or Notes & Attachments. Use Files unless you are certain every bundle will be under 25 MB. Map signer roles to Salesforce fields (Contact.Email, Contact.Mobile for one-time codes, or a per-signer password read from a signer record).
4. Add a button or quick action (no code)
Create a Lightning quick action or a custom button on Opportunity or Contract that launches the bundle. Configure the action so it passes the record Id and any signer lookup fields. This keeps the flow simple for sales reps: click the button, review the merged document in the preview, and send.
5. Or trigger by Flow
If you prefer automation, use a record-triggered Flow. Example: when Opportunity.StageName changes to "Awaiting Signature" start the Savvy DocGen bundle send. Make the Flow call the same bundle and pass signer emails and file-storage choice. This keeps clicks down and ensures consistency across reps.
6. Test in sandbox exactly like production
Test a full run in your sandbox: generate the merged PDF, confirm anchor-tagged signature positions are correct after repagination, and send via your Circularo account. The signed PDF should come back and attach to the same Opportunity or Contract record. Because Savvy DocGen works in sandboxes exactly as in production, your sandbox tests mirror production behavior.
Tips and common pitfalls
- Anchor tags survive repagination, so use them rather than fixed coordinates. Fixed coordinates are the wrong choice here because merged templates repaginate differently.
- Watch file size. A 60-page MSA plus three SOWs can easily exceed 25 MB when images or tracked changes exist. If the bundle is larger than 25 MB, choose Files for storage.
- Signer authentication: you can require an emailed one-time code, a per-signer password stored on the signer record, or both. Map those signer fields when you set up the bundle so the send enforces the right identity level.
- Make the button label explicit: "Send MSA + SOW for Signature" beats "Send for Signature". It reduces mistakes and training questions.
Concrete scenario
Hypothetical: you run 200 renewals a month. Each renewal needs a 60-page MSA and a 4-page SOW bundled with a 1-page cover. Bundling merges the three templates into one signature run, so sales reps send one package, signers complete one authentication step, and the signed PDF is filed on the Opportunity. That cuts confusion and avoids multiple separate signature cycles per deal.
What to hand over to your team
- A clear bundle naming convention and where to use each bundle (Opportunity vs Contract).
- Quick action on the record page and a short one-page runbook for reps: which button to press and what to check before sending.
- A test checklist for admins: validate anchor-tag positions, confirm storage location, verify signer authentication, and confirm the returned signed PDF attaches to the record.
Why this works for admins
This is a clicks-not-code setup. You build templates in Word, define the bundle and storage choices in Savvy DocGen, add a quick action or a Flow, and test in sandbox. There’s no managed package to install and nothing for security to review beyond authorising the connection to your Circularo account.
Savvy DocGen merges templates into a single signature run, places signatures with anchor tags, and writes the signed PDF back to the record so your process stays auditable and your reps stay fast. Try creating a bundle in your sandbox today and send a test from an Opportunity record to confirm anchors, storage and signer authentication behave as you expect.
Read next