Author: Ethan Garonzik, CEO & Founder of Vendori

CPQ, or configure, price, quote software, helps SaaS sales teams turn subscription terms into accurate, approved quotes. It brings together products, quantities, recurring prices, contract dates, and discount rules. When connected to subscription and billing systems, it also supports the information needed for expansions, amendments, and renewals.

That sounds straightforward until a prospect asks for a three-year agreement, a gradual seat rollout, and a discount that only applies in year one.

Sales wants to send the proposal today. Deal Desk needs to check the exception. Finance needs to know what will be billed each year. And RevOps needs to make sure the deal can survive the next change.

Subscription CPQ gives those decisions a repeatable process. Here’s how that process should work, from the first quote through renewal.

What does CPQ need to capture for a SaaS subscription?

A subscription quote needs to describe what the customer gets, what they owe, and how those terms change over time.

That includes the package and add-ons, licensed quantities, service dates, pricing periods, discounts, and billing frequency. It may also include a committed usage allowance, overage rates, or a one-time implementation fee.

The relationship between those details matters. A three-year term with annual invoicing has a different commercial structure from three separate one-year commitments. A discount that expires after 12 months needs an end date. A price quoted per user, per month needs to be calculated against the correct quantity and service period.

When those details live in free-text notes, someone has to interpret them later. A well-configured CPQ captures them as usable deal data.

How does subscription CPQ work from quote to renewal?

1. Configure a package the customer can actually buy

The sales rep starts with the customer’s requirements and selects the appropriate products, quantities, and term.

Configuration rules help make those choices valid. An add-on might require a particular edition. A bundle might already include premium support. An enterprise package might have a minimum seat commitment.

For example, imagine a SaaS customer buying a platform subscription with 60 seats in year one and 90 seats in years two and three. They also need a one-time onboarding service.

CPQ should let the rep capture that structure clearly. The platform, seat ramp, and onboarding fee each need the right pricing and dates.

For RevOps, this is also an administration question. When the business introduces a new package, who can update the rules, and how are those changes tested?

2. Calculate recurring pricing across the agreement

Subscription CPQ applies the pricing model and commercial rules to each part of the deal.

Those rules might cover per-seat pricing, volume tiers, platform fees, or negotiated annual increases. A ramp deal needs separate quantities or prices for each period.

Consider this illustrative agreement. The seat price is $100 per month, annual invoicing is in advance, and a 10% discount applies to seats in year one only.

The total committed charges are $321,800, excluding taxes and any later changes. The first-year discount expires, the seat count increases, and onboarding is charged once.

Those are three separate rules the quote needs to preserve. Finance should be able to understand the schedule without opening the spreadsheet used to build it.

3. Route exceptions to the right approvers

Once the deal is priced, CPQ checks it against the company’s approval policies.

A standard quote might proceed immediately. A larger discount, nonstandard payment term, or special cancellation provision could require additional approval.

The useful question is how precisely those rules work. If the rep discounts onboarding, does the whole subscription need another review? If an approved quote changes, which changes trigger reapproval?

Deal Desk needs to see the exception, its financial effect, and the version being approved. Sales needs to know who has the quote and what is holding it up.

4. Generate the quote and hand off the accepted terms

CPQ turns the approved deal into a customer-facing quote or order form. Products, pricing periods, and commitments should be understandable to the buyer.

After acceptance, the agreed terms need to reach the systems that maintain subscriptions, deliver service, and produce invoices.

CRM tracks the commercial relationship and opportunity. Billing needs the charge schedule. The subscription record needs the products, quantities, and effective dates.

A reliable handoff connects those records so teams can trace the billed subscription back to the accepted agreement. Read more about defining those responsibilities in CPQ and Billing.

5. Handle changes during the subscription

Now suppose the customer needs 15 additional seats halfway through year one.

The amendment needs to establish the start date, applicable price, and end date. It also needs to resolve what happens to the original ramp.

Do the 15 seats increase the year-two commitment from 90 to 105? Or does the customer still move to 90 because the expansion simply brought part of the rollout forward?

Either outcome could reflect the negotiated agreement. The system needs to capture the accepted decision.

Co-terming can align the added seats with the existing subscription end date. Upgrades and downgrades need their own rules for eligibility, timing, and any credits.

These changes should remain connected to the customer’s subscription history. For the detailed mechanics, see our guide to CPQ amendments, co-terming, upgrades, and downgrades.

6. Build the renewal from the current agreement

At renewal, the starting point should reflect accepted changes throughout the subscription.

For our example customer, that means checking the final seat commitment, active products, negotiated renewal terms, and any scheduled changes. The onboarding fee should stay out of the recurring renewal charges.

If the renewal quote was created before the latest amendment, the workflow needs to identify that mismatch. It should make clear what must be refreshed and whether anyone needs to review the revised offer.

This is a useful demo scenario because it tests how the system handles transactions that overlap in time.

How does CPQ handle usage-based SaaS pricing?

For usage-based subscriptions, CPQ captures the commercial terms of consumption. Those can include a base fee, included usage, a minimum commitment, and tiered overage rates.

The usage metering and billing systems then need to measure consumption and apply the accepted terms. Confirm which product performs each function when evaluating vendors.

For an AI product, for example, the quote might include a monthly platform fee, an allowance of processing credits, and a rate for additional credits. The agreement must explain when the allowance resets and whether unused credits carry over.

Ask a vendor to show how those terms move from the quote to the invoice calculation. Pay particular attention to a rate or allowance that changes during the contract.

When does a SaaS company need subscription CPQ?

The need becomes clear when recurring deal work consistently requires manual intervention.

Sales may rely on a pricing spreadsheet that only one person understands. Deal Desk may rebuild similar ramp quotes every week. Finance may ask for clarification on each signed order form. Customer Success may struggle to establish what an account should renew.

These patterns give you a practical starting point for requirements. Gather a few recent deals and identify where people had to calculate, interpret, or re-enter information.

Then evaluate CPQ against those specific tasks.

What should RevOps ask to see in a CPQ demo?

Bring a deal with enough history to test the full process. Include the initial sale, a change during the term, and a renewal.

Ask the vendor to demonstrate:

• A multi-year ramp with a discount that expires after year one.

• An expansion that affects future committed quantities.

• A downgrade scheduled for renewal.

• An amendment made after a renewal quote already exists.

• A pricing-rule update performed by the person who would maintain it.

For each step, establish what the platform handles automatically, what depends on an integration, and what a person must complete.

That walkthrough will help Sales, Deal Desk, and Finance assess the same workflow together.

See how Vendori handles your subscription deals

Vendori provides no-code CPQ for SaaS, AI, and B2B technology teams, with capabilities for pricing, approvals, and subscription changes. Its guided selling experience supports expansions, upgrades, and renewals.

Bring a real deal to the conversation. The phased rollout, the negotiated bundle, or the amendment your team keeps rebuilding is a useful place to start.

>> Book a Vendori demo to explore how your team could manage the initial quote and the changes that follow.

About the author

Ethan Garonzik is the Founder & CEO of Vendori. Before founding Vendori, he held finance and operations roles at enterprise technology companies and led global Deal Desk and pricing teams responsible for more than $3 billion in annual revenue. His experience informs Vendori’s approach to complex pricing, subscription quoting, and revenue operations.

Learn more about Ethan.