A construction company website that shows how you run a job
People hiring a builder are about to spend a lot of money and live with the result for years. They judge a construction company website on three things: finished projects that look like theirs, proof you're licensed and insured, and a clear sense of how you'll run the job. Then they want to send a brief and get a response.
Why trust comes before price
Most people know someone with a building horror story: the job that ran months over, the contractor who disappeared, the extension that leaked. So the first question isn't what you charge but whether you'll finish properly. A builder's site earns an enquiry by answering that worry with evidence: projects with details, named people, documents, and a process written down.
Completed projects with substance
Each project should be a page of its own, not just a photo in a carousel. Record the same facts for every job so a reader can find one like theirs:
| Field | Example |
|---|---|
| Project type | Rear extension, loft conversion, new-build house, commercial fit-out |
| Location | Town or district, never the full address without permission |
| Scope | Demolition, groundworks, structure, roofing, first and second fix, finishes |
| Duration | From start on site to handover, and whether it ran to programme |
| Working with | Architect, structural engineer, the client's own designer |
| Photos | Before, during and after, with progress shots of the structure |
In Anticode these live in a CMS collection with typed fields, so each project is served at its own address and the list stays consistent. Progress photos matter as much as the finished ones: steel going in, the roof being made watertight, neat site set-up. They show how you work, which is what the client is buying.
Licences, insurance and memberships
- Licences or registrations your country or state requires for building work, with the number and a link to the public register where one exists.
- Insurance: public liability and, where you have it, contract works and employer's liability cover. Say you'll show certificates on request.
- Warranties or guarantee schemes you belong to, and what they cover.
- Trade association memberships, only if current.
Explaining how you run a job
A process page answers the questions clients are too polite to ask at the first meeting. Set out the stages in order (site visit, written quote, contract, programme, start on site, weekly updates, snagging, handover and sign-off) and say what happens at each. Cover the practical things too: how payments are staged against progress, who the client's single point of contact is, how changes and extras are agreed in writing, working hours, how you keep neighbours informed, and how the site is left at the end of each day.
A project enquiry that captures a brief
A one-line contact box produces a lot of tyre-kicking and very little information. A structured enquiry helps both sides, either as prompts above the message box or as a custom form (up to 30 text fields, tied to a site function) or app-built form with a field for each question. Ask for the property type and location, what the client wants built, whether drawings exist and planning or permits are in place, the budget range, when they'd like to start, and how they heard about you. Put an "areas we cover" list beside the form so people outside it don't spend time filling it in.
Enquiries are saved and sealed at rest and can be emailed to you. With connectors they can go straight into HubSpot, Airtable or a Google Sheet as a lead, or into a Slack channel your estimator watches. Each submission is sent once, without retries, so keep an eye on the dashboard list too.
Mistakes generated builder sites make
- Stock photos of glass towers for a firm that builds extensions. Show the jobs you actually do.
- "Quality, reliability, integrity" as the whole message. Every builder says it; your projects and process prove it.
- Invented review counts or star ratings. Use real reviews with the client's permission.
- Hiding the area you cover until the last line of the contact page.
Building it with Anticode
Describe the firm in a sentence, such as "a building company in Kent doing extensions, loft conversions and renovations, with completed projects and a detailed enquiry form". The Architect asks up to three questions and shows the plan, typically with Work, Services, About and Contact pages. Swiss (Inter Tight) or Technical (IBM Plex Sans) give a solid, plain look; Brutalist (Archivo) can suit a firm with a strong, modern identity. Upload your own photographs. Bigger changes later, such as adding a commercial division, can be asked for in a sentence, with recent versions kept in history.
Limits
- No client portal for drawings, progress updates or invoices on the published site. A Next.js export with roles is the route if you need one built.
- No uploads in the enquiry form; plans and photos come by email.
- No estimating or scheduling tools. Anticode collects the brief; your own software handles quotes and programmes.
Questions people ask
What should a construction company website include?
Completed projects with detail and photos, licences and insurance, a written process, areas covered and a structured enquiry form.
Can enquiries go straight into my CRM?
Yes, if it's HubSpot, Airtable, Notion or Google Sheets, through a connector. Other systems can receive them by webhook.
Can I add new projects myself?
Yes. Projects in a CMS collection are added and edited from the dashboard without rebuilding the site.