Same curriculum. Different weighting.
Three cohorts.
One methodology.
Every cohort covers the full stack of AI competency. The difference is where the hours go. Pick the track that matches how you work.
Time Allocation by Cohort
Technical
Build systems that compound
Who:Developers, engineers, technical founders
Capstone:Build a tool or production system
Time Allocation
Business
Direct AI without writing code
Who:Ops, managers, founders, consultants
Capstone:Automate a process or design a system spec
Time Allocation
Creator
One person replaces the team
Who:Creators, marketers, educators, solo operators
Capstone:Build a content production system
Time Allocation
Sprint-by-Sprint
What each sprint covers
SPRINT_01 / Weeks 1-3
Foundation
AI architecture, prompt engineering patterns, Claude Code deep-dive, integration strategies (MCP, APIs, direct tooling)
AI mental models, prompt engineering for non-technical roles, understanding what tools can and cannot do
AI foundations, prompt craft for content, Claude Code basics, integration setup for creative tools
SPRINT_02 / Weeks 5-7
Application
Production patterns, async orchestration, agentic workflows, system design for scale
Workflow mapping, ROI modeling, directing technical teams, decision frameworks for AI adoption
Content pipeline design, audience scaling systems, multi-format repurposing, one-person workflows
SPRINT_03 / Weeks 9-11
Capstone
Capstone build, deployment, testing, demo prep, certification assessment
Capstone automation, stakeholder communication, system spec documentation, certification
Capstone production system, launch strategy, scaling playbook, certification assessment
Not sure which cohort?
Every cohort gets the same 18 hours of live instruction, the same 12 instructors, the same certification. The only difference is which topics get more depth. If you write code, go Technical. If you manage people or processes, go Business. If you create content or run solo, go Creator.
All cohorts: 100 seats each / 3 sprints + breaks / certification included