How Much Does a Website Cost: What the Price Is Actually Made Of

The question “how much does a website cost” almost always gets the answer “it depends”. That is honest and useless. Below is a breakdown of what it actually depends on, which parts of the budget always exist, and why two quotes for the same brief can differ threefold.

What makes up the price

Regardless of scale, a budget breaks down roughly the same way. The percentages are approximate, but the proportion holds.

StageShare of budgetWhat it covers
Research and structure10-15%Brief, competitors, sitemap, wireframes
Design25-35%Layouts for every page type, mobile versions, states
Build and development30-40%Code, admin area, forms, integrations
Content10-15%Copy, image processing, population
Testing and launch5-10%Checks, fixes, migration to hosting
Project management10-15%Communication, approvals, schedule control

If a quote has no line for research, content or testing, it does not mean that work will not happen. It means it will either be rushed or handed to you.

Relative cost by type

Absolute figures depend on the market and the team, so ratios are more useful. Take a simple landing page as the unit.

Type of siteRelative costTimeline
Landing page on a ready template0.3-0.51-2 weeks
Landing page with custom design13-4 weeks
Corporate site, 10-20 pages3-510-16 weeks
Multilingual site with blog and case studies5-814-20 weeks
Online store8-1516-28 weeks
Site with a custom admin panel and integrations10-2520-40 weeks

What affects the price most

  • The number of unique templates, not pages. A hundred pages on three templates costs less than ten pages each designed individually.
  • Integrations. Every external service is a separate task with unpredictable details. The most expensive are integrations with legacy systems that have no documentation.
  • Multiple languages. Adds roughly 20-30% to design and development, and doubles the content workload.
  • Animation. Complex motion sequences can cost as much as an additional page.
  • The number of approvers. Not a line item, but the one that most often consumes the time buffer.

Why two quotes differ threefold

The most common reason is that they cover different scopes without saying so. Five questions expose it:

  1. Is the design custom or an adaptation of a ready theme?
  2. Are mobile layouts designed separately, or is it “we will make it responsive during build”?
  3. How many rounds of revisions are included?
  4. Who writes the copy?
  5. Is migration of existing content included?

Usually after these questions the price gap halves, and sometimes disappears entirely: it turns out the cheap quote simply excluded half the work.

What is most often excluded

ItemWhen you find out
Hosting and domainAt launch
Plugin and font licencesDuring setup
PhotographyAt the content stage
CopywritingWhen the copy never arrives
Analytics setupAfter launch
Support and updatesA month after handover
Migrating old URLs and redirectsWhen traffic drops

The last item is the most underestimated. A redesign without correct redirects from old addresses routinely costs companies half their organic traffic.

Where saving turns into spending

A cheap site is not a problem in itself. The problem is saving on things you then have to buy twice:

  • A ready theme instead of structure. Works while the requirements are standard. The first non-standard requirement runs into the fact that replacing the theme is easier than reworking it.
  • Skipping wireframes. Changes to an approved design cost several times more than changes to a grey schematic.
  • No admin area for content. Every copy edit becomes a support request.
  • No support after launch. A site without updates becomes vulnerable within months.

How to read a proposal

Four signs a quote was put together honestly:

  • Work is broken into stages with separate figures, not “website development, one number”.
  • The number of revision rounds is stated.
  • There is a section on what is not included.
  • It specifies what happens after launch and what that costs.

The price of a website is not the price of pages. It is the price of decisions someone has to make: about structure, about priorities, about what to do with the awkward cases. Cheap proposals are the ones where those decisions were never budgeted, and you will end up making them yourself, mid-project, at your own expense.