Cohort 2 registration open · Starts 24 Aug 2026

Six weeks, you will build AI tools that save a week out of every month.

Cohort 1 sold out 100% money-back guarantee Small, selective cohort
Built by you
corporate-emissions-platform
The Corporate Emissions Platform dashboard
6 weeks · Real projects
Proof it works

They didn’t just finish a training. They shipped real tools that save them time.

What did students build in six weeks

You don't need to code. You need to know how to direct AI to build it.

Six weeks is enough to turn your bottleneck into a production-ready tool. Students built tools that save them time and upgraded their deliverables.

SBTi SME Assessment tool
Eligibility & targets

SBTi Assessment tool

A wizard that checks SBTi SME eligibility, calculates target ambition, and exports a submission PDF in minutes.

Supplier Engagement Platform
Value chain

Supplier Engagement Platform

A portal that onboards suppliers into your net-zero programme and walks them through what to submit and why.

Double Materiality Matrix
CSRD / ESRS

Double Materiality Matrix

An interactive matrix that plots impact vs. financial materiality across E, S and G by stakeholder.

Decarbonization Pathway Planner
Scope 1-3 / Decarbonization

Decarbonization Pathway Planner

Maps emission reduction levers against cost and timeline to build a credible net-zero roadmap.

Environmental Performance Dashboard
ESRS / Environmental Dashboard

Environmental Performance Dashboard

Tracks energy, water, waste and emissions KPIs in one live view for internal reporting and board updates.

Corrective Action Tracker
EHS / CAPA Tracker

Corrective Action Tracker

Logs EHS findings, assigns corrective actions, and tracks closure status against deadlines.

Zyad Hatquai
Who's teaching

A practitioner, who shipped actual tools.

"I have been helping sustainability professionals build production-ready tools to save them time, their business money, and get things done."

Zyad Hatquai · Chemical engineer & sustainability manager who learned AI by applying it to his own real work first.

How it works

Twice a week. Build, don't just watch.

Monday · Session 1 · 16:00–17:00 CEST

60 min · Build Together

I walk through the workflow live — not slides, actual work. You follow along on your own machine, building the same tool in real time. Your laptop must be open and ready. This is not a webinar.

Friday · Session 2 · 16:00–17:30 CEST

90 min · Show & Share

3–4 participants share what they built, why they built it, and what they'd do differently. Peer feedback, troubleshooting, iteration. This is where real learning sticks.

6 weeks · 2 sessions per week · ~15 hours live together + ~15 hours building on your own · Total commitment: ~30 hours · Time zone scheduling confirmed with accepted participants · Start time 16:00 CEST
The foundation underneath: the course, the material, and every recording live in the community. Something breaks mid-week? You get a response in under 24 hours.
The journey — Week 0 to ∞

Week by week, everything stacks.

Week 0

Ready before Day 1

Short pre-recorded lessons, done in your own time. You meet Claude properly, install your first skill, and learn how to brief a build so it comes back right. You arrive on Day 1 ready to build, not ready to set up.

Learn more
Week 0

Ready before Day 1

  • Claude Code installed and running on your own machine
  • What a skill is, and how to install one in three steps
  • What a product spec is, and why it decides whether the build works
  • Why the first version of anything stays deliberately small
  • The vocabulary you will use for the next six weeks

By Day 1: a working setup and a list of tool ideas from your own job.

Week 1

Build your first tool

By Friday you have a working tool, live on the internet, on its own URL. You meet Claude Code, turn a rough idea into a brief precise enough to build from, and put the result online. Not a prototype on your laptop. Something you can send to a colleague.

Learn more
Week 1

Build your first tool

  • Turning a vague idea into a precise brief, guided by an interview
  • Building your first working interface with Claude Code
  • Publishing it to a live URL anyone can open
  • Choosing what your tool actually needs, and what it does not
  • We build a double materiality matrix together, from a complete assessment

By Friday: your own tool, live on its own URL.

Weeks 2–4 — one tool, growing
Week 2One tool, growing

Build your second tool, and upgrade your setup

A second tool, and a setup that stops slowing you down. The manual steps from Week 1 disappear. Your work saves its own history, publishes itself, and remembers the rules you set, so you spend the time on your thinking instead of on the tooling.

Learn more
Week 2

Build your second tool, and upgrade your setup

  • GitHub, so your work has a history and a bad build is one click back
  • A publishing pipeline, so saving your work puts it live automatically
  • The documents that give Claude your rules, so it builds your way every time
  • Connecting Claude to the tools you already use
  • We start a supplier engagement portal, and grow it for the next three weeks

By Friday: your own tool, in your own repository, publishing itself.

Week 3One tool, growing

Your tool gets a memory

Right now your tool collects, then forgets. This week it remembers. It gets a database, so what people enter is still there tomorrow, structured, in one place you own. And the moment your data lives somewhere you control, everything downstream opens up. Analyse it, refine it, report on it, build a dashboard on top of it. This is the week that makes all of it possible.

Learn more
Week 3

Your tool gets a memory

  • What a backend and a database actually are, and how they talk to each other
  • Setting up your own database and designing what it stores
  • Deciding what deserves to be a record, and what belongs in a file
  • Reading your own data, and trusting what you see
  • Why stored data is the real unlock: analysis, reporting and dashboards all become possible from here, and we build both in Weeks 5 and 6
  • Handling keys safely, so nothing sensitive ever ends up somewhere public

By Friday: enter something, close the tab, come back tomorrow. It is still there, in your database.

Week 4One tool, growing

Protect your tool

Now you decide who gets in. Your tool gets a real login, so only the people you invite can use it, and every entry is tied to someone you can name. This is where a side project becomes something you can put in front of your boss, your IT team, or a client.

Learn more
Week 4

Protect your tool

  • How modern logins actually work, and why the best ones use no password at all
  • Invite-only access, so an address you never invited gets nothing
  • Signing in with Google, and when that is the better choice
  • Connecting your tool to outside services, so it can send real email
  • Putting your tool on your own web address instead of a platform subdomain

By Friday: you sign in through your own link. Someone you did not invite gets nothing.

Week 5

Roles, admins and users

Different people, different views. You build a carbon inventory platform where a plant manager submits their own site’s data and an ESG lead reviews and approves it. Same login, completely different screens, and nobody sees what they should not.

Learn more
Week 5

Roles, admins and users

  • Why getting in and being allowed to see are two different problems
  • Building roles, so each person lands on the view that belongs to them
  • Locking data down at the record level, not just at the door
  • Submit, review, approve, with a named person on every step
  • Putting the calculation inside the tool, so the person entering data cannot get the maths wrong

By Friday: your tool with roles. The data one role is not allowed to see is gone from their screen.

Week 6

Everything connects

Your capstone. You build a decarbonization roadmap, and then make it read what your emissions platform produces. One database, one login, two tools working as one system. Then we go a level up, so you can place whatever launches next without starting over.

Learn more
Week 6

Everything connects

  • Connecting two tools so one reads what the other produces
  • One login across everything you have built
  • What an AI model can and cannot do, in plain terms
  • RAG: how AI answers from your documents, with references you can check
  • The difference between a workflow and an agent, and when each one is right
  • How connectors let your tools reach the rest of your stack

By Friday: your own system, presented to the room.

Lifetime

The building doesn’t stop

The cohort ends. Your access doesn’t. Every recording, all the material, and a community of sustainability professionals building, breaking, fixing and launching together.

Learn more
Lifetime

The building doesn’t stop

  • Every recording and all the material, yours to keep
  • The community stays open, and the sessions keep going
  • Bring whatever you decide to build next
Your skill set so far27 of 27Check the full curriculum
Apply for Cohort 2
What you leave with

Not a certificate. Your own operating system.

6+ Deliverables

Real tools you built yourself that you'll take straight to work, plus the reusable skills I provide so you can build high-quality tools every time.

Multi-Tool Fluency

Claude Code, Netlify, Supabase, Resend, Anthropic API: a full stack that lets you build real, working tools, not toy demos.

Real Career Signal

A portfolio of AI-built sustainability tools to show your boss, your next employer, or your clients. Starting Monday.

SustainOS Workflow

This isn’t about tools built during the cohort. It’s the repeatable workflow behind it. You leave as the architect, who can build any tool any time.

Why now

The field is shifting. Early movers win.

+90%
of 1,000+ sustainability professionals say AI will change how the work gets done.

I asked over 1,000 sustainability professionals about the future of their work. Over 90% told me the same thing: AI will change how the work gets done. Almost none of them knew how to act on it.

That gap is the opportunity. In every shift like this, the winners aren't the most qualified. They're the earliest. The people who start building while everyone else is still waiting to see what happens.

If you're on this page, you already feel the size of what's coming. The only question is whether you move on it now, while being early still counts, or later, when it's just catching up.

Cohort 2 · Registration open

Cohort 1 is full. Cohort 2 registration is open.

Registration for Cohort 2 (starting 24 August) is open now. We keep every cohort small and personally vetted, to ensure everyone will get the most out of the AI Lab.

1
3 minutes, max

Fill in the application

A short form about your work and what you'd want to build. No payment, no commitment yet.

2
15 mins call

Book a fit call

This call is designed to check if the AI Lab is the right fit for your goals.

3
Limited seats, 16 max

Enroll & start building

Confirm your spot and join the cohort. The room stays small, serious, and committed.

Takes ~3 minutes · No payment at this stage · We review every application personally.

Every participant is personally vetted. This isn't just a course, it's a community you're joining.

Common questions

Before you apply.

Do I need coding experience?

No. You need to know your job. AI tools handle the technical complexity. If you can describe what you need, you can build it. I didn't consider myself a coder when I started — I still don't.

What's the time commitment?

About 30 hours over 6 weeks. ~15 hours of live sessions (Monday builds + Friday demos) and ~15 hours of exploring and building on your own. Intensive, but designed around a full-time role.

Will I work with my own data?

We work on real use case types drawn from actual sustainability work — while keeping your data exactly where it belongs. The goal isn't automation for its own sake. It's transforming high-effort work into low-effort work without compromising data privacy.

What if I miss a session?

As a founding member, I expect full commitment — please treat this as non-negotiable. Monday build sessions are recorded. But the Friday demos are where real learning happens. Plan to attend every one.

Why €2,000?

The programme runs 6 weeks with 2 live sessions per week, personal feedback on every build, and direct access throughout. You leave with 10+ real deliverables built on your actual job and lifetime access to the SustainOS community. The investment reflects the time, depth, and outcome — not a content library you never open.

Where can I learn in the meantime?

The SustainOS newsletter and YouTube channel are both free and updated regularly. Both cover AI tools for sustainability work, real builds, and the same practitioner-first approach you'll find in the cohort. Subscribe at newsletter.sustainos.io or watch at youtube.com/@ZyadHatquai.

Ready to build your own tool?

Registration for Cohort 2 is open. See the process, the price, and apply in three minutes.

Cohort 2 starts 24th of August · Limited, vetted seats