What a contractor website needs before anyone transfers a deposit

Contracting sells something the buyer cannot see yet. They hand over a large sum in advance for something that will not exist for months. The fear is therefore not that the finished work will be ugly. It is that the deposit goes, the work stalls, and the price climbs past what was agreed.

A site that is only beautiful photographs does not address that at all, because photographs prove you can produce beautiful things. They do not prove you finish on time and do not abandon jobs. Those two are what the reader is hunting for evidence of.

What separates a portfolio from an album

An album says what you have done. A portfolio says what you did on a job like the one this reader is planning: how long it took, what budget band it sat in, what went wrong along the way and how it was handled. That last part builds the most trust and is the part almost nobody writes.

People leave it out fearing that admitting problems looks weak. In practice the opposite holds. Anyone who has built before knows construction never runs perfectly, so the contractor claiming a flawless record reads as less credible than the one who explains how problems were solved.

What the site needs

• Projects with size, duration and budget band attached — so a reader can find the one that resembles their job rather than admiring an unrelated one.
• Company details that can be checked — registration, licences, insurance. This is the fear being answered directly.
• The team, with names and faces — who will actually be on site, and who the point of contact is.
• Unit price ranges for the work you do most — with what is and is not included, and a clear statement that the real number requires a site visit.
• A site-visit request form — area, budget, and target date, so the first conversation starts from something concrete.
• How the process runs, stage by stage — survey, quotation, contract, build, handover, and what is paid when.
• The warranty and what happens afterwards — what is covered, for how long, and how to raise it.
• Progress photographs, not only finished ones — a half-built site with tidy scaffolding says more about how you work than the final photograph does.

A page structure that works

• Home — what you build, at what scale, and for whom
• Projects — an index, then a page each with size, duration and budget band
• Services — the types of work you take on
• Process — the stages, and the payment points
• Team and credentials — people, registration, licences, insurance
• Pricing guide — unit ranges, with inclusions and exclusions
• Request a site visit — the form, and what happens next

What to have ready before the build starts

• Six to ten completed projects with area, duration and budget band
• Photographs of each, ideally including progress shots
• Company registration, licences and insurance details
• Team names and roles, with photographs if they agree
• Unit price ranges you are willing to publish
• Your stages and payment schedule as you actually run them
• Warranty terms in writing

Should prices go on the site?

Contracting cannot be priced exactly without seeing the site, but publishing nothing fills the inbox with enquiries whose budgets are nowhere near yours. The workable middle is unit ranges for the work you do most, stated inclusions and exclusions, and a clear line that the real figure needs a visit.

That filters out the mismatches before anybody spends a morning driving, which saves both sides time and raises the proportion of visits that turn into work.

If you want the project pages and the estimate form built, the contractor website page sets out what each package covers.