A campus solution should be scoped to the campus.
MTRX project costs depend on the use case, number and type of systems, data readiness, digital model availability, integration effort, deployment environment, security requirements and ongoing support. We recommend a discovery-led engagement before confirming a price.
Possible engagement stages
How scope and cost are agreed at each stage.
| Stage | Commercial approach | What must be agreed |
|---|---|---|
| Discovery / assessment | Fixed fee or separately scoped engagement, if offered. | Deliverables, meetings, data review, assumptions and exclusions. |
| Pilot | Project-specific scope and price. | Use case, environment, integrations, success criteria, support and acceptance. |
| Deployment | Quoted after pilot and technical assessment. | Sites, systems, data volume, user roles, security and rollout plan. |
| Ongoing support | Defined recurring fee or service arrangement, if offered. | Support hours, response targets, maintenance, updates and responsibilities. |
What affects price
There are no standard price bands. Scope is set by the factors on this list.
- Number of buildings, assets, locations and data sources.
- Availability and quality of BIM, GIS, asset and sensor data.
- Number and complexity of required integrations.
- Need for custom interfaces, reports or workflows.
- Security, hosting, data residency and institutional IT requirements.
- Training, change management, support and service-level expectations.
Pricing note. Project pricing depends on scope, data readiness, integration effort, deployment and support requirements. A proposal is issued only after scope, assumptions, dependencies and acceptance criteria are agreed.
Request a scoped proposal.
Share your objective and the systems you already have. We will arrange discovery before any price is confirmed.