All insightsWebsite operations · 6 min read

Website care or one-off updates: which fits your team?

Decide what you can manage yourself, where technical support is useful, and whether your website or store needs a recurring arrangement.

Match the arrangement to the work

I would choose support around the work you actually have. You might want your team to handle routine publishing and a developer to handle structural changes. You might prefer to send both to a partner. A defined fix can suit a one-off project, while recurring requests benefit from an agreed working rhythm. Before deciding, I would separate content editing, technical upkeep, business operations, and new development. Calling all four “maintenance” makes it difficult to see what you are buying and who remains responsible.

From my work

An ongoing relationship needs a useful queue

Ruhcare website project
Explore the Ruhcare case study ↗

Ruhcare’s website work has continued over an ongoing collaboration of more than two years. The original front-end and directory integration provides context for later work, but that does not make every new feature part of the original scope. It is a useful distinction for care: keeping the system working and extending what it can do are related jobs with different responsibilities.

Try this on your project

Write down your last six website requests. If they form a regular queue, discuss care. If they point to one bounded problem, scope that problem first.

Start with the last six requests

Write down six recent website or store requests, who supplied the inputs, and what delayed completion. Separate a service-description change from a new page layout, an integration problem, or an urgent checkout issue. Then add planned campaigns and changes that are genuinely likely. This record shows whether the missing ingredient is technical capacity, content, approval, or a clearer publishing system. Paying for ongoing development will not resolve a queue held up by missing decisions; a useful care plan names those dependencies.

Keep routine work with your team when that suits you

A supported editing setup can let the right people update articles, services, projects, or product information. During handover, agree which fields and templates are intended for those tasks and test them with the future editor. Self-management does not mean the client must maintain every integration or build new layouts. You can keep everyday publishing in-house and ask for development help when the structure changes. Equally, if nobody has capacity to publish, a managed arrangement may be more practical than an editor nobody uses.

Choose one-off work when you can describe the finish line

A single campaign page with approved content, one broken integration, or a defined group of accessibility fixes can suit a scoped engagement. Agree the deliverable, acceptance checks, inputs, and exclusions. Replacing an enquiry form might include its fields, validation, confirmation, delivery test, and handover. It would not automatically include rewriting the offer or reorganising the sales process. A clear finish line makes the work easier to estimate and gives both sides a sensible basis for sign-off.

Choose ongoing care when continuity has a job to do

A care arrangement can make sense when requests arrive regularly and understanding the existing system makes delivery more efficient. An illustrative queue could combine campaign pages, content changes, CMS improvements, and checks of important journeys. Choose one person to prioritise the queue and provide consolidated approvals. Agree how much work can be active and how larger requests are estimated. A recurring relationship gives the work a structure; it should not be interpreted as every possible request being included or immediately deliverable.

Make technical maintenance specific to the setup

Ask which responsibilities are covered for your actual platform: hosting, dependency or extension updates, backup procedures, monitoring, and checks after a change. The answer should match the proposal. For example, WooCommerce’s update guidance recommends preparation, backups, and testing; somebody must own those activities in a store using that setup. A hosted platform changes some responsibilities, but it does not remove the need to check custom code and connected services. Do not assume that a content-update package silently includes technical incident support.

Keep store operations separate from website care

Product entry might be an agreed content task, but stock accuracy, fulfilment, refunds, customer service, and commercial policy decisions need explicit owners. If a customer reports an order problem, decide who assesses whether it is operational, payment-related, or a website defect. Give the support partner the access and contact route needed for their part of the investigation. This prevents a development queue from becoming the default destination for every store question while still making it clear how technical problems receive attention.

Distinguish acknowledgement from resolution

Ask what response and completion commitments mean, which working hours they cover, and whether emergency coverage is included. A broken enquiry form and a request for a new animation have different consequences. Agree an incident route for business-critical failures and a normal queue for improvements. Some issues depend on a hosting, payment, or other service provider; your developer may investigate and coordinate without controlling that provider’s resolution time. Useful commitments describe the work the partner can actually perform.

Review the terms that affect usable capacity

  • The included tasks, technical responsibilities, and explicit exclusions.
  • The amount of work that can be active and who chooses its priority.
  • How large requests are estimated and when separate approval is needed.
  • How missing content, delayed decisions, and third-party access affect delivery.
  • The agreed response hours and route for a business-critical incident.
  • How pauses, unused capacity, cancellation, and handover work under the proposal.
  • A simple record of completed work, checks, open issues, and upcoming priorities.

Recognise when the foundation needs a separate project

If every small update exposes a fragile template or unsuitable content structure, carrying the same problem into monthly care may be inefficient. Ask for a focused assessment and a repair scope. A full redesign, platform migration, or new application also needs its own decisions and acceptance criteria. It may be delivered in stages, but a monthly invoice does not remove the need for a coherent plan. The aim is to make future work more manageable rather than repeatedly paying to work around the same defect.

Understand the No-Code Dev starting point

Website Care starts at $1,500 USD per month, billed in advance for a monthly time allowance agreed in your proposal. Requests are acknowledged within one business day during agreed support hours; completion depends on the work. The arrangement is month-to-month with 30 days’ written cancellation notice. Unused capacity does not roll over, and extra work needs approval before it starts. Monitoring, backup, and security responsibilities are scoped for your setup; store operations remain with your business. New builds include 30 days of fixes for issues within the delivered scope from launch. Bring a short request history and your upcoming plans so we can decide what support fits.

Sources & further reading

Put the checklist to work

Download the CSV and open it in your spreadsheet app. Replace the example entries with your own website, owners, and checks.

Example website request planner ↓

Bring your last six website requests.

Tell us what needed changing, what held it up, and what is coming next. We’ll discuss whether ongoing care or a defined project fits that workload.

Discuss website supportDiscuss your ongoing workload ↗
Back to topBook a call