An internal app after go-live is an ownership question. Who adds a user. Where a new field is requested. At month six, when the process changes, which queue holds the patch. Maintenance names those three in the handover. Launch is not the moment a file is dropped and left.
Where the code sits
Repository, hosting and access live in the buyer environment. A single copy on a developer personal account is not ownership. HED Creative writes those three at handover. Work from Berlin or Ankara does not end with an unstated key.
Users are a role
Opening a screen for a new hire is not a new project. A role you name creates the user, sets the role and closes it when they leave. A shared password does not do this job. It also erases who signed in.
A small field change and a new module do not share a queue. The field is a maintenance line. A new workflow is a separate scope. Mixing them delays the patch and leaves the cost unnamed.
The patch at month six
The process will change: a status, a threshold, a dealer field. The request is written, queued and visible in a release. A verbal ask is work that never became a record. The queue is a short list someone reads on a rhythm you set.
What maintenance refuses
Work left out of release one on purpose does not slip in under the name of upkeep. A second process, an integration or a new external door is written on its own. Maintenance keeps the record standing and lands the small adjustment.
Put ownership in the scope on web app development. The handover of the code is in who receives the code. A monthly queue sits with a software partner.