What happens after launch
Most software fails quietly after it ships. Running it properly is a job, and it should be priced like one.
Squircle · · 1 min read
Launch day feels like the finish line. It is closer to the start. The business keeps changing after the software ships, and software that does not change with it slowly stops fitting.
How software fails after launch
Rarely all at once. An integration breaks when a supplier changes its API. A report stops matching the numbers because a field changed meaning. Staff build workarounds around a missing feature, and the workarounds become the real process.
None of these is dramatic, which is exactly why nobody fixes them.
What running it involves
Hosting and security updates. Monitoring, so problems are found before customers find them. Fixes when something breaks. A regular look at how the system is being used, and small improvements from the roadmap.
Why it should be agreed up front
If running costs are left until after launch, they arrive as a surprise or not at all. We quote a monthly Run plan alongside every Build, so the full cost is known on day one. If you take it, the people who built the system are the ones who keep it working.
You still own your systems. The data, accounts and everything built for you are yours, so if you ever want someone else to run it, nothing needs to move.