Explain how much SaaS expansion came from price increases

An expansion category can contain several commercial events. An existing customer may buy more seats, move to a different product, lose an introductory discount or pay a higher unit rate. Retain the reported expansion total, then add a supporting analysis of those causes. That lets readers distinguish increased adoption from a change in pricing without redefining the headline metric each month.

ChartMogul's movement documentation explicitly includes expiring discounts among possible causes of expansion. This illustrates why the label alone does not establish what happened in the customer relationship. Use the agreement and price history to explain the movement rather than interpreting every increase as a larger deployment.

For each relevant subscription line, retain quantity, unit rate, discount, product, currency and billing interval at both dates. Normalize the period consistently. Identify amendments within the interval so a temporary price or quantity does not disappear behind two month-end snapshots. Keep one-time fees outside the recurring movement unless the stated measure explicitly treats them otherwise.

Review product substitutions before comparing unit prices. A move from a basic seat to a bundle with additional services is not necessarily a pure price increase. Classify it as a product or mix change when appropriate and explain the treatment. The supporting analysis should describe comparable units rather than dividing every customer total by a convenient seat count.

In a simplified example, 20 seats at $40 produce $800 a month, while 25 seats at $44 produce $1,100. Using opening quantities and rates, the price effect is $80 and the quantity effect is $200. The remaining $20 is the interaction between five additional seats and the $4 rate increase. Together they explain the $300 change.

Another valid convention applies the new rate to all added seats, assigning the interaction to quantity. Choose one method and disclose it. The arithmetic must reconcile, and the convention should stay stable across periods. This prevents two analysts from presenting different price effects while each claims to have isolated the same cause.

Record the effect of a discount beginning, ending or changing using the chosen bridge method. Confirm whether the headline metric includes that discount under its definition. A concession's expiry can improve recurring value while customer usage remains flat. The account owner should know whether the expiry was expected and accurately communicated.

If contracts use several currencies, evaluate commercial movements in the contract currency before presenting a translated total. Keep currency effects in a separate explanation under the business's reporting method. This avoids attributing exchange-rate movement to pricing decisions or sales activity. Reconcile the final bridge to the same closing metric used in the management report.

Show price-driven and quantity-driven changes by meaningful customer groups. Review whether higher rates coincide with seat reductions, product exits or unusual concessions. The report cannot prove a causal relationship, but it can identify accounts where the renewal team should investigate the customer's response.

Retain the underlying customer list and calculation version. When management plans another increase, it can compare the actual prior transition with the forecast rather than assuming all reported expansion represented deeper adoption. Keep exceptions visible so the analysis remains useful even when a complicated bundle cannot be separated into a neat price-and-volume formula.