Free playbook, 7 chapters
The AI-first company playbook
How to run your company on AI systems that already know how you work. Seven short chapters, one exercise each, and a 30-day plan at the end.
Read it all here for free. No email needed.

What is inside
- 1Why AI-first is a company decisionA chat tool in every browser tab is not an AI-first company. Here is the difference, and the one test that tells you which side you are on.9 min read, 1 exercise
- 2Map where your hours leakBefore you build anything, list the recurring work that eats the week. Score it. Pick three.10 min read, 1 exercise
- 3Build the company brainOne shared place that holds how your company works, so every AI system starts with your context instead of a blank page.12 min read, 1 exercise
- 4Ship your first three systemsA system is a task, a rule for a good result, and a person who reviews. Build the three you picked, one at a time.11 min read, 1 exercise
- 5Run it with an engineer on your teamSystems break on real data. Someone has to watch, fix and extend them. What that person does and how to get one.9 min read, 1 exercise
- 6Measure what changedA set of 20 real cases, a before and after, and one number per system. How to know it works and how to prove it.9 min read, 1 exercise
- 7The 30-day planFour weeks, one deliverable each. Map, brain, first system, measure and hand over.10 min read, 1 exercise
Built from shipped work
Every example comes from a client project or from our own Claude Code Challenge. The measurement method in chapter 6 follows our forward-deployed engineer roadmap.
Want a second pair of eyes on your hour-leak sheet? Talk to an engineer. 30 minutes, and you keep the notes either way.
Questions
- What is an AI-first company?
- An AI-first company writes down how it works in one shared place, the company brain, and runs AI systems that read from it and do the first pass of recurring work. A person reviews the result.
- How long does the playbook take to apply?
- Setting up the company brain takes hours. Getting the team running on it takes the 30-day plan in chapter 7.
- Do I need an engineer to use the playbook?
- No for chapters 1 to 3. You can map your hours and write the first brain files yourself. Chapter 5 covers when an engineer on your team pays off and how to brief one.
- Is the playbook free?
- Yes. Read every chapter on this site at no cost. The PDF version needs your email.
- Where do the examples come from?
- From AY Automate client work and our own Claude Code Challenge. Every number in the book comes from a shipped project.