Existing code can hold surprises.
A small-looking change may reveal a deeper issue. We review the setup first and discuss additional work before expanding the scope.
Support & growth.
Something changed? We’ll help you work through it. Maintenance, fixes, and useful improvements for what you’ve already built.
Keep what you’ve built working, then make it better.
We help look after a website or digital product once it is in use. The work can include updates, bug fixes, performance checks, publishing improvements, and small features that make everyday use easier.
We begin by understanding the setup and its current condition. Then we agree priorities and a working rhythm, separating routine care from larger changes. Feedback and useful measurements help decide what to improve next.
Keep it working. Make it better.
Find the problem, make the change, check it helped.
An example of an improvement cycle for a form people keep abandoning.
Understand the friction
We review feedback and available data, then reproduce the issue on the screens and devices people use.
Make a focused change
We improve the confusing field or broken interaction, test it, and release the change through the agreed process.
Check the result
We compare what happens after release and keep the next action visible, whether that is another fix or leaving it alone.
How we’ll work
together.
2–4 weeks to get set up
An initial review and setup, followed by ongoing website care.
Week 1
Learn the setup.
We review the site, hosting, dependencies, access, and known issues, and identify anything that needs attention before routine work starts.
Week 2
Agree the priorities.
We make a practical backlog, decide how requests are raised, and agree responsibilities, review points, and support expectations.
Weeks 3–4
Start with useful fixes.
We work through agreed maintenance and improvements, check changes before release, and keep a record of what has been done.
Ongoing
Review and adjust.
We look at new issues, feedback, and results together, then choose the next work instead of letting the backlog make the decisions.
Documentation, access, the condition of the code, and existing issues determine the initial review. Larger repairs or new features are scoped separately. We agree dates after scoping the work.
What you get.
We agree what’s included before starting.
Setup review
An initial review of the existing setup.
Prioritized backlog
A prioritized maintenance and improvement backlog.
Request workflow
An agreed way to request and review work.
Updates & fixes
The updates and fixes included in the care plan.
Release notes
Release notes and relevant performance checks.
Regular reviews
Regular reviews of priorities and the next useful changes.
What we need
from you.
- Access to the site, repository, hosting, and relevant accounts
- A list of known issues and available documentation
- A person who can prioritize requests and review changes
Things to consider.
A few things to agree before we start.
Care and new projects have different sizes.
Routine maintenance is different from a new checkout, rebrand, or major feature. Bigger changes need their own brief and estimate.
Improvement needs a clear measure.
A maintenance plan cannot guarantee traffic or sales. We choose changes around observed problems and review what the evidence can actually tell us.
Common questions.
Something else on your mind?
How is a care plan priced?
We review the setup, then agree the amount and type of work you need. The plan lists what is included, how requests are prioritized, and how extra work is approved. Hosting and third-party subscriptions are kept visible.
How long does getting started take?
Allow two to four weeks for the initial review and setup. Missing access, undocumented systems, or urgent repairs can change that. We identify those early and agree the next steps with you.
What information will we get about the work?
You get a record of changes and a visible list of upcoming work. We review priorities together and share relevant performance checks, so you can see what was done and what still needs attention.
Can we change the amount of support later?
We can review the arrangement as your needs change. The agreement sets out notice periods and any minimum commitment; we discuss changes before adding work or changing the plan.
Can you support something another team built?
We can start with a review of its technology, access, and condition. That gives us a basis for agreeing what we can maintain and whether any initial repair work is needed.
How quickly will you respond to an issue?
Working hours, priority levels, and response expectations are agreed in the care plan. Around-the-clock or emergency coverage is not assumed and needs a separate arrangement.
Can the plan include new features?
Yes, when their scope fits the agreed work. We keep larger changes visible as separate items so routine care and urgent fixes are not quietly displaced.