Maintenance & updates
Platform updates, dependencies, certificates, and security patches handled before they are urgent.
Ongoing Digital Support
Your systems shouldn’t slowly fall apart after launch.
A system that runs a business is never finished, because the business keeps changing. New services, new people, new processes — and unless something keeps pace, workarounds appear and the system quietly stops being true. We stay involved so it improves instead of ages.
Published starting price: From $750/mo. See scope and options
- Same person every month
- Defined monthly capacity
- Three-month minimum · 30 days’ notice
Build, launch, monitor, improve, and round again — because the business it runs keeps changing underneath it.
Sound familiar?
The slow drift between what you built and how you now work.
None of this happens at launch. It accumulates over the eighteen months afterwards, and it is why good systems get replaced instead of extended.
The site still describes services you’ve changed.
Editing it requires someone specific, so small updates wait until they become a project.
People have invented workarounds.
The process moved on, the system didn’t, and the workaround was faster than asking.
An automation stopped working and nobody noticed.
Nothing was monitoring it, so the failure showed up as a customer complaint weeks later.
Every small change becomes a new project.
There is no standing relationship, so each request needs scoping, quoting, and re-explaining the stack.
Updates and certificates are handled when something breaks.
Maintenance has no owner, so it is reactive by default and occasionally expensive.
The person who understood the system has left.
The configuration was in their head rather than documented, so the next person is guessing.
If nothing changes
What neglect actually costs.
The bill does not arrive as maintenance. It arrives as a rebuild, two or three years earlier than necessary.
Data stops being trustworthy
Once people work around the system, the records inside it are incomplete — and reports built on them are wrong.
Small fixes become large ones
Deferred updates compound. What was an hour becomes a day once three versions have passed.
The investment stops compounding
A system that does not evolve delivers less every quarter while costing the same.
You end up rebuilding
The most expensive outcome of no maintenance is paying for the same system twice.
What good looks like
What a maintained system looks like.
The measure is whether the system still matches the business a year after launch.
- Someone already knows how your stack is built — no re-explaining.
- Updates, patches, and certificates are handled before they become urgent.
- Automations and integrations are monitored, and failures are noticed by us.
- Small changes take days, not a new proposal.
- The system changes when the business does, in the same month.
- Configuration and decisions are documented and owned by you.
- You get told what is worth doing next, not sold whatever is largest.
- The stack is reviewed on a schedule rather than when something breaks.
How we approach it
A standing relationship, not a ticket queue.
A retainer with us is defined monthly hours with the same person — someone who already knows how your systems are put together and does not need the context rebuilt every time. That is most of the value: the difference between "here is the change" and two days of re-explaining.
The work splits three ways. Maintenance keeps things current and secure. Monitoring catches failures before customers do. And improvement is the part most support arrangements leave out — the small changes that keep the system matching the business.
We also tell you when to stop. If your hours are being spent on something that would be better solved once, properly, we will say so, even when that means a quieter month. A retainer that quietly absorbs a structural problem is not support.
The transformation
Eighteen months after launch.
Two versions of the same system, same starting point, differing only in whether anyone was responsible for it in the interim.
Today
Without ongoing support
- Launch — everything matches the business
- The process changes; the system does not
- People invent workarounds and stop using a field
- An automation fails quietly
- Reports drift away from reality
- Small changes queue up waiting for a project
- Eventually somebody proposes a rebuild
The system did not fail. It just stopped being true, one month at a time.
Connected
With ongoing support
- Launch — everything matches the business
- Monitoring catches failures before customers do
- Small changes ship in the month they are needed
- Configuration keeps pace with the process
- The stack is reviewed quarterly against what changed
- The system is worth more at eighteen months than at launch
The same system, still true, and still compounding.
- Build
- Launch
- Monitor
- Learn
- Improve
- Grow
And back to the top. A system that runs a business is never finished.
What we actually build
What a retainer covers.
Hours go where they are most useful that month. This is the range they are usually spent across.
Monitoring
Uptime, performance, automation health, and integration failures — surfaced by us, not by a customer.
Content & configuration changes
New pages, updated services, changed pricing, CRM fields, and workflow adjustments.
Small builds
The improvements that never justify a project on their own but matter cumulatively.
Automation upkeep
Keeping existing automations working as the tools around them change, and adding new ones.
Backup & recovery checks
Verifying that what should be backed up is, and that a restore actually works.
Reporting review
Checking that the numbers still measure what you need as the business changes.
Quarterly stack review
A scheduled look at what changed, what is now redundant, and what is worth doing next.
Living documentation
Configuration and decisions kept current, so the knowledge belongs to you rather than to us.
How it connects
Support covers whatever we built — and plenty we didn’t.
The retainer follows the systems, not the service line they came from.
- Modern WebsitesContent, performance, SEO, and the small improvements that keep converting.
- CRM & Business SystemsConfiguration that keeps pace with how the team actually sells.
- Automation & AIMonitoring existing automations and adding new ones as they are identified.
- IT ServicesThe infrastructure, identity, and backup layer underneath all of it.
What we support
- Astro & Next.js sites
- WordPress
- Payload CMS
- Sanity
- HubSpot
- Pipedrive
- Odoo
- n8n & Make
- Microsoft 365
- Google Workspace
Who this is for
Who a retainer suits.
Businesses just past launch
The first six months after go-live is when a system is most likely to drift and easiest to keep on track.
Teams with no internal technical owner
Where nobody’s actual job is to notice that something needs updating.
Operations running live automations
Anything running unattended needs someone watching it, or a failure becomes a customer complaint.
Businesses that keep changing
New services, new locations, new people — each one is a change the systems have to absorb.
In practice
What a typical month looks like.
A new service line goes live
Website pages, CRM fields, quote templates, and reporting all updated in the same month the business launches it.
An integration breaks after a vendor update
An alert opens an incident, the team checks impact and a workaround, then repairs the integration under the agreed response plan.
Steady conversion improvements
Small, evidence-led changes to the pages that produce enquiries, reviewed against what the analytics actually show.
A quarterly review that removes something
A look at the whole stack that ends with cancelling a tool nobody uses — occasionally paying for the retainer by itself.
Published starting prices
What ongoing support costs.
Choose 5, 12, or 20 reserved hours per month. Requests are prioritized with you; updates, monitoring follow-up, small changes, and support use that allowance.
Light Touch
$750/mo
Best for: Teams that have launched and want to stay current without a standing workload.
- 5 hours per month
- Updates and platform upkeep
- Monitoring and failure alerts
- Small content and config changes
- Monthly check-in
Business Retainer
$1,500/mo
Best for: The most common arrangement — regular changes, small builds, and steady improvement.
- 12 hours per month
- Everything in Light Touch
- Small builds and CRM changes
- Automation maintenance and additions
- Quarterly stack and roadmap review
Priority Partner
$2,500/mo
Best for: Businesses in active growth who need dedicated capacity month to month.
- 20 hours per month
- Everything in Business Retainer
- Priority response
- Ongoing strategy and roadmap sessions
- Continuous improvement programme
Work beyond the allowance is approved before it starts; larger builds are scoped as separate projects. Urgent requests follow the response expectations agreed for your tier, not a 24/7 guarantee. Three-month minimum, then 30 days’ notice; unused hours do not roll over. Project handoffs include 30 days of post-launch support without a retainer.
How it runs
The same process, every engagement.
You always know what's happening now, what's next, who owns it, and what it costs.
Discover
A free call to understand your business, goals, and current systems. No pitch, no pressure.
Plan
A written proposal with scope, deliverables, timeline, and a fixed price — approved before anything starts.
Build
Design, development, and configuration with regular check-ins so you stay informed end-to-end.
Launch
Deployment, training, and handoff documentation. Includes 30 days of post-launch support.
Support
Ongoing maintenance, improvements, and a partner who knows your systems as you grow.
Questions
What people ask before starting.
Do you support systems you didn’t build?
Yes, and it is a large share of the work. We start with a short review to understand how it is put together and what state it is in, so we are not making changes to something we do not yet understand.
What happens to unused hours?
They do not roll over. A retainer is reserved capacity rather than a prepaid balance — that is what makes the response commitment possible. If you are consistently under, we will suggest moving you down a tier rather than letting it run.
Are we locked in?
Three-month minimum commitment, then 30 days’ notice to cancel. The first month includes learning your systems and setting priorities for the work ahead.
Is a retainer required after a project?
No. Every project includes 30 days of post-launch support, and plenty of clients stop there. Many continue because small changes are cheaper and faster inside a standing arrangement, but it is a choice rather than a condition.
What if we need more than our hours in a month?
We tell you before the work starts, not on the invoice. Either it waits, or we agree the extra explicitly. If it keeps happening, the honest answer is a different tier or a separate project, and we will say which.
Who do we actually deal with?
The same person each month — someone who already knows how your systems are built. That continuity is most of what you are paying for compared with a general support queue.
The wider ecosystem
One business. More than one type of problem.
AdōDesign Digital handles the operational side. When a project needs something else, it stays inside the same team.
- AdōDesign StudioWhen the work needs 3D product visuals, renderings, animation, or video production.
- AdōDesign AppsWhen an off-the-shelf tool will not fit and the business needs its own portal, dashboard, or internal application.
- AdōDesignThe parent brand, and the shortest route to the right part of the ecosystem for anything outside Digital.
The next step
Let’s work out what your systems need month to month.
Thirty minutes on what you are running, what has already drifted, and what a sensible level of ongoing involvement looks like. Often that is less than people expect.
- 01
A conversation
Thirty minutes on what is slowing the business down. No pitch, no deck.
- 02
An honest read
Where we would start, what can wait, and whether we are the right fit at all.
- 03
A written scope
Only if it makes sense — deliverables, timeline, and a fixed price, in writing.