The renewal is already in the pipeline.Created the day the first Order is released.
Lead-to-Renewal is the last of the five workflows and the one that pays for the others. In Kugamon a renewal is not a spreadsheet someone checks in Q4 — it is a Renewal Opportunity created the moment the New Order is released, with a notice email, an auto-generated Renewal Order, a price uplift and a co-termed expansion path already attached, all as standard Salesforce records a rep can see and a report can count.
Lead-to-Renewal in Kugamon starts on the day the New Order is released: a Renewal Opportunity is created with a future close date, a renewal notice goes out 120–90 days before the Contract End Date, a Renewal Order is generated and optionally emailed 60–30 days out with the price uplift applied, and releasing that Order extends the Contract and creates the next Renewal Opportunity. Expansions co-term to the same Contract. Cancellations keep the record for churn reporting.
What happens at each step
| When | What Kugamon does | Where it lives |
|---|---|---|
| New Order released | Creates the Contract, its Subscriptions and Assets, and a Renewal Opportunity with a future close date and the renewable lines as Opportunity Products | Standard Opportunity, Renewal record type; Contract points at it as Current Renewal Opportunity |
| Any time mid-term | Expansion Opportunity → Quote → Order, co-termed and prorated to the Contract End Date; release updates the Contract and the Renewal Opportunity | Expansion record type; existing Assets and Subscriptions selectable at original purchase price |
| ~120–90 days before end | Contract Renewal Notice emailed to the buying contact by the hourly job | Email template in the Kugamon Email Templates folder; date on the Contract |
| ~60–30 days before end | Renewal Order generated from the Renewal Opportunity by the hourly job, and emailed if enabled | Renewal record type; uplift applied from the account's Renewal Price Uplift Percent |
| Rep adjusts | Refresh Products on the Renewal Opportunity rebuilds lines from the contributing Orders; Renewal Quote and Order generated as needed | Same configurator as any Quote or Order |
| Customer accepts | Online Order link, Accept or Accept & Pay; accepting contact captured on the Order and Contract | Order Accepted By; Contract Customer Signed fields |
| Renewal Order released | Contract extended (or a new Contract created), Subscriptions and Assets added, Invoice generated, next Renewal Opportunity created | Extend Contract on Renewal setting decides which |
| Customer cancels | Subscription cancelled and removed from the renewal, or Contract cancelled with subscriptions deactivated and the renewal closed lost | Subscription lines kept for churn reporting |
Automated renewal opportunities and orders
The Renewal Opportunity is a standard Opportunity with the Renewal record type, so it sits in the pipeline, the forecast and every report a sales leader already runs. It is created on release of the New Order for any order with a renewable service line, at the stage the admin set in Kugamon Settings, with the renewable lines as Opportunity Products. The Contract keeps a Current Renewal Opportunity link that is updated every time a Renewal Order is processed, so nobody has to find it.
Three scheduled jobs do the rest, created from the Subscription Automation button and recommended to run hourly. The Contract Renewal Notice job emails the buying contact when the Contract's notice date arrives — set by default 90 days before expiry and typically sent 120–90 days out. The Renewal Order Generation job creates the Renewal Order from the current Renewal Opportunity typically 60–30 days before the end date, and emails it if the Contract's Auto Email Renewal Order control is on. The Subscription Active Check keeps every subscription's active flag current, and creating it is what turns Subscription Management on. A rep who would rather work the renewal by hand uses Generate Quote and Generate Order from the Renewal Opportunity, in the same configurator as any other deal.
Renewal notices and price uplifts
The notice email and the renewal order email are Classic email templates in the Kugamon Email Templates folder, with organization name, buying contact and rep signature filled automatically; duplicate them before editing. Both are sent to the Contract's buying contact, which follows the last Order, so a change of contact on the Order updates who gets the notice.
Uplifts are set once and applied per account. The Renewal Price Uplift Percent in Kugamon Settings defaults onto each account's Additional Account Info record, where it can be overridden for a customer with a negotiated cap, and flows from there to the Renewal Opportunity. Products flagged Uplift Renewal Price have their sales price adjusted by that percent; products without the flag renew flat. A Renewal Product lookup lets a service renew onto a different product, which is how a legacy plan moves customers to the current one at renewal without a manual rebuild.
Co-terming and expansions
Mid-term growth is an Expansion — an Opportunity, Quote and Order with the Expansion record type, started from the Contract or from the Manage Contract view on the Account. Related Contract information is required, and in Add Lines the rep can pick from the Contract's existing Assets and Subscriptions and honor the original purchase price with one click. Kugamon co-terms and prorates every added line to the Contract End Date, and releasing the Expansion Order updates the Contract and the Renewal Opportunity so the renewal already reflects the larger footprint. The co-terming glossary entry defines the term; the amendments, proration and co-terming article works through the arithmetic.
Cancellations
Cancelling a Subscription sets it to Cancelled and, if it was set to renew, removes it from the Renewal Opportunity. Cancelling a Contract deactivates its active Subscriptions and closes the Renewal Opportunity as lost. In both cases the Subscription lines stay in place with their status rather than being deleted, so churn is a report you can run by month, product and account. The Extend Contract on Renewal setting decides whether a renewal pushes out the original Contract's end date or creates a new one.
When Kugamon is not the right choice
If your renewals are priced from metered usage that has to be rated first, Zuora has the rating engine and Kugamon does not. If renewing means renegotiating the contract document — redlines, clause libraries, counter-signature workflows — Conga's contract lifecycle management is the deeper tool, and Kugamon's contract management covers the Contract object, its roll-ups and its renewals rather than the negotiation. And if you sell one-time products with nothing to renew, this workflow does not apply; stop at Lead-to-Bill.
For a subscription business on Salesforce, this workflow is the Subscription Management edition at $95 per user per month, and the automate renewals article is the practical setup guide.
When the New Order is released, for any order with at least one renewable service line. It is a standard Opportunity with the Renewal record type, a future close date, the Renewal stage you set in Kugamon Settings, and Opportunity Products built from the renewable lines. Expansions update it, a released Renewal Order creates the next one, and the Contract always points at the current one.
Three scheduled jobs, created from the Subscription Automation button in Kugamon Settings and recommended to run hourly: the Contract Renewal Notice email to the buying contact, typically 120 to 90 days before the Contract End Date; Renewal Order generation from the current Renewal Opportunity, typically 60 to 30 days before, optionally emailed to the customer; and the Subscription Active Check that keeps every subscription's active flag current. The email templates live in the Kugamon Email Templates folder and should be duplicated before editing.
A Renewal Price Uplift Percent is set in Kugamon Settings, defaults onto each account's Additional Account Info record where it can be overridden, and flows to the Renewal Opportunity. Products flagged Uplift Renewal Price have their sales price adjusted by that percent on the renewal; products without the flag renew at the same price. A Renewal Product lookup lets a service renew onto a different product, which is how a legacy plan moves customers to the current one.
An Expansion Opportunity, Quote and Order are created from the Contract or from Manage Contract. In Add Lines the rep can pick from the Contract's existing Assets and Subscriptions and honor the original purchase price. Kugamon co-terms and prorates every added line to the Contract End Date, and releasing the Expansion Order updates the Contract and the Renewal Opportunity so the renewal reflects the larger footprint.
Cancelling a Subscription sets it to Cancelled and removes it from the Renewal Opportunity if it was set to renew. Cancelling a Contract deactivates its active Subscriptions and closes the Renewal Opportunity as lost. In both cases the Subscription lines stay in place with their status, so churn is a report, not a deleted record.
What Salesforce admins say on AppExchange
Quoted verbatim from the Kugamon listing on AppExchange. Reviewer names and dates as published there. Read all 134, including the critical ones →
★★★★★Easy to understand, easy to implement
“This SFDC-native platform is lightweight but powerful, bringing the entire sales process onto one pane of glass. No more disconnected Opportunities and Quotes/Orders, no more fractured approval processes, just more control over everything. Implementation is a breeze.”
★★★★★Clear & Intuitive
“The Kugamon team is incredibly responsive and handle support questions very quickly. It’s clear they genuinely value customer feedback and are always innovating.”
★★★★★A new bar for RevOps
“As someone who has set up Salesforce CPQ before, I found Kugamon to be much more straightforward and easier to use. It took us just a few weeks to get going, rather than the few months or even years required by other systems.”
Configure, price, quote, sign, bill, collect, and renew.
All natively in Salesforce. Deploys in weeks, not months, usually without a systems integrator.