Established businesses come to Vita when a tool, a spreadsheet, or an ageing application is now in the way of the work. The goal is software staff will actually use. Ruby on Rails is the usual core of that application, without a long agency layer.
We start from the workflow that hurts: quoting, ordering, reporting, or a public site that does not convert. The release is scoped around that workflow. Upgrades and rescue work are explicit options when the codebase itself is the problem.
Yes. Handover and pairing are part of rescue and upgrade work when someone else will own the app later.
No. Care plans exist for sites and assistants. Custom builds are scoped releases.
Yes. The point of a rescue or upgrade is that the next person can see what changed and why.