Skip to content
get it reimbursed

your manager's questions, already answered.

If your company has a training budget, it has a form nobody enjoys filling in. This page is the filled-in version.

Copy the email, paste the description, print the syllabus. If your L&D team asks something that isn't here, tell us and we'll answer it.

step one

the sentence that goes in the form.

Training-request forms ask what the program is. This is the description we use on invoices and completion documents, so what your finance team approves and what they later receive are the same thing.

a 6-week live, instructor-led hands-on applied-ai training program with a structured curriculum, weekly assessments, and a practical capstone project; certificate of completion included.

step two

the email.

Fill in the bracketed parts. Your price is confirmed before you pay, on /apply — put that figure in rather than a guess, because it is the figure the invoice will carry.

Subject Training request: AI Builders Program (6 weeks)

Hi [manager],

I'd like to use my L&D budget for a 6-week live, instructor-led hands-on applied-ai training program with a structured curriculum, weekly assessments, and a practical capstone project; certificate of completion included.

It runs for six weeks, entirely outside working hours — live sessions are on weekends and every one is recorded. I'd be building on my own equipment, on a problem unrelated to our business.

What I come back with:
- A production application I designed, built, shipped and can walk the team through.
- The agentic-engineering practices behind it: writing specs an AI can build from, reviewing every diff, testing and evaluating AI features rather than trusting them.
- Notes I can share with the team in a session, if that's useful.

Cost: [amount], one payment. I'd pay for it myself and claim it back — I can forward the invoice and the completion certificate for our records.

The next cohort starts [date]. Could I go ahead and register?

Thanks,
[your name]

what your employer receives

paperwork, done properly.

An employer paying for training expects records. All four exist, and none of them depends on the outcome of your project.

  • The syllabusWeek by week, with what gets built in each one.
  • The scheduleSix weeks, weekend sessions, all recorded.
  • The invoiceIssued on payment. Company details go through accounts@.
  • The certificateA completion credential. The criteria are at the end of the syllabus.
step three

the syllabus.

The same six weeks as /program, laid out for an approver: what runs, and what exists at the end of each week.

Download syllabus PDF

AI Builders Program

L&D review syllabus
duration
6 weeks
format
live, instructor-led
assessment
weekly
capstone
practical project

  1. week 0

    Arrive ready to start

    week focus

    1. Configure the required tool stack and verify access before live instruction begins.
    2. Frame three candidate problems around the user, the pain and the evidence available.

  2. week 1

    Get the stack green. Pick the right problem.

    week focus

    1. Build working fluency across the program’s AI, code, deployment and collaboration tools.
    2. Evaluate qualitative evidence from five audience conversations.
    3. Select one evidence-backed problem and commit to a six-week scope.

  3. week 2

    Freeze the spec. Commit the architecture.

    week focus

    1. Translate user evidence into stories, acceptance criteria and a tightly scoped core flow.
    2. Produce a build-ready product specification, out-of-scope list and system architecture.
    3. Establish the repository, data model, agent workflow and first live deployment.

  4. week 3

    Build the killer flow. Learn to judge it.

    week focus

    1. Identify and remove common AI-generated interface patterns.
    2. Direct coding agents through specifications, branches, reviews and tests.
    3. Build the core flow end to end with acceptance coverage and reviewed edge cases.

  5. week 4

    Put the product in front of people

    week focus

    1. Plan and run five usability tests without leading participants.
    2. Convert observed behaviour into Keep/Kill/Change decisions and prioritised fixes.
    3. Implement the changes, error states, edge cases and product analytics.

  6. week 5

    Do the hard twenty percent

    week focus

    1. Harden authentication, permissions, email, data migrations and background jobs.
    2. Build and clear a QA checklist from real user stories and failure paths.
    3. Close review findings, test with five new users and complete launch readiness.

  7. week 6

    Harden it. Put it on the internet.

    week focus

    1. Complete production safeguards, monitoring, positioning and launch assets.
    2. Connect a real domain, analytics and search visibility.
    3. Run a final launch review and prepare a concise product demonstration.

What completion requires

Attendance at all 10 live sessions — attend live, or watch the recording within 7 days and post a one-line takeaway; both count equally — plus all six weekly deliverables submitted, and a deployed application.

before they ask

what L&D checks.

The four that decide an approval. Answered here exactly as they are answered on /faq — your manager can check.

Will this conflict with my job?+
Usually not, and here's the honest guidance nobody else in this category gives you. Build off-hours, on your own equipment. Pick a problem unrelated to your employer's business — the Problem Bank is curated to be employer-neutral for exactly this reason. Charging users is an optional path in the curriculum, not a requirement. And read your employment contract's IP clause before Week 1, because we'd rather you know now than at Demo Day.
"I don't have time."+
It's about 12 hours a week. 10 live sessions across the six weeks, on weekends, and everything's recorded if you miss one. Here's the thing, though — you won't find the hours lying around. You'll trade them in from the tutorials you're already watching.
Which time zone are the sessions in?+
One shared time, worldwide. Live sessions run once — the same time for everyone, wherever you are — on weekends, so they're easier to protect around a full-time job. And every session is recorded, so a missed one is never a missed week.
Do I get a certificate?+
You get a product, which beats a certificate. We do issue a completion credential you can put on LinkedIn, and the L&D kit includes proper invoicing and completion documentation for your employer.

Anything else — specific invoicing details, a form your finance team needs filled in — goes to /contact, and the refund terms are at /refund-policy.

if the answer is no

what to say next.

“There’s no budget.”+
Ask two questions rather than accepting it: when does the budget reset, and who owns it? The line may not be your manager’s to spend, so ask HR as well. And nothing here requires your employer to pay. The seat is yours to buy either way.
“Not right now.”+
Ask which cohort they could approve, not whether. Cohorts have dates, registration closes before each one starts, and a later cohort can cost more, so “later” has a price attached.
“Can’t you learn this for free?”+
Some of it, yes. Free material is the information. What a seat buys is a deadline, work that gets assessed every week, a mentor reviewing your build, and a capstone running in production at the end.
“We already run AI training.”+
Ask whether it ends with a working application in production, live at a real domain. If it does, take theirs.
“How does this help the rest of us?”+
Offer to run a session for the team when you’re done. The syllabus above is what you’d be teaching from.

when it's approved

budget cleared. seat waiting.

Cohort 6 is capped at 10 seats. Your price is shown before you pay.

Claim your seatExplore program details