How to Turn One Architecture Project Into a Month of Marketing Content

Why architecture firms run out of things to post

Ask a principal why the firm does not post more and the answer is almost never that they have nothing to say. It is that they think a project earns one post, on the day the photographs arrive, and after that it is used up.

That is the whole problem. A project treated as an announcement produces one piece of content and a small spike of congratulations from other architects. The same project treated as a set of decisions produces a month of material and reaches people who might hire you.

The finished photograph is the least interesting thing about the job. Everything that led to it is where the content is.

What one project actually holds

Take any completed project and it contains at least five distinct stories before you have tried hard.

• The constraint. The site, the budget, the planning history, the thing that made this hard.
• The decision. The moment you chose one route over an obvious alternative, and why.
• The fear. What the client was worried about at the start, and what actually happened.
• The mistake. What you would do differently. This one outperforms everything else and almost nobody posts it.
• The result. Not the photograph, the outcome. Approval won, budget held, space gained, a business that now works better.

Cross those five with a few formats and the arithmetic gets generous quickly. Twelve pieces from one project is not a stretch, it is what is already there.

Write for clients, not for other architects

This is the correction that changes results fastest, and it is uncomfortable.

Most architecture content is written in the language architects use with each other. Massing, fenestration, programme, articulation. It circulates among peers because peers are who it speaks to, and then a firm concludes that content marketing does not bring in work. The reach was never the problem. The audience was.

A client cannot evaluate your plan. They can evaluate whether you explain a decision in a way that makes them feel capable rather than stupid. That is the entire mechanism. Posts that make a non-architect feel smart are the posts that produce enquiries.

The test before you publish

Read the first two lines and ask who nods. If the answer is an architect, rewrite it. If the answer is the person who would pay for the project, publish it.

Here is a post I drafted for LinkedIn: [paste the draft].

My actual audience is [describe the buyer: e.g. owners of ageing commercial buildings considering conversion, or developers doing their first residential scheme].

Rewrite it for that reader. Replace every professional term with the words they would use, or keep the term and translate it in the same sentence. Keep every specific detail and number. Cut anything that only impresses another architect.

Then tell me, in one line, which sentence in my original was doing the most to signal this was written for peers.

Mine the projects that are not finished

Waiting for professional photography is why most firms post nothing for months at a time. Live projects are better raw material anyway, because the outcome is still uncertain and uncertainty is interesting.

Get the client's agreement first, particularly on anything unannounced, then treat the messy middle as the content. A planning objection you are answering. A detail being mocked up on site. A decision you are still weighing between two options.

I run an architecture firm. Here is a project currently in progress: [2 to 3 sentences: type, stage, and what is genuinely uncertain or difficult about it right now].

Give me 5 content angles I can post before this project completes, without revealing anything a client would consider confidential.

For each: the hook as a first line, one sentence on what the post covers, and one line on what a potential client would take away from it.

Rank them by how likely they are to start a conversation with a potential client rather than another architect. Explain the ranking in one line each.

A cadence that survives a busy studio

The failure mode is not low frequency. It is the cliff. A firm posts daily for five weeks, a deadline lands, and nothing appears for four months. The algorithm forgets you and, worse, so do the people who were starting to recognise your name.

Two posts a week for a year beats daily posting that stops. To make that survivable, separate the two jobs that everyone accidentally merges.

• Extraction happens once a quarter. Sit down with three or four completed projects and pull every angle out of them in one session. This is the hard thinking, and it does not need to happen weekly.
• Publishing happens weekly and should be nearly mechanical. You are drawing down a bank, not creating from nothing on a Tuesday morning between site visits.

This is the same principle behind the 1:9 Content Flywheel we run with clients: one substantial piece of thinking becomes nine derivative pieces across formats and channels, so the expensive part happens once. The prompt below does the extraction session for you.

I run an architecture firm. Here are three completed projects:

1. [project, client type, the hard part, the outcome]
2. [project, client type, the hard part, the outcome]
3. [project, client type, the hard part, the outcome]

Build me a 6 week posting plan, 2 posts per week, 12 posts total.

Rules: no two consecutive posts from the same project. Mix these angles across the plan: the constraint, a decision explained plainly, a client fear answered, something I would do differently, a result, and one opinion the work supports.

For each post give me: week number, the project it draws on, the angle, the hook as a first line, and one sentence on the body.

Write for people who might hire an architect, not for architects.

What to do next

Open the folder of your last completed project. Write down the constraint, the decision you are proudest of, and the thing you would change. That is three posts, and you now have them without doing any marketing.

If proposals are the bottleneck rather than visibility, start with the six sections of a proposal that wins. If you want the wider framework for where AI fits in a practice, read the practical guide to ChatGPT for architecture firms.