Ongoing technical support: someone who answers, not a ticket into the void.
Bugs, updates, backups, performance. We keep WordPress sites, Laravel applications and legacy systems running on a written retainer, with one person who knows your project — not a different support form every time.
The starting point
The site is there.
Whoever keeps it up, is not.
People almost always call once the problem has already happened. Maintenance exists to move that phone call earlier.
How it goes without support
You find out from your clients
Nobody looks at the site until someone reports that it is broken.
Updates postponed out of fear
Every update is a gamble, so nothing gets updated. And the holes stay open.
Backups nobody has ever restored
They exist, probably. The day you need them you find out whether they were any good.
Every fix is a negotiation
Quote, wait, chase. For a twenty-minute change.
How it goes on a retainer
We see the problem first
Uptime, errors and performance monitored: we step in before anyone reports it.
Updates tested on staging
Test first, then go live. If something breaks, we roll back.
Backups actually verified
Restores get tested, otherwise it is not a backup: it is a folder.
Hours included every month
Small changes just get done, with no negotiation each time.
What it covers
Six things we do
every month.
Not on request: they are the content of the retainer, and at the end of the month they are written in the report.
Bugs and failures
Fixes on WordPress, Laravel and legacy systems, starting from whatever is blocking work.
Security and updates
Core, plugins, themes and dependencies updated on staging before going live. Known vulnerabilities closed.
Verified backups
Automatic copies kept off the site server, with periodic restore tests.
Monitoring and performance
Uptime, response times and errors under control. If the site slows down, we know first.
Small changes included
Copy, images, a new page, one more field in a form: that is what the included hours are for.
Monthly report
What was updated, what was fixed, how long it took. As a PDF, every month.
How we start
Three steps,
then it runs.
The first month is for finding out what is there. Surprises show up before signing, not after.
Initial check-up
We look at versions, backups, security and performance of what you have. Free, no commitment.
Output: written report
Securing
We close what is urgent: overdue updates, known holes, missing backups.
Output: a site in order
Monthly retainer
Monitoring, updates, fixes and included hours, with one person who knows the project.
Output: a report every month
How it differs from Software Rescue
First you recover it,
then you keep it alive.
Frequently asked questions
What people ask before signing.
Yes, and it is the most common case. We run the check-up first: if the site has structural problems we say so, rather than taking a retainer on something that will break anyway.
WordPress and WooCommerce, Laravel and Vue.js applications, and legacy PHP systems. If it is something we do not follow we say so straight away.
It depends on how many sites, how many hours are included and how critical uptime is. The retainer is written in the contract and does not change by surprise: after the check-up you know the exact figure.
Extra hours have a rate stated in the contract. We tell you how long it will take before starting: no surprise work on the invoice.
Always. Access, code and backups are yours and stay yours even if one day you change supplier. We hand everything over without fuss.
Six months to begin with, the time needed to clear the backlog and see whether it works. After that, month by month.
Let us start with the check-up.
It is free.
We look at versions, backups, security and performance of your site and tell you what you actually need. If you do not need a retainer, we will say so.
ISO 9001:2015 certified
Written requirements, tracked changes, a defined path for every issue.
Benefit Corporation
Goals written into the bylaws, an impact report every year.
Listed on MePA
The Italian public sector e-procurement marketplace.
