Should-Cost Model

A should-cost model is an independent, bottom-up estimate of a fair price, built for sourcing and negotiation, not for auditing signed vendor invoices.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Should-Cost Model

A should-cost model is an independent estimate of what a purchase ought to cost, built from underlying cost drivers rather than a vendor's quoted price. Procurement teams build one to have a reference point that does not come from the vendor being evaluated.

On the audit side, a should-cost figure matters less than the contract itself. Once a rate card exists, the invoice should match it exactly, and margin drift is measured against that document, not against a theoretical estimate.

1. What is a should-cost model?

A should-cost model is a bottom-up cost estimate built from a purchase's underlying drivers: raw materials, labor, freight, overhead, and a reasonable margin. Procurement analysts build it independently of a vendor's quote so they have a defensible number to negotiate against. It is used before a contract is signed, during sourcing and negotiation, and is separate from what a signed contract later says an invoice should charge.

The model breaks a price into components rather than treating it as one number. A freight quote, for example, decomposes into distance, fuel, weight, and accessorial charges, each estimated from public or internal data.

2. How does a should-cost model differ from a rate card?

A should-cost model is an estimate produced before negotiation; a rate card is the actual negotiated price list a vendor is contractually bound to. The should-cost model informs what a buyer asks for. The rate card is what an invoice is legally required to match once signed. After signature, only the rate card has enforcement weight; the should-cost estimate becomes a historical reference.

An invoice can undercut a should-cost estimate and still overcharge against the signed rate card, which is the version that governs payment.

3. Where does a should-cost model fit in vendor spend audit work?

A should-cost model fits in sourcing and contract negotiation, not in an invoice audit. Contract compliance work checks invoices against the terms already signed: rate cards, volume tiers, NTE caps, rebate clauses. A should-cost estimate has no contractual standing once those terms exist, so it is not the reference document an audit uses to identify overbilling or margin drift.

This distinction matters most in freight and 3PL audit and contract labor and staffing audit work, where signed rate cards already exist and are the only enforceable standard.

4. When is a should-cost model still useful after a contract is signed?

A should-cost model remains useful at renewal or renegotiation, when a buyer wants to test whether a vendor's current pricing still reflects underlying cost drivers. It is not useful for judging whether a specific invoice complied with the existing contract; that comparison requires the signed rate card, volume tier, and NTE terms, not a recalculated estimate of fair cost.

Rebuilding a should-cost estimate at renewal can reveal whether index escalation misapplied clauses still track real input costs, informing the next negotiation.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

Is a should-cost model the same as a rate card?

No. A should-cost model is an independent estimate built before a contract exists. A rate card is the actual negotiated price list a vendor is bound to once a contract is signed. Only the rate card has contractual enforcement weight.

Who builds a should-cost model?

Procurement or sourcing analysts typically build it during vendor selection or contract negotiation, using cost drivers like labor, materials, freight, and overhead rather than the vendor's quoted price.

Can a should-cost model catch margin drift on an invoice?

No. Margin drift is measured against the signed contract terms, such as a rate card or volume tier schedule. A should-cost estimate has no contractual standing once those terms exist, so it is not the reference an audit checks invoices against.

When should a company build a should-cost model?

Before signing a contract, during sourcing or negotiation, and again at renewal to test whether a vendor's pricing still reflects underlying cost drivers.

Does a should-cost model replace a contract compliance audit?

No. A should-cost model informs negotiation of future pricing. A contract compliance audit checks whether past invoices matched the rate card, volume tiers, and NTE caps already signed. They serve different stages of the vendor relationship.

What inputs go into a should-cost model?

Raw material cost, labor hours and rates, freight distance and fuel, overhead allocation, and an assumed margin, broken out as separate components rather than one bundled price.

Is a should-cost model useful for freight contracts specifically?

Yes, during rate negotiation. Once a freight and 3PL audit contract is signed, the applicable reference becomes the negotiated rate card and accessorial schedule, not the original should-cost estimate.

1. What is a should-cost model?

A should-cost model is a bottom-up cost estimate built from a purchase's underlying drivers: raw materials, labor, freight, overhead, and a reasonable margin. Procurement analysts build it independently of a vendor's quote so they have a defensible number to negotiate against. It is used before a contract is signed, during sourcing and negotiation, and is separate from what a signed contract later says an invoice should charge. The model breaks a price into components rather than treating it as one number. A freight quote, for example, decomposes into distance, fuel, weight, and accessorial charges, each estimated from public or internal data.

2. How does a should-cost model differ from a rate card?

A should-cost model is an estimate produced before negotiation; a rate card is the actual negotiated price list a vendor is contractually bound to. The should-cost model informs what a buyer asks for. The rate card is what an invoice is legally required to match once signed. After signature, only the rate card has enforcement weight; the should-cost estimate becomes a historical reference. An invoice can undercut a should-cost estimate and still overcharge against the signed rate card, which is the version that governs payment.

3. Where does a should-cost model fit in vendor spend audit work?

A should-cost model fits in sourcing and contract negotiation, not in an invoice audit. Contract compliance work checks invoices against the terms already signed: rate cards, volume tiers, NTE caps, rebate clauses. A should-cost estimate has no contractual standing once those terms exist, so it is not the reference document an audit uses to identify overbilling or margin drift. This distinction matters most in [freight and 3PL audit](/glossary/freight-and-3pl-audit) and [contract labor and staffing audit](/glossary/contract-labor-and-staffing-audit) work, where signed rate cards already exist and are the only enforceable standard.

4. When is a should-cost model still useful after a contract is signed?

A should-cost model remains useful at renewal or renegotiation, when a buyer wants to test whether a vendor's current pricing still reflects underlying cost drivers. It is not useful for judging whether a specific invoice complied with the existing contract; that comparison requires the signed rate card, volume tier, and NTE terms, not a recalculated estimate of fair cost. Rebuilding a should-cost estimate at renewal can reveal whether [index escalation misapplied](/glossary/index-escalation-misapplied) clauses still track real input costs, informing the next negotiation. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

Is a should-cost model the same as a rate card?

No. A should-cost model is an independent estimate built before a contract exists. A rate card is the actual negotiated price list a vendor is bound to once a contract is signed. Only the rate card has contractual enforcement weight.

Who builds a should-cost model?

Procurement or sourcing analysts typically build it during vendor selection or contract negotiation, using cost drivers like labor, materials, freight, and overhead rather than the vendor's quoted price.

Can a should-cost model catch margin drift on an invoice?

No. Margin drift is measured against the signed contract terms, such as a rate card or volume tier schedule. A should-cost estimate has no contractual standing once those terms exist, so it is not the reference an audit checks invoices against.

When should a company build a should-cost model?

Before signing a contract, during sourcing or negotiation, and again at renewal to test whether a vendor's pricing still reflects underlying cost drivers.

Does a should-cost model replace a contract compliance audit?

No. A should-cost model informs negotiation of future pricing. A contract compliance audit checks whether past invoices matched the rate card, volume tiers, and NTE caps already signed. They serve different stages of the vendor relationship.

Margin Drift Resources