Website development cost depends on what needs to be planned, created, built and checked before launch. Page count is only one factor. Content readiness, functionality, languages and editing requirements can change the workload even when two sites have the same structure.
A useful quote answers three questions: what will the business receive, what conditions define completion, and what will it cost to operate afterwards? Here is how to assess a proposal without trying to guess a fair price from the appearance of the finished website.
Why page count does not tell the whole story
Consider two websites with ten pages each. On one, eight service pages share a layout, and the client supplies approved copy and photographs. On the other, every service needs a different structure, content in three languages and a connection to a CRM. The page count matches; the work does not.
Distinguish pages from unique templates. Adding content to an existing template and designing a new interface are different tasks. Likewise, a simple contact form differs from one with conditional fields, file uploads and rules for routing enquiries.
Before discussing price, describe the actual journeys: what visitors read, what information they enter and what happens after an enquiry. These details give an estimate a clearer basis than a broad website category.
What belongs in a website development quote?
Ask for a breakdown you can understand. It should show whether the work between design approval and a functioning launch is included.
| Cost driver | Work it may involve | Question to ask |
|---|---|---|
| Structure and design | Navigation, templates, mobile layouts, interaction states | How many unique templates and revision rounds are included? |
| Content | Copywriting, editing, photography, page population | Who creates and uploads the materials? |
| Content updates | Agreed changes, content handover and publication process | Who will update the site and how will changes be approved? |
| Forms and integrations | Enquiries, CRM connections, notifications, error handling | Which workflows and third-party services are covered? |
| Languages | Translation, localisation, language switching | Does the price include translation or only language support? |
| Testing and launch | Testing, domain setup, analytics, access handover | What are the acceptance criteria? |
Each item should identify an outcome, a limit and an owner. “Basic content setup” leaves room for interpretation. “Upload approved copy and photographs to five pages” describes something both sides can check.
How to compare two proposals fairly
Give both teams the same brief. If one quotes for development alone and the other includes planning, design and content, the difference in totals says little about value.
Mark each requirement as included, charged separately or awaiting clarification. Check the currency, taxes, third-party charges and circumstances in which an estimate could change. Establish whether the total is a fixed fee, a preliminary estimate or a forecast based on time spent.
Read the change process carefully. Replacing approved copy, restructuring a signed-off design and adding booking functionality are different requests. Agree who estimates additional work and how you approve its cost before work begins.
Our guide to commissioning a business website explains the wider process. For comparing quotes, a short shared brief with clear launch requirements is a practical starting point.
A scope example: the same business, two different projects
Imagine a service business seeking enquiries for three services. Its initial scope includes a homepage, three service pages using a shared template, a contact page, one language and an enquiry form. The business supplies approved copy and photographs.
Now add two languages, copywriting, a case study section with an agreed update process and CRM integration. These changes introduce content production, a data structure, integration setup and additional checks. They are more than a few extra screens.
Both versions could look equally simple. The second proposal nevertheless carries more responsibility. Use this kind of comparison to decide which capabilities support launch and which have a reason to follow later.
Budget for what happens after launch
Separate the cost of building the website from the cost of operating it. Ongoing expenses may include domain renewal, hosting, paid services, updates, backups, technical support and new content. The exact list depends on the solution.
Request a schedule of recurring charges and identify who owns each account. Ask whether pricing changes with traffic, editor numbers, form submissions or external API usage. For a first-year budget, add development costs to expected operating expenses for that year.
Clarify what support means: fixing defects, updating dependencies, editing pages or developing features. If search traffic is part of your plan, separately budget for content and preparing your website for SEO. Launching a website does not by itself establish a customer acquisition channel.
Two budgets for one website
Plan for both creating the website and keeping it running.
Initial launch
Planning, design, development, content preparation, and checks.
Recurring costs
Domain, hosting, paid services, and agreed support. Confirm what is included and how often it is billed.
How to keep the first phase focused
Start with a complete customer journey: understand the service, assess the evidence and make an enquiry. You can postpone a feature if that journey still works. Automated booking, for example, may wait if the team can initially arrange appointments manually.
Supply approved materials, reuse templates where pages serve similar purposes and appoint one person to consolidate feedback. These choices make the workload clearer. Keep checks that protect the site's basic function, including mobile usability and successful form delivery.
Record deferred features with a reason and a trigger for reconsidering them. You might revisit automated booking when manual scheduling takes significant staff time. This gives later spending a practical basis.
Frequently asked questions about website costs
Can I get an exact price without a detailed specification?
A short description can support an initial estimate. A fixed price requires agreement on deliverables, materials, constraints and acceptance criteria. For a straightforward project, a concise scope document can be enough.
What should an all-inclusive website package cover?
There is no universal package. Ask for a written list covering design, development, content, domain, hosting, launch and account handover. Each item should identify who is responsible and whether its cost is included.
Is starting from a template cheaper?
A suitable template can reduce design and layout work. Extensive customisation, added features and work around its limitations still take time. Compare the full adaptation cost, including licences and maintenance requirements.
Can I commission a website in stages?
Yes, if each phase has a defined outcome and agreed dependencies. Establish what launches first, which materials it needs and whether the next phase will require changes to work already completed.
Start with the business requirement
Prepare your website's purpose, services, languages, available materials and essential launch features. Add a budget range and explain which constraints matter most. That gives the conversation enough detail to explore a realistic scope and its trade-offs.
Planning a new website? Tell XEVOR about your project, starting with the business goal and what the first version needs to do.