Making renewals tell the truth: committed volume, overage and net ARR change on the account

The problem

The play

1. 1
   A revenue-recognition object under the account, not a formula on the opportunity

   The structure is a custom object hanging off the account: a base contract plus monthly true-up rows covering committed volume, usage overage and fees.

2. 2
   Commitments stamped by contract year at close

   New opportunity fields capture the minimum commitment for each of up to five contract years, date-stamped, so current ARR only ever reflects the year actually in contract. Headroom was built past the typical term length on the reasoning that it is cheaper to build headroom than to retrofit it.

3. 3
   Separate the ARR types before netting them

   Upfront, subscription and minimum-commit ARR are tracked as distinct types, each with its own change field. The reason is concrete: a renewal can shrink the subscription while growing the commitment, and an account-level net number hides exactly the movement finance needs to see.

4. 4
   Model renewals as ARR movement, not as contract value

   Recommended splitting renewal opportunity types into flat, expansion and contraction so renewal outcomes become queryable ('where are our renewal expansions this year?'). On a renewal close, the ending current ARR is stamped and the difference is written as a net ARR change by ARR type.

5. 5
   Committed volume and overage move as one pool

   The case finance cared about most: when a renewal raises the committed volume, a corresponding amount of usage overage has to come out, or the variable bucket double-counts.

6. 6
   Automate the entry, not the judgement

   Because the fixed components and the multi-year commitments are all known at close, they flow into the revenue-recognition records automatically when the opportunity closes, the finance owner does not create three entries for three corresponding changes.

7. 7
   Handoff treated as part of the build

   Shipped a monthly-logging screen flow and page layouts, recorded walkthrough videos for the finance team, a bulk-upload template for historical data, and a sandbox validation of the historical ARR backfill against a real sample dataset from the client before anything touched production.

What it moved

From a LeanScale case studyRead the full case study →