After delivery, someone keeps watching
A system that is delivered and forgotten starts to fail silently. We take responsibility for it: we look at the numbers, fix what breaks and say what has changed.
Change log
- FixedToday
- UpdatedYesterday
- AlertThis week
Everything working
What you get
A record of what was done
Every fix and every change is written down, with date and reason.
Alerts when something is out of the ordinary
A person receives the alert and deals with it, instead of finding out from the customer.
Periodic summary
What went well, what failed and what we propose to change next.
How it unfolds
Assessment
We see what exists, how it is set up and what has already failed.
Agree what is monitored
We choose with you the signals that matter and who is alerted.
Ongoing support
We monitor, fix and record. Improvements are proposed before they are made.
What we do not promise
- We do not take on systems without first seeing them from the inside.
- We do not promise that nothing fails. We promise to know when it fails and to deal with it.
- Large changes are quoted separately, before they begin.
More detail
Why a system needs someone
Software does not wear out, but what surrounds it changes: the programs it is connected to are updated, volumes grow, people change the way they work. A system that nobody monitors does not stay the same. It becomes outdated.
Ongoing support means taking on that responsibility with a name attached. Someone knows how the system works, sees the signals and answers for it.
What always stays in view
We do not ask for blind trust. Everything we do is recorded and can be read by you or by another team: what changed, when and why.
What we are always asked
Do you support systems built by other teams?
Yes, after an assessment. We need to see the code, the access and the history before taking responsibility. If the state of the system does not allow serious ongoing support, we say so before starting.
What happens when something fails?
A person receives the alert, sees what happened and deals with it. At the end it is put in writing what failed, what was done and what changes so that it does not happen again.
Are we locked into the ongoing support?
No. The code and the data are yours. The record of what was done stays with you, so that another team can continue if you so decide.
Tell us what is holding back your operation.
Describe the problem in your own words. You do not need to know what has to be built.
- We read your request.
- We reply within one hour, by email or telephone, in English or in Portuguese.
- If it makes sense, we arrange a conversation.