The system works, and nobody in the building knows how to change it.
App Build and Support Management
Ongoing build and support for systems I built, so improvements keep happening after launch without you hiring for it.
A system that cannot change stops being an asset fairly quickly. The business moves, the process shifts, someone asks for one more field, and if there is nobody who can make that change the workarounds start coming back.
Most small businesses cannot justify a developer, and should not try. This is the alternative: I keep building on what I built, in small increments, against the same standard the original went through.
Scope boundary, stated plainly: I only provide ongoing support for systems I built myself. I do not take on support for third-party or legacy applications. If someone else built it, a Third-Party Review is the honest starting point instead.
Whether this is for you
A good fit if
Clients whose system I built and who want it to keep developing without hiring.
Not a fit if
Anyone looking for support on software I did not build. That is not a capacity question, it is a quality one. I cannot stand behind a system I did not build to the standard.
What you get
- Changes and improvements delivered in small increments
- The same testing and launch discipline the original build went through
- A named person who already understands the system
What it costs
This is arranged as part of an ongoing support arrangement rather than priced per change, because per-change pricing makes people sit on small problems until they become large ones.
How the work runs
Five phases, each ending with something you can read, disagree with and sign. Nothing starts before the last one closes, and the price is fixed at the end of phase two rather than guessed at the start.
Questions people ask
Will you support a system somebody else built?
No. Supporting software properly means understanding hundreds of decisions somebody made and did not write down, and doing that at a monthly fee price point means doing it badly. If that is your situation, a third party review is the honest first step, because it tells you whether what you have is worth keeping before anybody commits to looking after it.
What if I want to take it in house later?
It is yours already. Ownership of what I build for you transfers when you have paid for the build, not when a support arrangement ends, and you hold the code, the data, the documentation and the credentials throughout. If you want to move it in house I offer a handover: a walkthrough, a briefing for whoever is taking it on, and the transfer of environments and accounts. That is a defined piece of work at a price agreed at the start, and what it buys is my time rather than access to something you already own.
Start with four questions
About a minute, no email needed. Or get in touch and tell me what is going on. The first call is free.