Buyer checklist
Before you pay for a new website: 12 things to check.
A clear answer to these questions prevents most ownership, scope and launch disputes.
- Who owns the domain and can you access its account?
- Who owns the website files, content and design after payment?
- Exactly how many pages or templates are included?
- Who supplies and approves text, photos and legal information?
- Which mobile widths and browsers will be tested?
- Where do form submissions go, and how is delivery verified?
- Are analytics and conversion events configured?
- What basic search metadata and sitemap work is included?
- Which third-party subscriptions are required?
- How many revision rounds are included?
- What happens if a plugin or hosting update breaks the site?
- What documentation and access will you receive at handover?
A good fixed proposal should show
The deliverables, responsibilities, exclusions, price, payment stages and expected launch window should be written before work starts. “Unlimited” promises are less useful than a small scope with a clear definition of done.
Already have a proposal?
Send the public website or current plan. We will identify the smallest sensible next step before suggesting a build.
Request a written check