If you are joining an open cohort
- Do I need to be technical?
- No. There is no code in any business-track programme. If you can write a brief for a new colleague, you have the prerequisite.
- How much time does it really take?
- One live session a week of 90–100 minutes, plus the pre-work you submit beforehand and the applied work on your own task — 1.5–3.2 hours a week in total, depending on the programme. The applied part is what produces the result, so treat the whole number as the real commitment, not the live hour. Each programme page states its own.
- What if I miss a session?
- Sessions are recorded and applied work is asynchronous. But the schedule and the cohort are most of what you are paying for. If you expect to miss more than one, take the next cohort.
- Do I get a recording?
- Yes, for the duration of the cohort plus the two booster sessions.
- Is there a certificate?
- Only if you pass the capstone against the published rubric. We do not issue attendance certificates, because they do not mean anything and employers discount them.
- What is your refund policy?
- Full refund up to seven days before the first session. After the first session, a full refund if you attend and tell us it was not what was described.
- Which region should I book?
- Book the cohort whose weekly session time you can actually attend live. The curriculum is identical; only the timezone and regional pricing differ.
- Can I expense this?
- Most people do. Ask us and we will send a one-page justification you can forward to your manager, including the time commitment and the measurable outcome.
If you are buying for a team
- How many people can attend?
- 6 to 12. Above that the applied work stops functioning and it becomes a talk rather than a workshop — the labs run in breakout groups of three and every group needs attention within the session.
- Can you deliver onsite?
- Yes, in Canada and Pakistan as standard, elsewhere by arrangement plus travel. Onsite suits cross-functional groups where the room is part of the value.
- How far ahead do we need to book?
- Typically three to four weeks from a signed scope, which allows time for the needs analysis that makes the content yours rather than generic.
- Do you accept purchase orders?
- Yes. Purchase orders, Net 30 terms, and consolidated invoicing across multiple cohorts.
- Will you sign an NDA?
- Yes, before the needs analysis. Your material stays in your tenancy; we do not take copies of your data.
- How do you handle mixed seniority?
- Everyone shares the same foundation, then splits into role-appropriate applied tracks. Uniform training for a mixed group is the most common way this budget gets wasted.
- What do we get for compliance purposes?
- A training record covering who was trained, on what, tailored how by role and system risk, when, with versioned materials and the reasoning behind the design. If you deploy AI systems in the EU, this is the shape Article 4 asks for.
- What if training is not our real problem?
- We will say so. If a workflow needs an integration built or a data source made accessible, that is engineering work and we would rather scope that than sell you a workshop that cannot fix it.
- Can you train our trainers instead?
- Yes, from cohort three onward. The curriculum is authored as facilitator guides with timings and answer keys specifically so it can be handed over.
Still deciding?
The ninety-minute Foundations session exists precisely so you can find out cheaply whether the full programme is worth your time.