When I tell people that The Clementine hosts a maximum of fifty events each season, the response is usually some version of: why would you limit yourselves? It's a fair question. The business case for hosting more events is obvious. More bookings, more revenue, more utilisation of a space that took significant investment to build and maintain. The logic of volume is straightforward.
The logic of restraint is less immediately obvious but, I think, more interesting.
The decision to cap at fifty isn't primarily a marketing positioning — a number chosen to sound exclusive. It's a structural decision with practical consequences that run through almost everything else about how The Clementine operates. Understanding those consequences is, I think, genuinely useful for anyone considering the venue — because it changes what they can expect.
The most direct consequence is availability. A venue that hosts events every day of its season has, by definition, no flexibility in its schedule. There is no day before for a setup. There is no morning after for a careful derig. There is no room for the production build that needs two days rather than one. When every slot is filled, the answer to “can we have the day before?” is always no — not because the venue is unwilling, but because that slot already belongs to someone else's event. The commercial pressure of volume makes generosity structurally impossible.
Fifty events leaves room. Room for the florist who needs a full day to build something that will be remembered. Room for the lighting designer who wants to return at dusk to see the space in the conditions it will actually be experienced under. Room for the production team that's building something ambitious and needs to do it properly rather than quickly. This is not a bonus we offer — it is a consequence of how we've chosen to operate. The events we're most proud of are disproportionately the ones where the creative teams had time. I don't think that's a coincidence.
The second consequence is attention. When a venue hosts hundreds of events each year, the knowledge and focus of its team is necessarily distributed across an enormous number of clients, dates, and concurrent planning processes. Fifty events means that every booking is significant — not just commercially, but in terms of the knowledge and care invested in it. Our team knows the events on the calendar in a way that becomes impossible at scale.
The third consequence is what I'd call earned credibility with suppliers. When the same caterers, florists, and production companies return to a venue season after season — because they're on an approved list, because the relationship is valued, because the venue treats their team with the same consideration it treats its clients — the quality of what they deliver in that space improves over time. They know the quirks of the kitchen. They know how the light changes at 7pm in August. They know what the space rewards and what it resists. That institutional knowledge is not available at a venue where the supplier list turns over regularly and the events team is managing too many relationships to maintain any of them deeply.
Fifty is a constraint. It is also, I think, the reason that the events hosted here tend to be the kind that people talk about afterwards. Not because we have done anything magical — but because we have created the conditions in which the people doing the work can do it well.
That is, ultimately, what the number means.
