Ownership & handover

Your website should not become a hostage to its builder.

Our preferred setup keeps the domain, hosting account, billing relationship and production access under the client or agency that is meant to control them.

Ownership

Who should control what?

AssetPreferred owner/control
DomainThe intended registrant/client or the agency if that is its established operating model.
HostingThe client or agency that is meant to control production and billing.
Paid third-party servicesThe party responsible for the subscription and future renewals.
Primary credentialsThe account owner. We prefer not to receive them unless genuinely necessary.
Final deliverableDefined by the project agreement, including any third-party licences/components.
Third-party purchases

We can send the link. You can buy directly.

Where practical, WebAgencyOn recommends that the final client or agency contracts domains, hosting and other paid third-party services directly with the provider. You enter billing, identity and account information with that provider rather than sending it through us.

This reduces unnecessary handling of sensitive purchasing data and keeps renewal notices, invoices and ownership records with the party actually responsible for the service.

Referral disclosure.

If a recommended link is ever an affiliate or referral link, that relationship should be disclosed. The external provider’s own billing, privacy and service terms still apply.

Replacing a live site

Preserve before replacing.

Confirm the exact production site and document root.
Identify dependencies that must survive.
Create a pre-change backup where supported and in scope.
Deploy the approved build.
Check HTTPS, forms, links, responsive behaviour and agreed integrations.
Create a post-launch backup where supported/in scope.
Remove temporary access or leave only what was expressly agreed.
Private review

A preview is not a lock-in mechanism.

A private review environment may be used before launch. Final deployment goes to the production infrastructure agreed for the project. The review environment is not intended to become an unavoidable dependency.

Related 4ONL routes

Related routes, only when they fit the project.

Different projects need different routes. We do not rank a project by the size of the organisation; we route it by what needs to be done.

WebAgencyOn remains the specialist route for agency delivery, white-label work and external production capacity.

WebAgencyOn can work with agencies, businesses, organisations and independent professionals. The route changes with the project; the care and delivery discipline do not.

Start a project