A useful website budget starts with an agreed scope. Before comparing totals, check whether each quote covers the same pages, content, functionality, ownership, and ongoing work. A subscription for an editing tool and a quote for a finished website buy different things.
Give suppliers the same brief
Write down who the site is for, which decisions visitors need to make, and what they should do next. List the main services or products, the pages you expect, the languages needed, and any forms or integrations.
Separate what already exists from what someone needs to create. Finished copy, approved photographs, and a clear brand direction require different work from a folder of notes and a logo. Ask whether writing and image preparation are included.
Compare the deliverables
| Area | Questions that make quotes comparable |
|---|---|
| Content | Who writes it, checks the facts, and approves it? |
| Design | Which page types and screen sizes are covered? |
| Functionality | Does the form send messages, store records, or connect to another system? |
| Search | Are canonical addresses, indexing rules, redirects, and a sitemap included? |
| Migration | Which existing pages and assets move, and which old addresses redirect? |
| Handover | Who owns the domain, accounts, source, and original media? |
| Care | Who makes updates, handles failures, and pays recurring services? |
Ask each supplier to identify assumptions. A quote that assumes you provide finished content may look lower because writing has simply been left out.
Keep recurring costs visible
List domain renewal, hosting or builder subscriptions, business email, form services, optional analytics, and maintenance separately. Note whether a promotional rate changes on renewal and whether a third-party integration has usage charges.
For changes after launch, agree who performs them and how they are priced. A care arrangement should describe the work it covers and how requests are handled. A source handover should explain how another developer can run the site.
Use phases when the scope is uncertain
If a customer portal, product configurator, or internal workflow is still being defined, ask for a focused discovery or prototype step. Test the difficult part before quoting the full implementation.
For a marketing site, decide which customer questions the first release needs to answer. Keep those pages complete, with an inquiry path and real proof. Add further pages when they serve a distinct visitor need.
Questions to ask before you approve a quote
- What exactly do we receive, and how will we review it?
- Which content and approvals do you need from us?
- What can change the price or schedule?
- What do we pay after launch, and to whom?
- What happens if we move the site or use another developer?
A written answer to those questions gives you a stronger comparison than an industry average with a different scope, location, or year. If you are still choosing a platform, read our builder and custom-site comparison.
LifeVen website projects start from the business, content, and required functionality. Share your existing site, the result you want, and any examples you like so we can define the work and quote it in writing.