Ownership
What should happen after custom software launches?
Direct answer
After launch, a named person must be able to sign in as an administrator, see whether the system is up, restore a backup, and request a change without hunting for a developer who once knew the passwords. That operating model is agreed before launch, not invented on the day the original team is busy. The client should hold the accounts and the code.
Launch is a change of job, not the end of the job
Building is the work of making a workflow run. Operating is the work of keeping it running when someone leaves, a certificate expires, or a record needs a correction the screen did not imagine. Firms that treat launch as the end are surprised by ordinary events.
The surprise is avoidable. Before the system is called done, name the owner inside the firm, the owner of technical access, and which of those is Sunbeam if we are staying. Write down how a change is asked for. A system with two implied owners has none.
Access, backups, and a way to see failure
Administrator rights should be few, and the firm should hold them. A departed employee, including a departed vendor, loses access as a procedure rather than as a project. Backups are tested by restoring one, at least once, before anyone needs the restore to be true.
Monitoring does not have to be elaborate. Someone should learn, without a client calling, that sign-in is broken or that a daily job did not run. The engineering standard describes this as part of delivery. It is also the practical meaning of owning the system.
The first month is part of the design
Real use reveals the exception the workshop missed. Plan for a short period of corrections after people start living in the tool, and do not fill that period with the next big feature. The team is still learning the first one. Burying them in a second release is how adoption fails and gets blamed on the software.
Measure something small: are people updating the record, or keeping the old sheet “just in case”? If the sheet survives, the software has not become the system of record, and no amount of extra features will hide that.
A different engineer should be able to continue
Documentation, here, means the decisions: how to run it, where the data lives, what must not be changed casually, and how a release is made. It does not mean a novel about the code. The test is whether a capable developer who was not in the original team could make a small, safe change.
You can keep Sunbeam for that, hire, or move. The commercial model is allowed to change. The ability to leave is not optional. It is the difference between a system the firm owns and a system the firm rents without having agreed to rent it.