Software companies are experimenting with pricing models at a pace that would have been difficult to imagine a few years ago.

GitHub Copilot moved its plans to usage-based AI credits, with metered spend above included credits. Salesforce Agentforce has moved through three different pricing models since its launch.

The details are different, but the underlying challenge is the same.

Once a company decides how it wants to charge, that decision has to become something its Quote-to-Cash environment can actually represent, apply, explain, and validate.

That means the pricing decision has to survive multiple handoffs:

Quote → Contract → Usage → Billing → Revenue

These handoffs rarely happen in one system.

Commercial terms may pass through CRM, CPQ, contract management, entitlements, usage platforms, billing, revenue recognition, and reporting before anyone sees the final result.

Every additional handoff creates another place for a commercial rule to be interpreted differently.

Most companies know what their standard pricing looks like.

An enterprise deal might include:

• A negotiated discount
• A minimum commitment
• Promotional credits
• A customer-specific entitlement
• A different overage rate
• Grandfathered pricing
• A renewal incentive

None of these terms are particularly difficult on their own.

The difficulty comes from making sure the same rule exists consistently across every system that needs to act on it.

A discount entered in the quote needs to make it into the contract. The contract needs to inform billing. Billing needs to understand the customer's usage and entitlements. Finance needs to be able to reconcile the resulting charge back to the underlying commercial agreement.

When each team or system holds part of the logic, the original commercial decision can gradually become fragmented.

We saw this firsthand in one enterprise environment where introducing a new pricing model required changes across five integrations and three reporting layers, as described in Volume 16.

The pricing change was straightforward. The architecture required to support it was not.

This is where complex pricing becomes a Quote-to-Cash problem.

Imagine a customer has a usage-based agreement with included credits, a negotiated discount, an overage rate, and promotional credits.

When the invoice arrives, someone should be able to answer a simple question:

Why was this customer charged this amount?

That answer should not require reconstructing the deal from a spreadsheet, checking three different systems, or finding the person who originally configured the account.

The charge should be traceable back through the chain:

The quote: establishes the commercial terms.

The contract: records the agreement.

Usage: records what the customer consumed.

Billing: applies the contracted rates, discounts, credits, and overages.

The invoice: reflects the resulting charge.

Revenue: validates the amount against the underlying agreement.

The further that chain gets from the original commercial decision, the more important traceability becomes.

If a business cannot explain how a charge was produced, it becomes difficult to know whether the customer was billed correctly in the first place.

Behind every charge is a rule.

A discount. A commitment. An overage rate. A credit. An entitlement.

In many environments, that rule is defined in the quote, re-entered in the contract, configured again in billing, and then checked manually by finance.

That creates a deceptively simple question:

Who owns the rule that turns a commercial agreement into a billed amount?

The answer cannot be "everyone."

Each system may have a role in applying the rule, but the business needs a clear understanding of what the rule is, where it is maintained, and how it moves downstream.

That becomes especially important as pricing changes faster.

A pricing model that takes months of coordination to implement may not be a viable pricing model when the business needs to change it every quarter.

The question is not simply whether a billing system supports usage-based, credit-based, or hybrid pricing.

Most modern platforms can represent increasingly sophisticated models.

The harder question is whether the Quote-to-Cash architecture around the billing system can carry those models through the business without losing the commercial intent.

Before introducing another pricing model, leadership should be able to answer:

Can we represent the commercial agreement accurately?

Can we apply the rules consistently across systems?

Can we prove that the resulting charge is correct?

That is the difference between supporting a pricing model on paper and being operationally ready to sell it.

AI is making it easier to imagine new ways to charge customers.

That does not make those models easier to operate.

The companies experimenting with credits, consumption, commitments, and outcome-based pricing are not just changing their price lists. They are introducing new commercial logic into the systems that run their revenue.

The question is whether that logic can survive the journey from what was sold to what was billed.

When it can, pricing becomes something the business can change with confidence.

When it cannot, every new pricing model creates another layer of exceptions, integrations, and manual work for the teams downstream.

Related Reading: Can You Trace a Dollar of AI Revenue End-to-End?

See you next month,

The Synthesizer Team