Assess the site before agreeing a plan.
An up-to-date small site and an inherited shop with old custom code need different work. We review the current condition, accounts, licences and connected services before deciding what can be covered.
Write down the routine work.
Updates, backup checks and tests of important forms or shop journeys need a defined frequency and owner. The agreement states what is included, what evidence is kept and how a failed check is handled.
Make the response arrangements clear.
Support hours, contact route, response expectations and escalation are agreed in writing. Automated checks do not create 24-hour human cover. New features, content work and larger incidents need clear boundaries.
Keep the running costs visible.
Hosting, domain renewals, licences, maintenance and development are different costs. I identify the items relevant to your site and quote the arrangement. There is no published one-size-fits-all support subscription on this site.