Know what you receive.
Know how it is managed.

Who controls the domain and hosting accounts?

Start by identifying where the domain is registered, who holds the account, and who is responsible for renewals. The domain name and the website hosting are separate services. Knowing who can change each one helps avoid confusion when the site launches or a provider needs to be changed.

For an existing website, share what you know about the current setup before a rebuild is planned. We can discuss the access required and any limits that affect the approach. The agreement should identify the intended setup and who handles ongoing administration and costs.

What about the design, content, photos, and software?

Supplied materials and newly created work need to be distinguished. Tell Alex which photos, wording, logos, or other assets you can use, and identify any restrictions. The proposal should explain the terms for created work and any third-party elements involved in delivering the site.

A website may depend on a paid tool, licensed asset, or provider service. Access to the website does not automatically replace those providers’ terms. Ask what needs an ongoing subscription, what can be transferred, and what a change of platform would require for the agreed build.

Will I be able to edit the website myself?

That depends on the platform and editing workflow chosen for the project. Discuss which changes you expect to make: prices, opening information, photos, products, service details, or entire pages. A small set of regular updates can call for a different setup than frequent catalog changes.

Before approval, establish what editing access and guidance the project includes. Also agree on who handles changes that require development or affect connected forms and tools. The handoff should match how you actually want to run the site, with responsibilities explained in ordinary language.

Who looks after forms and connected business tools?

A contact form, booking system, CRM connection, or customer portal adds responsibilities beyond keeping pages online. Identify the destination for submissions, the person who checks them, and the accounts that support the connection. Agree on what the website confirms to a customer after submission.

For the agreed launch scope, define how those paths are checked and what support follows. If an outside provider changes its service or an account expires, there needs to be a clear person to contact. Avoid sharing passwords in a project inquiry; arrange the appropriate access method directly.

What should we agree before launch or a later move?

Ask what you will receive, which accounts you need, and what can be exported or moved. A move may involve content, files, records, redirects, and integrations, with different limits for each. The proposal should explain the relevant handoff and any work that would be separately scoped.

Ongoing SEO and website care is roughly $250 per month when arranged, with scope agreed for your business. Clarify that arrangement separately from domain renewals, hosting, paid tools, and the initial build. Clear expectations make it easier to maintain the site and to make informed choices later.

• Document who manages each account and recurring charge.
• Confirm the access, files, and guidance included in the handoff.
• Agree on post-launch support and how further work is requested.