Websites for construction companies

What you receive

Each item is a file or an account in your name, not a promise about traffic.

A page structure agreed in writing before design starts

Every page listed, with what it is for and which question from a buyer it answers. You approve the structure before anything is drawn, so the design is fitted to the content rather than the other way round.

A design system, not a set of mockups

Type, colour, spacing and components defined as exact values, so that a page added later by somebody else can match the pages we built.

The built site, server rendered

On Next.js, WordPress, Shopify or a static build, chosen for who has to update it afterwards rather than for fashion. Copy, headings and links exist in the served HTML, so a crawler receives the content without running a script.

A bid request form that survives a real set

Multi file upload with every file listed and its status shown, a link route beside it for large sets, and a failure that is reported rather than hidden.

Accounts registered to you

The domain, the hosting account and the code repository are set up in your name from the start. There is no arrangement where leaving costs you the site.

A written handover

How to edit each type of page, where the accounts and passwords live, and what to do when something breaks. Written for the person who will actually maintain it.

How a contractor site is structured

The structure follows how a buyer reads you before an invitation to bid.

Services, one page per scope

A buyer searching a scope should land on that scope. That means a real page per trade or capability, written in the language of your bid forms and cross linked, rather than one page listing everything you do.

Service areas as jurisdiction, not a city page farm

Where you work, and what differs there: agencies, bid forms, wage regimes. Not the same paragraph with the town name swapped.

Projects, with permission

Project references published only where the client has agreed, anonymised where they have not, and never stock construction photography captioned as your work.

About

Who you are, what you do and do not do, and who is accountable, with a named person where you are willing to name one.

Licensing and safety, authored by you

Licence numbers, bonding capacity and safety programme details are yours to state and we do not verify them. We build the page and you supply and stand behind the content.

Bid request

The page a general contractor uses to send you a set. It carries the form, the file limits stated plainly, and what happens to documents after they arrive.

What is included, and what is not

Stated here rather than discovered halfway through the build.

From first call to live

The sequence is fixed. A fee is agreed before design starts, and content is settled before design, because a design fitted to placeholder text is fitted to nothing.

1. 01

   Discovery

   A call about who buys from you, which scopes you bid, what work you want more of, who will edit the site afterwards and what exists today. If you have an estimate from us we already know the scopes.

2. 02

   A written fee and a delivery date

   Scoped and quoted individually, stated in United States dollars, before any design work starts. You approve it, then work starts. Nothing is invoiced that you have not agreed.

3. 03

   Structure and content

   The page list is agreed, copy is drafted from your input, and you supply photographs, project permissions, licence numbers and safety content. Anything we cannot verify stays out until you confirm it.

4. 04

   Design

   The system first, then pages built from it and reviewed on real content at phone and desktop widths. You see the pages that matter most, the scope pages and the bid request, before the rest.

5. 05

   Build

   Server rendered on the stack chosen at discovery, with forms wired and tested using real files. Images are sized and compressed, and the performance budget is checked on the pages a buyer lands on.

6. 06

   Launch and handover

   The checklist below is worked through, the site goes live on your domain, and the handover document and the account details are passed to you in writing.

The bid request form, in detail

This is the element that receives a set, so it is specified in detail and tested with real files before launch.

Every file listed with a status

Each file is shown as accepted or not accepted, with the reason, and a running total is always visible. Nothing goes missing quietly above some limit nobody was told about.

A link route beside the upload

For a set that lives in a plan room, a shared drive or an FTP, a link field sits next to the upload rather than behind a failure. For a large set, the link is the route we suggest.

Failure is reported, never faked

If the request does not reach its destination the sender sees that, with an email route, rather than a thank you message over nothing.

The questions are agreed with you

Project name, location, bid date and the scopes wanted are the starting point we propose. Which fields are required, and where a submission goes, is decided with you before launch, not left to a default.

A statement of what happens to the documents

The page says what the set is used for, who sees it and how to ask for it to be deleted. That wording is yours to approve, because it is a commitment you are making.

Performance and accessibility practice

These are the practices we apply on a build. We aim to make every build usable by keyboard and by screen reader, and the accessibility position on any build is stated to you honestly rather than claimed.

• A performance budget agreed before design starts rather than measured after the site ships, with the largest element on each landing page chosen to fit that budget.
• Images in compressed web formats with explicit width and height, lazy loaded below the fold, so the layout does not jump while it loads.
• Fonts self hosted, so no visitor data leaves for a third party font service.
• A skip link, keyboard operable navigation including any menu panel, and closed panels that keyboard and screen reader users cannot fall into.
• A visible focus indicator on every interactive element, and colour contrast checked against the design system values.
• Reduced motion respected wherever motion is used, and an accessible pause control on any video that plays by itself.
• Every form field labelled, every error message readable, and the upload status announced rather than shown by colour alone.

The launch checklist

Worked through in writing before the site goes live, and the completed list is part of the handover.

• Every form submitted with real files and a real link, and each submission confirmed at its destination.
• One H1 per page, a unique title and description per page, canonical tags, the sitemap and the robots file checked against the live domain.
• Structured data present where it is true, and no review markup unless real reviews exist.
• The site fetched from outside as a crawler and a link preview service would fetch it, not only loaded in a browser, so bot protection is not blocking indexing.
• Redirects in place from every old address that had traffic or links, so a rebuild does not throw away what the old site had.
• Phone, email and address correct on every page and in the structured data.
• Domain, hosting, repository and any analytics account confirmed as registered to you, with access handed over.

How this connects to the rest of the firm

One firm covers 11 service lines across construction and digital, and the web work draws on both halves.

Estimating and takeoff

The scopes we price for you, where we do, are the scopes the site is structured around. We measure across all 34 CSI divisions, so the trade language on your service pages is the language of your bid forms.

Bid and proposal support

The bid request page is built the way a set arrives for pricing: many files, mixed formats, a deadline. The same understanding of what a general contractor sends shapes what the form has to accept.

Shop drawings and plan review

Where you offer detailing or review as a capability, it gets a real page with the documents and units named, not a line in a list.

SEO

The structure is decided with search in mind. The SEO line audits what the build puts in place and plans the content that extends it.

Google Ads

The scope pages built here are the landing pages the Google Ads line sends traffic to, so a paid click lands on the service searched for rather than on a general page.

Branding and social media

If you have no mark, palette or type system, the branding line produces one that the design system is built from. The project pages give the social media line finished work to show instead of stock photographs.

Common questions