Back to Development
Development / Quoting

What a website costs depends on what it has to do

Every project here is quoted against its own scope, so there's no price list. What you get instead is the set of things that actually move the number, so you can come to a first call already knowing where a budget goes.

No price list: every quote is written for one scope Itemised against a written scope before any work starts Hosting, content and SEO quoted as separate lines
What drives the cost

Six things that change the number

A page count is the least useful way to price a website. These are the questions that actually shape a quote.

What the site has to do

A site that presents the business is a different job from one that takes bookings, sells stock or manages members. The more the site has to decide and remember, the more of the build is logic rather than layout.

What it connects to

A CRM, a booking platform, a payment provider, a stock system. Each connection has its own API, its own authentication and its own ways of failing, and each one is scoped on its own line.

Custom features or existing plugins

Where a well-maintained plugin already does the job, it gets used. Where your process is genuinely yours, the feature is built for it. The quote shows which is which, and why.

Content and page types

Who writes the copy, whether photography is needed, and how many distinct kinds of page the site has. Ten service pages that share one layout are one template, not ten designs.

How much design is new

Working from an established brand is a different job from creating the visual identity at the same time. If the brand needs work first, that is scoped separately so you can see it.

What it replaces

Moving from an existing site means redirects, carrying content across and protecting the rankings it already has. A brand new domain with nothing to preserve is simpler.

A page count tells you almost nothing about cost. What the site has to do tells you almost everything.
How quoting works

From first call to a written quote

01

Discovery call

A conversation about what the business needs the site to do, who it's for and what it has to connect to. Bring a budget if you have one.

02

Written scope

The page types, features, integrations and content responsibilities, plus what's deliberately out of scope, in writing.

03

Itemised quote

Priced line by line against that scope, so you can see where the budget goes and what could be phased into a later stage.

04

Build to the scope

If something new comes up mid-build, it gets quoted before it gets built. Nothing is discovered on the invoice.

Questions people actually ask

FAQ

Why don't you publish prices?

Because two five-page websites can be completely different jobs. One presents a business, the other takes bookings and talks to a CRM. A published figure would be wrong for almost everyone who read it, so each quote is written against the scope agreed on the call.

Can you work to a budget?

Yes. Share the budget early and the scope gets shaped to fit it. Anything that doesn't fit now can be planned as a later phase, rather than squeezed in and done badly.

What isn't included in a build quote?

Hosting, ongoing support, content writing and SEO are quoted as separate lines. You can see what each one costs and decide what you need, rather than paying for a bundle.

Is a template cheaper than a custom build?

Usually at the start. Whether it stays cheaper depends on how far the business has to bend around it. Compare what each option costs over a few years, not just the first invoice.

Will the quote change once work starts?

Only if the scope changes, and any change is quoted and agreed before it's built.

Available for projects

Tell me what's broken, or what you're starting.

One email or a fifteen-minute call. I read and reply to every one myself.