Annual continuity after year one
Websites bought through the managed checkout move to the £250/year care plan after 12 months unless cancelled before renewal.
Controlled updates, backups, practical checks and direct developer support for Stockport businesses. Existing websites are inspected before responsibility or pricing is agreed.
Send the website address and the main concern. Do not send passwords or access keys here; I will explain a secure access route if an inspection is appropriate.
An inherited website is not placed on a cheap plan before its access, software, licences, backups and existing faults are understood.
Do not send passwords or access keys in the form. A secure access route is agreed only if an inspection is appropriate.
Tell me who hosts it, what platform it uses if known, and which fault or maintenance gap is causing concern.
I check ownership, versions, licences, backups, forms and the parts of the website the business relies on.
Repairs needed before takeover are identified instead of being hidden inside a routine monthly or annual fee.
The update cycle, backup route, checks, support channel, change allowance, reporting and exclusions are agreed for this website.
Risky work starts from a recovery point and finishes with the agreed enquiry, checkout, booking or login check.
Unsupported software, larger repairs and new development are explained and quoted instead of silently ignored.
The managed renewal belongs to websites bought through the managed checkout. An inherited site is reviewed before its maintenance scope or price is agreed.
After the included first year, unless cancelled before renewal.
Choose by the current ownership and level of work, not by trying to force every website into the same plan.
Websites bought through the managed checkout move to the £250/year care plan after 12 months unless cancelled before renewal.
An inherited WordPress or business website is inspected before the maintenance scope and price are agreed.
From £350 per month where the brief includes continuing technical changes, content work or active improvement.
The £250/year managed plan covers the domain, hosting, security, backups, essential updates and support for the website bought through the managed checkout. It follows the included first year and can be cancelled before renewal.
The proposal identifies the update cycle, backup storage and restoration route, post-change checks, support channel, response arrangement, any change allowance, reporting and third-party subscriptions. It also lists faults that must be fixed before routine care begins.
Major repairs, redesigns, new features, malware clean-up, emergency out-of-hours work, paid plugin licences and unlimited edits are separate unless the written scope explicitly includes them.
WordPress advises creating a backup before updates and keeping both site files and the database recoverable. Read the official WordPress update guidance and backup handbook.
The website, its ownership and its important customer journeys are assessed before routine care begins.
Ad-hoc repair and ongoing maintenance solve different problems. A repair fixes the fault in front of you. A maintenance plan gives somebody continuing responsibility for the agreed checks, updates and small technical tasks that stop the website drifting back into the same state. I provide that ongoing route for Stockport businesses.
Sites built elsewhere are welcome for review, but they are not accepted blindly. I inspect the hosting, administrator access, software, theme or code, licences, backups, forms and known faults. If the site needs stabilising before routine care is sensible, that work is described and priced first.
Stockport is served from Web Spinner UK's Preston base as part of its North West coverage. There is no Stockport branch. Maintenance is carried out remotely through secure website and hosting access, with requests going directly to Sam.
The plan needs one clear owner on both sides. I need to know who can approve a change, which contact receives technical decisions and which journeys are business-critical. That prevents a routine plugin update, content request or form fault from disappearing into an inbox with no accountable next step.
An inherited WordPress site often has a mixed history: one supplier owns the domain, another holds the hosting, a former agency licence powers the theme, and several people share an administrator login. Updates may have been postponed because nobody knows whether a plugin is safe to change.
The takeover check turns that uncertainty into an inventory. I record the platform and versions, identify obvious unsupported components, confirm whether usable backups exist and test the main public contact route. Pre-existing defects are separated from routine maintenance so the continuing plan starts from an honest baseline.
Once the baseline is agreed, maintenance follows a controlled sequence: backup, change, check and record. A brochure site may only need its key pages and enquiry form checked after an update. A store, booking system or membership site needs a wider test because more can fail without the homepage looking broken.
Small content or technical changes are included only when they form part of the written plan. New pages, integrations, redesign work, emergency recovery and paid third-party licences are separate unless stated. Stockport businesses therefore know whether a request belongs to the plan before work begins, rather than discovering the boundary on the invoice.
Web Spinner UK serves businesses in Stockport as part of its wider UK service-area coverage.
A faster, clearer website with SEO structure, proof, quote paths, and lead capture.
View local service → Related local serviceSenior website support for businesses that need clearer pages and stronger enquiry routes.
View local service → Related local serviceLocal SEO planning, stronger service pages, and cleaner technical foundations for Google visibility.
View local service →Once access, ownership, the recovery route and the written scope are agreed, routine care follows a controlled change-and-check cycle. Work outside that scope is explained before it is added.
What changed and when. Which important journey was checked. What needs a decision from the website owner. What sits outside the agreed maintenance scope.
Routine updates and agreed requests are handled against the website’s written scope and important customer journeys.
Risky work starts only when the agreed backup or restoration route is available.
The maintained component is changed, then the relevant form, checkout, booking or login route is checked where applicable.
Material work is recorded. Unsupported software, larger faults and decisions for the owner are raised rather than hidden inside routine care.
There is no universal update timetable or emergency SLA. The maintenance cycle and response arrangement are written around the platform, risk and business-critical journeys.
Responsibility starts only after the site is reviewed, any required stabilisation is agreed and the maintenance proposal is accepted.
The routes are grouped so you can compare nearby coverage and related services without working through a wall of cards.