A website quote is only comparable when the pages, functions and responsibilities are clear. Start with what visitors need to do and what your team needs to manage, then decide whether you need a small site, an online shop or a custom application.
Specify a working website, not just a page count
Five informational pages and five pages connected to payments, bookings or customer accounts are different projects. Describe user actions as well as screens.
- Pages, content types, languages, integrations and any migration of existing content.
- Mobile behaviour, keyboard access, form validation and agreed performance checks.
- Hosting, deployment, analytics, backups, documentation and post-launch support responsibilities.
How to evaluate a web developer
Ask to see a project with similar functionality and clarify which parts they built. Discuss how they handle errors, accessibility and changes after launch. Ask for an explanation of the proposed technology that covers maintainability and your team’s ability to edit content, not only how quickly the first version can be built.
What drives web development costs?
Custom functionality, integrations, content migration, design readiness and testing needs affect effort. Ask for separate estimates for discovery, implementation and maintenance. Recurring hosting, third-party licences and support should be visible. Compare what each quote excludes, especially copywriting, photography, data entry and changes after approval.
Example website brief
“We need a bilingual eight-page website with an editable case-study section and an enquiry form. We will supply approved copy and branding. Please include responsive layouts, keyboard testing, redirects from the old site, deployment and a handover session. Price optional maintenance separately and define the checks required before launch.”
Accept the work against agreed checks
Use a staging site to check key journeys before launch. Confirm who controls the domain, repository and hosting. Record open issues and distinguish defects from new requests. Agree a support window, the process for urgent problems and how another developer could take over the project.
