Cornerstone
What a proper project write-up does that a brochure can't

What a proper project write-up does that a brochure can't

A PDF brochure sits unread in an inbox. A well-written project story ranks, gets shared and does the selling for you.

TopicContent
Read5 min
ByCornerstone Group

Ask most built environment firms for their marketing and they will hand you a PDF brochure. Beautifully designed, expensive to produce, and almost completely invisible. It sits in an inbox unopened, or on a website behind a download form, doing none of the things marketing is supposed to do. A written project story does the opposite, and costs a fraction to make.

A finished project has one story. A brochure buries it; a write-up lets it rank, share and sell.
A finished project has one story. A brochure buries it; a write-up lets it rank, share and sell.

The brochure problem

A brochure has three fatal flaws as a marketing tool. Google cannot read it, so it never brings you a single visitor. It is static, so it says the same thing to everyone and adapts to no one. And it is a dead end, produced once, printed, and slowly going out of date on a shelf.

It looks like marketing. It feels like marketing. It just does not do the job of marketing, which is to be found, to build trust, and to bring in work.

What a written project story does instead

Take the same project the brochure would have featured, write it up properly as a web page, and it starts working in ways a PDF never can.

It gets found

A page about a real project, with the right words in it, ranks for the searches your future clients are making. The brochure ranks for nothing.

It gets shared

A link to a story travels. Colleagues send it, publications reference it, social carries it. A PDF attachment goes nowhere.

It builds authority

Publish enough real project stories and you become the firm that clearly knows its field, to both Google and the people reading.

It compounds

Every write-up you publish adds to a library that keeps working for years, pulling in traffic and trust long after it is written.

Anatomy of a write-up that ranks

A project page earns its search traffic through structure, not luck. The pattern is consistent.

A title that matches a search

Project type plus place: office fit-out in Farringdon, terrazzo flooring for a Chelsea restaurant. That is what future clients type.

Prose Google can read

The problem, the approach, the result, written as sentences. Not captions, not a spec table alone, actual readable paragraphs.

Specifics that earn belief

Sizes, programmes, materials, named products. Detail reads as truth to both the reader and the algorithm.

Images that carry their weight

Your own photography with descriptive alt text, compressed properly so the page stays fast.

A link to the service it proves

Every write-up points at the service page it supports, passing its authority up the chain.

Where a write-up earns its keep

A brochure has one job and one moment: it is handed over or attached, and then it is finished. A written project page keeps working in several places at once, which is the real argument for the format and the part most firms never see, because they only ever measure the enquiry it did not immediately produce.

In search, for years

A page about a specific type of project, in a specific sector, with the constraints named, is exactly what somebody types when they have that problem. A PDF is barely readable to a search engine and almost never ranks.

In the pitch, as evidence

Sending a link to a written project beats attaching a brochure, because the prospect can see it is public, dated and standing behind your name.

In an AI answer

When somebody asks a model which firms have handled a particular kind of scheme, it draws on published, structured text. Content locked inside a PDF or a portfolio image is invisible to that entirely.

In recruitment

The people you want to hire read project write-ups to work out whether the work is interesting. Almost nobody reads a company brochure for that.

The cost difference is worth stating plainly too. A designed brochure is a fixed cost that starts ageing the day it is printed. A written project page costs an afternoon of somebody's time, gets corrected whenever something changes, and is still working in five years.

None of which is an argument against ever producing a document. It is an argument for writing the project up first, and letting the document, if you still want one, be assembled from it.

The shift worth making

This is not about writing more for the sake of it. It is about taking the work you are already proud of and telling it in a format that can actually be found and shared, instead of one that can only be handed over. The projects are the same. The difference is whether the story lives somewhere it can work, or somewhere it cannot.

Firms that make that shift stop producing marketing that sits still and start building marketing that compounds. Over a few years, the gap between them and the brochure-and-hope competition becomes very hard to close.

The practical test is what happens when somebody asks for an example of your work. If the answer is that you will send something over, you have a brochure problem. If the answer is a link you can send from your phone without leaving the meeting, the write-up is doing its job. That difference sounds small and it is the entire argument: one requires you to be available, the other works whether you are or not.

Sitting on a folder of finished projects?

That folder is unpublished marketing. We will turn the best of it into pages that rank, share and sell while you build the next one.

Publish the back catalogue

Keep reading