Solutions · Close and renew

A Salesforce renewal process that starts clean and ends with the right document

A renewal begins as a copy of something old and ends as a document a customer reads. Two apps cover those steps today, and a third piece, signing, is still a design.

The job, and why it hurts

Renewal season. Someone clones last year’s opportunity, someone else rebuilds the quote in a word processor, and by the time it reaches the customer there are three versions in circulation. One still has last year’s line items. Another has the old owner’s name on it.

The standard Clone button copies everything, and that’s the trouble. Whatever should have been reset (dates, status, notes, owner) is left to whoever clicks, and nobody remembers all of it. The document is the second hazard. Retyping figures from a record into a file is how a total ends up one digit off, and a month later nobody can say which version was sent.

The work is repetitive, and repetition is where careful people slip. It’s the same fix every cycle, so it should be written down once, in a form the whole team can read.

The apps for the Salesforce renewal process

Where things stand. Sistership and Purser are in early access with design partners. Purser Sign is a planned feature of Purser, in design, and nothing is built yet.

Sistership: clone a record and have the copy come out ready

Sistership, by GTM Cloud, is a custom clone button for Salesforce. Rules read like sentences (if the copy matches these conditions, then blank this, set that, protect the other), and you choose which related records come along. A log shows every changed field with the old value and the new one. The standard Clone button stays exactly as it is. See how Sistership cleans a copy.

Purser: generate the PDF or Excel file from the record

Purser, by GTM Cloud, reads in the Word or HTML file your team already uses, and an admin maps its merge fields. People then generate a PDF or Excel workbook from the record and see the real file before it saves. Every document is logged with the template version that made it. Purser doesn’t collect signatures. See how Purser generates a document.

Purser Sign: sign the document where it was made (in design)

Purser Sign is designed to let people sign a document Purser has generated, from a Salesforce login, in your portal or in person, and save the signed copy beside the original. It’s a simple electronic signature, and whether that’s enough depends on the document and the place. Nothing is built. Read the Purser Sign design and join the pilot.

How they hand off to each other

In the order a renewal moves:

  1. Sistership makes the renewal copy, with the stale fields reset by your rules.
  2. Purser generates the quote or proposal from that record, so the document matches the data.
  3. Purser Sign would then send it for signature. It would be a feature of Purser rather than a separate app.

Sistership and Purser each install alone, and neither needs the other.

See it first. Take it back. Keep the receipt.

Purser’s preview is the real file, shown before anything is saved, and a generated document can be removed again. Sistership has no undo, because a clone is a new record and the original is never touched. If you didn’t want the copy, you delete it. Both keep a log, and the promise says plainly where nothing needs taking back.

When a person should help

If your quotes run through Salesforce CPQ and you’re asking whether that setup should stay, the CPQ Exit Plan is a three-to-six-week piece of work: an inventory of what your setup really does, a target design, and a migration plan you can hand to whoever builds it. Renewals and documents are usually where the real answer shows up.

Questions people ask

How do I stop renewals copying old dates and statuses?

Add a second way to clone that resets the copy as it’s made. Sistership rules blank or set fields, fill a date or the current user, and protect others, while the standard Clone button stays untouched. Fields no rule mentions keep their copied value, so you only write rules for what needs to change.

How do I clone a record with its related records in Salesforce?

Choose which related records travel with the clone for each set of rules, such as an Account’s Contacts. Sistership lets people start a clone from a Flow action, a quick action or a page button, and the copy arrives with those records and your field rules already applied.

How do I generate a quote PDF from a Salesforce record?

Turn your existing Word or HTML quote into a template once, mapping each merge field to a Salesforce field. Then generate from the record and check the preview. Purser does this and logs each document. Its Quote starters need Quotes turned on in your org.

Can I get a document signed inside Salesforce?

Not with anything we’ve built yet. Purser Sign is a design for signing documents Purser generates, with a certificate page and a way to verify the file. It’s a simple electronic signature, and whether it suffices depends on the document and the place, so ask your legal advisor.

Should we keep Salesforce CPQ?

Start by listing what your setup actually does: which rules, which products, which documents it produces. Decide once you can see that list. The CPQ Exit Plan produces it, along with a target design and a migration plan, so the decision doesn’t rest on memory.

Name the record you clone every renewal

Book a Data Health Check and find out how much stale data rides along in your copies.