The problem we solve
After launch, most products end up without a technical owner. A user reports something in a side conversation and it is forgotten. Security updates are deferred because nobody is confident they will not break anything. When a real incident happens, the search begins for an available developer rather than one who understands the system. Spending shifts from scheduled maintenance to emergency repair, which costs more, takes longer and is far more visible to your customers. Meanwhile the product stops evolving, frozen until some future project that keeps getting postponed.
Expected outcomes
- One accountable team instead of a scramble for whoever is free.
- Regular security updates, validated on a separate environment before they touch production.
- A visible priority list that you control and that gets worked in agreed order.
- Known response times for each severity level, agreed before you need them.
- Steady improvements reaching users, rather than a product frozen until the next big project.
- A documented record of what changed and why, that survives staff turnover on both sides.
Who this is for
- Companies with a live site or platform and no in-house engineering team.
- Small technical teams that need extra capacity without permanent hires.
- Online retailers who cannot afford downtime during peak trading periods.
- Organisations that inherited a system built by someone else and lost the knowledge with them.
- Products that need continuous small improvements more than another large rebuild.
Use cases
- Taking over an existing site or system built by another team and maintaining it properly.
- Routine security patching for the platform, plugins and dependencies.
- Resolving reported defects within an agreed response time.
- Ongoing small improvements: pages, reports, integrations, interface refinements.
- Availability and performance monitoring with alert handling.
- Preparing a platform ahead of an expected peak season and standing by through it.
Deliverables
- A takeover document describing the system, its environments and known weak points.
- A service level agreement setting response times per severity level.
- A shared task board showing the live status of every ticket and request.
- A monthly report on work delivered, updates applied and risks observed.
- A documented changelog for every release applied to production.
- A rolling improvement plan, revisited at each review session.
Project phases
Takeover
Inventory of environments, access, dependencies and current state, with visible risks documented.
Stabilisation
Clearing the urgent items: trustworthy backups, overdue updates and obvious configuration gaps.
Steady operations
A monthly cycle of tested updates, monitoring and triaged fixes under the agreed severity policy.
Continuous improvement
Agreed enhancements delivered within the monthly allocation and released in small, reviewable increments.
Review
A recurring session covering delivered work, observed risks and reordered priorities for the next period.
- Estimated timeline
- 2 to 4 weeks
- An estimate that depends on scope and how quickly reviews come back — not a contractual commitment in itself.
- Pricing
- After scoping
- Billed monthly, priced against system size, the response level you need and the monthly development allocation. The duration shown above covers takeover and stabilisation only; the retainer then continues month to month with an agreed notice period. Hosting and licence costs are paid by you directly.
Scope and working details
What is in and out of scope, how we work, and what we need from you.
What is included
- A documented takeover: environments, access, dependencies and known risks.
- A defined support channel and a severity policy separating outages from improvement requests.
- Security updates for the platform, plugins and libraries, tested on staging first.
- Scheduled backups with periodic verification that a restore actually works.
- Availability and performance monitoring on your critical pages and user journeys.
- A monthly development allocation for improvements you prioritise.
- A recurring review session to re-rank priorities for the period ahead.
- A monthly report covering what shipped, what slipped and why, and what we recommend next.
What is not included
- Building a new product or a major module — scoped and quoted as a separate project.
- Supporting third-party systems we have no access to or authority over.
- Marketing campaign management, content production or design work.
- Hosting, licence and third-party subscription costs.
- Round-the-clock response, unless explicitly added to the agreement.
How we work
We begin with a real takeover rather than a formality: environments, access and dependencies are inventoried, and we document what exists rather than what is assumed to exist. The system then settles into a steady monthly rhythm — tested updates, monitoring, triaged fixes, and improvements delivered within the agreed capacity. Every request is logged on a shared board you can open at any time, so nothing disappears into a chat thread. And because priorities shift, we sit with you regularly to reorder them instead of grinding through a stale plan.
What we need from you
- Administrative access to the platform, hosting and source repository.
- One person on your side who sets priorities and answers open questions.
- Issues reported through the agreed channel, not scattered across private messages.
- Approval to apply security updates within agreed maintenance windows.
- Authority to purchase any subscription or licence the system depends on.
Methodology and technology
Anything that touches production is tested on a separate staging environment first, kept under version control, and recorded in a readable changelog. Tickets are managed on a shared board with a severity model that distinguishes work-stopping faults from schedulable requests. Monitoring covers availability and the performance of critical user journeys, with automated alerting. On WordPress sites we update core, plugins and themes after testing, and take a restore point before each update window. On custom applications we update dependencies and run the existing automated test suite before any release. A backup is not considered valid until a restore has been performed from it.
How this connects to the rest of our work
A service rarely works alone. These come before it or alongside it, and these are the solutions it forms part of.
Services that work with it
Cloud and DevOps Solutions
Stable cloud infrastructure and automated releases, with monitoring and cost you can actually see.
Corporate Website Design & Development
A fast bilingual corporate site that turns visitors into enquiries — and that your team can edit.
Web Applications and SaaS Development
A web app or SaaS product built around your real process — permissions, integrations and code you own.
APIs and Systems Integration
Documented APIs and an integration layer that keeps your systems in step — and alerts you when it cannot.
Part of these solutions
Frequently asked questions
What is the difference between maintenance and development here?
Maintenance is what keeps the system sound: security updates, backups, monitoring and fixing faults. Development is what adds new value: a page, a report, an integration, an interface improvement. The retainer covers both, and maintenance always takes precedence — building on an unstable system is wasted money.
Will you take on a system another agency built?
Yes, and roughly half our support work is exactly that. We start with a takeover review of the code, environments and dependencies. If we find structural problems that would make maintenance expensive, we put them in front of you with realistic options — gradual remediation or rebuilding a specific part — before an agreement is signed, not after.
What happens if something breaks outside working hours?
The standard agreement covers business hours, while automated alerts reach us at any time and we act on what can be handled remotely. If your business genuinely cannot absorb an overnight or weekend outage — a store in peak season, for example — extended cover is written into the agreement as an explicit term rather than left to goodwill.
Does unused development capacity roll over?
We put the answer in the agreement. The usual arrangement is partial rollover for a limited period, because the capacity is reserved in the team schedule whether or not it is used. If your business is seasonal, we shape the agreement around that from the start.
How do I end the retainer, and what do I get back?
With the agreed notice period and no exit penalties. You receive everything: full access, source code, documentation, the changelog and hosting details. Accounts are in your company name from the first day anyway, and we run a handover session for whoever picks the work up.
Can the retainer cover a large new feature?
The retainer suits continuous small and medium improvements. A large feature needs analysis, design and testing beyond the monthly allocation, so we scope it as a separate project with its own timeline. Support continues uninterrupted alongside it.