E-commerce
How much an e-commerce website actually costs, and what changes the number
A functioning e-commerce site with real checkout costs anywhere from $150 to $10,000 for the same scope, and the spread is mostly where the developer lives and how many people sit between you and the one typing. Hiring direct and offshore is the bottom of that range; an agency with separate design, QA and account management is the top.
The honest price bands
| Band | What it usually is | What you are actually buying |
|---|---|---|
| $80 – $200 | A direct hire with an offshore developer running a fixed process. My own tiers sit here | One person’s judgement, at their cost of living rather than yours. The build is real; the diligence is on you |
| $300 – $1,500 | A freelancer in the UK, US, EU or Australia | A similar output at a local rate, bought with an easier timezone and simpler legal recourse |
| $2,000 – $8,000 | A small studio: separate design, build, QA and someone who answers the phone | Capacity and process. Worth it when a project genuinely needs more than one person |
| $10,000+ | An agency, complex integrations, or enterprise procurement | A different market with different requirements — account management, SLAs, sign-off stages |
The spread is not a quality ladder. A developer in Islamabad and a developer in Manchester writing the same PHP produce the same site; what differs is the cost of living behind the invoice and how many salaries sit between you and the person typing.
What you give up going direct and offshore is not craft. It is convenience and easy legal recourse — and both are manageable with the right contract, which is the subject of a separate guide.
What actually moves the price
Clients usually expect page count to drive cost. It barely does — the twentieth product page costs almost nothing once the first one exists. Four things genuinely move the number.
- Catalogue complexity
- Simple variants are cheap. Configurable products with price formulas, per-variant stock, or combinations that must be blocked are the single largest cost multiplier in any store build.
- Integrations
- Every external system — accounting, dispatch, an ERP, a supplier feed — is its own small project with its own failure modes and its own testing.
- Content readiness
- If product photography, descriptions and specifications exist, the build flies. If they do not, someone has to make them, and that someone bills for it.
- Decision latency
- A project where feedback takes a week per round costs more than one where it takes a day, because the developer holds context open. Fixed-scope quotes absorb some of this; nothing absorbs all of it.
The five line items that hide the true cost
A quote can be technically honest and still leave you with a surprise. These are the five items to ask about explicitly, before you sign anything.
- Payment integration — is it included, or quoted as an extra once the build is underway?
- Content population — who types in the 200 products, and is that time in the quote?
- Post-launch fixes — how long, and does "bug" have a written definition?
- Hosting and domain — in whose name, and who renews it?
- Handover — do you receive credentials, code and documentation, or only a live URL?
On my quotes the first four are included and itemised, and the fifth is a written handover document. That is not generosity — it is that arguing about them later costs more than including them now.
Where a cheap build costs more
Cheap is not the problem, and I would be a hypocrite to argue otherwise while publishing a $150 tier. What makes cheap expensive is when the store has to be rebuilt eighteen months later because the data model could not carry the business — and that failure has nothing to do with the price and everything to do with whether stage one happened.
The warning signs are consistent. No written scope. No staging URL. Payment "added at the end". No mention of who owns the hosting. A quote that arrives in under an hour, which means nobody has looked at your catalogue.
Questions people ask about this
- Why do quotes for the same site vary so wildly?
- Two reasons stacked on top of each other. Location and overhead account for most of it. The rest is that the quotes are often not for the same site at all — one is a template with your logo, one is a modelled catalogue with tested checkout and documented handover. Ask each supplier what happens when a customer closes the tab immediately after paying. The answer separates the two instantly, at any price.
- Is it cheaper to hire an offshore developer?
- Usually, yes — the hourly rate is lower. The risk is not quality, it is contracting: data transfer legality, who owns the accounts, and what happens when they stop replying. Those are solvable with paperwork, and the supplier should have that paperwork before you ask.
- Do I pay all of it upfront?
- You should not, at any size. A 40% deposit with the balance on completion is the normal shape for a small build; three milestone payments suit a longer one. On a short build the deposit is small in absolute terms, which is rather the point — you are risking very little to find out whether the working relationship is any good.
- What are the ongoing costs after launch?
- Hosting from a few dollars a month, domain renewal annually, payment processing fees per transaction, and optionally a maintenance retainer. Budget for updates whether or not you buy a retainer — an unpatched store is a breach waiting to happen.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan — fifteen live client sites, six of them stores taking real payments. The examples in these guides come from those builds and from the audit that rebuilt this site, not from a content brief. More about how I work, or read the case studies.