For a focused construction company website, Smartcon Works’ published packages start at £595 for up to four pages. Your budget depends on the number of service and project pages, content readiness and enquiry requirements. A contractor with one clear service and approved photographs has a different brief from a firm with several divisions, a growing project archive and formal tender enquiries. Those requirements need an agreed scope before a price is confirmed.
For UK contractors comparing quotes, start with the services, project examples and enquiry process. This guide explains how those choices affect scope, where a focused four to six-page website can work, and what to prepare before asking for a price. The prices below are Smartcon Works’ own published packages, not a UK market average.
A brochure site and a project-led site are different briefs
A simple brochure site introduces the company, describes its work, establishes coverage and gives prospective clients a way to make contact. Selected projects might sit together on one page. That can be enough for a specialist whose reputation travels through referrals and whose work is straightforward to explain.
A project-led website gives individual jobs their own pages. Visitors can examine the scope, your role, relevant constraints and photographs before moving to a service or enquiry. Those pages require an agreed format and prepared content. A Projects link containing fifteen case studies represents more work than one page containing six photographs.
Choose between them by asking what a potential client needs to assess. A large contractor may also need separate sectors, regional operations, recruitment and document routes. That is a larger publishing responsibility, even if the homepage looks restrained. Our construction website checklist covers the overall content; here, the question is which parts belong in your budget.
Count services and project pages separately
List the services you actually want enquiries for. Refurbishment, commercial fit-out and planned maintenance may need different explanations, evidence and contact prompts. Conversely, several closely related installation tasks may belong on one well-written specialist service page.
Then count the project examples you want at launch. Distinguish an archive overview, individual project pages and any categories. Ask whether the price includes preparing and entering every agreed project, or only building the layout into which someone else will enter them.
For illustration, Home, Services, Projects, About and Contact is five pages. Adding three individual project records makes eight. Splitting Services into an overview and three detailed services increases that again. These are scope examples, not a recommendation that every contractor needs the same structure.
Photography readiness changes the amount of content work
A folder of original, approved photographs with project names saves sorting and investigation. A collection of compressed messaging-app images with no record of which job they show needs preparation before design can begin. Neither situation tells the designer what your company delivered in the picture.
Record who selects images, checks permission, writes captions and supplies missing views. Commissioning photography, visiting sites or retouching large collections should be explicit scope items. A website package should not be assumed to include a photographer.
Written content needs the same clarity. Turning approved project notes into a page differs from interviewing site teams and reconstructing the job from old records. Use our construction case-study structure to gather the facts before requesting a content allowance.
Coverage and credentials need accurate preparation
A local contractor may only need a clear service-area statement. A business with separate regional teams might need location pages with different contacts, services and relevant projects. Explain that operational difference before adding a long list of town pages to the brief.
Near-identical location pages create more copy to approve and maintain without necessarily helping a client. Budget for distinct information where it exists: which team covers the area, what work it handles and what evidence can be shown.
Accreditations and compliance information also take preparation. Supply current names, approved marks and the scope of any certification. Decide whether visitors need a summary, downloadable documents or a route to request current evidence. Your team must verify these details; the designer cannot infer them from an old badge on the existing website.
Keep first enquiries separate from tender workflows
A straightforward project form can ask for the service, approximate location, timeframe and a short description. Those details may be enough to route the enquiry to someone who can respond. Our guide to construction enquiry form fields explains how to keep that first step proportionate.
Drawing uploads, private document access, tender deadlines and automatic routing into business systems introduce different requirements. Agree file handling, access, storage, notifications and ongoing responsibility. A small upload button can conceal a substantial workflow.
Describe what happens after submission before asking for functionality. If the team normally qualifies a job and then exchanges documents through an existing process, the website may only need to start that conversation. Formal tender or document systems need separate feasibility and pricing.
Decide how future projects will be added
A content management system can be useful when someone in the company will regularly publish projects. The scope should cover editable fields, image handling, permissions, training and the person responsible for checking facts before publication. A login alone does not establish a manageable process.
If only occasional updates are expected, arranging changes through the studio may be simpler. Compare that arrangement with the cost and responsibilities of a CMS. Ask how later projects are priced and whether the agreed template can accommodate longer descriptions or different image sets.
Keep recurring costs visible: hosting, domain renewal, paid services, maintenance and content updates. Distinguish post-launch support for the agreed work from an ongoing allowance to publish new projects.
An existing website brings migration work
A rebuild may contain years of project pages, PDFs and service URLs linked from tender submissions or other websites. Identify which still matter before deciding what to remove. Moving ten useful project records is a different job from transferring one gallery.
Include an inventory of useful addresses, a plan for retained or changed URLs, and checks on redirects, downloads and enquiry delivery. If search enquiries matter, share the available search information with the supplier. No migration plan can guarantee unchanged rankings, but the responsibilities can be agreed.
Our website redesign cost guide covers the wider transition budget, while planning a rebuild around existing SEO value explains the detailed checks. Those tasks should have a named owner in a construction website proposal too.
Where Smartcon Works’ packages fit
Our published website packages are Essential at £595 for up to four pages, Business at £895 for up to six pages, and Bespoke from £1,295 for seven or more pages or tailored requirements. These are our prices for the stated scope. They are not a price range for construction websites across the UK.
A focused contractor website may fit Essential or Business when its services, selected projects and company information fit the agreed pages. A growing archive, several service pages, CMS requirements or document functionality calls for a scope discussion. Bespoke’s starting price does not mean every proposed function is included.
The construction website service explains how we assess those requirements. For a broader comparison of delivery approaches, use the small business website cost guide. The immediate decision is whether a defined package covers your actual content and enquiry needs.
Prepare a short scope pack before requesting quotes
- Your current URL and what the new website should achieve.
- Services, client types and geographical coverage.
- Approximate project count at launch and expected future additions.
- Available photographs, project notes and publication permissions.
- Current credentials and documents visitors need to see or request.
- The enquiry process, including any upload or tender requirements.
- Who will approve content and maintain it after launch.
Mark missing material honestly. If three projects are ready and seven still need client approval, suppliers can quote a first release and a later addition separately. That is more useful than describing all ten as ready.
Compare what each proposal actually delivers
Put the proposals beside the same scope pack. Compare page and project counts, writing responsibilities, photography, migration, form handling, revisions and handover. Confirm one-off and recurring charges, VAT treatment where applicable, and how additional work is authorised.
A lower price may reasonably assume approved copy, limited project entry and no CMS. That can be a good fit if those assumptions suit you. It becomes difficult to compare only when they are hidden. Ask what “content included” means and whether the enquiry route is tested through to the receiving team.
Choose the scope that explains the work you want and can be kept accurate. A smaller, complete website can be a sensible first release; a large contractor archive deserves a realistic allowance for every record behind the navigation.