WEBSITE COST GUIDE

How much does a small-business website cost — and what changes the price?

The useful answer is not a page-count price. Cost changes with the job the website must do, the material already available, the business rules behind each function and the responsibility required after launch.

THE MAIN COST DRIVERS

Price follows responsibility and uncertainty.

Two five-page websites can require very different work. These factors reveal the difference more reliably than page count alone.

Offer and information structure

A simple, well-defined service needs less discovery than a mixed offer requiring categories, locations, audiences and several customer routes.

Content readiness

Existing approved copy, brand assets and usable photographs reduce preparation. Research, writing, editing and asset creation add real work.

Customer functionality

A contact form is simpler than conditional quotes, bookings, product configuration, customer accounts or external data connections.

Migration and access

Preserving URLs, content, email, analytics, customers or orders requires careful access, mapping, backup and testing.

Risk and acceptance

Payments, personal data, staff access and operational workflows need clearer tests, responsibilities and fallback routes.

COMPARE PROPOSALS PROPERLY

Ask what the price actually buys.

A lower figure is not comparable if essential content, launch work or ongoing costs have been omitted.

Defined deliverables

List the pages, reusable layouts, forms, functions, content responsibility and number of agreed review rounds.

Assumptions and exclusions

State what the client supplies, which unknowns could change scope and what is explicitly outside the project.

Ownership and accounts

Confirm ownership of the domain, content, design assets, provider accounts and access after final payment.

Third-party and recurring costs

Separate domain, email, paid services, transaction fees, advertising, care and future changes from the build fee.

Launch and support

Define testing, backups, redirect work, handover, the launch window and what happens when an issue is found.

SPEND IN THE RIGHT ORDER

Protect the part that makes the website useful.

When the budget is limited, reduce breadth before removing the foundation needed for a reliable customer route.

01

First: clear offer and customer action

A smaller website with accurate services and one complete enquiry route is more useful than many unfinished pages.

02

Second: mobile clarity and essential content

Prioritise readable hierarchy, speed, trust information and the questions customers need answered before acting.

03

Third: measurement, ownership and care

Make sure enquiries can be tested, accounts are owned correctly and the website has a defined maintenance route.

04

Later: optional automation

Add accounts, complex integrations or secondary workflows after their benefit and administration are proven.

COMMON QUESTIONS

A few useful things before we start.

Can I get an exact price before a brief?

Usually not. An indicative range is possible, but an exact proposal needs the pages, content responsibility, functions, access and key risks to be defined.

Is a monthly plan always required?

No. Ongoing care is separate, but every website still needs someone responsible for hosting, updates, backups, security checks and small operational issues.

Can the website be built in stages?

Yes, when the first stage is a complete customer route and later stages do not require rebuilding the foundation.

GET A COMPARABLE STARTING POINT

Define the useful first version before asking for an exact figure.

The planning route captures the decisions that affect scope and produces an editable summary for JAMT review.

Scroll to Top