
Pages and content
Page count, sections, copy, images and case study materials.
Know what you’re getting before we start. We agree on the pages, design and features, then keep track of feedback and approvals as we build.
Share your goals, design files or reference sites, page list, features and languages. Your existing site, hosting requirements, budget and target launch date help us assess the work before we quote.

Page count, sections, copy, images and case study materials.

Forms, search, filters, memberships, integrations and admin features.

UI files, reference websites, brand colors, fonts and images.

Server, domain, languages, launch date and budget.
Your contract sets out the schedule, revision rounds, any included support time and handover. We start development once you’ve approved the design and feature list.

Review the pages, design, development, testing and project coordination needed.
Bring the quote, feature list, design approval and schedule together so everyone knows what will be delivered.
Use the initial quote to agree on the feature list, schedule and contract. Settling these details now makes later decisions easier.
The quote sets out the agreed pages, features, estimated work, price, payment milestones and service scope.

Once the initial quote is accepted, we confirm the features, organize the pages and functionality, and plan the work to be delivered at each stage.

The agreed feature list and project plan are included in the signed contract to keep the project scope under control.

At handover, you receive the design files, website code and review documents included in the contract. Third-party software, fonts and other licensed assets remain subject to their own licence terms.

Start by reviewing the homepage, then use the agreed direction for the other pages. Send your team’s feedback together for each design batch. We build from the version you approve.
Brand, structure and key visuals
Services, case studies and contact
Desktop, tablet and mobile
Brought together by your project contact
Version numbers and approval records
Based on the approved design
Clients may request changes during development

Small adjustments during development are handled within the scope and hours agreed in the contract.

Small additions are assessed first; structural changes or substantial features require separate agreement on cost and timeline.

We log small requests too, so you can see the time used, any included allowance and work that needs a separate quote.

A project lead coordinates communication and delivery through completion to keep everyone aligned.
An important distinctionIf the implementation differs from the approved UI or feature list, correction is the developer's responsibility. Changes to previously approved content are treated as minor adjustments or new scope.
We check the pages against the approved design, test desktop and mobile layouts, and review features, forms, links and browser behaviour. You then try the staging site and send one list of issues against the agreed scope.
A shared test checklist keeps open issues and review progress visible.
Once deployed to the test server, the client can browse and try the website online.
The website is deployed to production only after the client approves the online test version.
Fix development issues that differ from the approved version; record scope changes separately.
Complete acceptance and payment milestones as agreed in the contract.
After the agreed final payment, we hand over the project files, database, deployment notes, review documents and access included in the contract. Third-party licence terms still apply.
After launch, support follows the arrangement in your contract. This can include fixes, backups, security checks, updates and small changes. New features need their own assessment.
A maintenance plan can include uptime monitoring and alerts for detected problems. We agree the monitoring setup, notification contacts and response arrangements for your website.
Use the agreed support hours for eligible small fixes and changes. We check larger requests with you before adding work.
Automated checks can detect downtime and timeouts, but may miss unwanted pop-ups, redirects, injected code or changed content. Manual page checks and their frequency are agreed as part of the maintenance scope.
Keep a record of reported issues, the work carried out and the results. We agree how maintenance requests and review reports will be shared, so you can follow what has changed.