The Synthesizer
Vol 24
Your Customer's Contract Will Change Before Renewal. Can Your Billing Follow It?
Welcome back to The Synthesizer, where we unpack the decisions shaping modern revenue and billing in Quote-to-Cash systems.
Last month we looked at how a commercial decision travels from the quote to the invoice. That edition assumed the deal stays the way it was signed.
Increasingly, it does not.
Customers now expect to move spend between seats and credits, raise or lower usage limits, and change how they pay, all while the contract is still running. Some of the largest software vendors have just made those changes self-service.
Every one of those changes has to be reflected in the contract, the entitlements, the bill, and the revenue schedule. Most Quote-to-Cash environments were designed to handle change at renewal.
In This Edition
- Why vendors are building mid-term change into the contract itself
- What a single mid-term change touches across Quote-to-Cash
- Where mid-term changes most often break
- The question leaders should ask before offering contract flexibility
The Contract Is No Longer Fixed at Signing
In October, two of the most widely used business software platforms made mid-term change part of how they sell.
HubSpot now lets customers swap seats for credits, or for another seat type, on their own without waiting for renewal. It also turned on spend caps by default, set up to 50% above a customer's monthly credits, and added a choice between flat-rate credit packs and pay-as-you-go billing.
HubSpot's reasoning is worth reading closely. A contract reflects what the business needed when it signed. Then priorities shift, and the contract no longer matches the work.
Microsoft is moving in the same direction. From December 1, new Microsoft 365 Copilot Business licenses bought through partners will have usage-based billing switched on by default, with a spending limit of 4,000 Copilot Credits per user per month that admins can adjust. Each of those contracts will carry a fixed seat line and a variable meter from day one.
The broader market data points the same way. In Kyle Poyar's 2026 State of B2B Monetization survey of 230 software companies, hybrid pricing rose from 25% of respondents a year earlier to 37%. 29% already have AI credits in their pricing, and another 33% plan to add them within 6 to 12 months.
Seats, credits, caps, and meters inside one agreement give customers room to adjust. They also give every downstream system more to keep in sync.
What One Change Touches
From the customer's side, swapping five unused seats for credits is a few clicks.
Behind those clicks, the change has to land correctly in several places:
The contract: records the amendment and its effective date.
Entitlements: remove the seats and grant the credits.
Pricing: determines what the unused seat value converts to, and how the partial period is prorated.
The credit balance and cap: reflect the new allowance and the limit that governs it.
Billing: applies the new terms from the right date forward.
Revenue: reflects the change in the recognition schedule.
That last step is easy to overlook. Under ASC 606, each change to scope or price raises a contract modification question, and a change affecting obligations not yet delivered can shift when revenue is recognized. Credits that expire unused add another layer: that breakage is recognized in proportion to how customers use their rights.
One change from the customer becomes six updates across the business. Multiply that by every customer who can now make changes on their own, at any time.
Where Mid-Term Changes Break
The failure points tend to show up in the same places.
- Amendments made outside CPQ. A change agreed by email or entered directly in billing never reaches the contract record, so the next renewal quote starts from the wrong baseline.
- Caps enforced in the product but not in billing. The product stops usage at the limit, while billing rates against a different number. The customer sees one figure and the invoice shows another.
- Conversions no system fully records. The original seats, their converted value, and the resulting credits live in different systems, and no single record connects them.
- Expiring credits Finance never sees. Credits reset or lapse in the product, while the deferred revenue tied to them stays on the books until someone reconciles it by hand.
None of these are new problems. Self-service change makes them happen more often, and with less human review in between.
Poyar's survey adds one more signal: companies with hybrid pricing are generally the happiest with their model, yet struggle to explain it to customers. An invoice that reflects three mid-term changes is harder still to explain.
The Question for Leadership
The market is treating this as a serious systems problem. In October, Intuit agreed to acquire Sequence, a revenue management platform built to price, bill, and collect on revenue tied to consumption, usage, seats, and milestones. Sequence's CEO described revenue management as "the most fragmented workflow in the back office."
Before offering customers more flexibility mid-contract, leadership should be able to answer:
Can we change a live contract without opening a ticket?
Does every system that acts on the contract see the change at the same time?
Can Finance explain the next invoice, and the revenue behind it, without rebuilding the deal history?
If the answer to any of these depends on a specific person or a spreadsheet, the flexibility being offered to customers is being absorbed manually by the teams downstream.
Our Perspective
Contract flexibility is becoming a selling point, and customers will come to expect it from every vendor they buy from.
The companies that offer it well will be the ones whose Quote-to-Cash architecture treats an amendment as a normal event. That means one owner for the commercial rule, one record of what changed and when, and a clear path from that record into entitlements, billing, and revenue.
Where that architecture is missing, each new form of flexibility adds another set of exceptions for Sales Ops, Billing, and Finance to manage by hand.
The pricing conversation has moved quickly this year. The conversation about what happens to a contract after it is signed needs to catch up.
Where We Come In
Before introducing seat-to-credit swaps, spend caps, or mid-term pricing options, leaders need to know whether their environment can carry a contract change from the customer's request through to the revenue schedule.
We assess how amendments move across CPQ, contract management, entitlements, usage, billing, and revenue recognition today. That shows where a change is re-entered by hand, where systems disagree on what the customer bought, and where Finance loses the trail.
The goal is to make change to a live contract routine for the business, so offering customers flexibility does not add work for the teams who run revenue.