Launch is the start of an operating responsibility
Once customers depend on a website, someone must own content updates, account access, form delivery, and changes to connected services. A handoff should make those responsibilities explicit instead of assuming the original builder will always handle everything informally.
Know the important accounts
- Domain and DNS: who owns the registration, renewals, and routing?
- Hosting: where is the site deployed, and who can publish or recover a release?
- Forms: where do inquiries go, and how is delivery checked?
- Payments and bookings: who manages the provider and operating rules?
- Analytics: who can view traffic and inquiry sources?
- Connected tools: which subscriptions or credentials keep integrations running?
Define what maintenance means
Content editing, design improvements, dependency updates, incident investigation, and adding a new integration are different kinds of work. A useful care agreement specifies covered systems, included requests, communication channels, response expectations, and work that needs a separate quote.
Document the normal operating tasks
The business should understand how to update essential information, review inquiries, manage relevant reservations, and request changes. Keep credentials in appropriate account or secret-management systems, not in a shared handoff document containing passwords.
Plan for recovery and change
Retain a known-good release and a documented recovery approach. Recheck a form or integration after a meaningful change. When staff or providers change, review access and responsibilities. A website that still looks correct can have an underlying workflow that no longer reaches the right person.
Ask for care that fits the dependency
A simple presentation site and a booking/payment system need different support arrangements. Arbiter scopes ongoing website and automation care around the systems involved. Start by listing what the business relies on and where responsibility is unclear.