Not "intro to ChatGPT." Practitioner-led. Manager-visible. Outcomes you can measure.
AI fluency is on your 2026 capability roadmap. Generic LMS courses won't move the needle for the team you actually have. You need something that produces measurable workflows shipped, not just attendance certificates.
Your team is using ChatGPT in tabs and you can't see it on the P&L. You want practitioners on your team who can identify, design, and ship AI workflows for the business, without hiring.
Your delivery teams need to be 25% faster on the workflows they already do. Hiring AI specialists is slow and expensive. Upskilling the team you have is the answer, if the training actually translates to delivery.
The curriculum is shaped to your stack and use cases. The structure below is the default; we adjust per cohort.
Where AI helps, where it hurts, what 'production-grade' actually means. Each participant identifies one workflow in their own remit to target by week 6.
Beyond ChatGPT. Structured prompts, evaluation, prompt iteration patterns. Each participant prototypes a prompt for their target workflow.
n8n, Make.com, basic API integration. When no-code works, when it doesn't. Participants connect their prompt to an actual data source.
Multi-step agents, tool use, decision logic. Building reliability into agents. Participants extend their workflow to a multi-step agent.
How to know your agent is working. Logging, eval, error handling, the 80/20 of robustness. Participants instrument their workflow.
Each participant presents their workflow to managers and the cohort. Q&A, handover docs, deployment plan. Project: shipped.
On day 1, each participant identifies a workflow in their own scope of work, something repetitive, recurring, and currently done by hand. Across six weeks, they prototype, integrate, build, instrument, and ship the agent. Senior founder review weekly. Private cohort Slack for peer help. By showcase day, every participant has a working AI workflow they can demo to their manager and deploy on Monday.
8–20 working AI workflows live in your business by the end of the programme. Not concepts. Not plans. Live, deployed workflows your team owns and runs. The cohort's collective output is typically worth more than the programme fee in the first quarter alone.
Final session of the programme. Each participant presents their shipped workflow: what it does, what it cost to build, how much capacity it returns. Managers attend. The cohort votes on the standout build. We document everything in a manager-readable summary.
Throughout the programme, managers get a dashboard showing each participant's progress: prompts iterated, integrations completed, workflow live status, projected capacity returned. By week 6, you can see exactly what was built, what's deployed, and what each participant is now capable of. We send a written readout to managers at week 3 (mid-programme) and week 6 (final).
| Participant | Workflow | Status | Hrs/mo |
|---|---|---|---|
| A. Patel | Brief intake | Live | 42 |
| B. Chen | Vendor recon | Live | 28 |
| C. Rivera | QBR draft | Beta | 60 |
| D. Singh | Lead enrich | Live | 35 |
| E. O'Hara | Comms routing | Beta | 22 |
The training market is split between generic e-learning and expensive enterprise platforms. We're neither. We're the operators who use these tools every day, training your team in the workflows we ship for clients.
8–12 participants.
13–20 participants.
Their seat is forfeited. We can't substitute mid-cohort because the project work is cumulative. If a participant leaves before week 3, we'll work with you on a partial credit toward your next cohort. Beyond week 3, the seat is consumed.
Default is fully remote — sessions over Zoom, project work async, Slack between. We do hybrid (remote sessions plus one in-person showcase day) for an additional fixed fee scoped on the call, if your office is reachable. Fully in-person is bespoke; we quote separately.
No. Participants use your existing licenses or we recommend tooling for you to procure. We don't bundle reseller margin into the programme fee. The fee is for instruction, project supervision, and management visibility, not software.
None technical. Participants need to be able to articulate a workflow they own, have basic spreadsheet and SaaS literacy, and have manager support to spend roughly 4–6 hours per week on the programme. Engineers welcome but not required. Historically the best builds come from operators, not coders.
Yes. Several clients run two cohorts a year, typically Q2 and Q4. We offer a 10% discount on the second cohort if booked at the same time. We cap delivery at three concurrent cohorts globally.
We run cohorts quarterly. Apply to discuss fit and reserve seats. Typically 4–6 weeks lead time before the cohort kicks off.
