How much does a business website cost?

Start with the job the website needs to do

A simple website that introduces your business, explains your services and helps customers contact you is different from an online store or a membership portal. The number of pages matters, but so do the actions those pages must support.

Before asking for a price, write down your main goal: enquiries, product orders, bookings, member registrations or simply a credible place for customers to learn about your business. That goal shapes almost every design decision.

What changes the cost?

Most quotes reflect a mix of content, design effort, technical complexity and the work needed after launch. A custom design with unique layouts and more review rounds usually takes more time than a focused site based on an established structure.

• Scope: a five-page service website and a custom customer portal are not the same project.
• Content: who will supply writing, photography, product descriptions and branding?
• Features: payments, bookings, logins and integrations add testing and operational responsibilities.
• Ownership: will you have control of the domain, hosting and accounts used to run the website?
• Support: clarify what fixes and updates are included after launch.

Don't forget the ongoing costs

A website may also involve a domain name, hosting, business email, payment processing, licensed tools or maintenance. Some services are paid directly to third parties. Ask for a clear distinction between the one-time design fee and recurring expenses.

If your business will receive payments, confirm which provider is supported in your country and account category. A checkout screenshot is not the same as a tested, live payment setup.

How to compare two quotations fairly

Compare what is included, not just the final amount. A cheaper quote may omit essential pages, testing, training or content work; a more expensive quote may include features you don't actually need. Neither tells you enough on its own.

• Request a written list of deliverables and excluded work.
• Ask how many rounds of feedback are included and how changes are priced.
• Confirm mobile experience, accessibility basics and contact-form testing.
• Clarify who owns the domain, code or content, and what happens at handover.
• Agree milestones and the payment schedule before starting.

Start small if that fits the business

You don't need every possible feature on launch day. A focused website with the right content and enquiry journey can be a strong starting point. More complex workflows can be scoped as a second phase once their real value is clearer.

I quote projects after understanding what the business needs. That approach is less exciting than a universal price tag, but it helps avoid assumptions that become expensive later.