There's a familiar pattern on professional services websites we have noticed. When some firms want to communicate everything they can do, they make a list.

Sustainability. Advisory. Project management.

Then another list.

Residential. Commercial. Healthcare. Education. Infrastructure.

Then perhaps another one for capabilities.

Design. Consultation. Delivery. Strategy.

The intention is understandable. A prospective client should be able to see the full breadth of the practice. But a list has a particular limitation. It tells you what exists. It doesn't necessarily tell you why it matters.

"Facade engineering" is a capability. It doesn't tell you when that capability becomes particularly valuable, what kinds of problems the firm is good at solving, or what distinguishes its approach from another consultancy offering the same service.

A project can do all of that in a few paragraphs. Show the constraint. Explain the decision. Talk about the trade-off. Explain what changed as a result. Suddenly the reader isn't being told that the firm knows what it's doing. They're watching it happen.

This distinction becomes particularly important in industries where expertise is difficult for outsiders to evaluate. For instance, an architect can look at another architect's work and understand things a client might never notice. An engineer can recognise the quality of a technical solution without needing it explained in detail.

A prospective client often can't. They're looking for something that makes expertise visible. That's why the best project stories tend to contain more than finished photographs and a list of services. They reveal something about the thinking behind the work. What was difficult? What had to be weighed, and where did judgement actually matter?

These details do something a service list can't. They give expertise a shape.

Lists are very good at communicating breadth. They reassure a reader that a firm has range and can handle different types of work. But showing tends to communicate depth. One well-told project can reveal more about a firm's capability than ten service categories because it gives the reader something concrete to attach the claim to.

This doesn't mean firms should hide their services or replace every page with a case study. It simply raises a question about what each piece of information is doing. Is it telling someone what the firm offers? Or is it helping them understand what the firm is actually good at?

A list tells people what you can do, whilst a good example lets them see how you think. And in a market where almost every firm can produce the same list, the second tends to be much harder to copy.