Why does industry often overlook the very attractive benefits shown in a pricier proposal, choosing instead a low-cost solution without that benefit?
Who hasn't heard the objection "your proposal is more expensive than the competitor's"? That line is often said right after acknowledging the benefits the pricier proposal delivers. The return on investment is calculated, demonstrated, sometimes even validated by the client's own engineering team. Even so, the final decision goes to the lowest-price supplier.
In our experience, this happens for several reasons.
Price Is Verifiable. ROI Is a Promise.
Price is spelled out in the proposal, comparable line by line between proposals. ROI depends on assumptions — current availability rate, projected energy cost, actual equipment lifespan — and those assumptions require technical trust in whoever calculated them. For a buyer without the time or tools to audit each assumption, the lowest personal-risk path is to pick the number that doesn't require interpretation.
This isn't negligence — it's a well-calibrated risk calculation within a process where the error of accepting a projected saving that doesn't hold up costs the buyer's career more than the error of paying less and living with a plant that keeps running, even if suboptimally. Rarely is anyone held accountable later for choosing the cheaper option. The pricier option that didn't deliver exactly as projected — that gets noticed.
The Buyer Often Never Sees the Result
In industrial water systems, the gain from a good treatment program shows up in different budget lines than the one where the cost is booked. The chemical program and the consulting service enter as an immediate operating expense, under procurement or utilities. The energy savings, the lower outage frequency, the gain in plant availability show up in other areas' indicators, months later, and frequently without anyone connecting cause and effect.
Whoever signs the purchase is evaluated on budget. Whoever benefits from a pricier proposal — but with real gains — is evaluated on other indicators, in another cost center. In industrial systems this problem is compounded by the CAPEX/OPEX split: the efficiency gain often isn't even measured as a return on the water treatment investment — it's absorbed as "natural improvement" in operations.
Procurement Scopes Ask About the Product, Not the Problem
Industrial procurement processes are generally structured to compare equivalent items, not to compare different diagnoses of the same problem. When two water treatment proposals start from distinct technical readings of the system — for example, a different scale-inhibitor dosage based on hardness analysis and actual cycles of concentration — the quotation structure tends to level them as if they were the same product in different quantities. The technical differential that justifies the higher price simply has nowhere to be recorded on the comparison spreadsheet.
This explains why consultancies and suppliers that base their proposal on in-depth diagnosis often lose to generic, lower-priced proposals. The decision never actually compares the two diagnoses — it compares the two numbers.
What Actually Changes the Decision
For those selling technical solutions with superior ROI, the implication isn't to push the financial argument harder. It's to recognize that the financial argument, alone, doesn't change the incentive structure of whoever decides. What changes the decision is:
- Bringing the return calculation to the same cost center and the same person who will be held accountable for the plant's availability and efficiency — not just to procurement.
- Making the calculation's assumptions auditable and traceable, with operational data from the client's own system, rather than generic market projections — reducing the perceived risk for the decision-maker.
- Pursuing, whenever possible, a formal indicator that tracks the technical result, so the efficiency gain stops being invisible and becomes attributable to the decision that produced it.
Conclusion
Choosing the lower price, even facing an offer with superior technical returns, isn't the responsibility of just one side. It grows out of two reinforcing habits. The seller relies on the financial argument alone, as if one number were enough to change the decision-maker's incentive structure. The buyer treats an auditable price as synonymous with a correct decision, using a spreadsheet in place of a technical diagnosis.
Sellers need to connect the areas responsible for the cost with the areas that receive the benefits, using traceable assumptions. Buyers need to recognize that a plant running suboptimally, even without a formal error in the decision, is still a cost someone will have to manage later — just outside the spreadsheet that approved the purchase.
Understanding this changes how a technical proposal needs to be built, and also how it needs to be evaluated. Price is verifiable. ROI is a promise.