It covers our project work for your website rebuild, along with any agreed add-ons we confirm in writing as part of the same project. If you have accepted a proposal from us, that proposal and this agreement should be read together, so the scope, timing, and pricing match what you approved. We run the work in clear stages with sign-off points, and the terms below set out how we both make decisions, keep momentum, and finish with you in control of your site and access.
Scope of work
We will deliver your website rebuild in stages, with a clear sign-off at the end of each stage before we move to the next one. The point of the stages is to keep decisions tidy: requirements first, then structure, then design, then build, then launch.
The deliverables for this project are listed below. Anything not on that list is not included unless we agree it as a change in writing. You are responsible for providing the content and access we need on time. If we are waiting on access, content, or feedback, the timeline moves by the same amount so the sequence of sign-offs stays workable.
* Written requirements list * Wireframes and content map * Approved design comps * Rebuilt website in CMS * Migration and redirects * Handover session and admin access
Payment
To book the website rebuild, we invoice 50% of the total price when the proposal is signed. We schedule the project after that invoice is paid. We invoice the remaining 50% when the finished work is handed over, meaning the rebuilt site is ready for you to take over with admin access and our handover session is booked or completed.
Each invoice is payable within 14 days of its date. If a payment becomes overdue, we will pause work and planned launch activity until the account is up to date, and we will confirm any knock-on timing impact in writing so you always know what moves and why.
Revisions
Each stage includes one revision round, and we treat a revision round as one collected set of changes based on your feedback. For example, after wireframes you send one consolidated note, we update once, and you then approve or request the next revision round as a change. The same applies to design comps before we start build.
If you want additional rounds, or if feedback changes what was already approved (rather than refining it), we will price and schedule that work before we do it. Nothing extra is billed or added to the timeline unless you approve it in writing, so you stay in control of cost and pace.
Who owns what
You keep control of your domain, hosting, and admin logins throughout the website rebuild. We will only access accounts you invite us into, and we will not move ownership of anything away from you.
Once the final invoice is paid, you own the finished site files and designs we created for this project, and we hand over admin access and any agreed deliverables needed to run the site. What we do not hand over are our pre-existing tools, reusable code libraries, internal templates, checklists, and working methods. We may use those again on other projects, but we will not reuse your brand, content, or site-specific design in another client’s work.
Portfolio
After launch, we may show the finished website rebuild as part of our portfolio. That usually means a short case study and screenshots, and we may link to the live site so people can see the work in context.
If you need the project kept private, tell us in writing and we will not publish it. If there is a specific detail you want us to avoid sharing, such as a feature still in progress, internal pages, or performance results, we will follow that request. Even when we do show the work, we do not share your logins, private data, customer lists, or any non-public information you provide during the project.
Limits
We are responsible for delivering the website rebuild described in the scope, using reasonable care, and for fixing defects that are caused by our work and reported to us within a reasonable time after launch. We are not responsible for problems caused by changes made by others after handover, by third-party services you choose (plugins, payment providers, booking platforms, hosting outages), or by access being removed or restricted.
You are responsible for the accuracy and rights of the text, images, product details, prices, and claims you provide. We will flag issues we notice, but you make the final call on what is published. We do not cover indirect losses like missed sales, lost profit, or the cost of your staff time spent dealing with an issue.
Ending the project
Either side can end the project by giving notice in writing. We will agree the notice period with you in writing so it fits the project stage and what is booked in our calendar. If the project ends, you pay for the work completed up to the end date, including any stage that has been approved and any in-progress work we can reasonably evidence.
When the account is up to date, we will hand over what we have completed for the deliverables to that point, along with the current project files needed for you to continue with another team. If we have paid third-party costs on your behalf with your approval, you agree to reimburse those costs as part of the final account.
Signature
