Launching is not the end. Operating systems, browsers, libraries and the world around the product change, and bugs appear when real people use it.
Options
- The original developer on a retainer or as-needed. Best continuity, since they know the code.
- A different developer or agency. Possible if the code and documentation are good; this is why handover materials matter.
- In-house. Suits larger or continuously developed products.
- A managed platform that handles much of the upkeep, if you use one.
Settle before launch
- Who is responsible for fixing bugs, and for how long are they free under the project?
- Who monitors the system, and who is alerted?
- How quickly will problems be handled, and how do you report one?
- Who updates software and security patches?
- Where are the code, accounts, documentation and backups, and who has access?
- What does it cost, and what is included?
The risk of no plan
Unowned software works until something changes, then fails at a bad time and nobody knows how it is put together. A small, regular arrangement is almost always cheaper than emergency work.
Whichever route you take, keep ownership of the code and accounts so that you are never dependent on one person.