Support, Maintenance & Ongoing Development
After Launch, the Path for Maintenance and Development Should Remain Clear.
A website or digital product continues to require updates, troubleshooting, and decisions about new needs after release. Through a defined plan, we clarify which services are provided, how requests are reviewed and prioritized, and the scope and terms of the ongoing work.
Who Is This Service For?
This service is for clients whose website or digital product has been launched by ZARMIND and requires maintenance, troubleshooting, content updates, or phased development after release. The appropriate level of support depends on the product, how it is used, the importance of its different areas, and the business’s future plans. The scope and level of service are defined around the client’s actual needs and a clear agreement.
What Needs to Remain Clear After Launch?
Technical updates, potential issues, content changes, and new business needs require a defined path for review and action. When the type of request, its urgency, responsibility for the work, or the support boundaries are unclear, ongoing work becomes fragmented and unpredictable. The support plan should clarify which services are included, how requests are submitted, how they are prioritized, and which items require a separate estimate or agreement.
What Does Each Type of Request Mean?
Maintenance
Routine technical updates, backups, monitoring, and basic security and reliability reviews.
Troubleshooting
Investigating and correcting an area that is not working according to the agreed behaviour.
Content changes
Editing or replacing existing text, images, or information within the agreed scope.
Small improvements
Limited changes to an existing area to improve its use, performance, or management.
New development
Adding a new page, capability, integration, or workflow that requires separate review, design, estimation, and scheduling.
Guidance and planning
Reviewing new needs and defining the appropriate priorities and path for continued development.
The final classification of each request is determined after reviewing its effect on the product, the work involved, and its relationship to the agreed support scope.
What Can a Support Plan Include?
Each plan is defined around the product, the client’s needs, and the agreed level of service. It may include:
- Technical updates and routine maintenance
- Performance and reliability monitoring
- Backups and recovery checks
- Basic security reviews
- Issue investigation and resolution
- Small improvements and content updates
- New pages or functionality after review
- Content management or entry when agreed
- Periodic reporting on completed work
- Guidance and development prioritization
- Phased development around future needs
Not every plan includes all of these services. The scope, frequency, responsibilities, and limitations of each item are defined before work begins, and requests outside the agreement are reviewed separately.
What Should Support Maintain or Improve?
The intended result is a product that remains usable, reliable, up to date, and responsive to the business’s changing needs after launch. The client should know how issues are handled, where responsibilities sit, and which options are available for maintenance or future development. The outcome of each plan is defined by the agreed services and response level. This service does not promise a complete absence of errors, uninterrupted availability in every circumstance, or unlimited changes.
An Example of Ongoing Support
Maryam Zare Coaching
ZARMIND’s work with Maryam Zare continues after the website launch. The ongoing engagement includes responding to website issues, updating content, and developing new functionality in stages. An English version is also planned and will be added after its content has been fully prepared and reviewed.
How Is Each Request Handled?
Submit the Request
The client sends the issue, its effect on use, and the relevant information through the agreed channel.
Review & Classify
The request is reviewed to determine whether it is troubleshooting, maintenance, a content change, a small improvement, or new development, and to assess its priority.
Define the Path
We clarify whether the request falls within the support plan or requires a separate estimate, schedule, and approval.
Complete & Test
The approved work is completed and tested in proportion to the type of change.
Report & Continue
The client is informed of the outcome, the changes made, and any next action required.
How Is the Support Plan Defined?
The plan is shaped around the type and complexity of the product, its important areas, level of use, connected services, update frequency, monitoring and backup needs, and the expected volume of requests. The importance of each area and the effect of disruption on the business also inform the required response level. Before the plan begins, its service scope, duration, request channel, response times, responsibilities, cost, and exclusions are defined. New development is included only when its capacity and boundaries are explicitly agreed; otherwise, it is reviewed and estimated separately.
Frequently Asked Questions
No. Each plan has a defined scope, capacity, duration, and response level. Requests within the agreement follow the established support process, while items outside the scope are reviewed and estimated separately before work begins. These boundaries keep priorities, timing, and responsibilities clear for both sides.
If part of the product is not working according to the agreed behaviour, the request is handled as an issue for investigation and correction. If the request changes existing behaviour or adds a new page, capability, integration, or workflow, it is considered new development. Some requests may appear simple at first but affect other parts of the product. The final classification is made after technical review and clarification of the change involved.
Response times are defined within the support plan and are not the same as the time required to complete the work. After a request is received, it is reviewed and assigned a priority. Completion time depends on urgency, complexity, dependencies on other services, and the agreed support capacity. If the request requires separate investigation or development, its schedule is communicated and approved before the work begins.
Urgency is determined by the issue’s effect on the use of the product. Product unavailability, a confirmed security issue, or failure of a core journey such as sign-in, payment, or enquiry submission may receive a higher priority. Routine content changes, suggested improvements, and new functionality are not normally treated as urgent requests. The specific priority criteria and process for handling critical issues are defined within each client’s support plan.
When included in the plan, backups are handled according to a defined frequency, storage location, and retention period. Recovery should also be reviewed in relation to the infrastructure; the existence of a backup file alone does not guarantee successful restoration in every circumstance. If hosting or another provider handles backups, the responsibilities of ZARMIND and the service provider are clarified within the plan.
We first investigate the likely source of the issue. If it relates to configuration or integrations within ZARMIND’s responsibility, it is handled through the support process. If the disruption comes from the hosting provider, payment service, API, or another external provider, the agreed level of investigation and coordination is carried out, but the provider’s performance and resolution time remain outside ZARMIND’s direct control. The costs, terms, and limitations of third-party providers remain separate from ZARMIND’s services.
The conditions for pausing, renewing, or ending the plan are defined within the service agreement. At the end of the plan, the status of open requests, completed work, ZARMIND’s access, and responsibility for maintenance and service renewals are clarified and documented. The domain and core product accounts remain under the client’s control. Any later support or development continues only through a new agreement.
The cost depends on the type of product, service scope, response level, maintenance frequency, monitoring and backup needs, and the capacity required for requests. New development or work outside the plan is also reviewed and estimated separately before it begins, unless a defined capacity for that work is included in the agreement. Costs for services such as hosting, plugins, APIs, or subscription-based tools remain separate from ZARMIND’s fees and are identified clearly.
Submit Your Request for Review.
If your product was launched by ZARMIND, get in touch through our contact page and share the issue, its effect on use, and the relevant information. The request will be reviewed according to your support plan, with the outcome or next step communicated back to you.