If you are reading this, you are probably trying to put a number on something that does not have an obvious price tag. You are not alone. "How much does it cost to hire a web developer?" is one of the first questions every business asks, and it is one of the hardest to answer cleanly, because the honest answer is: it depends on what you actually need.

The three ways developers charge

Most developers price their work one of three ways, and each suits a different situation.

  • Hourly. Common for maintenance, small fixes, and projects where the scope is genuinely unknown. Rates vary widely, but you are paying for their time and attention, not for a finished thing.
  • Fixed project price. You agree on a deliverable and a price before work starts. This is usually the best fit for a defined project like a marketing site or a store — you know what you are buying, and they carry the risk of the scope staying put.
  • Retainer. A monthly fee for an ongoing relationship — a set number of hours, or standing availability for changes and support. This works well once a site is built and needs a long-term caretaker.

What the range actually looks like

Ballpark figures are useful only as a floor. A simple one-page or three-page brochure site might fall at the low end. A full ecommerce store with payments, inventory, and a custom admin panel lives at the high end. The difference is not the developer being expensive; it is the amount of moving parts.

The cheapest quote is rarely the cheapest project. If a price looks too good to be true, ask what it does not include — hosting setup, copy, images, training, or fixes after launch are common things that get quoted separately.

Where the costs quietly hide

  • Scope creep. The project that grew from "three pages" to "and can it do this too" is the classic cause of a quote being exceeded. A good developer writes down what is included so that "this too" costs extra in the open.
  • Ongoing costs. Domains, hosting, email, payment processing, third-party tools — these are recurring and are usually separate from the build itself.
  • Content. You or someone needs to write the words, take the photos, and supply the products. That time is real even though no developer bills for it.
  • Support after launch. A site is never really finished. Ask what happens a month after launch, and budget for looking after it.
What you are really buying is not a website. It is the certainty that the website works, looks the way you want, and can be changed when your business changes.

How to get a useful number

Send the same brief to two or three developers and compare what they ask. A good brief says what the site must do, who it is for, and what success looks like — not which colours you like. You will learn more from the questions they ask back than from their prices.

If you want a feel for what a project like yours involves and what it should cost, I have built a range of projects — from storefronts to fully custom platforms — and I am happy to look at your brief and give you a straight answer, including whether it is a one-person project at all. Reach me through the contact page.

See the projects behind this guide →