A renewal forecast fails when it starts with incomplete contract dates, duplicate opportunities, or a vague definition of what “renewal” means. Salesforce renewal opportunities give SaaS teams a record they can assign, inspect, and forecast before a customer’s current term expires.
The cleanest approach for recurring software and subscription services separates three jobs: tracking the active contract, forecasting the expected renewal, and creating a quote when commercial work begins. This structure creates a controlled starting point for software renewals, keeps churn risk out of new-business pipeline, and gives account owners a workable renewal queue.
How Salesforce Renewal Opportunities Work
In Salesforce CPQ, a contracted sale creates the records that support the renewal lifecycle. The contract captures the customer commitment, while subscription records track recurring products, subscription services, and their dates. Salesforce can then create a renewal opportunity tied to that contract for forecasting.
A forecast record is not a renewal quote
The renewal forecast checkbox creates a forecasting record with an expected amount, owner, stage, close date, and account relationship. Sales Operations can review and manage it before the rep needs to send paperwork.
A renewal quote is a separate event. Current Salesforce guidance distinguishes the two actions: Renewal Forecast supports the forecasting record, while Renewal Quoted initiates quote creation on the contract.
Don’t treat a forecast opportunity as customer-ready pricing. It’s a pipeline record until the team creates and approves a renewal quote.
Contract terms and renewal timing do different jobs
Contract terms describe the length of the agreement the customer signed. The renewal term field defines the term Salesforce should use for the next renewal.
For example, a customer may sign a 24-month contract but renew annually after that. In that case, set Contract Term to 24 months and renewal term to 12 months. Salesforce’s renewal forecasting walkthrough uses this same pattern.
Decide Your Renewal Record Model First
Configuration is easier when your team agrees on one renewal record per active contract or subscription group. Without that rule, reps may create manual records while system processes create another record for the same term.
Choose the record that controls the renewal
For a standard SaaS customer account with one agreement, use the standard Contract object as the source of truth when your configuration and commercial model support one contract per active agreement. Store the contract end date, Renewal Term, billing entity, renewal owner, and related subscriptions there.
Accounts with separately purchased products may need more than one contract. A customer might have an annual platform subscription ending in June and a later analytics add-on ending in November. Those are separate commercial commitments unless your co-terming policy joins them.
Use an immutable contract ID on the record, contract, and any renewal report. That ID is your best defense against duplicate records.
Define dates and revenue before automation
Pick one meaning for the renewal record’s Close Date. Many SaaS teams use the expected signature date or the renewal effective date. Either choice works if every owner follows it.
Also decide what Amount means. If a three-year agreement is worth $120,000, that figure is total contract value, not automatically annual recurring revenue. Add a governed ARR field if leadership forecasts ARR, and keep its definition consistent across renewals, expansions, and churn.
Track these fields before turning on automation:
- Contract end date and renewal effective date.
- Renewal owner, which may differ from the account owner.
- Renewal type, such as renewal, downgrade, cancellation, or co-term adjustment.
- Current recurring amount, proposed recurring amount, and an ARR field where needed.
- Customer health or risk status, plus a reason when the account is at risk.
Set Up Salesforce CPQ Renewal Opportunities
Salesforce CPQ works best when the product catalog, contract process, and renewal settings follow the same operating rules. Test the full path in a sandbox before applying it to active accounts.
Configure renewable subscription products
Your original quote must contain subscription products that the renewal process can carry forward. Review the product’s subscription configuration, including product pricing, pricing method, and term behavior.
Only quote lines representing recurring software should carry into the next term. Avoid making every catalog item renewable by default. Implementation fees, one-time migration work, hardware, and a warranty extension may belong on the initial quote but shouldn’t count as recurring SaaS revenue.
Create a test account with two compatible subscription products, a recurring add-on, one non-recurring service, and a warranty extension. This makes it easy to see whether the contract produces the expected subscription records.
Contract the closed won sale
After the opportunity is marked closed won, contract the opportunity or order through your established quote to cash process. Salesforce CPQ creates the contract and related subscription records from eligible quote lines.
Check the resulting contract before moving on:
- Confirm the Account, Contract Start Date, and Contract End Date.
- Confirm that expected subscription products and quantities appear.
- Set the renewal term to the length of the next expected agreement.
- Verify the contract owner and renewal owner follow your coverage rule.
Salesforce’s contract and renewal lifecycle guidance is useful for testing this sequence with sample records.
Turn on Renewal Forecast and verify the record
On the Contract record, select Renewal Forecast and save. The field, SBQQ__RenewalForecast__c, is defined in Salesforce CPQ contract field documentation as creating a renewal opportunity for forecasting.
The setting isn’t the same as the Renewal Quoted process. Confirm field availability and behavior in your Salesforce CPQ configuration before relying on it.
Then open the contract’s Renewal Opportunities related list. Review the generated renewal opportunity before anyone works it. Confirm the account, owner, close date, amount, opportunity type, and relationship to the original contract.
If the record doesn’t look right, fix the source data or catalog rules first. Editing the generated opportunity may hide a configuration problem that repeats across every future renewal.
Create Commercial Quotes and Handle Mid-Term Changes
Renewal work often starts months before a contract ends. The forecast opportunity can exist early, while pricing and commercial approvals wait until the account is ready.
Create the commercial quote at the right point
When the account owner is ready to price the next term, use the contract’s configured quoting process. This creates a commercial quote associated with the existing renewal opportunity.
That timing matters. A 120-day forecast opportunity helps leadership see upcoming revenue. However, a quote created that early may become stale after a product change, license pricing update, expansion, or approval change.
Keep the forecast opportunity open and set the stage based on real customer evidence. A customer who has not reviewed terms should not appear as Commit only because the renewal date is close.
Use amendment opportunities for active contract changes
When a customer changes an active subscription, create an amendment opportunity and amendment quote. An amendment quote includes active subscriptions and assets, but it excludes expired subscriptions.
Do not assume an amendment will automatically update an already-created renewal opportunity. Review the renewal record after any quantity change, product swap, discount change, or term adjustment. A warranty extension may also require review under your product and revenue policy, rather than being treated as a recurring subscription item.
If the expected renewal value has changed, update the forecast using your documented process. For contracts with different subscription end dates, decide whether your policy renews on the earliest end date or latest end date.
Salesforce CPQ may support both behaviors depending on the current CPQ configuration and documented renewal-date settings. Neither choice replaces a clear co-terming policy.
Salesforce CPQ Versus Custom Renewal Automation
Small SaaS teams may not need a full CPQ implementation. Yet custom renewal automation needs thoughtful data design once customers have expansions, downgrades, or multiple contracts. For SaaS businesses with cloud licensing, that includes classifying catalog items, such as a warranty extension, before deciding whether they should renew.
When native CPQ is the stronger fit
Salesforce CPQ is a good fit for established Salesforce-first teams with subscription products, complex amendments, co-terming, approvals, and contract-based renewals. Its native contract and subscription objects reduce the need to rebuild relationships between sold products and future pipeline.
The tradeoff is ongoing custom development and admin work. A product or pricing update can affect product rules, price rules, approvals, quote templates, and contract behavior. Test renewals and amendments whenever catalog logic changes.
Legacy Salesforce CPQ is end-of-sale for new customers, while existing customers can continue using it. New buyers should evaluate Salesforce’s Revenue Cloud direction before committing to a long-term architecture. For new automation, don’t choose process builder; use Flow or the current Salesforce-supported approach instead.
Build a lighter custom model with guardrails
Without CPQ, use standard Opportunities plus a controlled Contract record or custom subscription object. This lighter model requires more contract management because it must recreate relationships CPQ handles natively. A scheduled process can find contracts approaching their end date, check for an existing open renewal, and create one opportunity per contract and renewal term.
Custom Apex classes are safer when logic includes multiple contracts, owner rules, co-terming, or high record volumes. Before implementing Scheduled Apex, Batch Apex, or CPQ renewal jobs, verify the current official Salesforce documentation. Batch size guidance can vary by installed CPQ version, org configuration, and managed package.
For a lightweight custom build, require a unique contract ID, a renewal term key, and an “automation created” flag. Those fields help prevent a scheduled job and a sales rep from creating the same renewal opportunity.
Use Renewal Opportunities for Reliable Forecasting
A renewal pipeline should expose upcoming value and risk, not simply list every contract ending this quarter. Define which records qualify as a renewal opportunity, then separate renewals from new business with an opportunity record type, clear Type field, or dedicated sales process.
Make forecast stages reflect renewal evidence
Define the proof needed for each stage. Early-stage renewals may only have a verified end date and owner. Later stages should require a customer conversation, commercial approval, or signed order.
Map stages to forecast categories with care. A renewal with a red health score, open support escalation, and no customer response doesn’t belong in Commit. That rule keeps revenue forecasting grounded instead of allowing automation to create false confidence.
Build reports that expose risk
Start with a small set of pipeline reports instead of a crowded dashboard. Group records by renewal month, owner, product family, and risk status.
Useful views include renewal ARR due by month to measure forecast revenue, open renewals inside 90 days, forecasted renewal value by owner, and closed-lost renewal value with churn reasons. Track field history for Amount, Close Date, Stage, and Forecast Category so managers can explain material changes in the renewal forecast during a forecast review.
Key Takeaways
- Build one source of truth for each active contract before automating renewal creation.
- Use Renewal Forecast to create the forecast record, then use Renewal Quoted when pricing work should begin.
- Keep Contract Term and Renewal Term separate, especially for multi-year initial agreements that renew annually.
- Treat amendments as their own sales motion and review affected renewal forecasts after a change.
- Use custom automation only when your data model is simple enough to maintain without CPQ’s contract and subscription framework.
Frequently Asked Questions
Does the forecast create customer-ready pricing?
No. The forecast setting creates the renewal opportunity for forecasting. Create customer-ready pricing through the contract’s Renewal Quoted process when the account is ready for commercial renewal work.
Can a SaaS company manage renewals without Salesforce CPQ?
Yes, a small team can create renewal opportunities with standard Salesforce objects and custom automation. However, the team must maintain contract dates, subscription relationships, duplicate prevention, and amendment logic that CPQ handles natively.
How far ahead should a renewal opportunity be created?
Use the lead time that matches your sales motion. Many SaaS teams start 90 to 120 days before renewal, while enterprise accounts with procurement or security reviews may need more time. The important rule is consistent timing across similar accounts.
Build a Renewal Process People Can Trust
Reliable Salesforce renewal opportunities and software renewals depend on clean contract data, clear revenue definitions, and assigned ownership. Automation can create the record, but it can’t fix a missing end date or unclear renewal policy.
Keep forecasting, quoting, and amendments as separate actions with clear handoffs. That discipline gives account teams a usable work queue and gives leadership a renewal number worth believing.
