How much does a business website cost?
A responsible estimate is not based on page count alone. Compare scope, content, implementation, and the work that follows launch.
AT A GLANCE
The cost of a business website depends on the job it must do, the content required, custom functionality, integrations, and ongoing operation after launch. Comparable proposals need the same scope, responsibilities, and quality requirements. Without a verified rate card, this guide does not invent price ranges.
- Compare decision journeys and functionality, not page count alone.
- Clarify who creates and approves the content.
- Include handover, measurement, maintenance, and third-party costs.
What determines the cost?
The main question is which business decision and task the website must support. A focused service website, a content system for several audiences, and a customer experience connected to internal tools are different scopes. Research, information architecture, writing, design, development, and verification each require work.
Technical requirements matter too: multiple languages, permissions, booking, payment, CRM or invoicing connections, data migration, and a custom administration area. A proposal is easier to assess when these are not hidden inside one “website” line and responsibility for each outcome is explicit.
Why is page count a poor comparison?
Two five-page websites can require very different work. One may use approved copy and images; another may need stakeholder interviews, new positioning, image selection, search research, and several approval rounds. One long service page with several decisions can require more work than multiple short pages.
Ask for a functional and content breakdown. List the page types, states and forms, who supplies source material, which languages are involved, and how the result will be verified. This makes the real differences between proposals visible.
What belongs in a comparable proposal?
It should state the goal, audience, pages and functionality to be delivered, content responsibilities, technical environment, accessibility and performance expectations, and acceptance criteria. Domain, hosting, font, image, analytics, and other third-party fees should be visible separately.
A schedule needs more than a launch date. It should show decision points, client feedback and data dependencies, and revision rounds. Instead of saying “SEO included”, define whether that covers content planning, metadata, redirects, structured data, a sitemap, or post-launch checks.
Which costs continue after launch?
Website operation does not end at publication. Account for hosting, the domain, external services, security and technical updates, backups, corrections, and content maintenance. If the site supports enquiries, name who will review measurement and prioritise improvements.
Not every project needs a monthly package. What matters is knowing what the initial handover includes, what happens when something fails, who manages access, and how later development is requested. A cheaper initial proposal can become more expensive when these responsibilities are omitted.
What information is needed for an estimate?
Describe the audience, the offer they need to understand, the intended next action, available content, required system connections, and who will make decisions. Share examples of current problems, but do not send passwords or sensitive customer information.
The right result of an initial conversation may be that a complete redesign is unnecessary. If the current site has a sound technical and structural base, focused content work, measurement, or a small set of revised pages may be the better next step. Estimation should clarify the necessary scope, not maximise the project.
Sources and further reading
- SEO Starter GuideGoogle Search Central · Checked: 2026-10-31
- Planning and Managing Web AccessibilityW3C Web Accessibility Initiative · Checked: 2026-10-31
Borbély Kristóf
The developer behind Kriside, writing practical guides about web systems, automation, and AI solutions.