I’ve sat across the table for enough vendor negotiations to know the pitch by heart. Three-year payback. Clean energy savings numbers. A slide that makes the decision look obvious.
What’s almost never on that slide: the invoice that shows up in year two for a “custom integration.” The renewal notice with a price increase nobody negotiated. The line item that didn’t exist during procurement because nobody thought to ask about it.
None of that means the vendor lied. The energy savings number is usually real. It’s just not the whole number.
If you’re evaluating building analytics, fault detection and diagnostics (FDD), or energy management software right now, the ROI pitch in front of you is probably accurate and incomplete at the same time. This guide walks through where the real costs of “smart building” software tend to hide, and the specific questions that surface them before you sign, not after.
Why the Vendor’s ROI Number Isn’t the Whole Story
Industry analysis puts the upfront construction and equipment cost of a building at roughly a fifth of what it costs to own over its lifecycle. The remaining four-fifths goes to operating expenses: energy, maintenance, repairs, and staffing, spread across decades.
Procurement is built to optimize the visible fifth. Software contracts inherit the same blind spot. A vendor’s ROI slide is optimized to win the purchasing decision, which means it’s optimized around the number that’s easiest to compare across competing bids: the sticker price and the projected energy savings. Everything that shows up after signature day tends to get left off, not out of dishonesty, but because it’s genuinely harder to put a number on until you’re living with the contract.
Where the Real Costs Actually Hide
Subscription Fees That Compound
The number on the proposal is rarely the number you pay in year three. Multi-year SaaS contracts frequently include automatic renewal escalations, and if that clause isn’t in front of you during negotiation, you’re agreeing to a number you haven’t seen yet.
The Integration Fee
Connecting a new analytics platform, a maintenance system, or a second vendor’s tool to your existing building data shouldn’t require a special toll, but it often does. Some vendors call it an “API fee.” Some call it “custom integration.” Either way, it’s a cost that only shows up once you’ve already committed and need your own data to talk to something new.
Cybersecurity and Patching
Every sensor, controller, and gateway you connect becomes part of your IT attack surface. Someone has to own ongoing monitoring, patching, and vulnerability management for that surface. If nobody’s named for that job at contract signing, it either becomes an unbudgeted line item later or, worse, nobody’s job at all.
Forced Upgrades
Vendors sunset old software versions. When that happens, the platform your team spent a year learning can require a paid upgrade just to keep functioning, on a timeline the vendor sets, not you.
Training and Specialized Labor
Complex platforms don’t run themselves. Someone on staff has to learn the system deeply enough to actually use it, and if that person leaves, a meaningful share of that expertise usually leaves with them. Training budget for the first user rarely covers training budget for the third.
The Exit Cost
This is the one most procurement processes skip entirely: what does it actually cost, in time and money, to leave. Not hypothetically. If your team can’t answer that question with a real number, that’s itself a cost, because it’s the vendor’s strongest leverage in every renewal negotiation that follows.
The Questions That Actually Reveal the Real Number
Before signing anything, get written answers to these:
- What’s the renewal price escalation clause, in the contract, not a verbal assurance?
- Is there a fee to connect a new analytics or maintenance platform to this system? If so, is it capped, and by how much?
- Who owns cybersecurity patching for this platform, and is it included in the subscription or billed separately?
- What happens to functionality if we decline a version upgrade?
- Can we export our full operational history in an open, non-proprietary format, at no additional cost, within a reasonable time window?
- Has anyone actually modeled what it costs to switch vendors in year four, or are we just assuming we won’t need to?
That last one is worth sitting with. Most teams haven’t run the math because it feels premature during a purchase decision. It isn’t. It’s the number that tells you how much leverage you’re giving up.
The Sticker Price Was Never the Real Question
None of this makes smart building software a bad investment. It makes the sticker price a bad way to evaluate one.
We built CopperTree’s independent data layer around the same logic laid out above: the real cost of a platform includes what it takes to leave it, not just what it takes to install it. If you’re in the middle of evaluating vendors and want a second set of eyes on a contract before you sign, reach out to our team and we’ll walk through it with you.