How the guides are organised
There is one guide per use case, and they follow the same arc: where time goes now, which agents help, how the workflow runs and how to start. Read the one that matches your setting, then skim a second if you straddle two, as a tutoring centre selling online courses might. They are written for school leaders, operations staff and product teams, not for engineers, so you can forward one to a colleague without a glossary.
Reading time is listed on each guide so you can plan it, from six to nine minutes. They are meant to be read once, discussed with colleagues and then set aside in favour of the blueprint, which turns the general approach into something specific to your school, centre or company.
A reading order that works
If you are new to agents, start with the guide closest to your setting and read it with a pen in hand. You are looking for your own week in it. Mark the places where time disappears, note who handles each task now and circle the one you would most like to hand over. That note is a strong starting point.
- Mark the tasks that eat your week
- Note who currently approves each of them
- Circle one task for a small pilot
- Bring that note to a discovery call
Using a guide with your team
A guide is most useful as a meeting prompt. Share it with the people who would work alongside an agent and ask what they would hand over, and what they would not. Their answers tell you where approvals belong. The guides describe a general approach, not a promise of results. Details such as your systems, policies and tone are settled in the blueprint, which your team reviews before building starts.