Events9 September 2026

How to run an architecture event people actually turn up to

By Vladislav Akhmetov · 9 min read

The fear with any industry event is the same one: a good venue, a decent speaker, and forty empty chairs. It happens constantly, and almost never because the idea was bad. It happens because filling a room is treated as the last task on the list instead of the first.

We run our own event series, Architecture After Hours, and we are increasingly asked to run other people's. This is what the work actually consists of, written for anyone deciding whether to do it themselves.

Decide what the evening is for, and pick one thing

An architecture event can do three jobs. It can put you in front of people who could commission you. It can establish you as the practice that convenes the industry. Or it can build relationships with the specific people you already want to know.

All three are legitimate. Trying to do all three at once produces an evening that does none of them, because each one implies a different guest list, a different format and a different room. The first question is not the venue. It is which of those three you are buying.

The venue decides more than you think

A venue is not a backdrop, it is half the reason people accept. An evening 43 floors above the City is an easier invitation than the same talks in a conference room, and the difference in acceptance rate is not marginal.

The other thing worth knowing is that the best venues are often the cheapest ones. A venue partner, a showroom or a corporate headquarters, will frequently host at no cost, because an evening puts their space in front of exactly the audience they want and they get a room full of the right people without running the event themselves. Both of our editions work this way: London sits in Bentley's UK headquarters on the 43rd floor of 8 Bishopsgate, Berlin in the Schüco showroom on Schlüterstraße. That single arrangement removes the largest line in the budget and usually improves the venue at the same time. It is worth asking before you start pricing hire fees.

Go and stand in the room

Photographs and a floor plan will not tell you what you need to know. Visit the venue in person, early, and walk it twice.

Walk it first as a guest. You arrive off the street after work: where do you go, who meets you, where does your coat go, where is the first drink, and where do you stand in the first ten minutes when you do not know anybody yet. That last one decides whether people settle in or leave early.

Then walk it as a speaker. Where exactly do you stand, what is behind you, can the back of the room see you, where does the laptop go, and how do you get to the front once the room is full.

Then check the unglamorous things, because these are what actually fail on the night:

  1. Power. Where the sockets are, how many, and whether they reach the places the speaker and the bar will actually stand.
  2. Sound and screen. What the room already has, what you have to bring, and whether the screen still reads at that hour with that daylight.
  3. Where the bar goes. It decides how the room distributes itself more than any other single object.
  4. The room with people in it. An empty hall sounds and feels nothing like the same hall with eighty people talking in it.
  5. The door. Where a queue forms, and who is standing there to greet people.

One practical constraint worth settling on that visit: in corporate buildings entry is controlled by the venue, not by you, so guest details are usually due a couple of working days ahead in the format their security expects. Ask what that format is while you are standing there, not the week of the event.

The point of all of it is simple. Picture the evening as if it has already happened, from the guest's eyes and from the speaker's, and fix what you find now, while fixing it is free.

Shape the evening in three acts

The format that works for us is deliberately simple:

  • Doors and welcome drinks. People arrive over half an hour, get a drink, see the view. Nobody is asked to sit down and concentrate the moment they walk in from work.
  • Talks, short and one idea each. Not a conference. Short talks with a single argument, no filler, ending while attention is still high.
  • Networking, with a real bar. This is not the afterparty, it is the point. The talks give people something to open a conversation with. The bar is what keeps them there long enough to have it.

The shape stays the same, the clock does not. An evening for people leaving a London office starts earlier than one built around students and practitioners in Berlin. Set the times around when your particular audience can realistically arrive, and keep the three acts as they are.

The mistake is to over-programme. An evening built for people who came from a full working day should ask less of them than a conference does, not more.

Speakers: what you are actually asking for

A strong lineup does two jobs at once. It makes the evening worth attending, and it makes every speaker's own network aware the evening exists.

For our London edition on 23 September we have senior voices from ZHA, Foster and Partners, KPF, Heatherwick Studio and David Chipperfield Architects, alongside a computational designer, Bentley's emerging technologies lead and the founder of an AI practice. That lineup is not only programming. Each of those names travels.

Practical points that matter more than the invitation wording: ask early, because senior people are booked out months ahead. Give them a defined slot and a single question rather than a topic, because it makes preparation easy and the talk better. And be honest about the size of the audience when you invite them. A senior speaker is not put off by a small room, they are put off by being misled: promise three hundred people, deliver eighty, and they will not come back. Say eighty and deliver eighty, and nobody minds at all.

Filling the room is a marketing problem

Here is the part most practices get wrong, and it is the part we came to this from.

Invitations do not fill rooms. Reach fills rooms, and then invitations convert it. An event announced to an existing list of contacts reaches the people you already know, which is precisely the audience an event is supposed to expand.

We know what that funnel looks like because we measure it on client accounts every month: reach, then profile visits, then link clicks, then the action. In what Instagram actually returns for an architecture firm we published the numbers, including the finding that a smaller and tighter audience converted attention roughly three times better than a large one. That applies directly here. For an event, a few thousand relevant people beats a large irrelevant reach, because the metric that matters is not views, it is seats.

In practice this means announcing early enough that the announcement can be repeated, giving people a real page with a date to land on, and treating the registration link as a funnel rather than a formality.

One evening, four weeks of content

The reason an event pays for itself is not the evening. It is that a single night produces material for a month: the talks, the room, the conversations, the photographs, the short clips, the follow-ups. Practices that shoot nothing get one night of value. Practices that plan the capture in advance get a month of it, plus an asset library they use long after.

Plan that before the day, not on it. Decide who is shooting, what they are shooting, and what each piece is for. It is the difference between an event as an expense and an event as a content engine.

What we are seeing in the market

Something has shifted in the last year. Architecture firms are no longer asking how to promote an event they are already planning. They are asking whether someone can run the whole thing.

That makes sense. The work above is not architecture, it is production, logistics, programming and audience building, and there is no reason a practice should build that capability in house for two evenings a year. We now do this both ways: our own series, and other people's events as a partner.

Our Berlin edition on 16 October is the clearest example of a co-hosted evening. It is run with Future of Architecture, the non-profit closing the gap between architecture school and how a building actually comes about, which we wrote about here, and it is hosted in the Schüco showroom. The job that evening is buying is the third one on the list above: putting students and practising architects on the same floor for ten-minute talks and questions straight from the room, then a bar and music. Two generations in one place, which is a different evening from the one we run in London, and deliberately so.

Common questions

What does it cost to run an architecture event? It depends almost entirely on venue and catering, which are the two lines that move, and the venue line often goes to zero if you find a host partner whose space benefits from the audience. The costs people forget are the ones that decide whether it works: photography and video, and the time spent filling the room.

How far in advance should you announce an architecture event? Earlier than feels necessary. Senior speakers need months, and the announcement needs to be repeated several times before it is seen. A page with a confirmed date is the anchor everything else points at.

How many people should an architecture evening have? Fewer than you would guess. Eighty people who belong in the room beats two hundred who half belong. Conversation quality falls off quickly with scale, and conversation is what people came for.

Should an architecture firm charge for its own event? It filters. A paid ticket, even a modest one, dramatically improves the ratio of people who register to people who arrive. Free events routinely lose a third of the room on the night.

Can you run an event for us? Yes. That is increasingly what we are asked for, from the programme and the production through to filling the room and the material afterwards.

The room is the deliverable

Everything else is arrangements. The evening succeeds if the right people are in the room and they stay long enough to talk, and almost every failure traces back to treating that as something that will sort itself out.

If you are planning something and would rather hand it to people from your own field who have run it before, tell us about it. And if you would rather see how we do it before deciding, come to London on 23 September or Berlin on 16 October.

About the author

Vladislav Akhmetov

Vladislav Akhmetov is the co-founder and CTO of Skala Social. An engineer by training, he built the analytics and reporting the agency runs on, turning Instagram data into the monthly funnel that tells architecture and engineering firms where their leads actually come from.