App build · Ongoing Support
The system works, and nobody in the building knows how to change it.
A system that can't change soon stops being useful. The business moves, a process shifts, someone asks for one more field, and without anyone to make that change the workarounds creep back in.
This gives you the benefits of a developer without the salary. I keep building on what I built, little and often, to the same standard as the original.
Ongoing support covers systems I've built myself. If someone else built yours, an Independent System Review is the best place to start.
Who this is for
Clients whose system I built and who want it to keep improving without taking on a developer.
Who this is not for
Software built by someone else. For that, an Independent System Review is the right first step.
Questions
Will you support a system someone else built?
Ongoing support covers systems I've built, because I know every decision behind them. If someone else built yours, an Independent System Review is the best first step. It tells you whether what you have is worth keeping before anyone commits to looking after it.
What if I want to take it in house later?
It's already yours. You own what I build from the day you've paid for it, and you hold the code, the data, the documentation and the logins throughout. If you want to bring it in house, I offer a handover: a walkthrough, a briefing for whoever's taking it on, and the transfer of accounts. It's a defined piece of work, priced up front.
Start with the diagnostic, or just ask.
Four questions, about a minute, no email needed. If you would rather talk, the first call is free.
I reply within 2 business days.