One Time WordPress Repairs or Monthly Support

A one-time repair addresses a defined problem. A maintenance agreement assigns ongoing responsibilities. Neither automatically replaces the other: a recurring plan may exclude an existing major defect, and a successful repair does not mean future updates and backups are managed.

Use a one-time scope for a specific failure

Examples include a form that stopped sending, a mobile layout conflict or a broken link after a change. Provide the URL, reproduction steps, recent changes and any non-sensitive error message. The proposal should define the investigation and the condition that counts as fixed.

Ask what happens if the cause sits with a payment provider, host or unsupported extension. A repair can identify a dependency without having authority to change another company's account or service.

Use recurring support for continuing tasks

Updates, backup review, key-journey checks and agreed monitoring need an owner and a schedule. Confirm the actual tasks, frequency, exclusions and reporting. Words such as care or managed are not enough to define the work.

A site with frequent content changes or active store orders may need different recovery arrangements from a small brochure site. Describe how the website operates before choosing a plan based only on price.

Ask how updates are tested

Staging, backups and functional checks should fit the risk of the change. A simple update count does not show that the contact form or checkout still works. Agree which journeys are checked and who approves a higher-risk release.

Confirm the recovery process if an update causes a problem. Restoring a database can also remove newer orders or inquiries, so the plan needs to account for changes made since the backup.

Make support boundaries explicit

Separate response expectations from resolution guarantees. Confirm working hours, emergency arrangements, included changes and how additional development is quoted. Hosting charges, domain renewals and paid licenses may remain separate.

Record the accounts your business controls and the access a support provider receives. Keep a handover route so the website is not dependent on an undocumented personal account.

Start with the right conversation

If there is an urgent defect, begin with a repair assessment and then decide what ongoing care would prevent or detect a recurrence. If the site is currently stable, inventory the dependencies and assign maintenance tasks before the next problem.

StartMyWeb offers WordPress maintenance and support with a proposal covering tasks and boundaries. Include the current website, known problems, update responsibilities and the outcome you need; do not send passwords in the initial inquiry.