Defined service scope / Quote based
Theme Maintenance & Support
Agree support for compatible theme versions, maintenance and recovery checks.
Choose a bounded engagement, then agree its systems, access, deliverables and acceptance criteria.
Who it is for
A clear starting point.
- Teams seeking an agreed, bounded implementation scope
Customer fill-in scope template; no customer completion, fixed price, hours or SLA is asserted.
The delivery
What we agree to produce.
- Supported version and change approval record
- Agreed backup and isolated restore check
- Scoped updates, support channels and evidence report
Scope limits
Confirm the boundary.
- Unapproved hours or SLA
- Automatic production changes
- Hosting, licences and third-party charges unless separately agreed
Pricing approach
A quote around your scope.
Pricing is confirmed after reviewing:
- Compatible versions, environment and agreed acceptance scope
- Product, setup and support quoted separately
No fee, service allowance or delivery date is approved by this page. Platform licences, hosting and provider charges are identified separately where applicable.
Read the customer fill-in scope templateAgree the delivery
Review, scope, accept.
- Review a representative example. Choose a workflow, screen or test case that demonstrates the outcome you need.
- Confirm the requirements. Agree versions, access, data volume, owners and the exact deliverables before work starts.
- Record acceptance. Compare agreed results with observed behaviour, record unresolved cases and hand over the evidence and operating notes.
Start with one useful delivery
Describe your
operational context.
Tell us the systems and versions involved, the people who own the workflow, and the result you need to observe.
Prepare a structured briefThe request receipt distinguishes local capture from confirmed CRM recording. It does not approve payment, deployment or a licence.