A CMMS quote is not complete because it contains a total.
The useful question is:
What does that total buy?
Two proposals can both say “CMMS implementation” while placing licensing, migration, integrations, training, hosting, support and future work on different sides of the price.
Before comparing totals, establish the quote boundary.
The Quote Boundary
CMMSBuyersGuide uses five commercial states:
Included | Excluded | Assumed | Optional | Future
Every material component of the proposed solution should fit one of them.
If it does not, the quote still contains commercial uncertainty.
Included
The quoted price covers it under the stated scope and quantity.
Excluded
The proposal explicitly does not cover it.
Assumed
The price depends on a condition being true.
Example:
“Migration price assumes customer supplies cleansed asset data in vendor template.”
That assumption has commercial value.
If it fails, the price or schedule may change.
Optional
The item is priced but not part of the base total.
Future
The item is expected later but is not currently priced or committed.
This is useful for later phases, integrations or modules that everyone expects but nobody has placed inside the current commercial boundary.
What sophisticated buyers make vendors expose
Public procurement cost forms show how serious buyers structure this problem.
AlexRenew's CMMS procurement breaks pricing into software and licensing, third-party components, hosting, implementation work, data loading, integrations, testing, training, go-live, support/maintenance and multi-year totals.
These structures expose a principle:
Price becomes more useful as the buyer can see the components, assumptions and time periods underneath it.
1. Software and licensing
The quote should state:
- product/edition
- licensing model
- quantities
- user types
- sites/facilities
- assets if relevant
- included modules
- optional modules
- minimum commitments
- tier thresholds
- billing frequency
- initial term
If the price is “enterprise,” define the enterprise boundary.
2. Implementation and project management
Clarify whether the quote includes:
- discovery
- process design
- project management
- system configuration
- workflow configuration
- security/roles
- forms
- reports
- dashboards
- testing support
- cutover
- go-live support
- stabilization
“Implementation included” is not sufficiently precise if neither party knows which deliverables are inside it.
3. Data migration
State:
- which data objects will move
- approximate volumes
- number of migration cycles
- cleansing responsibility
- transformation/mapping responsibility
- attachment/document migration
- historical work depth
- validation
- rejected-record handling
- final cutover load
A fixed migration price can still depend on assumptions about data quality and volume.
Those assumptions belong in the quote boundary.
4. Integrations
Price integrations individually where possible.
For each one, identify:
- source/target system
- business purpose
- direction
- implementation responsibility
- middleware or third-party dependency
- initial build cost
- recurring cost
- API/usage cost if any
- testing
- support ownership
“ERP integration included” can hide enormous scope ambiguity.
5. Training and adoption
Clarify:
- administrator training
- planner/supervisor training
- technician training
- requester training
- train-the-trainer
- materials
- recordings
- number of sessions
- remote vs onsite
- travel
- refresher training
- post-go-live support
If training is capped by hours or sessions, show the cap.
6. Hosting and environments
For SaaS, ask what the subscription includes.
Potential items include:
- production
- test/sandbox
- training environment
- storage
- backups
- disaster recovery
- data retention
- additional environments
Do not assume every environment is included merely because the software is cloud-hosted.
7. Support and maintenance
Define:
- support tier
- support hours
- channels
- included support
- premium support
- software updates/upgrades
- health checks
- named support resources
- annual maintenance if separate
- response/service commitments if contracted
8. Third-party components
Ask whether the proposed solution depends on separately licensed:
- middleware
- mapping/GIS components
- reporting tools
- databases
- identity products
- connectors
- mobile/device software
- other third-party services
Identify who contracts for them and who supports them.
9. Professional services after go-live
Request rates or the pricing method for work outside the initial scope.
Examples:
- additional configuration
- custom reports
- new integrations
- data work
- training
- consulting
- upgrades
- enhancement projects
10. Travel and expenses
State whether travel is:
Included | Capped | Reimbursable | Not expected | Excluded
Do not leave it implicit.
11. Term, renewal and escalation
The initial quote should state:
- contract term
- renewal structure
- renewal pricing method
- escalation assumptions/caps
- price protection
- notice dates
- treatment of added users/assets/sites/modules
Renewal belongs in the initial quote analysis because today's licensing structure becomes tomorrow's baseline.
12. Assumptions and exclusions
This may be the most valuable page in the quote.
Ask the vendor to list all assumptions and exclusions in one place.
Examples:
- customer provides cleansed data
- customer supplies integration documentation
- no custom development
- training remote only
- travel excluded
- only one migration cycle
- only specified reports included
- third-party fees excluded
An assumption is not fine print.
It is part of the price formula.
The Commercial Completeness Test
Before calling a quote complete, ask:
- Can we explain what the total includes?
- Can we identify required items outside the total?
- Can we identify assumptions that could change cost?
- Can we distinguish one-time from recurring cost?
- Can we identify the commercial meter and quantities?
- Can we see how price changes after the initial term?
- Can we explain what another buyer would need to add to reproduce the same operating scope?
If not, the total is not ready for comparison.
The Quote Boundary worksheet
Use these columns:
Component | Required? | Included? | Quantity/Scope | One-time | Recurring | Assumption | Exclusion | Optional/Future | Evidence
The Evidence column should point to the quote, proposal, statement of work or contract section supporting the classification.
That prevents commercial understanding from living only in meeting notes.
The buying principle
The purpose of a CMMS quote is not simply to produce a number.
It is to define the commercial boundary around a working maintenance system.
A total without a boundary is not yet a comparable price.
How to compare two CMMS proposals on the same price boundary
Sources
- Alexandria Renew Enterprises — RFP No. 22-001, Provision, Implementation and Maintenance of CMMS
The cost proposal form separates software licensing, third-party components, hosting, planning, configuration, data loading, potential system integrations, system testing, pre-go-live training, go-live, support and maintenance, with yearly and five-year totals, and requires all assumptions to be listed and explained.