Support and Maintenance
We support web applications and internal systems built by other teams. Before signing a support agreement, we audit the code, infrastructure, and access setup.
When you need this
- →The system was built by a contractor or employee who is gone
- →The application works, but any change takes months
- →No confidence you would learn about an outage before your clients do
- →The product needs development, but hiring a team is not worth it
What's included
- Audit and intake of the system, a cleanup plan
- A response and recovery proposal after the audit
- Uptime monitoring and incident notifications
- Dependency updates and vulnerability fixes
- Feature development in sprints along an agreed plan
- Monthly reports: what was done, what we recommend next
Process
How we work
- 01
Initial conversation
We clarify the context, arrange a call, and sign an NDA before materials are shared if needed.
- 02
Preliminary assessment
We review the process, data, and existing systems, then prepare an approach and sequence of work.
- 03
Plan and contract
We describe the first milestone: the work, the acceptance result, and the required time and budget.
- 04
Pilot and development
The first milestone may validate the riskiest part. The remaining work and acceptance process are stated in the plan.
- 05
Launch and support
We run acceptance and transfer milestone deliverables after payment. Documentation and training are included when the client needs them.
Post-launch support
We fix warranty defects for three months after delivery. Ongoing support, monitoring, and development are covered by a separate agreement.
Questions and answers
Will you take a system you did not build?
Yes. We first audit the code, infrastructure, documentation, and access. The result lists critical problems and proposed support terms.
Which support terms can be fixed?
After the audit, support hours, severity levels, and response times can be agreed. Specific values are written into the contract.
How quickly do you get up to speed on a new project?
We allow two to four weeks for the audit and access setup. The exact time depends on system size and documentation quality.
Will we end up locked in to you?
The client retains the code and operational access. Documentation is updated with each change, so another team can take over the system.
Get a preliminary assessment
Describe the task. After reviewing it, we will propose a call and a list of materials for an initial assessment.
contact@amplifylab.it.com