Maintenance & Operation
After launch, small tasks pile up: an outdated text, an untested form, a pending update. Maintenance starts by asking what exists and which work should explicitly belong to it from now on.
Maintenance fits when nobody has a full overview of access and recent changes, or recurring tasks keep getting stuck behind day-to-day business.
It doesn't replace a fundamental refresh. If the technology is outdated or the page structure no longer fits, a redesign can be the more sensible step.
This is usually about bounded content changes, updates, form tests, error analysis, and small adjustments to existing functions.
Before taking anything over, I check available access, hosting, system status, forms, and visible dependencies. The check shows which tasks can actually be taken on responsibly.
If key information is missing or the technology isn't worth continuing, I say so before any ongoing agreement.
After the initial check, concrete changes can be prioritized and handled as bounded tasks.
Larger text work, new functions, or a rebuild of the page structure aren't treated as small maintenance tasks.
Tasks, access, and boundaries are recorded in writing. Legal review, search engine rankings, and editorial work with no defined scope aren't included.
The agreement only covers the named tasks. New topics get scoped each time before work on them begins.
If the current offer no longer fits the page structure, or every technical change triggers more errors, individual fixes stop being much help.
At that point the maintenance assessment ends with a recommendation for a separately planned relaunch.
Yes, after an initial check and with named tasks. Scope and cadence aren't assumed across the board.
I look at access, hosting, forms, core functions, and dependencies. That produces a prioritized list rather than a general safety promise.
You describe the new topic; I check whether it fits the agreed area. If not, its scope gets defined separately before work starts.
Yes, if the change is clearly described and covered by the agreed scope. Ongoing editorial work is separate from that.
When technology, content, and navigation no longer fit together overall. Then a standalone relaunch gets assessed instead of adding more individual fixes.
Send me the website address and describe the open tasks. I'll then tell you which access and information need checking for a takeover.