Moving your signing to SignSecure is a checklist rather than a project. Rebuild your templates and field placements, bring your executed documents across for retention, run a quarter in parallel while the team gets comfortable, install the Salesforce package, and settle into an invoice that counts seats and nothing else.
Work down this list once. Most teams do the whole column in a day or two, and an agent works through it with you as part of setup.
| Item | What to bring | Where it lands |
|---|---|---|
| Documents | The source file for each agreement you send regularly, as a PDF or a Word file. | Uploaded once and saved as a SignSecure template. |
| Field placement | A signed example of each document, so you can see where signatures, initials and dates belong. | Drag the fields onto the page. Saved with the template, so every send opens pre-tagged. |
| Signer roles | The list of roles on each document: customer, countersigner, witness, approver. | Named roles on the template, resolved to real people at send time. |
| Routing order | Who signs first, who follows, and what is parallel. | Routing order on the template, set once. |
| Reminders and expiry | Your current chase cadence and how long a document should stay open. | Reminder schedule and expiry date on the template. |
| Email wording | The subject lines and body copy your signers already recognise. | Customisable send and reminder emails. |
| Executed documents | An export of your signed agreements, with their completion certificates. | Stored for retention, and attachable to the matching Salesforce record. |
| Users | Who sends, and who only needs to view finished agreements. | Seats for senders. Viewers do not need a seat. |
| Salesforce mapping | The merge fields you populate and the fields you want written back. | Field mapping in the managed package. |
| API and integrations | Any scripted sends or connected tools that create documents today. | The REST API, included on every paid plan. |
Finished agreements are records, and records need a home for years. Export them once, keep them whole, and put them somewhere your team already looks.
Nobody should move everything on a Monday. Give yourself a quarter with both routes open, and use the Salesforce install sequence below so production only ever sees a tested configuration.
Pick a team with a high volume, repeatable document, usually NDAs or order forms. Everything else carries on exactly as it does today. By week four that team has a real opinion, and you have templates that are proven on live agreements.
Install into a sandbox first, assign the permission sets, add the send button to the page layouts, map merge fields and write-back fields, and send test documents end to end. Then install to production and switch it on for the pilot team.
Add the remaining teams a group at a time, using the templates the pilot already proved. Keep your archive read only for as long as your retention policy asks, and let new agreements start life in SignSecure.
One line, and the line is seats. $12 per user per month billed annually, or $15 month to month. Everything the team actually does with the product is inside that number.
Everything above, on one line of the invoice.
Billed annually. $15 per user month to month.
Rebuild a single template, send it for real, and see how the rest of the checklist feels. An agent will work through it with you.