Why some web designers price by the page, and what that hides

What per-page pricing is meant to simplify

Per-page pricing exists to make a quote easy to read at a glance. Count the pages. Multiply by a rate. Get a number you can hold up next to another quote and compare directly, without doing any extra math on your end.

For a small, straightforward site, that math genuinely holds up. It gives you something concrete to check, and it's harder to inflate quietly than a single lump figure with no breakdown attached to it at all.

The simplicity is real, but it isn't the same thing as accuracy. A model built to be easy to read isn't automatically a model built to reflect what each individual page actually takes to build from scratch.

That gap between readable and accurate is exactly where a per-page quote can either serve you well or quietly work against you, depending entirely on how the builder handles the details underneath it.

Think of the rate as a starting point for a conversation rather than the finished answer. A number on a page is only as good as the definition sitting behind it, and that definition is rarely printed anywhere near the price itself.

What counts as one page versus several

Is a simple contact form one page. Is a twelve-section landing page with a gallery, testimonials, and a booking widget also just one page. On paper, both are a single URL with a single address, indistinguishable in a page count.

In build time, they are nowhere near the same job. One takes an afternoon to finish properly. The other takes considerably longer, and a flat per-page rate has no built-in way to reflect that difference unless someone designs the pricing to account for it on purpose from the start.

Ask the person quoting you to define what a page means in their pricing model, specifically and in writing, before anything gets counted. Does a page with a form cost the same as a page with just a paragraph and one image. Get that definition settled before you count anything against it.

A long scrolling page built from several distinct sections raises the same question. Is that one page, or is it several pages stitched together and billed as if it were one. Ask directly, and get the answer written down somewhere you can point back to.

A gallery page with fifty images and a filter tool is a different build than a gallery with five static photos, even though both would sit under a single "gallery page" line item on a quote that doesn't distinguish between them. The label is identical. The work behind the label is not, and only one of the two determines how long the build actually takes.

Functionality that doesn't map cleanly to a page count

A lot of what makes a site expensive doesn't live on a single page at all. A booking system, a payment integration, a login area — these touch one page visually but require work that has almost nothing to do with how many pages exist across the site as a whole.

The features that quietly move a website quote higher covers this directly: complexity, not page count, tends to be the real driver behind most of the total you end up paying at the end.

A per-page quote that doesn't separate feature cost from page cost is one where the page count is doing work it was never built to do in the first place. That's not necessarily dishonest pricing on the builder's part, and it rarely is.

It's just imprecise, and imprecise pricing is exactly where disagreements tend to start once the project is already underway and the invoice for extra work arrives unexpectedly.

When per-page pricing under-quotes a complex site

The failure mode here is predictable once you see it laid out. A site with five pages sounds small on paper, easy to estimate at a glance without much thought. If two of those five pages carry a booking calendar, a payment form, and a filterable gallery, a flat per-page rate will under-price the work by a wide margin.

That's because the rate was built to account for a page existing, not for what actually sits inside it once it's built out in full. The shortfall doesn't vanish once work starts on the project.

It shows up later, as a change order, a tense scope conversation, or hours quietly absorbed by the builder that eventually show up in the quality of the finished work instead of on the invoice itself. Neither outcome is one you want to discover after launch.

The safest read of any per-page number is to treat it as a floor, not a ceiling. Assume complex pages will cost more, ask specifically by how much, and build that answer into your budget before work begins rather than after.

Asking what's inside each page's price before agreeing

Before agreeing to a per-page number, ask what's included in a standard page versus what pushes a page into a higher tier of pricing entirely. A carefully built quote will already separate a basic page rate from a complex page rate, clearly labeled and easy to check line by line.

A quote that treats every page as identical, regardless of what's actually on it, is worth a direct question before you sign anything at all. This is really one piece of a larger comparison exercise between builders competing for the same project.

How to compare website quotes against each other walks through the fuller method, and what actually drives the cost of a website is worth reading alongside this one before you commit to any single pricing model over another.

More from the blog

All posts