Why this site

I am not a developer. I have never written production software for a living. My background is in building companies, advising startups, and operating across business functions — sales, strategy, partnerships, operations, communications, the full stack of running something.

For the last few years, my relationship with AI tools was the same as most people’s: I used them to draft, summarise, and answer questions. Useful. Occasionally very useful. But I was still the one doing things.

Then something shifted.

A few months ago, I started using Claude Code not as a writing assistant but as an execution engine. The distinction sounds subtle. It isn’t.

A morning digest arrives on Telegram at 7 AM — today’s meetings, upcoming calls, what’s on my plate, anything I need to know before I start. Claude does it, every day, without being asked.

I started writing about this because nobody else seemed to be.

Most Claude Code content online is written by developers for developers. Tutorials on generating code. Tips on writing better prompts. Walkthroughs of coding tasks. All useful if you’re building software.

I am not building software. I am running a business. And the question I kept asking — how do I use this to get operational work off my plate — had almost no good answers anywhere. So I started documenting what I was building and what I was learning.

This site is for business operators. Founders, entrepreneurs, professionals — people who are drowning in execution work and are beginning to wonder if there is a better way.

Not people who want to learn to code. People who want things done.

The articles here fall into two types. Some are observations — short pieces on the philosophy of working with AI, on what changes when your tools can act instead of just advise. Others are practical — the specific automations I have built, how they work, what it took to get there.

Start anywhere.