Salesforce Renewal Automation with Flow | SalesSign

Salesforce renewal automation turns renewals into a repeatable motion using Salesforce Flow. Most renewal revenue is predictable, yet most renewal processes are not. A rep notices a contract is ending, exports the line items into a spreadsheet, rebuilds a proposal in a separate tool, emails it for signature, then re-keys the result back into Salesforce. That manual loop is where renewals slip, discounts creep and forecasts drift. This guide shows how to build proper Salesforce renewal automation with Flow — from creating the renewal opportunity to sending a signed proposal — and where a native tool removes the last gaps.

Why Salesforce renewal automation matters

New-business and renewal motions look similar on the surface, but they behave differently. A renewal already has a known customer, a known product set and a known price book. The information you need to generate a proposal almost always exists in Salesforce already. The problem is rarely missing data — it is the manual stitching between objects, documents and signature tools.

Good renewal automation does three things: it surfaces upcoming renewals early enough to act, it assembles an accurate proposal without re-keying, and it keeps the signed outcome inside the CRM so your forecast and reporting stay clean. Flow handles the first two. The third is where most teams still drop out to email and PDF.

Step 1 — Model your renewal data

Before automating anything, decide where a renewal lives. There are two common patterns:

• Contract-driven: use the standard Contract object with an End Date, and generate a renewal Opportunity as that date approaches.
• Opportunity-driven: clone the original Closed Won opportunity and its OpportunityLineItem records into a new opportunity flagged as a renewal.

Either works. The important part is having a reliable date field to trigger from and a clear way to mark an opportunity as a renewal (a record type or a checkbox such as Is_Renewal__c). You will also want a field for the renewal window — for example, Renewal Notice Date calculated as End Date minus 90 days.

Step 2 — Trigger the renewal opportunity with a Scheduled Flow

A Schedule-Triggered Flow is the cleanest way to create renewal opportunities on time. Configure it to run daily and query for the right population:

1. Start: Schedule-Triggered Flow, run daily at, say, 06:00.
2. Get Records: find Contracts where End Date is exactly 90 days from today and Status = Activated, and where no renewal opportunity already exists.
3. Create Records: create a renewal Opportunity linked to the account, set the record type to Renewal, set Close Date to the contract end date, and carry over the amount as a starting point.
4. Copy line items: loop the original line items and create matching OpportunityLineItem records so pricing is pre-populated.
5. Assign and notify: set the owner to the account team and send an alert so the rep knows a renewal has opened.

Use the 90-days-out trigger rather than a date-range filter so the same contract cannot generate duplicate opportunities on consecutive days. If you prefer a Record-Triggered approach, fire a Flow when a contract is activated and schedule a paused path to resume at the notice date.

Apply default uplift automatically

Renewal pricing is often formulaic — for example, a standard 5% annual uplift unless the rep overrides it. A simple Assignment element inside the Flow can multiply each line item’s unit price by your default uplift, then let the rep adjust before sending. Encoding the default in Flow means your baseline renewal value is consistent across the team rather than dependent on who happens to own the account.

Step 3 — Turn the opportunity into a proposal

This is the step where most automation stalls. You have a clean renewal opportunity with accurate line items — and then someone exports it to build a document elsewhere. Every export is a chance for the price, term or quantity to drift from what is recorded in Salesforce.

A Salesforce-native proposal tool closes that gap. SalesSign builds, sends, tracks and eSigns renewal proposals without leaving Salesforce, drawing the line items, pricing and account details straight from the opportunity. Because the proposal reads live CRM data, there is no re-keying and no version that disagrees with the record.

You can launch the proposal as part of the same Flow. A Flow action or a button on the opportunity can generate the proposal from a renewal template, so the rep moves from “renewal created” to “proposal ready” in one motion. The template handles the layout; Flow handles the data; the rep handles the relationship.

Step 4 — Send, track and eSign inside Salesforce

Once the proposal is built, the remaining manual steps are sending it, chasing it and recording the signature. Doing this natively keeps the whole renewal on one timeline:

• Send the proposal to the customer contact directly from the opportunity.
• Track opens and views so reps follow up when interest is highest, not on a guess.
• eSign with signatures that comply with ESIGN & UETA in the US and eIDAS / the UK Electronic Communications Act 2000 in the UK and EU.
• Update the record automatically when the proposal is signed.

Because the customer documents and CRM data sit in your own Salesforce org, the signed proposal and its audit trail live where your team already works — no separate document store to reconcile.

Step 5 — Close the loop back to the forecast

The final piece of renewal automation is reacting to the signature. A Record-Triggered Flow can watch for the proposal’s signed status and then move the opportunity to Closed Won, stamp the agreed renewal value, and create the next contract record. With the new contract’s end date set, your Step 2 scheduled flow will pick it up next year — the cycle becomes self-sustaining.

At that point your renewal pipeline is genuinely automated end to end: opportunities appear on time, proposals build themselves from accurate data, signatures complete inside Salesforce, and the next renewal is already queued. Reps spend their time on the conversations that change the number, not on the admin around them.

A sensible build order

1. Agree the data model and date fields.
2. Ship the Scheduled Flow that creates renewal opportunities and copies line items.
3. Add default uplift logic.
4. Wire up native proposal generation from the renewal template.
5. Add the signed-status Record-Triggered Flow to close and re-contract.

Each step delivers value on its own, so you can roll it out incrementally rather than waiting for a big-bang launch.