Ongoing Systems Support
Change requests & small builds
The next small thing, without starting a new project.
The work
A change that takes an afternoon should not need a quote, a scope and a quarter's wait. Most of the time it does, which is why it never happens.
We take small work as it comes, with an estimate first so nothing arrives as a surprise, done by the person who built the thing in the first place. Documentation stays true as changes land, and when something genuinely needs a project we say so rather than letting it quietly become one.
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.