Enterprise AI Bootcamp · Google Cloud or Microsoft 8 weeks from container to deployed system.

For developers who already code. Sundays: Google Cloud mornings or Microsoft evenings.

Choose your track Google Cloud session map
Google Cloud · Sun 9.30am – 1.30pm · from October 202620 of 20 seats left
Microsoft · Sun evenings20 of 20 seats left
Screened. Shipped. Secured.
A BuildrLabs Lego tech lead in a Hatch lanyard
Backed by our partner ecosystem
01 · Choose Your Track

Two tracks. Same Sundays. Separate cohorts.

Google Cloud in the mornings, Microsoft in the evenings. Each track is its own cohort of twenty, with the same screened entry, in person at Hatch Works, Colombo.

Sunday Mornings

Google Cloud Track

Sundays · 9.30am – 1.30pm · from October 2026
20 of 20 seats left Full curriculum below
LKR 95,000 / seat
  • Google Cloud credits provided for every learner
  • Your own budget-capped Google Cloud project, live for the programme plus 14 days
  • One enterprise agent system built across 8 Sundays
  • BuildrLabs certificate plus Google Skills badges
Sunday Evenings

Microsoft Track

Sundays · evening hours confirmed on application
20 of 20 seats left Curriculum announced soon
LKR 95,000 / seat
  • Enterprise AI engineering on the Microsoft stack
  • A separate cohort with its own 20 seats
  • Same screened entry, in person at Hatch Works, Colombo
  • Full session map shared with enrolled learners first
0:51 · Student stories
Where you’ll build

Your Sundays. At Hatch Works.

Real BuildrLabs sessions at Hatch Works, Colombo, September 2026: working developers at their laptops with a practitioner at the table. This is the room your cohort builds in.

  • Sundays, AM or PM
  • Hatch Works, Colombo 01
  • Google Cloud credits provided
  • Screened cohort of 20
Choose your track See you on Sunday.
Google Cloud Track · Sunday Mornings · Full Programme Looking for the Microsoft Track? ↑
02 · Format & Schedule

Eight Sunday mornings. One system.

Thirty two contact hours in person, under LKR 3,000 per hour, with Google Cloud credits and every lab included in the fee.

20 of 20 seats left Enrol now
Format
8 live Sunday sessions, one enterprise system built across all eight
Schedule
8 Sundays · 9.30am – 1.30pm · starts October 2026
Location
In person at Hatch Works, Colombo
Commitment
32 contact hours, plus 5–6 hours per week between sessions (~75 hours in total)
Environment
Google Cloud credits provided — your own budget-capped Google Cloud project, live for the programme plus 14 days
Investment
LKR 95,000 per seat — cloud environment and all material included
Certification
BuildrLabs certificate plus Google Skills badges
A Sunday, start to finish

Every Sunday runs the same rhythm.

Guided lab, then unguided lab, then your own build. That progression is what turns a workshop into a bootcamp.

09:30
Ship review

Last week’s pull requests on screen, learners present

09:50
Concept block

The week’s core idea, taught against the system being built

10:40
Guided lab

Instructor at the front, everyone at the same checkpoint by the end

11:40
Break
11:50
Unguided lab

Spec given, learners build, instructor and TA float

13:05
Demo round

This week’s ship defined, homework briefed

13:30
End
03 · What You Build & How You’re Assessed

One system, built across all eight sessions.

Pick an enterprise vertical on day one and keep it throughout. Synthetic data and mock APIs are supplied, so you build against something that behaves like a real enterprise.

Banking Telco Insurance Retail Internal IT
01

Agent Gateway

Policy control, injection defence

02

Coordinator Agent

Workflow graph, deterministic paths

03

Knowledge Agent

Grounded on enterprise data

04

Transaction Agent

Tools and MCP, human approval gate

05

Escalation Agent

Remote, reached over A2A

06

Memory and Runtime

Persistent memory, deployed endpoint

07

Eval Suite

Adversarial cases, CI gate

08

Identity and Registry

Least privilege, no agent sprawl

Assessment

Four gates. All four required to pass.

You are assessed on what you ship, not on attendance. The final Sunday is Demo Day: your system running live in front of an invited industry panel, as your final assessment and a showcase of what you shipped.

01 Weekly ships

At least six of seven merged on time.

02 Evaluation

Eval set includes adversarial cases and catches a real failure.

03 Security

Red team findings addressed, identity and gateway configured.

04 Demo

System runs live in front of the panel.

04 · Entry

Screened in, then supported all the way.

Twenty seats and a screened entry, so nobody spends eight Sundays out of their depth.

Entry Requirement

A 45 minute take home task.

Before enrolment is confirmed: call the Gemini API, force a strict JSON schema, handle one failure, push to a repo. Pass or fail.

Assumed Knowledge

You already code.

Intermediate Python, Git and the command line, and you have consumed a REST API before. No prior LLM experience is needed.

Support in the Room

Never building alone.

  • Instructor plus teaching assistant throughout every session
  • One to one architecture review at the midpoint
05 · Pricing

LKR 95,000 per seat, either track.

Thirty two contact hours, under LKR 3,000 per hour. The cloud environment and every lab, dataset and mock API are included, so there is nothing further to buy.

Google Cloud Track
LKR 95,000
Per seat · 8 Sundays · 9.30am – 1.30pm
20 of 20 seats left
What the Fee Covers
  • 32 hours of live, in person instruction
  • Google Cloud credits provided: an individual budget-capped project, live for the programme plus 14 days
  • All labs, synthetic enterprise datasets and mock APIs
  • Weekly pull request review and written feedback
  • Demo Day before an invited industry panel
  • BuildrLabs certificate plus Google Skills badges, and alumni channel access
Enrol now
Microsoft Track · Sunday Evenings

Same fee, LKR 95,000 per seat, for a separate cohort of twenty. Curriculum announced soon. Enrol on the Microsoft Track

Optional Add On

Voice and Multimodal Agents

A full day elective, priced separately, open to cohort learners and to non cohort developers. Pricing confirmed on application.

Payment Options
06 · FAQ

What developers ask us first.

Anything else? WhatsApp +94 76 925 6780.

01 What is the difference between the Google Cloud and Microsoft tracks?
They are two separate cohorts, each with its own 20 seats, and both run on Sundays in person at Hatch Works, Colombo. The Google Cloud Track runs on Sunday mornings from 9.30am to 1.30pm and includes Google Cloud credits. The Microsoft Track runs on Sunday evenings and teaches enterprise AI engineering on the Microsoft stack; its curriculum is being finalised, and evening timings and start date are confirmed on application. Choose the cloud your company runs on, or the one you want to work in. Both are LKR 95,000 per seat.
02 Do I need prior LLM or AI experience?
No. We assume intermediate Python, comfort with Git and the command line, and that you have consumed a REST API before. No prior LLM experience is needed. The entry task is designed to confirm exactly that baseline.
03 What is the entry task?
A 45 minute take home task you complete before enrolment: call the Gemini API, force a strict JSON schema, handle one failure, and push to a repo. It is pass or fail, and it exists so that nobody sits through eight Sundays out of their depth.
04 How is this different from the Agentic AI Pathway?
The Agentic AI Pathway starts at Python and takes you to production agents over two stages. This track assumes you can already code and spends all eight Sundays on one enterprise grade system on Google Cloud: gateway, multi agent coordination, evaluation, security and governance.
05 Does the fee cover the cloud costs?
On the Google Cloud Track, yes. Google Cloud credits are provided, so your own budget-capped Google Cloud project is included and stays live for the programme plus 14 days after Demo Day. All labs, synthetic enterprise datasets and mock APIs are supplied. The Microsoft Track environment will be confirmed with its curriculum.
06 What is Demo Day?
The final Sunday is Demo Day: you present your working system, running live, to an invited industry panel. It is your final assessment and a showcase of what you shipped.
07 How much work is there between sessions?
Plan for 5 to 6 hours per week. Across the eight weeks that is roughly 75 hours in total including the live sessions. The weekly ship is what the next Sunday opens with, so it is not optional.
08 Do I get a certificate?
Yes. On the Google Cloud Track you receive a BuildrLabs certificate plus Google Skills badges. You are assessed on what you ship, through four gates: weekly ships, evaluation, security and the Demo Day system running live.
09 Is there an instalment option or an early bird price?
Instalment options available. Reach out for more information. Early bird pricing and the team rate for three or more seats are being finalised; enrol now and we will confirm what is available to you.
07 · Google Cloud Session Map

Eight Sundays. Eight ships.

Every session ends with something merged. The next Sunday opens by reviewing it on screen. Click any session to expand.

01 Session 01 · One Sunday · 4 hours Foundations, Gemini and Your First Agent

Where the line sits between a chatbot, a workflow and an agent. Model selection as engineering. Structured output as the foundation.

By the end of Session 01
An agent running locally, schema valid JSON, one tool.
02 Session 02 · One Sunday · 4 hours Tools, MCP and Grounding Enterprise Data

Tool design as API design. Debugging tool choice from logs. MCP local and remote. Grounding, chunking, hybrid retrieval, citation.

By the end of Session 02
Two tools, one MCP connection, grounded retrieval, first eval set.
03 Session 03 · One Sunday · 4 hours Workflow Graphs and Human in the Loop

The hardest session. Deterministic paths versus model decided paths. Approval gates as architecture, not fallback. Callbacks and guardrails.

By the end of Session 03
Coordinator as a workflow graph with a working approval gate.
04 Session 04 · One Sunday · 4 hours Memory and First Deployment

Sessions and state versus memory. Memory schema design and the cost of remembering too much. Deployment, rollback, budget caps.

By the end of Session 04
Deployed agent on a live endpoint, budget alert proven to fire.
05 Session 05 · One Sunday · 4 hours Multi Agent Systems and A2A

What deserves to be an agent, what should stay code. Agent Cards and signed identity. Failure design for distributed agents. A2A versus MCP.

By the end of Session 05
Signed Agent Card published, one cross project delegation.
06 Session 06 · One Sunday · 4 hours Evaluation and Observability

Eval sets that mean something. Trajectory versus final answer, because the right answer by the wrong route is still a bug. Drift in production.

By the end of Session 06
Eval suite with adversarial cases, CI gate blocking regressions.
07 Session 07 · One Sunday · 4 hours Security and Governance

Prompt injection, tool poisoning, data exfiltration, over permissioned agents. Least privilege for non human actors. CBSL, PDPA and regional framing.

By the end of Session 07
Identity assigned, gateway enforced, red team report written.
08 Session 08 · One Sunday · 4 hours Hardening, Cost and Demo Day

Fix what the red team found. Model downgrade paths, caching, where token spend actually sits. The architecture document that outlives the code.

By the end of Session 08
Working system, architecture document, eval report, recorded demo.

Morning or evening.
Pick your track.

Twenty seats per track, screened entry. Google Cloud on Sunday mornings from October 2026, Microsoft on Sunday evenings. The sooner you enrol, the sooner your seat is held.

Questions? WhatsApp +94 76 925 6780