- One-off fix
- A specific symptom, agreed diagnosis or change, regression checks and handover.
- Routine care
- A supported stack and a defined repeat task list with capacity and a review cadence.
- Larger improvement
- A project with content, design or functionality that needs its own scope and acceptance.
Guide / comparison
Choose support around the work you actually need.
A one-off repair, routine care and a larger improvement program have different boundaries. Compare the tasks and responsibilities before the subscription.
01 / Guide / comparison
Sort the tasks by how often they recur
02 / Guide / comparison
Compare providers on the same task list
This blank worksheet stays in the page. Use roles and non-sensitive examples. Unknown values identify decisions to resolve; they are not a score.
Use roles and hypothetical examples. These fields stay in this page; no information is submitted or saved.
Include concrete examples and a task-size rule.
Separate status from an actual service promise.
Check security/incident exclusions and manual fallback.
Use supplied amounts and explicit assumptions; no market-price guarantee.
One repair does not automatically require a subscription.
When the issue is bounded and a recurring need is not established: Keep a one-off repair separate
03 / Guide / comparison
Read the response promise carefully
A response acknowledges or assesses a request. Resolution depends on the cause, access, third parties and scope. Ask what the working window, escalation and emergency boundary actually mean rather than assuming round-the-clock cover.
04 / Guide / comparison
Ask what the technical checks include
No. An update process, vulnerability response, monitoring and tested recovery are distinct tasks. Ask which are included, who acts on a failure and what evidence of completion you receive.
05 / Guide / comparison
Compare limits and costs
- Tasks included and the supported site or platform
- Capacity, request handling and review cadence
- What happens to unused capacity and added work
- Provider fees and separately paid software or hosting
- Cancellation, access removal and handover
06 / Guide / comparison
Keep ownership and the exit practical
Identify business-controlled accounts, source files, licenses and exports before signing. Ongoing care should not make account ownership harder to understand.
07 / Guide / comparison
Start with the current task list
List recurring needs and occasional projects separately. Use one-off repair scope when a repeat need has not been established.
If a different decision is blocking you: Choose another question in this topic