What This Is
A support retainer is a predictable monthly commitment that gives your business ongoing access to development, maintenance, and support — without needing to scope and price every change as a separate project. You get a set amount of development time each month, used for whatever your system needs: new features, bug fixes, integrations, performance improvements, security updates, or system changes as your business evolves.
This is not a help desk. It is a continuing development relationship. The same team that built your system continues to improve it — which means no onboarding period, no context loss, and no explaining how your business works to a new developer every time something needs changing.
Most of our long-term client relationships are retainer-based. A typical pattern: we build a system as a project engagement, it goes live, and the client moves to a retainer because the system needs to keep evolving. The first month is bug fixes and adjustments. By month three, the client is requesting new features they did not know they needed until they started using the system daily.
When You Need This
A retainer becomes the right model when your system is live and you need ongoing development capacity without the overhead of project-scoping every change. Common scenarios:
- Your system is in production and needs regular maintenance — security patches, dependency updates, framework upgrades, and monitoring
- You have a steady stream of small-to-medium changes — new features, workflow adjustments, integration updates — that do not warrant a full project engagement each time
- You need priority access to a development team that already knows your system, rather than competing for availability in an ad-hoc arrangement
- Your business is growing or changing and the system needs to keep up — new user roles, new integrations, new reporting requirements
- You want predictable costs rather than surprise invoices when something breaks or needs updating
This is not the right model if you have a single, well-defined project with a clear end point. That is a project engagement. Retainers are for ongoing evolution, not one-off builds.
How We Work
Retainers run on a monthly cycle. At the start of each month, we align on priorities — what needs to happen this month, what can wait, and what has changed since last month. During the month, you can add or reprioritise requests as they come up.
The engagement is flexible by design:
- No minimum term — retainers run month to month, though most clients stay for years because the value compounds
- Rollover or flex hours — if you do not use your full allocation one month, we can flex it into the next (within reason)
- Direct communication — you have a dedicated channel to the team working on your system, same as during a project engagement
- Same-day response for urgent issues — if something is broken in production, it does not wait for the next planning cycle
The work itself follows the same iterative approach as our project work — short cycles, working software, direct communication. The difference is that the engagement is continuous rather than having a defined end point.
What You Get
- A set monthly development allocation — predictable cost, predictable capacity
- Priority access to a team that already knows your system architecture, codebase, and business context
- Maintenance and security — dependency updates, framework patches, and monitoring included
- Feature development — new capabilities, integrations, and improvements as your business evolves
- Bug fixes and performance work — issues resolved quickly by a team that knows the codebase
- Monthly reporting on what was delivered, what is coming next, and any risks or recommendations
What It Costs
Retainer pricing depends on the level of ongoing development your system needs. We offer retainers at several tiers based on monthly hours. Get in touch for specific pricing, or see our pricing page for more detail.
Related Systems
Retainers are how most of the systems we build continue to evolve after launch. A client portal that launches with five features has twelve by the end of year one. A reporting dashboard that starts with three data sources adds new integrations as the business adopts new tools. The retainer is what makes systems living infrastructure rather than frozen deliverables.
Start a Retainer
If you have a system that needs ongoing development — or you are about to launch one and want continuity from day one — get in touch and we will design a retainer that fits.
