A website has no single price. The cost follows the scope: what the site must do, how much of it is custom, who supplies the content, and how long it needs to stay dependable.
People often ask what a website costs before they have described what the website is for. Two sites that look similar on the surface can need very different amounts of work underneath — one may be a handful of clear pages, the other a store, a customer portal or a connected internal system.
This guide explains what moves the price up or down, so you can describe your project clearly and compare quotes fairly. It deliberately gives no price list: any honest figure depends on your scope.
1. The type of website
A business website that explains services and collects enquiries is a different project from an online store, a web application with user accounts, or an internal system that staff log in to. The more a site has to remember, calculate or connect to, the more design, building and testing it needs.
Start by writing one sentence on what the site must achieve — for example, “let customers understand our services and contact us”, “sell products online” or “let staff manage orders”. Everything else follows from that sentence.
2. Size and content
The number of different page layouts matters more than the number of pages. Ten service pages that share one layout take less work than ten pages that each need their own. Content also takes real effort: writing, editing, photography, and moving existing content from an old site. Decide early who will supply the content and by when, because waiting for content is one of the most common causes of delay.
Extra languages, large catalogues of products or articles, and detailed structured information such as directories or listings all add work.
3. Design
A site built on a ready-made template starts faster than one designed from scratch around your brand and customers. Custom design takes more time but can fit your business more closely. Other design factors include how many unique page designs are needed, whether a reusable design system is wanted, and how much user research or testing goes in.
Whatever the approach, ask what you will receive: layouts for desktop and mobile, a style guide, and the design files.
4. Features and integrations
Each feature has a build cost, a testing cost, and often an ongoing cost. Common ones include contact and quote forms, booking, payments, user accounts, search, an area your team can use to edit content, and connections to other tools such as a CRM or an email service.
Integrations deserve special attention. Connecting to another system means depending on that system, so it needs documentation, error handling and a plan for when the other side changes.
5. Platform and technology
Using an established platform such as WordPress or WooCommerce can reduce build time and give your team familiar tools for editing content. A custom-built application can fit unusual requirements exactly, at the price of more building and more care to maintain. Neither is automatically better. Ask which option suits the project, who will maintain it, and what licences, plugins or hosting it needs.
6. Speed, security and accessibility
These are not optional extras to add at the end. A site that loads slowly on a phone, leaves administrative access unprotected or cannot be used with a keyboard costs more to fix later than to plan now. Our article why a business website needs more than good design covers these basics.
7. Timeline and decisions
A tighter deadline can mean more people working at once and less room for revision. Slow decisions, many rounds of changes, or unclear approval ownership stretch a project and its cost. One person with authority to approve work, and a clear list of what is in and out of scope, keeps both time and budget predictable.
8. What happens after launch
The build is not the whole cost. Plan for the domain name, hosting, security certificates, backups, software updates, content changes and technical support. These are usually smaller recurring costs rather than one large one, but they are what keeps the site dependable. Our guide to what website maintenance costs cover explains how to compare plans.
How to ask for a quote you can compare
The more clearly you describe the project, the more comparable the quotes will be. Before you ask, work out:
- What is the website for, and who will use it?
- Which pages and features do you expect, and which can wait for a later phase?
- Who supplies the text, images and product information, and by when?
- Which other tools must it connect to — payments, CRM, email, booking?
- Do you have a brand style, or do you need design from scratch?
- Who will maintain it after launch, and what support do you expect?
- What is your timeline, and what budget are you working with?
Then compare like with like: what is included and what is not, how many rounds of changes are covered, who owns the finished work, and what support follows launch. A lower figure that leaves out content, testing or aftercare is not the same offer as a higher one that includes them.
How ByteRoots approaches it
At ByteRoots we start by understanding your requirements, budget and timeline, then agree the scope and a quotation with you before work begins. You deal only with ByteRoots, which manages the project, the communication and the quality. If you would like to talk about a website, you can contact us or read more about our website development service.
Foundations before acceleration.
