Ongoing Systems Support
Backups & security basics
Restores that have actually been tested, not just backups that ran.
The work
A backup nobody has ever restored is a hope, not a backup. The only real test is whether you get the data back on the day you need it.
We test restores on a schedule, keep copies somewhere separate from the thing they protect, and write down how far back you can actually go. Alongside that: a password manager the team will genuinely use, two-factor where it matters, and a one-page plan for the bad day.
How it runs
Understand
We watch how the work really moves, which is never what the process document says. Where does it stop? What gets typed in twice? What only works because Dawn on the front desk remembers the workaround, and what happens the week Dawn is in Portugal?
Scope
Then we pick. Whatever costs the most hours or carries the most risk goes first, written up as a bounded job with a price on it. You'll know exactly what you're getting before anyone writes a line of code.
Build
We build it, then put it in front of the people who actually have to use it every day, while it is still cheap to change. They always find things we missed, which is the whole reason they see it in week two rather than at the handover.
Handover
You get the working system, clear documentation, and a handover to whoever owns the process. Keep us involved afterwards if it helps. The point is that you do not have to.