Deal types overview
Dealops supports the three core motions of a B2B revenue lifecycle. Each one is aware of the customer's contract history, so reps never start from a blank page when there's an existing relationship.
| Deal type | When it happens | What the quote starts from | Result |
|---|---|---|---|
| New business | First deal with a customer (or a win-back) | A fresh quote built from your catalog | A new contract and engagement |
| Expansion / amendment | Mid-term change to an active contract | The active contract's current state | An amended contract, co-termed to the existing end date |
| Renewal | The current term is ending | The full end-state of the prior contract | The next contract in the chain |
New business
A new business deal establishes the relationship: the first contract under a new engagement. Reps build the quote from the catalog with full pricing guidance — list prices, target prices, and discount guardrails — and can model any supported structure from day one: tiered usage pricing, multi-year ramps, minimums, and bundles.
There's nothing special to configure for new business; it's the baseline flow described in The quote lifecycle.
Expansion and amendment
Expansions and amendments modify a contract that's already running — adding products, increasing commitments, or renegotiating pricing mid-term. They live inside the same contract as the original deal, and by default they co-term: new line items align to the existing contract's term so everything renews together.
Renewal
A renewal starts the next contract term. Dealops seeds the renewal quote from the true end-state of the expiring contract — the original deal plus every expansion signed during the term — and applies your configured renewal rules (which products carry forward, which get substituted, which drop). Renewals support everything new business does, including re-ramping commitments for the next multi-year term.
See Renewals.
How deals chain together
A typical enterprise relationship looks like this:
Contract 1 (New Business, 12 mo)
├── Expansion: +1 product, month 4
└── Expansion: commitment increase, month 9
Contract 2 (Renewal, 24 mo) ← seeded from Contract 1 + both expansions
└── Expansion: +2 products, month 6
Contract 3 (Renewal, ...) ← seeded from Contract 2 + its expansion
Each renewal compounds the relationship's history. Because Dealops tracks the chain natively, reporting on net expansion, carry-over versus new ARR, and lifetime contract value is automatic — and the next renewal is always staged and ready before the current term ends.
Renewing before the current term ends is fully supported: the new contract records an effective start, and the prior contract's value is truncated accordingly in lifetime metrics.