Ongoing care for the software your business runs on
Our support plans keep live software healthy. For a fixed monthly fee, we keep your application secure, current, and improving: security patches, dependency updates, monitoring, bug fixes, and a block of development hours for the changes your business needs. It is planned care, not a break-fix number you ring once something has already gone wrong.
Software is never finished. Requirements change, security vulnerabilities get discovered, frameworks release updates, and the third-party APIs you depend on evolve or occasionally disappear. A system that was current two years ago is quietly accumulating risk today. The question is not whether yours needs attention, but whether that attention is planned or reactive. A support plan is the planned kind.
No long contract and no lock-in. It runs month to month, you give a month's notice to pause or change plan, and what you get is a guaranteed slice of our team's time each month. Not unlimited work, which nobody can honestly promise, but a dependable amount you can rely on.
Three plans, scaled to how much your software is moving
Not every system needs the same attention. A stable application that rarely changes needs watching and patching. One that is central to daily operations and always evolving needs hours and fast response. Pick the plan that matches today, and move between them as things change.
Essential
The baseline plan
Security patches, dependency updates, performance monitoring, and bug fixes, with next-business-day response. Keeps a stable, working system healthy and secure without drama.
Active
Everything in Essential, plus
A block of development hours every month for new features and changes, and faster response. For systems that keep evolving alongside the business.
Priority
Everything in Active, plus
More development hours, same-day priority response for critical issues, and a named lead who knows your system. For software your operations depend on hour to hour.
If your system is stable enough that even Essential is more than you need, we also work pay-as-you-go: you call when something needs doing and we scope and quote it. The trade-off is the queue. That work is scheduled around our plan clients, so it waits its turn.
What every plan includes
The baseline under every plan is the work that keeps an application secure, current, and reliable. The higher plans add development hours and faster response on top of this. They do not unlock the basics, because the basics are never optional.
-
Security patches Framework and dependency security updates applied promptly. We run a dependency audit (for Laravel, that is
composer audit) so when a vulnerability is disclosed, your system gets patched before it becomes a problem. -
Dependency updates Regular updates to keep your application on supported versions of its framework, language, and packages. Staying on a Laravel long-term support release means small, frequent updates instead of large, risky ones.
-
Performance monitoring We keep an eye on response times, error rates, and resource usage, so slowdowns and issues are caught early, often before your team notices them.
-
Bug fixes When something breaks, it gets fixed. On the Active and Priority plans you do not wait for a separate quote and approval cycle. We fix it and report back.
No lock-in. Month to month, a month's notice to pause or change. We keep clients by being worth keeping, not by tying them in.
What maintenance actually involves
The work breaks down into four categories, the same four set out in the international standard for software maintenance (ISO/IEC 14764). Understanding them explains why "it is finished, we do not need to touch it" is not a viable long-term position.
Corrective
Fixing bugs. Every application has them, no matter how thorough the testing. Some surface the week after launch, others lurk for years before a specific combination of inputs brings them out. Corrective maintenance keeps the system working as intended.
Adaptive
Keeping the system compatible with the world around it. PHP releases a new version roughly once a year and supports each for about two. A payment provider updates their API. A browser drops a feature you rely on. Adaptive maintenance keeps your application working as everything underneath it moves on.
Perfective
Adding features and improving what exists as your business changes. A new product line needs tracking. A workflow that made sense two years ago no longer matches how your team operates. Perfective maintenance keeps the software aligned with the business it serves.
Preventive
Refactoring code, improving test coverage, and addressing technical debt before it becomes a problem. This is the maintenance you never see the results of directly, because the result is the absence of the crisis that would have happened without it.
What happens without it
We have seen this pattern enough times to describe it with confidence.
Year one: Everything seems fine. The system works. Small things occasionally need attention but get worked around. Dependencies fall one version behind, then two. A security patch gets missed. Nobody notices.
Year three: The framework is two major versions behind. Upgrading is no longer a simple update; it is a project in itself. Several dependencies have known vulnerabilities. The PHP version is approaching end-of-life. You are now facing an expensive crossroads: invest significantly in catching up, or start talking about a rebuild.
The cost of ongoing care is a fraction of the cost of that catch-up work. Regular, planned attention keeps a system in a state where updates are small and affordable. Neglect turns them into projects. Our software maintenance strategy page explores this in depth.
Who it is for
A support plan suits anyone with a live application their business depends on, whether we wrote it or not.
The long view
We are still maintaining systems we built in 2008. Not because the clients are locked in, but because the relationship works. They have a team that knows their system inside out, responds quickly, and cares about the quality of what runs under their name.
Software that gets regular attention does not age the same way as software that gets ignored. It stays current, stays secure, and keeps serving the business year after year. In our experience the clients who have been with us longest tend to spend the least per year, because steady investment prevents the expensive catch-up work that neglected systems eventually demand. That is also the difference between owning the software your business runs on and slowly losing control of it.
Keep your software healthy
Whether we built it or you are bringing us an existing system, we will look after it properly. Tell us what you have and we will recommend the right plan. The first conversation is free and comes with no obligation.
Talk to us about your system →