Production software needs someone who will look at a real error, change the smallest amount of code that fixes it, and tell you what happened. That is this service. It is also where framework upgrades live when you do not want a new product, you want the one you have on a supported version.
Who this is for
- The app is live and something is broken.
- Dependencies are old enough that you cannot safely install anything new.
- You want a known number of hours each month instead of opening a new contract for every small change.
- The original developer is gone and you need a read of the repo before anyone promises a date.
This is not unlimited support and not a helpdesk for your customers. Your users still contact you. We contact the code.
What we build
- A reproduced bug, a cause, and a fix in the repository.
- Upgrades that keep behaviour the same unless you asked for a change. Behaviour changes are listed, not slipped in.
- Retainer work against a written hour block. Each block of time has a short note: what was done, what was left.
- Dependency updates you have agreed to, not a surprise major-version jump.
The support window after a new build is a different thing. That window is agreed on the original project quote. A retainer starts when you want cover beyond it. The number of days in a standard support window is confirmed when you set it; until then it is not stated as a fact on this page.
Process and timeline
For a bug, send the steps and the error. We reproduce it, then quote a small fixed price or a handful of hours. For an upgrade, we read the dependency list first. For a retainer, we agree the monthly hours, the kinds of tasks that fit, and how unused hours are treated. Unused-hour rules are written in the agreement, not assumed here, until you confirm the policy you want.
Response during the working overlap is part of the arrangement. Exact hours are listed once you confirm them. See how we work for billing and reporting, and pricing for the three engagement types.
What changes the price
How quickly the bug reproduces, whether production data is required, how far behind the framework is, and how many hours you want reserved each month.
Related services
Laravel and PHP when the change is really a feature, not a fix. AWS and deployment when the failure is the server, not the application code.