Digital products ·
Build a construction firm's website from the project to the client's decision
A request for a construction company website can quickly become a project gallery and a “Contact us” form. Yet a client chooses a contractor for a particular job, budget and level of risk. Before development, follow one decision from a comparable project to a clear next conversation. That journey produces a stronger structure than a generic list of pages.
Begin with one type of enquiry
Choose a specific service, such as fitting out a commercial space or renovating an existing building. Who contacts the firm: an owner, operator, architect or procurement manager? What do they already know about location, area, deadline and an active business on site? Which decisions must they make before meeting a contractor? Also note what the firm cannot know before inspecting the property.
Then select one completed project relevant to that request. Use a real project for which facts and material may be shown, not an invented ideal case. Gather the original brief, work boundaries, sequence of decisions, team contribution, verifiable images and outcome without unsupported claims. Where a contract limits disclosure, describe the type of work more generally rather than exposing someone else's information.
A project record should explain comparability
A polished exterior shot is not enough. Visitors need to see whether the project resembles their task. A useful record names the building type, the firm's actual role, starting constraints and the decision made. Captions explain the stage rather than saying “our work” under every image. Where permitted, include a date, location and scope; where that is not possible, do not hide missing facts behind superlatives.
Group projects by a distinction customers use: service, building type, scale or region, when it really helps comparison. Filters added only for appearance create maintenance work; every new project must be classified and checked. A first release may need only a few substantial records with a clear route between a service and a relevant project.
Explain the boundary of price and responsibility
Construction rarely fits a universal tariff. Rather than promising an exact price without the inputs, explain how an offer is formed and what can be estimated before a survey. Name standard jobs with fixed conditions separately if the firm really offers them. If an inspection is needed, say what the client receives afterwards: an estimate, scope, schedule or list of assumptions.
Define the firm's responsibilities across design, procurement, construction, supervision, subcontractors, documents and aftercare, including only work it actually performs. The client cares less about a long list of services than about avoiding an unexpected gap between stages.
An enquiry form should carry the job forward
For a first contact, building type, location, approximate scale, desired timing and a contact route may be enough. Allowing plans or photos can help, but should not block someone who is still comparing contractors. Ask the sales team which facts enable a useful next response; collect the rest in conversation.
After submission, confirm receipt, say who will reply and when, and name the next step. If the enquiry reaches a CRM, inspect the record: can the manager see the chosen service and the project the visitor viewed? Without that context, the client has to retell the journey. Complex approvals also need an owner and a handoff rule between teams.
Test one complete route
Ask someone outside the firm to find a relevant service, compare two projects and explain what they would need for an initial conversation. Have a manager follow the same journey from the incoming enquiry. Do not guide either person through the screen. Record where a visitor infers the wrong price, timetable or scope; those misunderstandings matter more than preferences about colour.
For a first release, test one route: service → comparable project → conditions → enquiry. Other services can grow from that pattern without losing its logic. I can help map the journey and design a [company website](/en/dialogue) around a client's real decisions. The [general guide to website structure](/en/apocrypha/website-structure) covers the broader principles; this piece focuses on construction projects and estimate enquiries.
Start with the website's purpose
If you are planning a website or rethinking one, we can begin with its role in your business, its structure and the visitor's path to an enquiry.