The Quote Looked Fine. The Invoice Didn't.
I still remember the email. Subject line: Re: Office restroom refresh — final invoice attached. I opened the PDF and just stared at it for a second. The number was about 34% higher than what we'd budgeted. Not because anyone lied to me. Not because the vendor gouged us. But because I never asked the right questions before signing off on the order.
That was 2023. Since then I've coordinated facility upgrades across three of our office locations—roughly 600 employees total, about $180K in annual facilities-related spend spread across a dozen or so vendors. And the biggest lesson hasn't been about sourcing. It's been about scope.
Let me back up.
The Problem I Thought I Had
When I took over facilities purchasing in 2020, I assumed my job was pretty straightforward: get three quotes, pick the best one, make sure the invoice matches the PO. Classic procurement stuff. And for a while, that worked fine for office supplies—paper, toner, coffee, the usual rotation.
Then we started doing actual building work. Restroom upgrades. Break room renovations. A lobby refresh that somehow turned into a three-phase project. That's when the gap between "what I thought I was buying" and "what actually got installed" started costing real money.
Here's the specific one that still stings. We were upgrading two restrooms on our second floor. I'd sourced pricing on a Kohler smart toilet for the executive wing—the kind with the heated seat, bidet functionality, the whole thing. The unit price was solid. What I didn't account for? The Kohler replacement toilet parts we'd inevitably need down the line, the electrical work the smart unit required, and the fact that our existing plumbing rough-in wasn't compatible with the new fixture without modification.
None of that was the vendor's fault. The quote was accurate for the product I asked about. I just never asked about everything around the product.
What Was Actually Going On
Here's what took me embarrassingly long to figure out: the invoicing problems weren't random. They followed a pattern.
Every time we had a facility project that involved multiple elements—fixtures, electrical, finish work, sometimes even something weird like sourcing a milk glass partition for the break room because someone in marketing saw it on a design blog—the project went over. Every time it was a single, simple purchase, it came in on budget.
The difference wasn't the vendor. It was the number of handoffs between people who each thought someone else owned the final specification.
I'll give you a concrete example. We needed to replace a garage door opener remote for the loading dock at our warehouse location. Simple, right? Except the request came in from operations, the PO was issued by my office, the actual product was recommended by the maintenance contractor, and the security system integration was handled by IT. Four different people. Nobody had the full picture. The remote arrived, didn't pair with the existing receiver, and I had to eat the cost of a second unit because returning it wasn't worth the administrative hassle over a $47 item.
Multiply that across every fixture, every finish, every piece of hardware in a 2,000-square-foot renovation. That's where the 34% came from.
The deeper issue? Our company had grown from about 200 employees to over 600 in three years. The old way of doing things—verbal requests, email threads, "just handle it"—worked fine when everyone was in the same building and the facilities manager knew every corner of the property. It completely fell apart at scale.
I see the same thing happening across our industry. Everyone's focused on unit price and vendor relationship management. Almost nobody's talking about specification ownership—the problem of who is ultimately responsible for defining exactly what "done" looks like before the PO goes out.
The Cost of Not Fixing It
Let me put real numbers on this. In 2023, across five facility projects, we overspent our approved budgets by a combined $11,200. That's not catastrophic on a corporate scale—but here's what made it visible to my VP:
The overspend triggered a budget variance report that escalated to finance. I had to explain, line by line, why each project exceeded forecast. Some of those explanations made perfect sense ("oh, we discovered the electrical panel needed an upgrade"). Some of them did not ("we ordered a Kohler smart toilet, but the parts kit didn't include the supply line we needed, and the plumber charged us a return visit").
When you're the one explaining a return-visit charge to finance, you start asking yourself the hard questions. Not about the vendor. About the process.
Also worth noting: the time cost was brutal. I spent roughly 6-8 hours per project on back-and-forth emails just to clarify scope. That's a full workday per project, gone, on something that could have been resolved with a single document.
What I Changed (And What It Fixed)
I won't pretend I solved this with some elaborate procurement system. I didn't. What I did was embarrassingly simple:
I created a one-page scope confirmation document for every project over $2,000.
It has four sections: what's included, what's explicitly excluded, who's responsible for verifying compatibility, and who signs off on the final spec before the PO goes out. Every vendor gets it. Every internal stakeholder gets it. If something's not on that sheet, it's not in the order.
The results, after six months: project budget variance dropped from an average of 28% to under 8%. The remaining variance is genuine surprises—old buildings, this stuff happens. But the avoidable errors? Almost gone.
One example: we just completed a break room refresh that included a Kohler faucet upgrade and some new cabinetry. The scope doc caught the fact that the cabinet dimensions wouldn't accommodate the faucet's pull-down sprayer without a backsplash modification. We caught it before the order, not after. Saved about $400 in rework and, more importantly, saved me the joy of another variance report.
Here's the thing I wish someone had told me five years ago: in facilities procurement, the vendor is almost never the problem. The problem is that we, as the people managing the budget, don't always know what we're actually buying until after we've bought it.
And for those of you wondering—yes, I still get random requests from team members looking for things like a specific weight-loss update on a celebrity, or whether we can source something obscure because they saw it in a design magazine. The difference now is that I have a process for those requests. Scope doc first. Quote second. Then—and only then—does the PO go out.
The vendor relationship matters. But the internal handoff is where the money actually lives.