Build a service offer.
Make its scope explicit.
A maintenance provider and a site manager.

What gets stuck
today.
Two offers with the same name can cover different equipment, visits and exclusions. The sales rep must check the installed base and the scope before applying a package.
Study an annual offer for three sites and twelve pieces of equipment, with two preventive visits per piece of equipment and a support option.
Clear parameters.
Guided decisions.
What the Cortex should check
- Collect the type, condition and location of the equipment before confirming eligibility.
- Distinguish included services, travel, parts and excluded interventions.
- Display only the service commitments actually offered and validated by the provider.
Define the scope
Build the proposal
Madus links
the whole deal.
In this application to be studied, the Cortex would build the offer according to the customer’s terms; Madus would hold the file and the opportunity follow-up. Technician scheduling and intervention reports would be a separate scope to be studied.
Discover management and steering ↗A file ready to use.
The 24 equipment visits do not necessarily mean 24 trips. This scenario does not present Madus as an existing CMMS.
Maintenance contract
- 24 annual equipment visits to organise
- Proposal with explicit services and exclusions
- Summary of the installed base and options to validate
No made-up prices: quoting would use the price grids, rules and terms validated by the supplier.
A business question.
Would Madus organise the maintenance rounds?
This case covers building the offer and its sales follow-up. Operational scheduling and intervention management would require a specific scope or integration.
To carry out this project, we would need to gather the catalogue or offer, the rules, the price grids and validated examples. The scope and feasibility would then be defined together.
More time to sell.
More visibility to act.
Let’s see how Madus can support your company and your network.
Request a demo ↗