COOPERATION FORMAT
Technical maintenance for websites and digital products
For a launched product needing a clear process for errors, updates and smaller changes. We first define the supported systems and responsibilities.
Discuss this format ↗WHEN IT HELPS
Choose by the work ahead
Useful for a website or service requiring regular technical attention while support tasks need to be distinguished from major new development.
DELIVERABLES
What we agree to deliver
- A list of systems and access covered by maintenance.
- A process for recording, prioritising and handling requests.
- An agreed update and backup-verification plan.
- Work reports and a list of unresolved questions.
WORKING PROCESS
Three steps to an agreed scope
- Review the system and its current operation.
- Agree on hours, channels, priorities and available capacity.
- Handle requests and plan preventive maintenance.
COMMERCIAL TERMS
Planning, budget and responsibilities
A time allowance or another maintenance scope is set out in the proposal. Major capabilities and external costs are estimated separately.
Response times, restoration times, on-call cover and responsibility for external services are agreed separately. Round-the-clock service is not an automatic commitment.
FAQ
Before we start
Can you take over another developer’s project?
Yes, following a technical review and access checks. Coverage depends on the system’s condition and documentation.
Does maintenance include new features?
Smaller changes can be included in the agreed scope. New subsystems and major capabilities are planned as separate phases.
RELATED SECTIONS
Plan the next step
Tell us the goal and how to reach you. Detailed planning follows our first conversation.
