What an engineering consultancy website needs
A consultancy sells judgement, and judgement cannot be photographed. An engineering consultancy website therefore has a harder job than most: it must let a client see how the firm thinks, who does the thinking, and what that has produced.
What is the client really buying?
Not drawings. They are buying the confidence that the design will be sound, approved by the authorities, and buildable within what was planned. So they read your site for signs of rigour: how precisely you describe your work, whether you state your exact role, whether the people are named. Loose wording on the site suggests loose wording in a specification.
How should the disciplines be presented?
In the order a project moves. Studies and feasibility, concept and detailed design, permits and approvals, tender documents, site supervision, project management. Under each, name the disciplines you cover in-house, such as architectural, structural, mechanical and electrical, and say which you bring in through partners. A client planning a project recognises their own stage and sees at once where you come in.
How should projects be shown?
With your role stated first. Design only, design and supervision, or review of the work of others. Then the type of building or facility, its scale in words, the location and the status. A sentence about the main technical question and how it was resolved says more than a gallery of photographs. Publish drawings and client names only with permission, since both usually belong to the client.
Who should appear on the site?
The engineers. In this field the client wants to know who will sign the drawings and who will stand on site. Show the partners and the heads of each discipline with their qualifications, their professional registration and their experience described honestly. A real photograph of each helps. A team page made of stock portraits does the opposite of what it intends.
What credentials matter?
The ones a client can verify. The licence of the office, its registration or accreditation with the engineering body in your country, its classification where one exists, and professional indemnity cover if you hold it. State the references and issuing bodies. Requirements differ between countries and between public and private clients, so list what applies where you practise and keep it current.
What is the contact path?
A request for proposal, not a chat. Offer a form that asks for the type of project, its location, the stage it has reached and the services wanted, and that accepts an attached brief. Say who reads it and when the sender can expect a reply. Keep recruitment on its own page, because graduate applications will otherwise crowd out client enquiries in the same inbox.
How I handle it
A consultancy site depends on precise content, so I ask for your project list and team details early and draw the pages around them in Figma. The build starts only once you have approved that design. After handover you hold the dashboard, and adding a project, a team member or a new registration is an edit your office makes on its own. Support remains available for 180 days from the day the site goes live. Tell me which disciplines your office covers and the kind of clients you want to reach.
New articles every day on our Facebook page: Learn with MK
Have a project in mind?
Tell me what you are building and I reply within 24 hours.
