The quote in front of you is one number with a discount attached to it. Underneath that number is a cost structure that determines whether the price is stable, and nobody is going to show it to you.

You can infer the shape anyway. Not the numbers, the shape, which is enough to tell you which parts of your price are durable and which parts are being subsidized until renewal.

A price that was never going to hold

Composite from a few knowledge-work evaluations: a professional services firm, a couple of thousand fee earners, document review and drafting support across several practice areas.

They negotiated hard and negotiated well. Illustratively, something like fifty-five percent off list, three-year term, annual true-up on volume. Procurement was pleased and had every right to be.

Adoption then grew, which was the entire point of the purchase. By year three the firm was running several times the volume it had modeled. At renewal the price roughly tripled, and the argument for the increase was the firm’s own success.

Nobody was deceived here. The original number had been an acquisition price, priced to win a logo in a competitive segment, and the vendor had been reasonably transparent that volume growth would change things. What nobody on the buying side had done was ask which parts of the price moved with usage and which parts didn’t. They’d negotiated the total, which is the one number that told them least.

Four layers under the number

Every price in this category sits on the same four layers. You can’t see the values. You can reason about the behavior.

Compute. Moves with your usage. Falls over time as models get more efficient, but never to zero, and it doesn’t fall on a schedule anyone can commit to. This is the layer that makes a flat price unstable when your volume grows.

The product around it. Their engineering, interface, and everything that makes the underlying capability usable. Fixed cost, spread across all customers, so the per-customer cost falls as they grow. Cheap for them to be generous with, which is why feature access is usually the easiest concession to win.

Cost to serve you specifically. Implementation, your custom connector, your security review, the quarterly business review, the named support contact. Large, lumpy, and mostly independent of how much you use the product. This is why a small contract often has worse unit economics than it looks and why vendors push hard on term length for smaller accounts.

Acquisition. Sales, marketing, and the discount itself. Recovered across the expected life of the account, which is precisely why the term matters more to them than the annual figure. A three-year commitment at a deep discount can be a better deal for them than one year at list.

Reading the concessions

What a vendor gives away easily and what they defend tells you where their cost sits. This is the most reliable instrument you have, because it works on behavior rather than on claims.

What they do	What it suggests
Deep discount for a longer term	Acquisition cost is being amortized. Expect a reprice at renewal.
Feature tiers collapse easily	The product layer is cheap to them. Ask for more of it.
Accepts a cap on unit price, resists a cap on volume	Their per-unit cost is falling and they expect to grow into it. Good sign for you.
Accepts a volume cap, resists a price cap	The reverse. Your unit cost is exposed.
Resists both, offers a bigger headline discount	The discount is the concession and it expires. Read the renewal terms first.
Implementation fee is non-negotiable	Cost to serve is real and they’re not absorbing it. Usually honest, sometimes a partner margin.

None of these are certainties. They’re priors, and they’re much better than the prior you get from the proposal document, which is written to be read in one direction.

The question that gets you the shape

There’s one question that does most of the work, and it isn’t hostile, which is why it gets answered:

Which parts of this price move if our usage doubles, and which parts don’t?

A vendor with a considered pricing model answers it in a couple of minutes and often quite openly, because it’s a question about structure rather than about margin. A vendor who can’t answer it is either not close to their own economics or is hoping you won’t model it, and both are worth knowing.

Then take it further and ask for the same quote at half your projected volume and at double it. Three points on a line show you the shape: whether your unit price improves with scale, stays flat, or quietly worsens past a threshold you hadn’t spotted.

I’ve had a vendor decline to produce the double-volume quote on the grounds that it was hypothetical. It was hypothetical. It was also the volume in their own business case for us, which they had presented the previous month.

Where the subsidy lives

A price below the vendor’s cost to serve you isn’t a victory. It’s a repricing with a date on it.

That doesn’t make it a bad deal. Being an early customer in a category that’s subsidizing growth is often genuinely good value, and the subsidy is real money you get to keep for the term. The mistake is treating the introductory price as the price and building a three-year business case on it.

So model two lines. What you’ll pay under the contract, and what you’d pay at something closer to list with your projected volume. If the business case only works on the first line, you’ve bought a discount rather than a capability, and you’ll find that out at renewal when your usage is embedded and your alternatives have narrowed.

One thing to do differently

Ask for the same quote at half your projected volume and at double it, before you negotiate the headline number.

It takes them a day. It tells you more about what you’re signing than any amount of discussion about the discount, and it moves the conversation from a single number you can argue about to a structure you can plan against.