The hosting decision is a responsibility decision. A site may be live, fast and visually finished, yet no one knows who can restore it, renew the domain or respond when a form stops working.
For an agency, these gaps often surface months after the launch team has moved on. The client calls the person they know: you. That is why maintenance should be scoped while the project is being sold, even if another specialist runs the infrastructure.
Draw a simple ownership map
Write down the owner and working contact for the domain registrar, DNS, hosting, CMS, transactional email, analytics, licensed software and backups. Record which accounts belong to the client and which are managed by the agency or partner. A shared password in a message thread is not an ownership plan.
Ask one uncomfortable question: if the current contractor disappeared tomorrow, could the client and agency recover access and keep the site running? If the answer is unclear, the handoff is unfinished.
Define what “managed” includes
The phrase can describe very different services. Spell out monitoring, backups and retention, restore tests, software updates, security response, content edits, performance review and support hours. List exclusions as plainly as inclusions.
A backup is useful only if someone knows where it is, how old it may be, and how to restore it. An update policy should explain whether changes are tested first and what happens if an extension breaks. These are operating agreements, not marketing bullets.
Decide how incidents travel
If the client sees an error on a Friday, who receives the report? Who can tell whether it is a hosting outage, an expired service, a code change or a third-party integration? Who communicates with the client while the technical person investigates?
The agency does not need to run a server desk to give a confident answer. It does need a clear route between the client and the person who can fix the issue.
Keep the exit usable
A good hosting relationship should allow the site to move. Document where files, databases, DNS records and service credentials are held. Agree on export and transfer steps before the relationship is under strain. If the platform is proprietary, explain what can and cannot be taken elsewhere.
The result is a quieter launch. The client knows who supports the site. The agency knows what it has promised. The technical partner knows which systems and response times are actually in scope. Explore managed hosting for agencies.