Why Losing One Pub Cost Me Three
If you have read the story of The Sun Inn, you know how it ended.
A lease contracted out of the Landlord and Tenant Act 1954. A building sold to a developer. A rent review that would have taken annual costs from £18,000 to £70,000 in a reduced space after a trading closure of unknown duration. I walked away. Nearly seven years of work. A business generating £800,000 in annual revenue. Gone, not because the business failed, but because of a clause in a document I had signed at twenty-six without fully understanding what I was agreeing to.
What I have never written about, until now, is what happened next.
Because the lease clause didn't just close The Sun Inn. It closed everything.
What the Sun Inn Article Doesn't Tell You
The Sun Inn article is the story of one pub. The honest version of that is that by the time I lost it, The Sun Inn was no longer just one pub. It was the financial engine of a small group.
At peak, I was running three sites simultaneously.
The Sun Inn in Bethnal Green. The Dew Drop Inn in Berkshire was a destination pub in a forest between Henley and Marlow, with a menu built around local farms, foraged ingredients, and fresh game from the local shoot that used the pub as a base each week. The Half Moon in Cuxham, Oxfordshire, was fine dining, sitting somewhere between English and French, thankfully without sinking in the channel.
There had been a fourth, The Waverley Arms in Nunhead, South London, a community pub I took on a peppercorn rent. I walked away from that one cleanly when the lease terms on offer weren't what I needed. There was no loss, financial or otherwise. Knowing when not to commit is a discipline. I mention it here because it becomes relevant to how I think about what followed.
The weekly circuit, at peak, looked like this: The Sun Inn on Friday night. The Half Moon for early Saturday dinner – they ate early in Cuxham, a rhythm I had learned to work with rather than resist. Back to London for the later half of Saturday night. The Dew Drop for Sunday lunch – where I would always be in the kitchen. I had management in each site, which is how the operation was possible at all. But I was present for the key shifts. That was the quality control mechanism: not constant presence, but deliberate, well-timed presence at the moments that mattered most in each venue.
It worked. The group worked. And it worked, I understand now with a clarity that I lacked at the time, because of what The Sun Inn was doing commercially underneath everything else.
What a Cash Cow Actually Does
The Sun Inn was generating the best part of a million pounds in annual turnover. At that volume, it earned exceptional supplier terms – the kind of relationships and pricing that only become available when you are consistently moving significant stock. Those terms didn't just apply to The Sun Inn. They applied across the group. The buying power of one high-volume site was subsidising the economics of the other two.
The Half Moon operated on fine dining margins. Fine dining is a particular kind of commercial discipline: the labour costs are high, the wastage is significant, the covers are limited, and the margin per cover, while better than a pub on a good night, does not generate the kind of turnover that a well-run volume operation does. Fine dining works as part of a portfolio when the other parts of the portfolio generate the cash flow and buying leverage that keep the whole thing viable. It is the last thing that works when the portfolio loses its engine.
The Dew Drop operated on a different model. It was a destination pub with a strong food offer, good trading on weekends, and a loyal local base. But it too was operating within a balance sheet that had been built for a million-pound business. The credit terms, the stock levels, the staffing model: all of it was calibrated to the turnover of the group, not to what any one site could sustain alone.
I knew all of this in the way that you know things when they are working and you are busy. What I did not know – what I had never been forced to think about clearly – was how quickly the whole structure could reverse once one component failed.
The Domino
When the Sun Inn's lease expired at the end of 2013, the developer's offer made trading impossible. I walked away.
The immediate financial consequence was straightforward and brutal: I had lost the best part of a million pounds in annual turnover. Not profit, but turnover. The cash flow that serviced costs, earned supplier terms, and funded the balance sheet for the group stopped.
I gave notice on The Half Moon's lease almost immediately. There was no version of the maths in which fine dining without the Sun Inn's engine made sense. The margin is too tight at that level, the costs too fixed, and the volume too limited to absorb a shock of that scale. It was not a difficult decision in the sense of being emotionally easy – I had built something good there, the team was strong, and the Half Moon had its own identity that I was proud of. But it was a clear decision, and clarity in those moments is a mercy.
The Dew Drop I tried to hold. The Berkshire pub had its own strengths – the destination trade, the shoot, the Boxing Day crowds, and the identity built around the landscape – and I believed, for a period, that it could stand on its own. The numbers told a different story. The balance sheet that had made it viable was built around a group with significantly more revenue than it now had. Suppliers who had extended generous terms to a business doing a million a year were now extending those terms to a business doing a fraction of that, and when they realised the Sun Inn had gone, my credit terms went too. The model didn't hold.
Within a relatively short period of losing The Sun Inn, I had lost everything.
The Lesson I Should Have Known Earlier
I want to be precise here, because the lesson is easy to misstate.
The easy version is: know your leases. Understand the Landlord and Tenant Act 1954. Get independent legal advice before you sign anything. All of that is true, and I have said it in every context where it's relevant since 2013.
But that is the lesson of the Sun Inn article. This article is about something different.
The lesson here is: understand which part of your business is carrying the others, because that dependency is the most significant risk in your operation, and it is almost invisible when everything is working.
Most multi-site operators consider their group to be a collection of individual businesses. Each site has its own P&L, its own management team, and its own trading identity. That framing is useful for operations, but it is dangerously incomplete for strategy. Because what you actually have is a system, and systems have load-bearing elements. Parts of the structure that are doing more than their share of the work. Parts that, if they fail, don't just take themselves down.
In my case, the Sun Inn was that element. It was the turnover that generated the supplier leverage. It was the cash flow that funded the balance sheet. It was the trading volume that made the fine dining margins viable and the destination pub financially sustainable. When it went, the whole architecture went with it, not because the other sites were poorly run but because they had been built within a structure that depended on the Sun Inn's performance.
I did not know this clearly enough at the time to have done anything differently about the lease. But if I had known it clearly enough, I would have done several things differently about the structure of the group. I would have stress-tested the model against the loss of the highest-performing site. I would have ensured that each site could, in extremis, sustain itself independently. I would have built less interdependency into the supplier relationships. And I would have held more cash against the scenario that, as it turned out, was not as unlikely as I had assumed.
None of that would have saved The Sun Inn. The lease was the lease. But it might have saved the Dew Drop.
What This Means If You Are Thinking About Expanding
I work with operators who are at various stages of building a group, and there is one question I ask early in every expansion conversation that often produces a long pause.
Which site, if it failed tomorrow, would take the others with it?
Most operators haven't considered it in those terms. They've thought about the new site, the opportunity, the location, the concept, and the numbers at realistic trading volumes. What they haven't thought about is the structural dependency that expansion creates, and what it would mean if the best-performing site had a bad year, lost a key member of the team, faced a rent review, or, in the scenario I know best, was taken away from them by circumstances they didn't anticipate and couldn't control.
The question is not designed to discourage expansion. It is designed to make expansion honest.
If you can answer it clearly – if you know which site is load-bearing – and understand what it would mean if that site failed, and have either reduced that dependency or made peace with the risk, then you are making an informed decision. That is the only kind of expansion worth pursuing.
If the question produces a long pause, that pause is telling you something. It is telling you that there is a risk in your operation that you have not yet mapped. And unmapped risks have a way of becoming expensive ones.
The Part Nobody Tells You
Hospitality expansion is sold as ambition-realised. The second site. The group. The brand that means something beyond one address. I have seen operators build genuinely extraordinary multi-site businesses, and I know what the right foundations look like, and so it can be all of those things.
But it is also the fastest way to multiply every structural problem you haven't fixed. An owner-dependent operation becomes two owner-dependent operations. Thin margins become thin margins across a larger cost base. And a financial architecture built around your strongest site's performance becomes a liability the moment that site underperforms.
I lost three pubs because of a clause in a lease. But I would have lost fewer of them, perhaps only one, if I had built the group differently. If I had stress-tested the model against the failure of its most important part, if I had held more in reserve, or if I had ensured that each site could, at a minimum, service its own costs without the group's overall performance carrying it.
That is the version of the expansion story I tell now. Not the circuit (Friday Bethnal Green, Saturday Oxfordshire, then back to London, Sunday Berkshire, back to the office in London on Monday), although that part is true and I am still proud of it. But the structure underneath the circuit. The architecture that either holds when something goes wrong or doesn't.
Build the architecture first.
Benjamin Sawyer is the Founder of Atelier Sawyer, a boutique hospitality consultancy operating between London and Málaga. With over thirty years of hands-on experience across six venues in the UK and Spain, he works with independent restaurants, bars, and cafés through subscription-based consulting and bespoke project work.
If you're thinking about expansion and want an honest conversation about whether the foundations are ready for it, start here: Book a free consultation or reach us at enquiries@ateliersawyer.com
→ Read the Sun Inn story first: What a Turnaround Actually Looks Like
→ Read about expansion support: The Grow Package