Small business website A small business website needs a clear goal, a sound budget and one owner for each choice.
Ask three agencies for a price and you will get three different numbers. A useful budget is something else. It is a list of decisions about what must be ready at launch, who is supplying the content, which systems need to connect and who will look after the site afterwards. Two proposals can both say “business website” while describing very different amounts of work.
Start by writing down the commercial job of the site. A brochure site for a consultant, a booking site for a clinic and a catalogue for a manufacturer may each contain six pages. However, the research, content, forms and integrations are not comparable. Price makes sense only after that job is clear.
Divide the budget into five parts
1. Discovery and structure
This is the work required to decide what the website needs to say and how visitors will move through it. It can include stakeholder interviews, page planning, competitor review, content inventory and a written brief. A very small project may handle this in one working session. A project with several audiences or services usually needs more thought before visual design begins.
2. Content and evidence
Clarify who writes the copy, selects images, prepares case studies and checks factual claims. “Content supplied by the client” can reduce the fee, but only if the material is complete and usable. If the designer must turn notes, old pages and voice messages into finished copy, that is additional work and should appear in the scope.
List every item the site needs: service descriptions, team or company information, prices, photographs, policies, testimonials that can be verified, downloadable documents and contact details. Mark each item as ready, needs editing or needs creating.
3. Design and build
A template configured around existing brand assets is different from a custom interface designed for a specific journey. Neither is automatically better. The right choice depends on how distinctive the experience must be, how much content exists and how often the business will update it.
Ask whether the proposal includes responsive layouts, accessibility checks, browser testing, form validation, image optimisation, redirects from old URLs and basic search metadata. These are easy to assume and expensive to discover late.
4. Integrations and operational work
A contact form that sends one email is simple. A form that creates a CRM lead, records consent, assigns an owner and retries after an API failure is a small software workflow. Booking systems, payment providers, customer portals, product imports and multilingual content introduce similar differences.
For every integration, record the account owner, subscription cost, data being transferred and what should happen when the third-party service is unavailable. This makes hidden operational costs visible before launch.
5. Running costs after launch
Separate the build fee from domain renewal, hosting, platform subscriptions, premium extensions, payment processing, maintenance and future content work. Confirm which supplier holds each account. The business should be able to access its domain, hosting, analytics and essential platform accounts without relying on one individual.
Check VAT and payment terms in UK quotes
UK prices are not always presented on the same basis. GOV.UK explains that prices aimed only at the general public include any VAT due. business-only prices do not usually include VAT and may have it added. Ask every supplier to state whether VAT applies and whether each total is VAT-inclusive before comparing proposals.
Record the deposit, payment stages, invoice due dates and what happens if the project pauses or its scope changes. The final invoice is a separate document from the proposal. where VAT applies, it should identify the VAT amount as well as the total owed. This avoids a proposal appearing cheaper only because tax or a later payment stage was not visible in the headline figure.
A comparison worksheet for proposals
Put competing proposals into the same structure before comparing totals:
- Outcome: the visitor action and business result the site is intended to support.
- Pages and templates: named pages, reusable layouts and any exclusions.
- Content responsibility: who writes, edits, approves and uploads each type of content.
- Functionality: forms, payments, booking, search, accounts, imports and integrations.
- Quality checks: mobile, accessibility, performance, browsers, forms and redirects.
- Revisions: what is reviewed, how many rounds are included and who approves.
- Ownership: files, source code, licences, domain, data and account access.
- Launch and support: deployment, training, warranty period and ongoing maintenance.
- Third-party costs: recurring charges paid directly by the business.
If a line is absent, do not assume it is included. Ask the supplier to confirm it in writing. This is especially important for copywriting, product entry, premium software licences and ongoing search or marketing work.
Use a phased scope when the budget is tight
Reducing quality is not the only way to reduce initial cost. A focused first phase can launch one clear offer, a credible company page, essential proof and a tested enquiry path. Later phases can add supporting services, resources, automation or ecommerce after the core journey is working.
Do not create empty pages merely to make the website appear larger. A smaller complete site is more useful than a large collection of placeholders. Keep a written backlog so deferred work is an explicit decision rather than a forgotten promise.
Warning signs in a cheap or expensive quote
A low price is risky when the scope is vague, ownership is unclear or important work is described only as “SEO included”. An expensive proposal is not automatically safer. it should still explain the people, deliverables, review points and measurable checks behind the fee.
Ask what happens if content arrives late, an integration changes, the project pauses or the supplier becomes unavailable. The answer reveals more about the real cost than a long feature list.
Before requesting a quote
Prepare a one-page brief with the business objective, priority audience, required pages, essential functions, available content, target date and named decision-maker. That gives suppliers the same starting information and makes their answers easier to compare.
A worked example
A six-person accountancy practice in Leeds asks three suppliers for a website to replace an ageing brochure site. The quotes come back at £2,400, £7,900 and £18,000, which looks like an impossible comparison until the five parts are separated out.
The £2,400 quote covers design and build on a template, with the practice writing all copy and supplying photography. The £7,900 quote covers the same build plus copywriting for nine pages, a photo day. three months of post-launch changes. The £18,000 quote includes a client portal with document upload, which nobody asked for.
Once the middle quote is stripped back to the same scope as the cheapest, it sits around £4,100. The remaining £1,700 buys the copywriting the practice would otherwise have to write itself, over roughly forty partner hours. That is the actual decision, and it is not the one the headline numbers suggested.
Sources and further reading
- GOV.UK guidance on where VAT appears in prices — the source used to distinguish public-facing, mixed-audience and business-only price presentation.
- W3C Web Content Accessibility Guidelines overview — the reference used for the accessibility checks mentioned in proposal comparison.
- Google Search Essentials — Google’s published technical and content requirements for pages intended to appear in Search.
Our service pages show the current published packages in GBP. For work that does not fit a package, send the brief and request a written scope before committing to payment.
Quick small business website action plan
- Set the main goal for the site. Write down the result. Name one owner.
- List the pages that help that goal. Test this step. Keep proof of the test.
- Choose the proof each page needs. Use real data. Check each fact.
- Set a budget for build and care. Ask one user. Note what feels hard.
- Keep the domain in the business name. Fix each fault. Run the check again.
- Plan copy before design starts. Set a due date. Review the result.
- Test each form from start to end. Write down the result. Name one owner.
- Track leads that reach the team. Test this step. Keep proof of the test.
- Choose one clear goal. Use real data. Check each fact.
- Name the owner for each task. Ask one user. Note what feels hard.
- Test the full path before launch. Fix each fault. Run the check again.
- Set the next review date. Set a due date. Review the result.
- Keep the plan where staff can find it. Write down the result. Name one owner.
- Use plain words in each note. Test this step. Keep proof of the test.
- Save proof for each key check. Use real data. Check each fact.
- Fix one issue at a time. Ask one user. Note what feels hard.
- Check the result with a real user. Fix each fault. Run the check again.
- Remove work that does not help the goal. Set a due date. Review the result.
- Share each major change with the team. Write down the result. Name one owner.
- Run the same checks after each update. Test this step. Keep proof of the test.
- Check the source of every key fact. Use real data. Check each fact.
- Keep private data out of public notes. Ask one user. Note what feels hard.
- Plan what to do when a check fails. Fix each fault. Run the check again.
- Give each choice a clear reason. Set a due date. Review the result.
- Keep old files until new work is proven. Write down the result. Name one owner.
- Ask for help when the risk is high. Test this step. Keep proof of the test.
- Check phone and desktop views. Use real data. Check each fact.
- Make the next step easy to find. Ask one user. Note what feels hard.
- Track the result that matters most. Fix each fault. Run the check again.
- Close each task when proof is saved. Set a due date. Review the result.
Use this small business website plan as a live check. Keep the notes short. Review the work after each major change.
