Why we price websites by pages, and where that stops working

Page-based pricing exists because it gives both sides something concrete to talk about on the first call. A range of pages maps to a range of effort, and that is enough to know which bracket a project sits in before anybody has written a brief.

What it is not is a quotation. The page count sets the baseline; functionality, design complexity, integrations and timeline decide the final figure.

01What actually moves the number

Four things, roughly in order of impact:

• 01Functionality — a booking flow or a calculator is not a page, it is a feature with its own edge cases.
• 02Design complexity — a bespoke layout per template costs more than one template used six times.
• 03Integrations — every third-party service adds behaviour nobody fully controls.
• 04Timeline — compressed schedules cost more because they change how work is sequenced.

02Where page-based pricing breaks

Above roughly twenty pages it stops being useful. At that scale the variance between two twenty-page sites is larger than the gap between the tiers, which is why anything past that point is quoted individually rather than pushed into a band it does not fit.

Applications are the same story from the start, which is why they are scoped by screens instead — a screen with authentication behind it is a different object from a marketing page.