The $4,200 Bid That Cost Us $18,000
Let me tell you about a project I managed back in Q3 2023. We needed a specialized engineering assessment for a new subway line expansion—the kind of work a firm like Sweco (or their competitors) would bid on. I had three quotes on my desk. Vendor A (a smaller firm) came in at $4,200. Vendor B was $6,500. Vendor C, which was Sweco's regional office, quoted $11,000.
The numbers said go with Vendor A. My gut said something felt off. Turns out my gut was right. That $4,200 bid ended up costing us nearly $18,000 by the time the project was finished. The 'cheap' assessment missed three critical structural constraints that Vendor B had flagged in their proposal. We had to redo the work, delay the tender by 6 weeks, and pay for 2 emergency consultant meetings.
I'm not a structural engineer, so I can't speak to the technical specifics of how the load calculations were wrong. What I can tell you from a procurement perspective is how to spot the difference between a low bid and a smart investment. And that's where understanding a firm like Sweco's pricing—and your own hidden costs—becomes critical.
The Surface Problem: Everyone Thinks 'Lowest Bid = Best Value'
If you've ever managed a budget for a data center build, a hydrogen plant feasibility study, or an energy retrofit, you know the pressure. Your CFO wants cost savings. Your board wants on-time delivery. You look at three quotes, pick the cheapest, and feel like a hero.
But here's the reality: in 60% of my projects over the past 6 years, the lowest initial quote has had the highest total cost. That's not an exaggeration. I've tracked every invoice, change order, and rework request in our system. The pattern is consistent.
The Deep Reason: You're Not Buying 'Hours,' You're Buying 'Outcome'
Most procurement people (including me, early on) make the same mistake: they compare price per hour. Sweco's rate might be $180/hour, while a smaller consultancy charges $120/hour. Simple math, right? Wrong.
The real issue is scope assumptions. Here's what happens:
- The low bidder assumes a 'standard' project. If your project has nuance—and every infrastructure project does—that assumption is wrong.
- The low bidder doesn't price in risk. They give you a clean number, hoping the change orders will make up the margin.
- Sweco, and firms like it, price in the 'what-ifs.' Their $11,000 quote included 3 site visits, 2 stakeholder review meetings, and a contingency allowance for ambiguous regulatory requirements. That's not padding; that's reality.
In my experience, the 'cheap' vendor's strategy is simple: get the contract, then find every reason to issue a change order. The $4,200 bid becomes $4,200 + $2,500 for 'unforeseen site conditions' + $1,800 for 'additional coordination' + $9,500 for 'rework of original assumptions'.
To be fair, I get why people go with the cheap option—budgets are tight. But the hidden costs add up fast.
The Cost of Not Seeing the Big Picture
What's the real cost of choosing the wrong vendor? It's not just the direct overrun.
Consider this: for a recent energy system feasibility study (similar to what Sweco's hydrogen division might do), we needed stakeholder alignment across 5 departments. The low-bid firm delivered a technically correct report—on time, on budget. But they hadn't interviewed the operations team. The report recommended a solution that Operations couldn't implement. We didn't find out until 3 months later, when the report's recommendations were being used in a board presentation.
That 'on time, on budget' study cost us 4 months of rework, 2 emergency board meetings, and a significant loss of credibility with our own operations stakeholders. The total cost of that 'cheap' study was probably 5x the original bid, when you factor in management time and lost momentum.
That's not an indictment of small firms. Some of my best vendor relationships are with small consultancies. But the decision can't be made on hourly rate alone.
The 'Cheap' Option Often Costs You Your Reputation
And then there's the invisible cost: how the stakeholders perceive you. As a procurement manager, I've learned that my internal reputation is tied to project outcomes. A 'low-cost' procurement that ends in rework and delays is remembered much longer than the 15% budget savings.
The $4,200 story I opened with? The director of engineering still brings it up in meetings. 'Remember when we tried to save money on that assessment? Never again.' That one decision created a 'no-cheap-vendors' policy that now affects every project in our department. The 15% I saved on that one bid cost me influence for years.
So when I look at a quote from Sweco—or any major engineering firm—I don't just look at the line item. I ask: what am I actually buying? Am I buying a PDF report, or am I buying a solution that my team can actually implement? Because those are two very different things, and they have very different price tags.
What I Do Now (It's Not Complicated)
I've developed a simple, unscientific test. When I get three quotes, I ask each vendor three questions:
- "What's the one risk my project faces that I might not have thought of?"
- "How many hours have you budgeted for stakeholder alignment?"
- "What's your process for handling a scope change, and what does that cost look like?"
The cheapest vendor often says, 'We'll handle it when it comes up.' The more established firm—like Sweco—has a defined process, a rate card for changes, and a clear understanding of what's in-scope and what's not. That clarity is worth money.
I'm not saying always pick the most expensive bid. I've had excellent outcomes with mid-range vendors who understood the project deeply. But I am saying: stop comparing hourly rates. Start comparing the expected cost of the outcome.
Prices as of January 2025; always verify current market rates and project-specific assumptions before making any procurement decision.
Discuss this screening note
Share your related duty question and Sweco will connect the topic to your plant conditions.
Ask an engineer