Every release becomes revenue you can see.Subscriptions, assets and roll-ups on the standard Contract.
Lead-to-Revenue is where the released Order stops being a transaction and becomes the install base: services become Subscriptions, products become Assets, both hang off a standard Salesforce Contract that rolls up MRR, ARR and TCV, and the Revenue Management add-on writes the monthly revenue rows finance forecasts and recognizes from. No export, no second system, no month-end tie-out.
Lead-to-Revenue in Kugamon turns a released Order into the install base: Subscriptions from the service lines, Assets from the product lines, both on a standard Salesforce Contract that rolls up MRR, ARR and TCV. The Revenue Management add-on writes monthly Revenue records from the Order or the Invoice. Every one of those rows is a native record, so forecasting and recognition run on reports, not exports.
What happens at each step
| Event | What Kugamon creates or updates |
|---|---|
| New Order approved | Assets from product lines, with purchase price and date |
| New Order released | Contract (Effective when active and in term), Subscriptions from service lines, the next Renewal Opportunity with a future close date, Revenue records if set to Order Release |
| Contract active | ARR, MRR, TCV, subscription count, total quantity, start and end dates rolled up; Duration shows tenure |
| Expansion Order released | Lines co-termed and prorated to the Contract End Date; Subscriptions and Assets added; Renewal Opportunity updated |
| Invoice sent or posted | Revenue records if set to Invoice Sent or Invoice Posted; Posted locks the Order |
| Renewal Order released | Contract extended or a new one created; Subscriptions and Assets added; next Renewal Opportunity created |
| Subscription or Contract cancelled | Subscriptions deactivated or cancelled; Renewal Opportunity decremented or closed lost; lines kept for churn reporting |
Subscriptions and assets
The rule is simple and it drives everything: only services create Subscriptions, only products create Assets. Both switches live on the product, so the admin decides once and every Order after that behaves the same way. Assets use the standard Salesforce Asset object, created on approval per line — ten bikes on one line become one Asset with quantity ten — or per quantity, where five phones become five Assets each with its own serial number. Assets link back to the Order and, once released, the Shipment, so support and field service see the same Asset sales created. Refresh Assets rebuilds them from the Order if a line was changed after approval.
Subscriptions are created on release, carry the effective price from the Order service line, and compute an IsActive flag from four conditions — not cancelled, Contract effective, Order approved or released, today within the dates — by an hourly scheduled job. Creating that Subscription Active Check job is what turns Subscription Management on. A parent subscription or asset can be tracked, so a seat pack under a platform license is modeled, not just listed.
The Contract as the container
Releasing a New Order creates a Contract — the standard object — and everything about the customer relationship attaches to it: contributing Orders, Assets, Subscriptions and the current Renewal Opportunity. The roll-ups finance and RevOps ask for are fields on it: ARR, MRR, TCV, subscription count, total quantity, start and end dates, and a Duration that shows how long the account has been a customer. Multiple active Contracts per account are supported when the setting is on.
Manage Contract from the Contract shows every active subscription with a visualization of growth over time; from the Account it shows every effective Contract with trending indicators — renewal revenue lower, higher or the same — and a smart button to start an Expansion or manage the current Renewal. Because the standard Opportunity Amount ignores time, Kugamon adds an Opportunity Amount field that factors the service term, so the pipeline value of a three-year deal is the three-year number.
Revenue recognition
The Revenue Management add-on creates monthly Revenue records at one of three events set in Kugamon Settings: Order Release (recommended), Invoice Sent or Invoice Posted. A three-year order invoiced annually creates 36 monthly records on release, or 12 as each yearly invoice is processed. Products and one-time services recognize per record; subscription services can recognize a larger initial share and separate it from the term; additional charges recognize per record. Revenue Type is set from the revenue date, revenue is broken down by tax, and a Posted/Locked flag prevents edits and prevents the Order from being un-released. Un-releasing an Order that is not locked deletes its Revenue records, and Refresh Revenue rebuilds them from a corrected Order.
Reports for revenue by Order and by Account over time ship in the Kugamon report folder and drop onto the record pages as chart components. What this is not: a revenue subledger. It does not run the five-step ASC 606 model or allocate standalone selling prices, and the Zuora comparison concedes that Zuora Revenue does.
Forecasting from native roll-ups
Because ARR is a field on the Contract, revenue is a record per month, and the Renewal Opportunity is a real Opportunity with a real close date, the forecast is a Salesforce report. Renewal pipeline by quarter, expansion by product, churned subscriptions by month, revenue by account over time — none of it needs a data warehouse or a nightly sync. The subscription metrics article defines each number and where it comes from.
When Kugamon is not the right choice
If revenue is metered consumption — usage events rated into charges at high volume — Zuora has a mediation and rating engine and Kugamon does not. If finance needs a subledger that automates ASC 606 with SSP allocation across performance obligations, Zuora Revenue or your ERP is the tool, and Kugamon's add-on is a reporting layer that feeds it. If you sell one-time products with no recurring element, this workflow is more than you need; Lead-to-Bill is the right stopping point.
For a subscription business on Salesforce, this workflow is the Subscription Management edition at $95 per user per month for companies over 200 employees, or Subscription Billing at $125 with invoicing and payments included. What happens as the Contract approaches its end date is Lead-to-Renewal.
Only services create Subscriptions and only products create Assets. A service line whose product has Create Subscription set becomes a Subscription when the Order is released; a product line whose product has Create Assets set becomes an Asset when the Order is approved or released, either one Asset per line with the line quantity or one Asset per unit so each can carry its own serial number.
On the standard Salesforce Contract. Releasing a New Order creates the Contract as the container for its Subscriptions, Assets, contributing Orders and next Renewal Opportunity, and the Contract rolls up ARR, MRR, subscription count, total quantity and start and end dates. Expansions and renewals update the same Contract, so the roll-up is always current and any standard report or dashboard can read it.
The Revenue Management add-on creates monthly Revenue records at an event you choose in Kugamon Settings: Order Release, Invoice Sent or Invoice Posted. A three-year order invoiced annually creates 36 monthly records on release, or 12 as each yearly invoice is processed. A subscription can recognize a larger share in its first month, a Posted/Locked flag prevents edits and un-release, and revenue-by-Order and revenue-by-Account reports ship in the Kugamon report folder.
No. It is a recognition and reporting layer that gives finance monthly revenue rows inside Salesforce. It does not automate the five-step ASC 606 or IFRS 15 model or allocate standalone selling prices. Companies that need a finance-owned subledger with SSP allocation use Zuora Revenue or their ERP.
Cancelling a Subscription sets its status 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, but the Subscription lines are kept rather than deleted, so churn can be reported instead of erased.
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.