Consultancy website for infrastructure projects: how to explain complex services before the first call

Consultancies that sell complex work rarely lose a client to a competitor. They lose them to confusion. A municipality or a private developer lands on the site, cannot tell in a minute what the company would actually do for them, and moves on to the firm that explained itself. The fix is not more content. It is a site structured around the reader’s decision instead of the consultancy’s expertise.

Here is how to do that for services that are genuinely hard to explain, using an infrastructure consultancy as the worked example.

The problem with expert websites

Experts write for other experts. It is a habit, not a fault, and it produces websites that describe methods, programmes and standards in language only a peer follows. The person who decides to hire a consultancy is usually not that peer. They are a mayor’s office, a procurement lead, an investor. They want to know three things: what will you do, what will it cost me in time and attention, and can I trust you with public money.

Readers scan. On a page built around a methodology, the scan finds nothing to hold. On a page built around a problem and an outcome, it finds the answer in seconds and keeps reading for proof.

Structure the site around decisions, not disciplines

The pattern that works for complex services has four layers.

1. A homepage that names the client and the outcome

Not “integrated consulting services for strategic investment projects”. Something closer to “we help municipalities and developers plan, fund and deliver infrastructure, from the funding application to the last inspection”. Name who it is for and what changes for them.

2. One page per service, written for the signer

Each service gets a page with the same skeleton: the situation the client is in, what the consultancy does about it, what the client has to provide, what they get at the end, and how long it takes. Technical depth lives below the fold or on a linked page for the engineer who needs it.

3. Proof that a non-specialist can read

Projects with a place, a scale and a result. “Street lighting for a town of 40,000, delivered under a public programme, 30% lower energy cost” beats a list of certifications. Certifications go in the footer, where the procurement officer will look for them.

4. A short path to a conversation

Complex services are sold in conversations. The site’s job is to make the first one shorter and better informed. A clear contact route, a simple form that asks about the project, and a promise on response time.

What it costs and how long it takes

This is a Launch project. The effort goes into the writing and structure far more than into visuals, so the number of service lines drives the range.

Scope	Typical range	Timeline
Brand refresh, homepage, up to 4 service pages, project showcase	€8k to €10k (about £7k to £9k, $9k to $11k)	2 to 3 weeks
Up to 8 service pages, downloadable project sheets, team page	€10k to €15k (about £9k to £13k, $11k to $16k)	3 to 5 weeks
Above plus a second language and a tender document library	€15k to €20k (about £13k to £17k, $16k to $22k)	5 to 6 weeks

Case study: Oxidelta

Oxidelta provides consulting for the development, implementation and supervision of publicly funded infrastructure projects, alongside smart-city products: intelligent street lighting, vehicle weighing systems and smart urban furniture. A diverse offering, technical by nature, and almost impossible to grasp from the old site in one visit.

We rebuilt the identity and the corporate website around the client’s decision rather than the consultancy’s disciplines. Each service line got a page a municipal officer can act on, with the technical detail one level deeper for the engineers who evaluate it.

• +125% lead generation: more qualified enquiries from municipalities and private developers
• -58% client education time: prospects arrive at the first call already understanding the offer, so the call is about their project
• +156% service discovery: visitors explore beyond the service they came for

“Our services are hard to explain in a meeting, let alone on a website. Now a municipality can understand what we do before the first call, and those calls are shorter and better. It’s done its job quietly ever since.”

Mihai D, CEO @ Oxidelta

A test you can run on your own site today

Send your homepage to someone outside the industry and ask them to tell you, in one sentence, what your company would do for a town. If they cannot, the site is written for your peers. That is the whole diagnosis, and it is fixable in a few weeks.

Explaining complex work is our job too

If your consultancy sells services that take a meeting to explain, send us the site and the two services you sell most. We will tell you honestly whether the problem is the structure, the writing or something else, and what it would take to fix.