06 / Sustain · Continuity
We maintain and evolve the tools we made for you, with coverage and response times agreed in advance.
When we get the call
This is how most enquiries start, and this is what changes once we solve it.
“We want peace of mind that what works will keep working.”
Whatever fails is handled within the agreed times, by people who know the system inside out.
“Every so often something breaks and we find out late.”
Updates, monitoring and backups that are actually tested.
“We want to add features, and the tool is no longer enough.”
New features and adjustments prioritised by impact, reviewed with you.
“We never quite know what was done or what is missing.”
A record of every intervention and a regular review of what comes next.
What it looks like
This is what a sample year looks like: the system keeps improving after delivery.
Month 1
Catch-up
Access, backups and monitoring reviewed: we start knowing where everything is.
Month 2
Update
Versions and security patches up to date, outside working hours.
Month 3
Improvement
An adjustment your team asked for: a filter, a report, one step fewer.
Month 4
Prevention
A test restore, to know the backup actually works.
Month 6
Review
We go over what was done with you and reprioritise what comes next.
Month 8
New feature
Something the business started to need, built on top of what was already there.
Month 10
Update
The platform up to date, with no surprises for your operation.
Month 12
Year in review
What improved this year and the plan for the next.
What we built, healthy and up to date after handover.
The solution keeps pace with the business as it grows.
How we do it
What is covered, during which hours and with what response time.
You keep The coverage agreement, in writing.
Access, backups and monitoring reviewed before we start.
You keep The state of the system, documented.
Updates, backups and attention to whatever fails, within what was agreed.
You keep A record of every intervention: what happened and what was done.
Improvements are prioritised by impact and reviewed with you.
You keep The improvement plan, reviewed from time to time.
The system, the documentation and the access remain yours, always.
How long it lasts It is ongoing: it starts when the project goes into production and lasts as long as you need it. The price comes from what has to be covered and during which hours.
What we need from your side
What you take away
Questions
It depends on what has to be covered and during which hours. The price comes from that scope, is agreed in writing and does not change with every call.
Whatever we agree for your operation: which hours, what response time and how much improvement work per month. It is written down before we start.
If your operation needs a response at night or at weekends, it goes into the agreement from the start: that way it is covered before it is needed.
First we analyse it and set up a project to standardise and fix it. Once it is in order, we look after it like anything we built ourselves.
See BuildA large feature is handled as a project, with closed scope and price, and then returns to the coverage plan.
Next step
A conversation to understand the problem before talking about technology. If after that there is nothing to build, we will tell you.
Or write to us at hello@alubyte.com