Performance & SEO
Premium Support & Continuous Evolution
A technical retainer with committed response times, monitoring that alerts before a customer notices, and a monthly development allowance spent on whatever adds the most value. Not reactive support - evolution with a direction.
Per branchOne diary per location, one system · GIGI Nails
Sound familiar?
- When something breaks, the email round starts to find out who can look at it.
- Your platform has not changed in two years because it is never anyone priority.
- You pay for maintenance and cannot say what you get in return.
- You find out about outages because a customer tells you.
Why a site degrades on its own
It does not degrade from use. It degrades because the environment moves while the site stands still: dependencies shipping security patches, browsers changing behaviour, third-party services retiring an API, and ranking criteria tightening.
A project with no continuity agreement does not break in month one. It breaks eighteen months in, all at once, and fixing it then costs more than maintaining it would have.
What separates a retainer from maintenance
The word evolution. Classic maintenance is reactive: you pay for someone to answer when something fails, and if nothing fails, nothing happens. The result is a platform that has been identical for two years while the business changed three times.
Here there are two deliberately separate budgets. Incidents are handled under a severity-based SLA. Separately, a monthly development allowance is prioritised with you and delivered in sprints. If a month had no incidents, that month there is more product - not a better excuse for the invoice.
What gets measured
Uptime, incident response time, field Core Web Vitals and patches applied. All of it goes into the monthly report, alongside what was built and what we propose next. A retainer you cannot audit with numbers is a subscription fee, not a service.
What you get
- Committed response times by severity, written into the agreement.
- Uptime, error and Core Web Vitals monitoring, alerting before a user notices.
- Monthly development allowance prioritised with you and delivered in sprints, not burned firefighting.
- Dependency updates and security patches, with a record of what was applied.
- Verified backups - we test the restore, not just the backup.
- Monthly report covering what was done, what was measured and what we propose next.
How we work
- 01
Handover
1 to 2 weeksPlatform inventory, access, known fragile points and a baseline for uptime and performance.
- 02
Going on watch
1 weekMonitoring set up, alerts routed to your team channel, and backups verified through a real restore.
- 03
Monthly cycle
ongoingEvolution sprint prioritised with you, patching kept current, and a closing report with what was done and measured.
Investment
Scoped quote
A costed proposal within 3–5 business days
Scope drives price. Send us the project: within one business day we tell you whether it fits, and the proposal — what is in, what is out and what it costs — arrives within three to five business days.
Monthly fee based on service level and the development allowance. Reviewed each quarter with the report in hand, not at annual renewal.
Proof of work
Frequently asked questions
What does 24/7 monitoring mean?
That checks and alerts run continuously, every day. Human response follows the agreed severity-based SLA: a full outage and a typo on one page cannot carry the same commitment, because paying for that would be absurd. What gets signed is the response time per severity level, in writing.
How is this different from normal maintenance?
The development allowance is not for firefighting. Incidents are handled separately, under SLA. The monthly allowance goes to evolution prioritised with you, which is why at the end of the month there is something new running instead of an invoice with no story.
What if we do not use the hours in a given month?
They roll over within the quarter. What we do not do is let them expire quietly, or push unnecessary work to justify them - both destroy the trust a retainer runs on.
Do you work on platforms you did not build?
Yes. The handover includes an inventory and a fragility review. If we find something that makes the service commitment unsustainable, we say so before signing, not at the first incident.
How do I know the backups are any good?
Because we actually restore them, into a separate environment, on a schedule. A backup that has never been restored is not a backup, it is an assumption.