JumpinoWe list the domain, hosting, repository, dependencies and external services. For an existing project I check what I can maintain and which problems need separate work. The proposal separates initial setup, provider charges and recurring tasks.
Updates need checks and a route back to the previous version. For data, we agree what to back up, where to keep it and how to test restoration. Having a backup file does not prove that the service can be recovered.
What we can build
- An inventory of domains, accounts, services and responsibilities
- Repeatable deployment with public website checks
- Agreed updates and tests of important workflows
- Backups and restoration tests in a separate environment
- Monitoring and notification arrangements defined in the plan
When it makes sense
Useful when you need a technical contact for a website or application. Before taking over a system, I review its code, access and operating requirements. Urgency and response times are agreed explicitly.
Know what happens before we start
Agree the scope
The goal, pages, features, languages and materials become a proposal with costs, timing and responsibilities.
Review an early version
You see the structure and workflows before release. We discuss extra requests separately so the scope stays clear.
Check and hand over
We check phones and desktops, forms and access. Handover covers the agreed repositories, credentials, instructions and maintenance arrangements.
A handover you can use
- Agreed code and accounts, with credentials shared through an appropriate channel.
- Instructions for content updates and recurring operations.
- Documented external costs, backups and operational responsibilities.
After the launch
Updates, backup checks and new features need a plan. We agree what is included, who responds and how requests are handled. Round-the-clock support is not included unless explicitly agreed.
Questions before starting
Is hosting included in the website price?
Provider charges and technical maintenance are separate items in the proposal. We specify which accounts remain in your name and which recurring tasks are included.
Do you guarantee the site will never go down?
No. We define checks, alerts and recovery procedures to reduce risk. A maintenance plan cannot prevent every provider outage, application error or incident.
Can you set up email for my domain?
I can review DNS and connection to an email service, including SPF, DKIM and DMARC checks. Sending, receiving, backups and support also depend on the chosen provider.