Ongoing Systems Support
Hosting & uptime
Somebody notices it is down before your customers do.
The work
The first person to notice a site is down should not be a customer. Usually it is, because nobody is watching and the reminder went to an address nobody reads.
We check continuously that it responds, and responds correctly, and send alerts to a person who can act on them. Certificates renew before they expire, hosting stays in your own account so moving is possible, and every outage gets written up with what stopped it recurring.
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.