AI Agents for Pragmatic Builders - Claude Code, LangGraph, n8n

That is up to you and how much time you want to put in. To get a sense, check out these demos from our alumni.

Note, however, we see commonly that participants end up refining their original idea in terms of scope and approach. So you have to be open to evolving your idea as we provide feedback and you experience the feasibility firsthand.

Per week:

• 1 hr - group office hour live session
• 1 hr - [optional] community event live session
• 2-5 hrs - The reading / watching material
• 10+ hours of project

Summary. You need 10ish hours a week to get the absolute min. out of this course. The upper bound is however much time you want to spend on the project or digging deeper into the material.

It is understandable that your circumstance might change or after starting the course you might decide that you need more time to prep to take the most out of the course. To accommodate that, you are allowed to transfer your registration to a future cohort until the end of the third week of the course.

Note that this is a one-time option.

Yes!

• If you are an AISC member, check Slack.
• If you want to be part of the above, send an email to maven@ai.science

AND, you can apply for our incentive program for up to 75% refund.

See group purchase options on the top of the page.

Send me an email to discuss details if you are interested in private cohorts or you want to register groups larger than 10 and want to coordinate.

Yes! Minimum group size is 10. The cost depends on the group size, and the level of customization needed, but you can imagine approximately 50%-100% higher rates that individual registrations. Send me an email to discuss details.

The primary purpose of the live sessions is for you to ask your questions. So, it is strongly encouraged that you arrange your schedule for the few weeks of the cohort to join those. We will try our best to provide the recordings of the live sessions.

That depends on how involved you want your project to be. Typically people end up using:

• Strategy and architecture (eg. Google Docs, Miro)
• Quick prototyping (eg. N8N, LangFlow, Dify)
• Coding (eg. Python, LangGraph, Langchain)

Plenty. 1 on 1 mentorship sessions. Group office hours. Async questions / answers on slack.

After the course, you can stay in the same Slack workspace and post your technical questions and the course alumni and the broader community can answer.

Most of the mentors also do contract advisory work, if needed, outside of the bootcamp.

Ideally, but not necessarily!

You can also brainstorm with the mentors about rough ideas you have and refine them into concrete project ideas during onboarding.

Or you could team up with others who have concrete ideas.

We do also provide some "default" projects you can work on if your goal is just learning the techniques.

Given that this is NOT a formal advisory engagement, none of the mentors are under confidentiality restrictions.

Please do not share any information that is sensitive in terms of IP or confidentiality with the mentors or peers.

For alternative engagements, book me to discuss the best option.

Yes. See this link for more details. If you go all the way to the end, the video from your public demo will also act as a great "proof of work" that you can show off.