Closing a deal feels like the finish line. In a subscription business, it is closer to the starting line. The customer signs, and then real life begins: they add users, they upgrade, they want to pause one product and expand another, and eventually their term comes up for renewal. The deal you signed is rarely the deal you end with. Managing that drift is, in my experience, the genuinely hard part of revenue. This is where contracts and amendments earn their place.
Let me explain how Salesforce handles change after the handshake.
What a contract is
A contract is the binding record of the agreement between you and your customer. Where the order captured what was sold, the contract governs the relationship over time: the term length, the start and end dates, the renewal terms, and the commitments both sides made.
If the order is the moment of yes, the contract is the agreement that yes lives inside. It is the object that says “this customer has these products, at these prices, for this period.” For a one-time purchase you might barely think about it. For a subscription, the contract is the spine of the whole relationship, because everything that changes later changes relative to it.
The order records what was sold once. The contract records what is true over time, and over time is where revenue actually gets complicated.
Why change management is the hard part
Here is the truth that surprises newcomers. Selling something new is relatively easy to model. Changing something that already exists, mid-term, without losing track of history, is hard. That is what amendments are for.
An amendment is a change to an active contract during its term. The customer started with 50 user licenses in January; in April they need 75. You do not tear up the contract and start over. You amend it. The amendment adds 25 licenses, prices them correctly, often prorates them for the remaining months, and keeps the original contract intact as the source of history.
Amendments handle situations like:
- Adding seats or quantities mid-term.
- Upgrading to a higher tier or a more expensive product.
- Downgrading or removing products the customer no longer wants.
- Co-terming, so new additions end on the same date as the original contract.
The difficulty is that every one of these has to stay consistent. The new quantity must flow to billing so the customer is invoiced correctly. The proration has to be exact. The contract has to reflect the new reality while preserving what came before. Get one of these slightly wrong and the customer is billed for the wrong amount, which is the fastest way to lose their trust.
This is the part of revenue where small details matter most. A teacher knows that the student who struggles is rarely struggling with the big idea; it is one small misunderstood step underneath. Amendments are the same. The concept is simple, “the deal changed,” but the precision required to reflect that change everywhere is where projects succeed or fail.
Renewals, briefly
Eventually a contract reaches its end date, and the question becomes: does the customer continue? A renewal creates a new term, usually based on the existing contract, carrying forward the products the customer already has. Renewals are where recurring revenue is either retained or lost, so they deserve real attention, but the mechanics build directly on the contract you already understand. The renewal looks at the current state of the contract, amendments included, and proposes the next term from there.
This is exactly why amendments must be accurate. The renewal inherits whatever the contract currently says. If the amendments along the way were sloppy, the renewal carries those errors forward into a brand new term.
The e-signature handoff
Contracts and amendments usually need a signature to become binding, and that is where Salesforce hands off to an e-signature tool. The contract document is generated, sent to the customer for signing, and the signed result comes back and is stored against the record. This is one of the most common integration points in the whole Quote-to-Cash chain, and I cover the mechanics of it in DocuSign and Salesforce. For now, just know that the signature is the moment an amendment stops being a proposal and becomes part of the binding agreement.
Where contracts sit in Quote-to-Cash
Contracts sit in the second half of the journey, after the order and feeding directly into billing. The order says what was sold; the contract holds the ongoing truth; and billing reads that truth to generate invoices. Because billing follows the contract, every amendment must update the contract accurately, or the invoices go wrong.
Contracts are where a deal stops being an event and becomes a relationship. Learn to manage change here, and the rest of recurring revenue becomes far less intimidating.
Your next step
Follow the journey forward and sideways with these:
- Quote-to-Cash Explained Simply
- From Quote to Order
- Billing Basics: Turning Contracts into Invoices
- DocuSign and Salesforce
Or browse everything in the Revenue Cloud category.