James Watt’s Response

James Watt’s response to the open letter, republished here from the Equity for Punks forum.

Hey Everyone,

Just to let you know. We saw the Punkspurpose tweet and we will post a full response soon. On our growth journey we have not always got things right and we are happy to admit when that is the case.

However, we have always had a high performance culture, we have always moved at speed and we have always focussed on growth.

It is fair to say that this type of fast paced and intense environment is definitely not for everyone, but many of our fantastic long term team members have thrived in our culture. Our culture is built on rewarding and developing great people and focussing on growing our business .

We will a share a full update soon.


And his subsequent apology, also from the Equity for Punks forum.

Hey Everyone,

I wanted to give you all an update in light of the recent Punks With Purpose open letter.

At BrewDog we are focussed on building the best business we can, which is why the open letter we saw on Twitter was so upsetting, but so important. Our focus now is not on contradicting or contesting the details of that letter, but to listen, learn and act.

As a fast-growing business, we have always tried to do the best by our team — we do have many thousands of employees with positive stories to tell as a result. But the tweet we saw last night proves that on many occasions we haven’t got it right. We are committed to doing better, not just as a reaction to this, but always; and we are going to reach out to our entire team past and present to learn more. But most of all, right now, we are sorry.

It’s hard to hear those comments, but it must have been harder to say them. We appreciate that and we will endeavour to honour that effort and courage with the real change it deserves. We aren’t going to make excuses, we’re going to take action. From our commitment to sustainability to our passion for beer, BrewDog has always been defined by taking responsibility and continually improving. This is no exception.