The 400-year-old brewery that beat every productivity tool ever invented
Mar 05, 2026 7:03 pm
A client of mine spent $4,200 a month on AI tools last year.
Full stack. ChatGPT Teams, a custom GPT his developer built for $8,000, automations wired into everything. His team of twelve had access to all of it.
He was still the only person who could finalize a client proposal.
When I asked him to show me how proposals got built, he opened his laptop and started clicking. I stopped him and asked: Can you write down every step you just did?
He stared at me like I had asked him to describe color to someone who had never seen it.
That was the problem. Not the tools. Not the budget. Not the team.
He had never written the recipe.
Here is something I have been thinking about all week: Gekkeikan Sake has been running since 1637. The founder has been dead for centuries. The brewery is still producing. No AI. No growth stack. No 47-tab operations dashboard.
Just a process so well-documented that the business does not need the person who built it anymore.
Meanwhile, most of the founders I talk to are doing the opposite. They are automating before they have documented. Buying tools before they have written a single step down. The result? Faster chaos. More expensive chaos. But the bottleneck is exactly where it has always been.
Here is the order that actually works. I call it the Brewery Method:
1. Write the Recipe first. Pick the task only you can do right now. Do it once slowly and write down every single step including every "I just know this part." If you cannot write it, you do not fully understand it yet.
2. Automate the Repetition second. Once the recipe exists, look for the steps that require zero judgment. Just consistent execution. Those get automated. Not the creative decisions. Not the judgment calls. The repetition.
3. Outsource the Judgment third. For whatever is left, ask: What criteria should drive this decision? Write the criteria. Now someone else can make the call.
My client and I spent 90 minutes documenting his proposal process. Every step, every decision tree, every "I just know." Three weeks later, his ops manager was building proposals without him.
He did not need more AI. He needed to externalize what was living only in his head.
If you are nodding right now, you probably have the same thing: a ton of knowledge locked inside you that your business cannot access without you in the room.
That is the actual problem. And it is fixable.
If you want to work through your specific version of this with me, start at talktoari.com. I do Carbon Voice conversations that are 15-30 minutes and surprisingly effective at pinpointing exactly where your recipe is missing.
To doing less,
Ari
P.S. The first recipe you write does not need to be perfect. It just needs to exist. Once it is on paper, everything else gets easier to see.