Our take: the cheapest quote is rarely the cheapest website

Why the lowest number usually costs the most over three years, where the difference hides, and how to compare quotes properly.

3 minread 723words last updated

The short answer

When three quotes arrive for a website, the lowest is usually lowest for a reason, and the reason is rarely efficiency. It left things out: discovery that would have found the real requirements, testing for speed and accessibility, documentation, ownership in your name, a maintenance plan, and the questions that would have raised the price. What was left out does not disappear. It arrives later as change requests when the assumptions fail, as a slow site that loses customers, as an incident on an unmaintained platform, as a rebuild in year two, or as a hostage situation at exit. Compared over three years including maintenance, hosting, likely changes and what the site loses, the ranking usually reverses. A genuinely cheap website exists, a well-scoped static site on a mainstream stack in your name with light maintenance, and it is rarely the lowest number on the table.

Where the difference hides

Left out of the low quoteHow it comes back
DiscoveryRequirements discovered during the build as change requests
Testing for speed and accessibilityA slow site losing mobile customers; a failed audit
Mainstream stackA page-builder site nobody else can maintain; a rebuild in two years
Ownership in your nameHosting and domain in the builder’s name; a dispute at exit
DocumentationA takeover that takes months
Maintenance planPlugins months behind; an incident; emergency rates
Content and migration”We assumed you would provide that” in week three
Integrations priced honestlyThe form that never reached the CRM

Comparing so the cheap one is actually cheap

  1. Rewrite each quote under the same headings: discovery, scope, not included, stack, testing, ownership, documentation, maintenance, hosting.
  2. Fill the blanks by asking; a blank is a future cost, not a saving.
  3. Add thirty-six months of maintenance and hosting at each quote’s stated terms, or at market rates if unstated.
  4. Add a line for what the site loses if it is slow, insecure or unowned, estimated roughly.
  5. Compare the totals. Then weigh the quality of the answers.

What a genuinely cheap website looks like

A tight scope agreed in discovery. A static site on a mainstream stack, fast by construction, with almost no hosting cost. Accessibility and speed tested before launch. Domain, hosting and repository in your name. Documentation that a successor can use. Light monthly maintenance that keeps it current. It is not the lowest possible number, and over three years it is the lowest total, which is what cheap should mean.

What this means for you

Treat the lowest quote as a question, not an answer: what did it leave out? Rewrite all quotes under the same headings, add three years of running costs and what a poor site would lose, and compare totals. Choose the genuinely cheap website, tight scope, mainstream static stack, your name on everything, light maintenance, which is rarely the lowest number and reliably the lowest cost.

Written by the CivSec S.M.A.R.T team

We build and run websites, software and AI systems for businesses. We write about what we see in that work, in plain language, and we update articles when things change.

Last checked . Spotted something outdated? Tell us.

Frequently asked questions

Is a low quote always a warning sign?

No; a low quote for a small, well-scoped site from a builder who works efficiently on a light stack can be exactly right. The warning sign is a low quote for the same scope as higher ones with no explanation of the difference, no not-included list and no maintenance plan. Ask what was left out; the answer is either a good reason or the future invoice.

Where does the difference usually hide?

In the parts a client cannot see at launch: whether it is built on a mainstream stack or a builder's habit, whether accessibility and speed were tested, whether the code and accounts are in your name, whether there is documentation, whether anyone will maintain it. The site looks the same on day one. The difference shows in month six and at exit.

How do we make the cheap option actually cheap?

Scope tightly, insist on a static mainstream stack, ownership in your name and documentation, and buy light maintenance from the start. That combination is genuinely inexpensive to build and to run, and it is what an honest low quote describes. The dishonest low quote describes the same price with those things removed.