A municipality buys 500 office chairs. Bidder A offers them at EUR 89 each. Bidder B offers them at EUR 145 each. Lowest price wins. Bidder A gets the contract.
Three years later, 200 of Bidder A's chairs have broken mechanisms. The municipality either replaces them (another procurement, more time, more money) or repairs them at EUR 40 each. Meanwhile, Bidder B's chairs were designed for 10-year institutional use and came with a 7-year warranty.
Five-year cost: Bidder A = EUR 44,500 + EUR 8,000 in repairs + staff time for a new procurement. Bidder B would have been EUR 72,500, full stop.
This story repeats itself across public procurement every single day. Different products, same pattern.
What lifecycle costing actually means
The concept is simple: total cost of ownership includes everything, not just the purchase price.
Acquisition costs. Operating costs. Maintenance and repair. Energy consumption. Training. Integration with existing systems. Disposal at end of life. Environmental externalities, if you want to be thorough.
For an IT system, this might mean: server costs + licensing + support contracts + migration from the old system + staff training + eventual decommissioning and data migration to whatever comes next.
For a vehicle fleet, it's: purchase price + fuel or electricity + insurance + maintenance + downtime + residual value at disposal.
For a building contract, it's: construction cost + energy efficiency over 30 years + maintenance schedule + material durability + demolition/recycling costs.
The purchase price is often less than half of the total lifecycle cost. For complex systems, it can be less than a third.
The numbers on adoption
Despite EU Directive 2014/24/EU explicitly allowing and encouraging lifecycle costing, adoption remains low.
Research shows that 64% of public authorities still use purchase cost as their primary evaluation criterion. Only 6% predominantly use lifecycle costing or total cost of ownership. The remaining 30% use some hybrid approach.
In Latvia, where 73% of contracts go to the lowest bidder, lifecycle costing is even rarer. The Valsts Kontrole audit in December 2024 called the system "complicated and inflexible" — and lifecycle costing is one of those areas where complexity deters use.
Why procurement teams don't use it (even when they want to)
Talk to procurement professionals off the record and most of them understand that lowest purchase price is a bad metric. They know it leads to worse outcomes. They've seen the consequences. So why don't they use lifecycle costing?
Three reasons, all practical:
It requires technical knowledge. Calculating the lifecycle cost of an IT system requires understanding maintenance cycles, scalability implications, integration costs, and technology obsolescence. Calculating the lifecycle cost of a construction project requires engineering knowledge about material durability, energy performance, and maintenance schedules. Procurement teams are generalists managing dozens of sectors. They can't be domain experts in all of them.
It requires data that bidders don't always provide. Lifecycle cost analysis needs inputs: expected maintenance frequency, energy consumption figures, warranty terms, expected useful life. If the RFP doesn't ask for this data in a structured way, bidders provide it inconsistently — or not at all.
It's harder to defend against challenges. A lifecycle cost analysis involves assumptions. What discount rate do you apply? What's the expected useful life? How do you value environmental externalities? Each assumption is a potential point of legal challenge from a losing bidder. Lowest price is simple and defensible. Lifecycle cost is correct but arguable.
What this costs in practice
Let me make this concrete with categories where lifecycle costing matters most in public procurement:
IT systems. A lower-cost system with proprietary architecture locks you into one vendor for support, updates, and integrations. Over 5-7 years, the cost of vendor lock-in often exceeds the original price difference. We see this in procurement documents constantly — bidders promising low upfront costs while building in dependencies that ensure expensive renewals.
Energy and infrastructure. A cheaper HVAC system with lower energy efficiency costs more per year in electricity than the price difference would justify. Over the 15-20 year life of the system, the "expensive" option was dramatically cheaper. The EU's push for green procurement and the ESPR regulation are partly about forcing this calculation.
Professional services. A lower hourly rate with less experienced staff produces more revisions, more errors, more supervision time, and longer delivery timelines. The cost per deliverable often exceeds what a more expensive, more experienced team would have charged.
Vehicles. This one is becoming measurable. Electric vehicle procurement increasingly shows lower lifecycle costs than combustion vehicles despite higher purchase prices, once you factor in fuel, maintenance (EVs have far fewer moving parts), and residual value. But if you evaluate on purchase price, the EV loses every time.
How AI makes lifecycle costing feasible
The core problem with lifecycle costing isn't the concept — it's the analysis. Understanding what a bidder is actually committing to, what assumptions are embedded in their pricing, and where the hidden costs lie requires reading technical proposals in detail.
When an AI agent reads a proposal, it can identify maintenance commitments (or lack thereof). It can flag pricing models that front-load low costs but imply expensive renewals. It can compare energy efficiency claims across bidders. It can note warranty terms and what they actually cover versus what they exclude.
A human evaluator doing lifecycle analysis manually might spend 2 days per bidder going through technical and financial proposals to build a comparable cost model. With 5 bidders, that's 10 days — more time than most evaluations get in total.
An AI that reads everything and surfaces the relevant data points for lifecycle comparison makes the analysis feasible. Not automatic — the procurement team still needs to build the model and apply judgment. But the raw material is extracted and organized, which removes the biggest time barrier.
A shift that's coming whether we're ready or not
The EU's direction is clear. The Ecodesign for Sustainable Products Regulation (ESPR), which entered into force in July 2024, will increasingly require environmental lifecycle data for products sold in the EU. The Industrial Accelerator Act's "Made in Europe" requirements add supply chain considerations. Green public procurement criteria, moving from voluntary to mandatory, will embed lifecycle thinking into evaluation.
Within a few years, evaluating only purchase price won't just be suboptimal — it may not be legally compliant for many procurement categories.
Procurement teams that build lifecycle costing capability now — whether through training, tools, or both — will be ahead when these requirements bite. The ones that don't will be doing what they've always done: choosing the cheapest option and hoping for the best.
Hope isn't a procurement strategy.