The Guild curriculum
AI is a fast moving domain. This curriculum aims to create a structure to help members of the AI Momentum Guild to deepen knowledge and implement AI within their world.
How it is organised
Three groups. Two of them are ordered tiers; the third deliberately is not.
Tier 1 – Foundation Modules
Foundational AI topics, starting with an overview of the whole territory. Start here is you are getting started.
Tier 2 – Scaling Modules
These modules go more in depth and discuss how to scale your use of AI in the organisation.
Specialisms
Stand alone modules you take when the need arises, at whatever point that happens.
Some subjects appear in both tiers at different depths. Giving AI your context is a foundation; grounding it in your own data is the same subject at scale. Expect a 101 and a 102 of several of these as we build them out.
AI Kickstart
Several of joined by first attending an AI Kickstart workshop.
Kickstart runs horizontally. In a 3 hour session it crosses almost every module in this list at introductory depth: prompting, custom GPTs, NotebookLM, projects and context, agents and automation, the mindsets, and where you sit on the journey from Explorer to Builder to Leader. It shows you the whole territory.
The Guild runs vertically. Each module is where we cover one part of that territory more deeply, until you have something working in your own business rather than a sense of what is possible.
So Kickstart is the map and the Guild is the expedition. If you did the workshop and then wondered what to do with it, that is the honest answer: this list is what to do with it.
Foundation Modules
The five that everything else stands on. Roughly in order, and each one leans on the ones before it.
Scroll the table sideways to see all three columns.
| Module | What it covers | Sessions |
|---|---|---|
| 0. The territory | How the pieces fit together and why they are split this way, the mindsets that make AI adoption work, where you currently sit on the journey from Explorer to Builder to Leader, and enough of a governance overview that nobody hands an agent the keys without knowing what that means. | This is the ground the AI Kickstart workshop covers, and the Journey Planner assessment. I will add a shorter session tailored for guild members who haven’t attended an AI Kickstart workshop. |
| 1. Getting good answers | Briefing AI properly, structuring a request, and judging what comes back. Using good prompts: a skill everything else depends on. Using Prompt Cowboy. | 8, 21 – needs more sessions |
| 2. Giving AI good context | Memory and personal context. Getting your business into the AI’s head, and keeping it true as things change. Starting a basic RAG system with open brain. Keeping context and memory up to date and accurate. | 5, 10, 15, 23, plus the Rot Lab and the memory audit skill |
| 3. Building reusable assets | Skills, prompts and templates that persist instead of being retyped every time you need them. Getting started with vibe-coded dashboards and apps. | 4, 11, 18 |
| 4. Delegating real work | Agents and agent teams. Handing over an outcome rather than a list of steps. | 3, 12, 16, 17 |
Scaling Modules
What you build once the foundations are in place and doing it by hand has stopped working.
Scroll the table sideways to see all three columns.
| Module | What it covers | Sessions |
|---|---|---|
| 5. Automating routine work | Pipelines and workflows that run without you, on a schedule or a trigger, and keep running. | 2, 9, 14, 20 |
| 6. Grounding AI in your own data | Retrieval. Managing personal, global and other domains of context and managing access within teams. Introducing RAG systems. | 1 – needs more sessions |
| 7. Running it safely and affordably | Cost, model choice, and what you let AI touch (governance). Both cost and governance start to become more and more important as you scale AI throughout your team/organisation. | 22 covers cost well; governance – needs a session |
Specialisms
Modules you take when the need arises, at whatever point that happens.
Scroll the table sideways to see all three columns.
| Module | What it covers | Sessions |
|---|---|---|
| Content and creative | Working across text, images, audio and video, and producing more than a small team otherwise could. Using JSON specs to control images | 7 – video and audio need sessions |
| Being found by AI | Whether your business shows up when a buyer asks an AI instead of searching. | Needs a session |
| Building small tools | Developing applications, software tools, websites and dashboards without a developer. This covers | 13, 19, 21 |
| Useful Knowledge | Markdown basics & Typora. Understanding how and when to use JSON. Git benefits and basics. Databases. | 21 – needs another session |
How the curriculum grows
Some modules have more content than others. Over time we want all modules to be covered well.
Measuring Module Coverage
A module is fully fleshed out when it has all four of these layers:
- Taught – we have run a session on it and/or we have recorded extra videos.
- Recorded – there is at least one recording available in the portal and you can find it.
- Testable – there is something you can run yourself on your machines.
- Deployable – there is a skill or tool you can put to work.
One module per quarter
We are extending one module out to all four layers each quarter.
Which module gets extended is chosen by members, so the ranking of what matters most is influenced by members.
AI Momentum Guild curriculum. Last updated 10 August 2026.