Fill it in while it's fresh
Complete what you can within the week of the workshop. Waiting a month means guessing at your own week instead of remembering it.
Map AI to your real work. Three checkpoints, twelve weeks, no fluff. The workshop guide we run with founders and operators, now an interactive planner you fill in on this page.
Last updated: 17 August 2026
A licence gets bought, a few people try it, and three months later nobody can say what changed. Not because the tool was wrong — because nothing was ever pointed at a specific task, on a specific date, with a specific person accountable for it.
This plan starts with your week instead. You pick one task that genuinely costs you time, you run it for thirty days, and then you make an honest call about whether it earned a permanent spot. Twelve weeks later you either have something that is now standard practice, or you know exactly why it isn't — which is also useful.
Complete what you can within the week of the workshop. Waiting a month means guessing at your own week instead of remembering it.
Each horizon builds on the one before it, so work through Day 30 before you jump to Day 90. Day 90 is a decision you earn, not a forecast.
Every prompt asks for something specific. If your answer is vague, the plan won't hold up in twelve weeks — vague plans quietly expire.
Before you touch a tool, get specific about what's actually eating your time. List five recurring tasks from your week, however small. Be honest about how often you do them and how much of the work follows a pattern.
Then circle the task with the highest time cost and the highest repetition. That's your Day 1 pilot. Not the most exciting task, not the one that would impress people — the one that costs you the most and changes the least.
| Task / activity | How often | Time cost / week | How repetitive? |
|---|---|---|---|
| Weekly client status updates | Weekly | 3 hrs | High |
| Proposal first drafts | Fortnightly | 2 hrs | Med |
An example, not a template answer. Highest time cost × highest repetition is your Day 1 pilot.
Rate repetition as High (almost identical every time), Med (same shape, different details) or Low (varies a lot).
Each horizon has one job and five questions. Work them in order — Day 90 is a decision you earn from the first sixty days, not a forecast you write on day one.
Goal. Get comfortable with how AI actually works for your role, run one pilot on a real task, and produce one result you can show someone.
If you lead a team: pick a task from someone else's role too, not just your own. You want proof it works beyond you before you ask the team to trust it.
What this horizon asks you
Goal. Turn the pilot into a habit. Either it earns a permanent spot in how you work, or you retire it and move to the next task on your list.
If you're mapping your own role: this is where you decide what stays and what goes back to being manual. Don't keep something running just because you built it.
What this horizon asks you
Goal. Decide what's now standard practice, put a number on what it actually got you back, and set next quarter's priority.
If you lead a team: this is the point to formalise, document, and hand off. What only you can run isn't a system yet, it's a habit.
What this horizon asks you
AI does the labour. People make the calls. Before you scale anything past Day 30, every one of these has to be true.
Set all three review dates before the session ends. A plan without dates in the calendar is just a nice idea.
Between checkpoints, a ten-minute weekly check on the current pilot is enough. You're not auditing, you're just noticing what's working and what's quietly not.
The interactive version of the workshop guide. Your answers save in this browser as you type, and you can print the finished plan or copy it as text.
We train teams to use AI on their real work, then build the systems that keep it running once the plan is signed off. Book a free 30-minute consultation.
Book a free consultation