What Does a CMMS Actually Cost?

Software price can be only part of the project

Novato Sanitary District provides a clean example.

In 2026, the district authorized a three-year Trimble Unity Maintain software agreement for $97,650, or $32,550 per year.

Implementation was authorized separately at $144,900.

That produced a combined initial three-year authorization of $242,550.

The implementation scope included software installation, process discovery, training, project management, interface development and data conversion.

In this particular procurement, implementation represented approximately 59.7% of the combined software-and-implementation authorization.

That percentage is useful for understanding Novato.

It is not a general CMMS implementation ratio.

Another buyer may require different migration, configuration, integrations, training or professional services.

The broader lesson is simpler:

The software number alone would have described less than half of Novato’s initial documented software-and-implementation authorization.

Buyer question:
What work required to put our CMMS into operation is outside the software price?

View the Novato procurement profile →

Licensed doesn’t necessarily mean operational

A software capability can already be licensed and still require paid work before an organization can use it.

West County Wastewater illustrates the distinction.

The organization went live with Cityworks in October 2023.

About a year later, West County wanted to begin using Cityworks Storeroom for inventory and material-cost management.

The Storeroom module was already included in its annual Cityworks license.

West County nevertheless authorized $24,800 for professional services to configure and implement it.

The $24,800 was not a new Storeroom software license.

It was the cost of putting an already licensed capability into operation for that organization.

That distinction matters when evaluating a proposal.

“Included” can describe licensing without answering what it will take to make the capability usable.

Buyer question:
Which capabilities included in our license will require additional paid configuration or implementation before we can use them?

View the West County Wastewater procurement profile →

The first purchase doesn’t define the full relationship

A CMMS purchase can generate new cost events long after the original agreement.

Stockton entered a five-year Cityworks agreement in 2020 for $700,000.

Later public records document:

• a $140,000 extension
• a $14,850 server-upgrade evaluation
• another $141,200 extension

The authorized contract total through March 2027 reached $996,050.

Those later amounts do not mean the original purchase was incomplete or incorrectly priced.

They show that the economics of a CMMS relationship can continue to develop after the initial purchase.

The system remains in use.

Technology changes.

Contracts expire.

New workflows may be added.

The organization may need additional services.

A five-year purchase decision therefore should not be evaluated solely by asking what the first contract costs.

Buyer question:
What events could cause us to spend more on this system during the next five years?

View the Stockton procurement profile →

Unknown doesn’t mean zero

One of the easiest ways to understate a technology project is to treat an unpriced requirement as though it costs nothing.

Ames provides a useful example.

In 2019, the city approved a three-year Limble agreement for $68,796.

The procurement record also identified cleaning and updating inventory information as a separate project.

Its cost had not yet been determined.

That amount is not $0.

It is unknown.

Six years later, Ames documented another three-year Limble agreement for $94,374.

We can report both documented agreements.

We should not fill the missing inventory-data amount with an estimate simply to make the earlier project total look complete.

The same principle applies to a buyer comparing proposals.

If one vendor includes migration and another says migration will be scoped later, the second proposal does not currently contain a $0 migration cost.

It contains an open cost.

Buyer question:
Which work required for this project has not yet been priced?

View the Ames procurement profile →

Required services and optional services are different

A proposal can contain several layers of potential spending.

Some work is required to put the system into operation.

Some services may be optional.

Some costs may be triggered only if the buyer chooses additional training, integrations, modules or scope.

Those amounts should not automatically be collapsed into one number.

Elk Grove’s procurement illustrates why the distinction matters.

Its records identify software licensing and maintenance, implementation services, optional ancillary services and later additional work.

The buyer evaluating a proposal should therefore ask two separate questions:

What do we need to spend to reach the intended operating state?

What might we choose or need to spend later?

An optional amount is not the same thing as a committed amount.

But ignoring it can also hide a plausible future cost.

Buyer question:
Which services are required for our planned implementation, which are optional, and what would cause us to need the optional work?

A valid number isn’t necessarily a comparable number

A procurement record can be well documented and still be a poor comparison for another transaction.

Suppose one public record shows:

one year of software for one department.

Another shows:

three years of software, implementation, integrations and training across a large utility.

Both amounts may be perfectly valid.

Comparing the two headline totals as though they represent equivalent CMMS purchases would still be misleading.

This is why we separate evidence quality from analytical comparability.

Santa Clarita Valley Water provides an example of a strongly documented project whose amounts require context.

Its records identify a substantial Phase 1 implementation, multi-year software costs and a broader project authorization, while additional Phase 2 integrations were planned separately.

Those figures are useful evidence about that project.

They should not automatically be placed beside a smaller or differently structured procurement and interpreted as a vendor-price comparison.

Buyer question:
Are these two prices actually describing sufficiently similar purchases?

Contract amount and money paid are different measurements

A contract ceiling and an expenditure are not interchangeable.

A public record may show what an organization was authorized to spend.

Another may show what it actually paid during a period.

Roosevelt Island provides a simple example.

Its public record identified a Brightly contract amount of $16,875.28 for the period examined.

The same record showed $6,543.54 expended and $10,331.74 outstanding.

Each number answers a different question.

Contract amount:

What financial commitment or ceiling was documented?

Expenditure:

What had actually been paid?

Outstanding amount:

What remained against that documented contract amount?

A database that treats all three as equivalent “prices” loses information.

Buyer question:
When someone cites a CMMS amount, are they describing a contract, an authorization, a budget or money actually paid?

The vendor contract may not be the whole project

An organization’s implementation project can have a wider boundary than the CMMS vendor’s agreements.

Moulton Niguel Water District provides a useful example.

Its records identify:

• $85,000 for software licensing and maintenance.
• $540,880 for NEXGEN implementation services.

That gives $625,880 in identified vendor agreements.

The broader Asset Management Program / CMMS Implementation project budget was $1,041,979.

Those numbers should not be treated as contradictory.

They describe different boundaries.

The vendor agreements identify particular contracted components.

The larger number describes the organizational project budget.

We also cannot simply subtract $625,880 from $1,041,979 and declare the difference to be money spent on a specific category.

The source does not establish that.

Buyer question:
What costs required for this project sit outside the CMMS vendor’s proposal?

View the Moulton Niguel procurement profile →

Upgrades can become new implementation events

Going live does not necessarily end implementation-type spending.

Corpus Christi provides a clear example.

The city documented $906,403.88 for three years of Maximo licensing, hosting and maintenance.

A later Maximo 8 upgrade required $542,400 in professional services.

The point is not that buyers should expect a $542,400 upgrade.

Corpus Christi’s scale and technical environment are its own.

The useful observation is that an established CMMS can later require another substantial professional-services event when the underlying platform changes.

An upgrade may involve more than installing a new version.

It can require configuration, migration, testing, integrations or other implementation work.

Buyer question:
What happens economically when this product undergoes a major platform upgrade?

Successful adoption can increase cost

Higher CMMS spending is not always evidence that something went wrong.

Sometimes the organization uses the system more.

Metroparks Toledo adopted Cityworks and later documented additional subscriptions as more departments engaged with the platform.

The additional subscription amounts across the documented periods totaled $314,533.80, with another $4,500 authorized for migration support.

The important point is not the amount.

It is the trigger.

Broader adoption created additional licensing needs.

That means a buyer should not model future CMMS cost only around failure scenarios.

Success can change the price boundary too.

More people use the system.

More workflows move into it.

More departments participate.

The system becomes more important to the organization.

Buyer question:
If adoption is stronger than expected, what happens to our licensing and service costs?

Growth can change the pricing model

Sometimes growth changes more than the quantity purchased.

It can change the commercial model itself.

Miami Beach historically documented a Cityworks arrangement of approximately $45,000 per year with limited users.

As the system expanded into additional departments, the city moved to an enterprise arrangement with unlimited employees at $66,000 per year for three years.

Later city records described the organization as having outgrown its existing work-order environment as multi-department requirements increased.

This does not establish a universal Cityworks pricing threshold.

It shows something more useful:

The pricing structure that fits one operational state may not be the pricing structure that fits the next one.

Buyer question:
What happens to the commercial model if another department, facility or large group of users joins the system?

Commercial terms belong inside the price

The number on the first invoice is only one part of a commercial offer.

Terms can change the economics.

Public records provide examples of:

• price locks
• annual escalation limits
• renewal options
• multi-year commitments
• user or population thresholds
• optional contract years

Omaha Public Schools documented a three-year Layer Platform agreement with the 2024 price locked through January 31, 2027.

The Port of Newport documented a three-year commitment with annual increases capped at 7%.

San Marcos documented an initial one-year Maximo renewal with up to four additional one-year renewals.

Those terms matter even when they do not change today’s price.

A proposal with a lower first-year amount and weak renewal protection may not remain less expensive.

A proposal with a longer commitment may provide price stability while reducing flexibility.

Buyer question:
What commercial terms determine how this price can change?

A long-term CMMS relationship can contain many kinds of spending

Large long-term contract values require especially careful boundaries.

Los Angeles Sanitation provides an example.

A 2024 Ellipse-related contract had a maximum not-to-exceed amount of $8,125,451 across a long potential contract period.

That amount included multiple components:

• maintenance
• Ellipse/FMS integration
• on-call professional services
• mobile integration
• additional software licensing

Calling $8.125 million “the software price” would erase most of what the number actually represents.

Likewise, dividing the amount by the maximum potential contract years would create an annualized figure without necessarily describing the timing or composition of the spending.

The useful information is in the components and the boundary.

Buyer question:
When we see a large contract value, what kinds of spending have been combined inside it?

Why headline CMMS prices can mislead

Public procurement records show why the question “What does a CMMS cost?” often produces unsatisfying answers.

The number may describe:

• software only
• software plus implementation
• one year
• several years
• one department
• an enterprise deployment
• an initial purchase
• a renewal
• an expansion
• an upgrade
• a project budget
• a contract ceiling
• actual expenditures

Those aren’t interchangeable units.

This is also why a simple average of public CMMS contract values would create false precision.

A mathematically correct average can still be analytically meaningless when the observations describe different things.

The first job is not averaging the prices.

The first job is understanding them.

The CMMS price boundary

Before comparing CMMS prices, put the proposals on the same boundary.

We use four dimensions.

Components

What is included?

• Software
• Implementation
• Configuration
• Data migration
• Integrations
• Training
• Support
• Hosting
• Professional services
• Other required work

Operational scope

What does the system need to support?

• Users
• Departments
• Facilities
• Assets
• Workflows
• Inventory
• Mobile use
• Integrations
• Modules
• Other operational requirements

Time

What period does the price cover?

• Initial implementation
• Year one
• Three years
• Five years
• Renewal
• Optional periods

Commercial conditions

What can change the price?

• Additional users
• Additional facilities
• Asset growth
• New departments
• New modules
• Integration work
• API usage
• Renewal increases
• Pricing-tier changes
• Major upgrades

Two CMMS prices are only meaningfully comparable when they describe sufficiently similar boundaries.

Put every vendor on the same boundary

Before comparing totals, define the operating scenario every vendor is pricing.

For example:

Then ask each vendor to price that same scenario.

Without a common operating scenario, the proposals may be answering different questions.

Most of this scenario comes out of the work described in building your CMMS requirements, and it is the same material to bring to a first vendor call.

Compare the proposals

For any missing component, the buyer should enter:

UNKNOWN

or:

NOT REQUIRED

Do not default blank components to $0.

A missing component is not $0. It is unknown until responsibility for it is established.

The wider evaluation around these amounts is covered in comparing CMMS solutions.

Compare the commercial terms

A proposal can look less expensive because important future costs sit outside the initial price.

Commercial terms help reveal where those costs could appear.

Stress-test what happens when the operation changes

A CMMS is purchased for an operation that may not stay the same.

Before selecting a system, ask each vendor to explain what happens if:

• Technician count increases 25%.
• Another facility is added.
• Another department adopts the system.
• Inventory management is added.
• A new ERP or accounting integration is required.
• Asset count doubles.
• API usage increases.
• The organization crosses a licensing tier.
• The product undergoes a major platform upgrade.
• The contract renews after the initial term.

The purpose is not to predict every future event.

It is to expose which changes can move the price outside today’s boundary.

Several of these questions can be raised while watching the system work, using the CMMS demo checklist.

The CMMS cost lifecycle

CMMS cost can appear at different stages of the system’s life.

Define

Requirements, process analysis, data assessment, procurement and related planning.

Deploy

Software, configuration, implementation, migration, integrations, training, testing and go-live.

The work behind that stage is described in what to expect during CMMS implementation.

Operate

Hosting, support, maintenance, administration and continued use.

Evolve

Additional users, departments, facilities, modules, integrations, upgrades, migrations and changes in operational scale.

Renew or replace

Renewal, reimplementation, migration or replacement.

Not every organization incurs every cost.

The framework is not a spending formula.

It is a way to ask where costs can appear.

The public records examined in this research show cost events occurring well after the initial purchase.

That leads to a broader observation:

CMMS cost follows operational change.

So what should a CMMS cost?

The public record does not support one defensible answer.

The transactions cover different operations, components, contract periods and lifecycle events.

Publishing a single average from them would imply comparability the evidence does not provide.

A more useful question is:

What will it cost to put our operation into this system and keep it working as the operation changes?

To answer that, define the operation first.

Then define the components required to support it.

Then define the period you are evaluating.

Then identify the commercial and operational events that can change the price.

Only after those boundaries are visible should the totals be compared.

The requirements are already in the operation.

The cost analysis should begin there too.