The Unexpected Thing Automation Gave Us Back

We hired our first developer two weeks ago. The practical reasons were obvious: we needed someone who could turn the AI tools and processes we'd been cobbling together into proper, maintainable systems. Someone who understood what was technically possible and could build it efficiently. That's the version of the story that makes sense on paper, the one you'd put in a job description.

What actually happened in the first fortnight was something we didn't anticipate at all. And it's changed how we think about what automation is actually for.

The three-layer intersection that makes AI work for small producers

What became apparent almost immediately was that we'd created a productive overlap between three distinct types of knowledge. Asterley Bros has deep domain expertise: we know our liquid, our ingredients, our production processes, our brand inside out. We also have years of accumulated knowledge about our specific market, the vermouth and amaro niche, how customers buy, what bartenders care about, which retailers think about the category.

The developer brought a third layer: technical execution. Not just coding skills, but an understanding of how to leverage AI tools efficiently, how to build quickly, how to turn instincts and processes into templates and automations that actually work. That intersection of domain expertise, niche market knowledge, and technical capability is where interesting things start to happen. Each layer makes the other two more useful.

Automation as a cognitive tool, not just an efficiency one

Here's what caught us off guard. As processes started getting automated (things we'd been doing manually, reactively, constantly) we didn't just get more hours in the day. We got a different quality of time.

Running a small business means living in a state of perpetual reactive triage. Something needs ordering. A customer has a question. The website's got a bug. An invoice is overdue. You spend your days bouncing between problems, solving each one just well enough to move on to the next. It's productive in the sense that things get done, but it's corrosive to the kind of thinking that actually moves a business forward.

When the automations started handling some of that reactive load, something shifted. Not just the hours freed up, but the headspace. The ability to stop and actually think about where the business is going, rather than just keeping it running, was quite revelatory. That word might sound strong but it's honestly how it felt. Like recovering a capacity we'd forgotten we had.

Why strategic headspace matters more for small businesses

Larger companies have the luxury of dedicated strategists, planners, people whose entire job is to think about the future while others handle the present. Small businesses don't have that separation. The person thinking about next quarter's product launch is the same person chasing a late delivery and fixing the label printer. Strategy happens in whatever scraps of attention are left over after the operational noise subsides, which is usually not much.

Automation in that context isn't just an efficiency play. It's a cognitive one. The value isn't primarily in the hours saved (though those matter) but in the quality of attention those hours contain. Uninterrupted thinking time, where you can hold a complex problem in your head long enough to actually solve it properly, is genuinely rare in a small operation. Getting some of it back changes the kind of decisions you make.

We're early in this. Two weeks in, with a developer still getting up to speed and systems still being built. But the direction is already clear enough to be worth noting. The conversation about automation in small business tends to focus on cost savings and efficiency metrics. Those are real, and they matter. But the bigger unlock might be something much harder to quantify: the return of the headspace to think.

Frequently asked questions

How does automation help small businesses beyond saving time?
Automation returns cognitive capacity, not just hours. Small business owners spend most of their time in reactive task management. When automations handle that operational load, the recovered time contains a different quality of attention, allowing strategic thinking that reactive schedules prevent.

What is the three-layer intersection for AI in small businesses?
It is the overlap of domain expertise (deep product and production knowledge), niche market knowledge (customers, channels, competitors), and technical execution capability (building tools and automations). Each layer makes the other two more valuable.

Should small drinks producers hire a developer?
It depends on how far your AI and automation ambitions go. A developer turns instincts and manual processes into maintainable systems and templates. The unexpected benefit we found was not just efficiency but the return of strategic headspace that constant reactive problem-solving had consumed.

What kind of processes should small businesses automate first?
Start with the reactive, repetitive operational tasks that fragment your attention throughout the day: order processing, stock alerts, routine customer queries, report generation. The value is not just the time saved but the uninterrupted thinking time you recover.

Robert Berry is co-founder of Asterley Bros, a London-based premium aperitivo company, and Absolution Labs, an AI automation consultancy for drinks businesses.