Managing Facilities Spend at Scale? Ask This Before You Sign Your Next CMMS Contract

A CMMS contract has a listed price, but whether or not that price holds over a multi-year term is a different question.

“Configurability” is a word that shows up in nearly every CMMS pitch (and we certainly prioritize flexibility here at Fexa), but for a VP or director managing facilities spend across hundreds of locations, configurability matters less than the financial picture. 

To the person who owns a facilities budget, configurability is less important than making sure that when your business evolves, that growth doesn’t lead to new, unexpected FMS invoices and increased costs. New approval thresholds, changed workflows, and updated notification logic–these are all the things that accompany business growth. Will they also increase the costs associated with your CMMS? 

In short, is your software contract a fixed cost or an open-ended one with the potential to grow and grow? 

Why is your R&M budget subsidizing your CMMS vendor’s roadmap?

There is a pattern that has surfaced across large account evaluations that is consistent and striking. 

Two different enterprise multi-site operators managing thousands of locations described their original CMMS platform’s change process in blunt terms: every modification, however routine, required going back to the vendor, getting it approved, and then waiting, often half a year or more, while it worked through a development queue. Meanwhile, they were paying a premium just to wait.

One of those multi-site operators described a notification template for emergency work orders that took six months to build and couldn’t be edited after deployment.  What looked at first glance like an inconvenience became a recurring budget exposure that was priced like custom work. 

The incentive structure underneath this model is frustrating but easy to spot. After all, a vendor whose revenue depends on billable change requests has no financial reason to make the platform genuinely self-service. 

Every workflow modification, every custom report, every communication update that requires their engineering team is, from their perspective, a revenue opportunity. From your perspective, though, it’s an uncapped line item hiding inside what looks like a fixed annual cost. It’s also something you need to understand before you choose your next CMMS. 

What Does “Flexible” Actually Cost You Over a Multi-Year Contract?

When we speak with companies who are making the change from one CMMS platform to another, one of the most common issues we hear is that the sticker price of their original CMMS contract never captures the full picture of what they actually pay. 

Whether you realize it quickly or over time, it’s frustrating to realize that a provider sold you the idea of flexibility as a feature when really, it’s flexibility as an ever-growing line item in your budget. 

The total cost of facilities work includes CMMS implementation, training, support, and the ongoing cost of platform changes. That last category is the one that facilities management professionals are most likely to underestimate when they sign their contracts. 

At scale, these costs compound quickly. Consider what it takes to make a change to your approval workflow at a 500+ location organization. You’re looking at a formal request, development ticket, approval cycle, and multi-month wait. The changes you want to make to your workflow now can’t actually go into effect for six months! In the meantime, every location in your portfolio is running on a process that no longer reflects your actual business reality. 

This is a lot more than a software limitation. It’s also a capital problem. You can’t make confident, sound R&M budget decisions when your platform isn’t keeping pace with your operational reality. 

There’s also an opportunity cost dimension that doesn’t show up in the contract. When your facilities team has to queue change requests rather than execute them, there is a time cost that falls on your internal team, your vendor management workflows, and ultimately your margins. 

One of the most direct articulations of this frustration came from a senior facilities leader at a large multi-site retailer undergoing a full CMMS evaluation: the incumbent platform required coding knowledge just to build a standard report.  Not a complex custom analysis, a standard report! 

These costs don’t announce themselves as line items, because they show up as delayed process improvements, workarounds that persist longer than they should, and a gradual erosion of confidence in the numbers your platform is producing. 

All of this leads to a frustrating reality, where your R&M data is only as current as your last approved change request, which could have been months ago. This means that your real-time information is inaccessible, and you’re working from a delayed picture of what’s going on in your facilities. 

What Should Procurement Require Before You Sign (or Renew)?

This is a contract-level conversation, not an IT checklist. The right questions belong in the room where the CFO and the facilities VP are evaluating total cost of ownership. It’s part of the due diligence your operations deserve. 

The first question is the most fundamental: which categories of platform change are included in the contract price, stated explicitly in writing, and which are billed as new work? Vague language about “configurability” in a sales deck is not a binding answer. You want a specific list of what’s self-service and what triggers a development request and a separate invoice.

Second, what is the vendor’s contractual timeline commitment for processing a change request — not the marketing language about responsiveness, but the documented SLA? If the answer is “it depends on the roadmap,” that’s informative. It means the vendor’s development priorities, not your operational needs, determine when your platform reflects your business.

Third, who bears the cost when a “small” change turns out to require engineering work, and is there any cap on that exposure in the contract? Change requests have a way of expanding in scope once they enter a vendor’s development queue, and the operator typically has limited recourse once the work is underway.

These questions are worth putting to any CMMS vendor, including Fexa.You’re not asking because there is one perfect answer out there that you want to hear. Instead, it’s that the quality of the answer tells you something real about the incentive structure you’re signing up for. 

A vendor who can answer the first question with a specific, written list of self-service capabilities is demonstrating something different than one who responds with general assurances.

What Does Capital-Confidence-Grade Configurability Actually Look Like?

For most day-to-day operational needs, you need more than just configurable features. You also need your people to be able to make changes without constantly filing requests and waiting for a complete development cycle. 

Even though there will probably be a time when you do need to make a major change that requires some time and capital commitment, the problem emerges when every little change requires this kind of timeline and spending.  

Fexa is built specifically for multi-site enterprise operators, and the capabilities that matter most in this context are the ones that don’t require engineering involvement to use. Custom fields can be created, modified, and put to work at any time, at no additional cost.

Workflows, approval rules, and communication logic are configurable through Fexa’s workflow designer without requiring a development ticket for standard adjustments. For a facilities team managing hundreds of locations, that means most routine operational changes (like adjusting an approval threshold, updating notification recipients, adding a data field to track a new asset attribute) don’t generate a change-order invoice.

That’s not the same as saying you’ll never need Fexa’s team to be involved. New third-party integrations, certain reporting builds, and more complex data model changes still involve Fexa’s engineering resources. Even though we hand over a lot of control of operational changes, we don’t abandon you when implementation is over and say, “You can configure it on your own now!” Our goal is that the common, recurring category of change shouldn’t carry a recurring cost surprise. 

There’s a meaningful difference between a platform that bills you every time you need to adjust a workflow and one where adjusting a workflow is something your team does on a Tuesday afternoon.

The broader principle is worth keeping in front of both procurement and finance through any CMMS evaluation: a platform that controls the cost of change controls your budget in ways that don’t show up in the initial contract. Budget predictability is a product feature, not just a negotiating point. 

You know that things can be different–so what happens now? 

Those three questions we posed above are worth bringing to your next vendor conversation, no matter who you’re talking to.

1. What’s included in writing?
2. What’s the contractual timeline for the work?
3. Who bears the cost of scope creep? 

We want you to ask us these questions, because we are excited about the answers. If you’d like to put them to Fexa directly, request a personalized demo.