Skip to content
Audixa
Audixa

Service

Somebody keeping an eye on it after launch

Software that is finished still decays. Dependencies get advisories, certificates expire, a provider changes an API, and the small change nobody had time for turns into the reason a page is broken for a month. Maintenance is a monthly arrangement to run the checks, apply the updates, and be the person who answers when something is wrong.

Talk to us about maintenance

A person reads it and replies, usually within two working days.

What it costs

A monthly fee, quoted after the initial review and based on how many applications are covered and how much change you expect. Cancellable monthly. Work beyond the allowance is quoted before it starts, never after.

Who it suits

Three situations this is for

  • You have something live and nobody watching it

    The build works and the developer moved on. This is the most common situation we are asked about, and the one where an advisory sits unread the longest.

  • You are an agency with sites you still get called about

    A dozen client sites you delivered and still feel responsible for. A monthly scan across all of them turns an incident into a maintenance conversation you can bill for.

  • You need small changes without a project each time

    A price change, a new page, a form field. Each one is twenty minutes and none of them justifies a statement of work.

How it goes

The engagement, step by step

Written out because the thing people actually want to know before sending an enquiry is what happens next, and how easy it is to stop.

  1. A review of what you have

    One-off, before any monthly arrangement starts. We need to know what is there before promising to look after it, and occasionally the answer is that something needs work first.

    Quoted separately, and it is not wasted if you decide not to continue.

  2. An agreement naming the projects and the allowance

    Which applications are covered, how many small changes a month, and how quickly we answer. Monthly, cancellable monthly — a maintenance contract with a lock-in is a contract that stops earning its keep.

  3. Every month, the same routine

    Scan, triage, update, deploy, write it down. The note is short and it says what we did nothing about as well as what we changed, because the things deliberately left alone are the ones you would otherwise wonder about.

  4. Anything larger is quoted separately

    A new feature or a version upgrade that touches everything is a piece of work, not a small change. We quote it and you decide, rather than it quietly consuming the month's allowance.

What you end up with

  • A scan every month across the projects in the arrangement, with the findings triaged rather than forwarded
  • Dependency and security updates applied and deployed, with anything risky flagged before it lands
  • A short monthly note: what was updated, what was found, what we recommend and what we did nothing about
  • An agreed allowance of small changes each month, whatever they are
  • A named person to email, with a response time in the agreement rather than implied

Boundaries

What this does not include

Better to find the edge here than after an invoice.
  • We are not a 24/7 on-call rota. Response times are within working hours and the agreement says exactly what they are, because implying otherwise would be the dishonest part.
  • We do not take over an application without reviewing it first. Agreeing to maintain something unseen is how you end up responsible for a decision nobody wrote down.
  • Major version upgrades and new features are quoted separately rather than absorbed into the monthly allowance.
  • Maintaining an application does not make it secure, and a month with no findings is not a certificate.

Questions

About maintenance and evolution

Do you maintain applications you did not build?

Yes, after a review. That review is the whole basis of the arrangement — we cannot commit to keeping something running while it is still a surprise to us.

What counts as a small change?

Something a competent developer finishes inside an hour without changing how the application works: text, an image, a price, a form field, a redirect. The agreement gives examples, and when something is borderline we ask before spending your allowance on it.

Can I just have the monthly scan without the changes?

That is a paid plan rather than a service. A Pro or Agency subscription gives you the scans and the findings; this arrangement exists for when you want somebody to act on them.

Send an enquiry

Talk to us about maintenance

Enough detail that we can give you a real answer rather than ask for a call to find out what you meant.
No obligation, no automatic charge

Sending this does not commit you to anything and does not start any billing. You will get a confirmation with a reference straight away, and a reply from a person after that.

Incluye el prefijo del país, por ejemplo +34.

Opcional.

Opcional. Nos ayuda a revisar tu infraestructura previa.

Qué tienes, qué necesitas y los plazos previstos. Unas pocas frases son suficientes.

Opcional.

Un especialista lee cada solicitud. Recibirás una confirmación con número de referencia de inmediato y una respuesta técnica personalizada. No hay cargo automático.