How it works
Three connected commitments
Go-live starts the protection, not the handover. Each commitment leads into the next.
Included · First 90 days
Adoption ProtectionWe stay until your team uses it.
Go-live starts the protection, not the handover. Testing, adoption support and one defined correction cycle for eligible in-scope issues.
- A named owner for the workflow
- Testing with real inputs and exceptions
- A clear fallback when automation cannot proceed
- An early review, before habits harden
Paid program · Months 1 to 12
Reliability CareProblems caught before they cost you.
Proactive care that keeps the workflow healthy as your people, inputs and systems change. Completing it unlocks the Performance Guarantee.
- Monitoring for failures and growing exceptions
- Maintenance for in-scope drift and minor changes
- Regular reviews against the documented criteria
Conditional · Months 13 to 36
Performance GuaranteeCovered failures fixed, no extra service charge.
Up to 24 more months of protection for clients who complete Reliability Care, measured against the criteria agreed in writing.
- Measured against criteria agreed in writing
- Covered failures diagnosed and corrected
- No extra professional-service charges
Side by side
What changes when protection is part of the offer
| Topic | A typical provider |  Globatro |
|---|---|---|
| Where it starts | With tools and ideas | With the workflow and how often it is handled |
| What gets built | What the buyer asks for | The right choice of simplify, configure, buy, build or wait |
| How results are reported | Theoretical hours saved | Net usable capacity, after residual effort |
| After go-live | The project ends | 90 days of Adoption Protection |
| Ongoing support | Generic, if offered | 12 months of Reliability Care, then up to 24 months of performance protection |
"A typical provider" means a project-based implementation that ends at go-live. We are not claiming nobody else can automate well; the difference is the commitment after go-live.
Boundaries
Clear about what is covered, and what is not
A guarantee is only worth something if its limits are plain.
MRMT INC., operating as Globatro
The Performance Guarantee, in brief
The plain-language version. Full coverage, eligibility, exclusions and remedies are set out in written terms, agreed before work starts.
What is covered
- Failures against the performance criteria agreed in writing
- Diagnosis and correction of covered failures
- No extra professional-service charges for covered failures
What is not covered
- Return on investment, labour savings or financial results
- Changes to the scope after it was agreed
- Changes made without our authorization
- Failures or downtime of third-party systems
Your part
- A named process owner for the workflow
- Representative inputs, including exceptions
- Access to the systems involved
- Completing Reliability Care to stay eligible
Valid months 13 to 36 after go-live
Eligibility clients who complete Reliability Care
Terms agreed in writing before work starts
Questions
About the Assurance
Is the 36-month protection automatic?
Adoption Protection comes with every implementation. The Performance Guarantee is for clients who complete the 12-month Reliability Care program and follow the written terms.
Does Reliability Care cost extra?
Yes. Reliability Care is a paid program. The 24 months of performance protection that follow it come at no additional charge.
What counts as a covered failure?
The workflow not meeting the performance criteria agreed in writing, for a reason within the agreed scope. Third-party outages, scope changes and unauthorized modifications are excluded.
Does the guarantee promise a financial return?
No. It covers documented operating criteria, not ROI, labour savings or third-party availability. We measure financial benefit honestly, but we do not guarantee it.
What if our business changes the workflow?
Tell us. Reliability Care reviews record changes as they happen, and changes in scope are agreed in writing so protection stays clear.
It starts with one workflow
The Capacity Recovery Assessment decides whether a workflow is worth automating, and sets the boundaries the Assurance is built on.