Digital products ·
The price of a website begins with responsibility, not page count
“How much does a website cost?” has no honest single-number answer. A landing page, catalogue and web service can look equally polished while requiring very different research, architecture, integrations and testing. The price becomes clear when the website is described as a working system with a defined responsibility.
Define the website’s job first
A website may present a company, collect enquiries, sell products, issue documents or serve existing clients. Until the main user action and business outcome are known, the number of pages says little about the scope.
I begin with scenarios: who arrives, what they need to understand, what they should do and where the result goes. One clear scenario can support a compact site. Multiple roles, states and internal processes turn the task into a digital product.
Research and content affect the estimate
Before layout work begins, the team needs services, audiences, competitors, brand constraints and search demand. If copy, photography and structure are absent, producing them is a separate part of the work rather than a free addition to design.
A useful prototype establishes content hierarchy before visual treatment. Missing steps, redundant sections and contradictions between a promise and a form are cheaper to correct here.
Design is a system, not a single hero screen
Design includes typography, grid, form states, mobile rules, reusable components and behaviour with different content lengths. One striking mock-up does not describe the whole website.
The cost rises when every page needs a unique composition, complex motion or commissioned artwork. That can be right for the project, but it should be named early and tied to a purpose.
Development includes the invisible layer
Behind the interface are content management, forms, integrations, analytics, SEO metadata, accessibility, security, backups and performance. Commerce adds catalogue, basket, payment, stock and notifications; a portal adds users, roles, records and activity history.
AI can speed up implementation, debugging and variation, but it does not remove architecture or acceptance. Responsibility appears in the constraints chosen and in proving that the system survives more than the ideal path.
An estimate should expose its boundaries
Proposals can only be compared against the same scope. A useful estimate names stages, deliverables, revision limits, content, integrations, testing, launch and the defect-correction period.
A low starting price may exclude copy, mobile adaptation, domain transfer or post-launch support. That is not automatically wrong, but the client needs to know what is being purchased and what will cost more later.
A reliable price follows a short diagnosis
An initial assessment needs the goal, audience, core scenarios, integrations and desired timing. That is enough to choose between a template landing page, an authored website, a catalogue or a web application and to offer a range with explicit assumptions.
Within the Method, I map the task and its risks before proposing a form. This protects both the Concept and the budget: money is spent on what helps a person act and gives the business a measurable result.
Start with the website's purpose
If you are planning a website or rethinking one, we can begin with its role in your business, its structure and the visitor's path to an enquiry.