What Does a Monthly PHP Maintenance Retainer Cover vs Evolution?

By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.

Adrian's GitHub · Adrian's LinkedIn.

Published: · Last technical review:

My PHP maintenance retainer, from €60/month + VAT*, covers security updates, backups, and bug fixes for existing PHP and MySQL applications, built by me or third parties. New features and evolutions are analysed and quoted separately in writing, without confusing maintenance with unlimited development.

Criteria: distinguish maintenance from a new feature

If you have an application running, I propose explaining separately what you need to keep, the bug you observe, and the new capability you want to add. They are related conversations, but my offering does not present them as a single unlimited service.

As preparation, describe the expected behaviour before using the word «bug». Then indicate whether you are asking the application to do something it did not do yet. I am not deciding the classification of your request from here; I propose a way to raise it without hiding scope changes behind a generic phrase.

Published conditions that I can cite

Maintenance : Includes security updates, backups, and bug fixes.

Evolution : New features are quoted separately.

Monthly benchmark : Maintenance from €60/month + VAT*.

Existing applications : Can be PHP applications I built or others already operational in your company.

These conditions do not establish a number of interventions, working hours, or a restoration procedure. Nor do they turn the starting price into a quote for any application. It is important to read what is published without completing its boundaries with expectations we have not agreed upon yet.

My own proof: the scope of my service

On my homepage, I describe the work of maintaining, fixing, and evolving existing PHP and MySQL applications. The FAQ reaffirms that offering and separates new features once again. I can use both parts as evidence of scope, not as a specific contract for your company's system.

I propose that you describe a specific need and the outcome you expect to review before making a decision. A visual reference does not replace that analysis, nor does it substantiate compatibility, coverage, or results in your project.

If you need an additional condition, I propose naming it. "Maintenance" is a service category; it does not replace the conversation about your tool and its requirements. My published process requires analysing each project and agreeing on deliverables, timeframe, and quote in writing before development.

Security and backups: what you should not assume

The inclusion of security updates substantiates one part of the service, but it does not allow me to promise an absence of incidents or take an unfamiliar application as reviewed. I propose explaining what system you have and what doubts you need to resolve before describing concrete coverage.

Backups are part of maintenance. I make daily backups of the entire database and files, retaining them for 7 days on my server. The restoration procedure must be specified for your application.

I make daily backups of the entire database and files, retaining them for 7 days on my server. If your website, web application, or contracted service goes down, notify me by email or WhatsApp: I respond within one hour. This is an initial response time, not a resolution deadline. For commercial inquiries, I will reply within 24-48 business hours.

The written scope must set out the conditions of your application, rather than relying on generic assumptions about what a backup covers or how the service would be recovered.

How to separate an evolution request

As a preparation exercise, first write down what the application does today. Then write down what you want it to do differently. If you need to incorporate a new feature, my published condition is to quote it separately; I do not present it as a fix covered by default.

If the expected behaviour is not clear, I propose flagging that uncertainty. You do not need to prove the cause of the problem yourself to contact me, but neither is it advisable to claim something is a bug simply because it does not match a new need. The distinction must rest on scope and evidence of the case.

In the checklist self-assessment, you can separate these needs: whether you already have a PHP and MySQL application with bugs or pending changes, what security, backups, and evolution you need to agree on, and what deliverables we will set out in writing.

When you should NOT hire based on an implicit expectation

You should not hire a retainer thinking it covers any subsequent development. My offering states the opposite regarding new features. Nor should you interpret the initial response to an inquiry as a resolution commitment: the published response time and project turnaround are distinct concepts.

If what you want is to build a tool that does not yet exist, the starting point may correspond to the application service, not to the maintenance of an operational application. I propose explaining that difference before discussing the monthly benchmark. The offering distinguishes categories and does not justify fitting any requirement into the lowest-cost one.

What I propose you prepare in writing

You can write a summary of what your application is used for, what you need to address, and what you expect to keep. Add separately the improvements you would like to have assessed. If you do not know a condition regarding code or hosting, indicate it as pending without disclosing credentials.

For the conversation about maintenance, you can finish with specific questions about what does not appear detailed in the offering. You do not need to invent a technical policy: it is enough to identify what you need clarified. The goal of this preparation is that we can discuss the real service, not a coverage expectation built on assumptions.

How to read the monthly benchmark

When assessing the benchmark from €60/month + VAT*, keep in mind that the specific scope is defined for each application after reviewing it, always keeping the separation clear between periodic maintenance and the separate quotation of new features.

How we agree on maintenance or evolution for your PHP

Tell me via the form or WhatsApp what PHP and MySQL application you have running, and I will reply within 24-48 business hours with an initial written diagnosis. Before starting, we set out in writing what the monthly maintenance covers (from €60/month + VAT*) and, if you need new features, their scope, timeframe, and budget separately.

A clear request prevents mixing coverage

When you communicate a need to me, identify what behaviour you want to keep and what change you expect. If the problem affects a feature you already use, describe what happened and the expected outcome. If you want to incorporate another way of working, note it down as an improvement to be assessed, even if it appears while reviewing a bug.

For backups, prepare the questions you need to clarify: what information must be recovered, what material exists, and who can authorise a review. Do not publish access credentials to answer them. The retainer is a maintenance benchmark, not an implicit authorisation for any intervention, nor a guarantee that a specific backup is usable without testing it.

Frequently asked questions

Does it include security and backups?

My PHP maintenance, from €60/month + VAT*, includes security updates, backups, and bug fixes for existing PHP and MySQL applications. I make daily backups of the entire database and files, retaining them for 7 days on my server. Verification and restoration are specified for your application, without promising unlimited protection.

Are new features charged separately?

New features for a PHP application are quoted separately from maintenance. I distinguish with you the behaviour that should be kept from the additional capability you want to incorporate. If there are doubts about that difference, I review the scope and the specific case before classifying the request; a retainer does not imply unlimited development.

PHP maintenance and evolution

PHP maintenance and evolution

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Related articles

* Indicative starting prices, subject to conditions and change. VAT not included: charged separately at the applicable rate. The final amount is set in a written quote after reviewing your project and is binding only once accepted by both parties. Quotes are valid for 30 days. Full terms: General terms.