Skip to main content

Renewals

Renewals are where most quoting tools fall apart: the expiring contract has been amended three times, half the SKUs have been repackaged since the customer first signed, and someone has to reconstruct "what does this customer actually have?" in a spreadsheet.

Dealops treats the renewal as a first-class deal type with its own automation.

Renewals are staged automatically​

When a new business deal or renewal closes, Dealops stages the next renewal immediately: an upcoming contract is created alongside the active one and linked to the renewal opportunity in your CRM. By the time the renewal conversation starts — whether that's 90 days out or a year early — the deal already exists, with full context.

Chained renewals work the same way: each closed renewal stages the next one, indefinitely.

Seeded from the true end-state​

The renewal quote is seeded from the prior contract's cumulative state — the original deal plus every expansion and amendment signed during the term:

  • Products carry forward with their negotiated volumes and pricing structures.
  • Commitment increases are folded in. If the customer committed to $250k and expanded to $400k mid-term, the renewal starts at $400k.
  • Tier structures merge coherently. A product whose tier ladder grew across multiple expansions renews as one clean ladder, not a stack of fragments.
  • Multi-year ramps resolve to where the customer ended up — the renewal starts from the final period's levels, ready to re-ramp for the next term.
  • One-time fees are excluded. Implementation and setup charges from the prior term don't pollute the renewal.
  • Invoicing details carry over, so billing configuration doesn't need to be re-entered.

The seed is a starting point, not a straitjacket — reps can then adjust anything the deal requires: new term length, re-ramped commitments, added or removed products.

Renewal rules for an evolving catalog​

Catalogs change between a deal and its renewal. Dealops lets admins define, per product, what happens at renewal time:

  • Carry forward — the default; the product renews as-is.
  • Substitute — the product maps to a successor SKU (with an ordered list of substitution targets, so retired products land on the right replacement).
  • Drop — the product doesn't carry into renewals (common for one-time or promotional items).

This means a customer who bought a SKU you've since repackaged still gets a clean, current-catalog renewal quote — automatically.

Early renewals​

Renewing before the term ends is fully supported. The new contract takes effect on its negotiated start date, the prior contract is closed early, and lifetime metrics (TCV, ARR trajectory) account for the truncation — no double counting.

What the renewal flow looks like​

  1. The prior deal closes; Dealops stages the upcoming renewal contract and links the CRM renewal opportunity.
  2. A rep opens the renewal quote — products, volumes, tiers, and commitments are pre-seeded from the contract's end-state, with renewal rules applied.
  3. The rep negotiates: new term, re-ramped commitments, expansion items, updated pricing.
  4. Standard approvals, documents, and signature.
  5. On close: CRM writeback, the next renewal is staged, and — for usage-based billing — a new billing contract is provisioned, linked to its predecessor so billing history stays connected. See Billing with Metronome.

Measuring the renewal​

Because Dealops knows the prior contract precisely, every renewal quote reports:

  • Carry-over vs. net-new ARR — what's continuation and what's expansion.
  • Net expansion / contraction against the prior term.
  • Lifetime engagement value across the whole contract chain.
Renewals of ramped deals

A three-year ramp renewing into another three-year ramp is the canonical hard case. Dealops resolves the expiring ramp to its final-period state, seeds the renewal from there, and lets the rep build the next ramp on top. See Ramps & multi-period deals.