Save 8 hours per comparisonNo credit card
SpecLens Logo
Procurement decision tree showing when to use should-cost analysis, TCO modeling, or bid leveling
Cost Analysis
May 8, 2026
13 min read

Should-Cost vs TCO vs Bid Leveling: A Sourcing Decision Tree

Three procurement methodologies, three different questions. Should-cost models what a product *should* cost; TCO models lifecycle cost across vendors; bid leveling normalizes received bids onto the same scope. The decision tree for picking the right one.

RK

Rhea Kapoor

Head of Procurement Research, SpecLens

  • 850+
    companies trust SpecLens
  • 99%
    extraction accuracy
  • 8 hrs
    saved per comparison
  • AES-256
    encrypted · GDPR compliant

Key takeaways

  • Should-cost models what a product *should* cost from materials, labor, overhead, and margin — used pre-RFP or against sole-source suppliers.
  • TCO models lifecycle cost across vendors over 5-10 years — used for capital equipment, IT infrastructure, fleet, anywhere acquisition is <60% of lifetime cost.
  • Bid leveling normalizes received bids onto the same scope — used after bids arrive, before the award decision.
  • The three methodologies stack rather than compete: should-cost informs the RFP, bid leveling normalizes responses, TCO selects across normalized vendors.
  • Specification intelligence accelerates each by extracting the structured spec data the methodologies depend on — BoM for should-cost, lifecycle specs for TCO, inclusions/exclusions for bid leveling.

Three Methodologies, Three Different Questions

Procurement leaders routinely confuse should-cost, total cost of ownership, and bid leveling — using one when another would have answered the actual question. The terms get used interchangeably in vendor pitches and procurement conferences, which only deepens the confusion. The reality: each methodology answers a different question, applies to different procurement situations, and produces a different artifact.

This is the decision tree for picking the right methodology — should-cost, TCO, or bid leveling — based on the procurement situation in front of you. Use the wrong one and the analysis answers the wrong question; use the right one and the procurement decision becomes defensible.

Quick Answer: Which Methodology When?

Use should-cost analysis when you need to model what a product or service should cost from raw materials, labor, overhead, and margin — typically before issuing an RFQ or to challenge a supplier's pricing. Use total cost of ownership (TCO) when you need to compare lifecycle cost across vendors over multiple years — including acquisition, operating, maintenance, and disposal. Use bid leveling when you have received bids and need to normalize them onto the same scope before awarding — accounting for inclusions, exclusions, and plug numbers. The three methodologies stack: should-cost informs the RFQ, bid leveling normalizes the responses, TCO selects across normalized vendors.

Should-Cost Analysis — What a Product Should Cost

Should-cost analysis starts from raw materials, labor inputs, manufacturing overhead, and reasonable margin and works upward to a calculated "should-cost" figure for a specific product or service. The methodology is most common in direct-materials sourcing, custom-fabrication procurement, and any category where the buyer wants to challenge a supplier's pricing with first-principles math rather than competitive benchmarking alone.

What it answers: "Is this supplier's quoted price reasonable, given the material, labor, overhead, and margin assumptions we can defend?"

When to use it: Before issuing an RFQ to set internal pricing expectations; during negotiation when a supplier's quoted price exceeds the buyer's benchmark; when the buyer needs leverage in a sole-source situation; when category management requires periodic should-cost refreshes for tracked commodities.

Inputs: Bill of materials with material grade and weight; labor hours by operation with standard hourly rates; manufacturing overhead percentages; SG&A and margin assumptions; freight, packaging, and import duties.

Output: A modeled should-cost figure (typically a range, not a single number) that becomes the buyer's internal benchmark.

For the deeper methodology, see the should-cost analysis guide.

Total Cost of Ownership (TCO) — Lifecycle Cost Across Vendors

TCO methodology calculates the complete lifecycle cost of acquiring, operating, maintaining, and disposing of a product or service over a defined analysis period. The methodology is most common in capital equipment procurement, IT infrastructure decisions, fleet evaluations, and any category where the acquisition price is materially smaller than the lifetime cost.

What it answers: "Which vendor delivers the lowest total cost over the relevant lifecycle, accounting for everything beyond the acquisition price?"

When to use it: Capital equipment procurement (servers, MRI scanners, CNC machines, EV fleet); IT infrastructure (cloud vs on-premise, server refresh, storage refresh); facilities equipment (HVAC, generators, building automation); any decision where the acquisition price is less than 40% of the 5-to-10-year lifetime cost.

Inputs: Acquisition cost; annual operating cost (energy, consumables, labor); annual maintenance cost (preventive plus corrective); annual support and licensing; end-of-life disposal cost; expected residual value; analysis period; discount rate.

Output: Per-vendor TCO over the analysis period, typically expressed in net-present-value terms.

For the full methodology and a free calculator, see the TCO calculator guide and the free TCO calculator.

Bid Leveling — Normalizing Bids Onto the Same Scope

Bid leveling normalizes received bids so that competing proposals can be compared apples-to-apples on the same scope. The methodology is most common in construction subcontractor selection, custom-equipment procurement, and any category where bids arrive in different formats with different inclusions and exclusions.

What it answers: "Now that we have the bids, which one represents the best value on the actual scope we need delivered?"

When to use it: After bids are received, before the award decision; whenever bids arrive in different formats; whenever bidders propose "or-equal" substitutions; in construction subcontractor selection; in equipment procurement where bidders quote different configurations.

Inputs: Per-vendor as-bid pricing; per-vendor inclusions and exclusions narrative; plug numbers for missing scope; non-price factor scoring (schedule, references, safety, financial stability).

Output: A leveled comparison matrix showing as-bid total, plug-number adjustments, leveled total, and non-price scoring per vendor.

For the full bid-leveling workflow, see the bid leveling guide.

The Decision Tree

Use this decision tree to pick the right methodology:

  1. Have you received vendor bids yet?
    • No → Are you trying to model what the product should cost from first principles? Yes → should-cost analysis. Are you trying to forecast lifecycle cost across vendors? Yes → TCO modeling.
    • Yes → Move to question 2.
  2. Are the bids comparable as-received (same format, same scope, same units)?
    • NoBid leveling first, then TCO if lifecycle cost matters for the decision.
    • YesTCO if lifecycle matters; direct comparison if not.
  3. Is the acquisition price the dominant component of total cost (>60% of 5-year cost)?
    • Yes → Bid leveling and direct comparison are usually sufficient; skip TCO.
    • No → TCO is mandatory; lifecycle cost will dominate the decision.

How the Three Methodologies Stack in Practice

The three methodologies are not alternatives — they are sequential stages in a mature procurement workflow. Best-in-class procurement teams use all three on different categories.

Stage 1 — Pre-RFP (should-cost): Before issuing the RFQ or RFP, the procurement category manager runs a should-cost analysis to set internal pricing expectations. This becomes the benchmark against which incoming bids will be evaluated.

Stage 2 — Post-bid (bid leveling): Once bids are received, the procurement team levels them onto the same scope using inclusions/exclusions narrative and plug numbers. The leveled total becomes the comparable apples-to-apples figure.

Stage 3 — Award decision (TCO): If lifecycle cost matters (capital equipment, IT infrastructure, fleet), the leveled bid totals feed into a TCO model that projects 5-to-10-year cost per vendor. The lowest TCO — not the lowest leveled bid — wins the award.

Skipping any stage produces a worse decision. Skip should-cost and the buyer accepts inflated supplier margins because they have no benchmark to push back. Skip bid leveling and the lowest as-bid price wins on paper while the project absorbs the excluded scope as change orders. Skip TCO and the cheapest acquisition wins while the lifetime maintenance, energy, and disposal costs dominate the actual outcome.

Common Misuses

Misuse 1: Should-Cost Where TCO Was the Question

A procurement team running should-cost on an MRI scanner asks "what should this scanner cost from materials and labor?" The answer is irrelevant because the dominant cost over the 10-year scanner lifecycle is service contracts, energy, and operator training — not the manufacturing cost. TCO was the right methodology.

Misuse 2: TCO Where Bid Leveling Was the Question

A construction GC running TCO across three subcontractor bids asks "which sub has the lowest 10-year cost?" The bids haven't even been leveled yet — vendor A excluded mobilization, vendor B excluded warranty extension. The TCO model rests on incomparable inputs. Bid leveling was the precondition.

Misuse 3: Bid Leveling Where Should-Cost Was the Question

A category manager facing a sole-source supplier with no competing bids cannot do bid leveling — there are no bids to level. Should-cost analysis is the only methodology that gives the buyer leverage in this situation. Building a should-cost model lets the buyer challenge the supplier's pricing with first-principles math.

How Specification Intelligence Connects the Three

Specification intelligence platforms do not replace should-cost, TCO, or bid leveling — but they accelerate each by extracting the structured spec data the methodologies depend on.

  • Should-cost: The platform extracts the bill of materials, material grades, and labor inputs from supplier-provided documentation, accelerating the input-collection step.
  • TCO: The platform extracts vendor-claimed power consumption, maintenance schedules, warranty terms, and end-of-life specifications from QuickSpecs and data sheets, accelerating the input-collection step.
  • Bid leveling: The platform reads bid documents, identifies inclusions and exclusions in narrative form, and surfaces the apples-to-apples comparison automatically.

For the deeper category framing, see what is specification intelligence; for the workflow that pairs all three methodologies with AI, see how to compare vendor proposals with AI.

Templates and Tools

SpecLens publishes free templates and calculators for each methodology:

Pick the Right Methodology for Your Next Decision

The three methodologies are not alternatives — they stack. Should-cost informs the RFP; bid leveling normalizes the responses; TCO selects across normalized vendors. Use all three on capital procurement; skip TCO when acquisition price dominates lifecycle cost; skip should-cost when the category is well-benchmarked. Try the workflow on your next RFP using SpecLens for the spec-extraction step, the free TCO calculator for the lifecycle model, and the quote comparison template for the bid-leveling step.

References

  1. 1.ISM — Institute for Supply Management — ISM — Total cost of ownership methodology and procurement cost analysis (2025)
  2. 2.CIPS — Chartered Institute of Procurement & Supply — CIPS — Global Standard for Procurement & Supply (2025)
  3. 3.Construction Industry Institute — Front End Planning — Construction Industry Institute Front End Planning — 6-25% cost variance (2025)

Frequently Asked Questions

Ready to Transform Your Procurement Process?

Try SpecLens today and experience AI-powered specification comparison. Save time, reduce errors, and make better purchasing decisions.