Goal: Understand what AI is, how modern AI learns, the main AI problem types, how models are used through inference, and where AI fits into products.
Day01
Explain AI in simple terms and distinguish AI systems from ordinary software.
Day02
Explain the basic idea of learning from data rather than hand-coding every rule.
Day03
Identify common AI problem types and match a product problem to an appropriate AI approach.
Day04
Explain what a model does and how inference turns an input into an output.
Day05
Translate a real product requirement into an AI-enabled feature and explain where the model fits.
Checkpoint: Problem → AI approach → model → inference → product feature.
Week2
Understand How Modern AI Learns
Days 6–10
Goal: Build a practical mental model of neural networks, training, loss, gradients, deep learning, NLP and attention.
Day06
Explain a neural network as layers that transform inputs into useful representations.
Day07
Explain how loss measures error and how gradients guide model improvement.
Day08
Explain why deeper networks can learn richer representations and where deep learning is useful.
Day09
Explain how text can be represented and processed for language tasks.
Day10
Explain attention as a way for a model to focus on relevant parts of an input.
Checkpoint: Data → neural network → training → loss/gradients → learned behavior; explain NLP and attention.
Week3
Understand LLMs
Days 11–15
Goal: Understand Transformers, LLMs, tokens, context, generation and model selection.
Day11
Explain the high-level Transformer pipeline and why it changed language AI.
Day12
Explain what an LLM does and what kinds of tasks it can perform.
Day13
Explain tokens, context windows and why context affects an LLM's output.
Day14
Use an LLM API and explain the basic request → model → response flow.
Day15
Choose an appropriate model for a simple task using capability, quality, latency and cost considerations.
Checkpoint: Text → tokens → Transformer/LLM → context → generated output; use an API and justify a model choice.
Week4
Build with LLMs
Days 16–20
Goal: Turn LLM knowledge into usable application features through prompts, structured outputs and task decomposition.
Day16
Build a simple application that sends user input to an LLM and uses the response.
Day17
Write prompts with clear instructions, context, constraints and expected output.
Day18
Use zero-shot and few-shot examples and explain when examples improve results.
Day19
Make an LLM return predictable structured data that an application can consume.
Day20
Break a larger AI task into smaller model calls or deterministic steps.
Checkpoint: Build an LLM feature, write a strong prompt, compare zero/few-shot, validate structured output and decompose tasks.
Week5
Make AI More Reliable
Days 21–25 Mini Project 1
Goal: Learn to evaluate prompts and use embeddings and vector search to improve relevance.
Day21
Compare prompt variants using a repeatable test set and simple quality criteria.
Day22
Explain embeddings as numerical representations of semantic meaning and generate them for text.
Day23
Retrieve semantically similar content using vector search.
Day24
Define the problem, users, inputs, outputs and AI workflow for Mini Project 1.
Day25
Build the first working version of Mini Project 1 and test it with representative inputs.
Checkpoint: Evaluate prompt variants, generate embeddings, run vector search and explain semantic retrieval.
Mini Project 1 is introduced this week — you choose one idea, then build it over two independent studio days. See project details
Week6
Build Knowledge-Grounded AI
Days 26–30
Goal: Understand grounding, RAG and RAG quality, and begin building agents.
Day26
Improve Mini Project 1 from testing feedback and make a meaningful functional change.
Day27
Identify common hallucinations and explain how grounding can reduce unsupported answers.
Day28
Build a basic retrieval-augmented generation flow: retrieve relevant context, then generate an answer.
Day29
Test retrieval and answer quality and identify where a RAG pipeline fails.
Day30
Explain an agent as a system that can reason through a task and use available actions/tools.
Checkpoint: Find grounding failures, build/test RAG, assess retrieval/answer quality and explain what makes a system agentic.
Week7
Build Agents
Days 31–35 Mini Project 2
Goal: Build tool-using workflows and understand memory, vision/OCR and voice AI.
Day31
Connect an LLM to a tool and explain the input → tool → result → response loop.
Day32
Build a simple multi-step workflow and explain what information should persist between steps.
Day33
Use AI to extract or reason over information in images and documents.
Day34
Explain the speech-to-text → reasoning → text-to-speech flow and prototype a voice interaction.
Day35
Define the problem, workflow, AI capabilities and success criteria for Mini Project 2.
Checkpoint: Connect tools, build a multi-step workflow, use vision/OCR and voice, and explain persistent information.
Mini Project 2 is introduced this week — you choose one idea, then build it over two independent studio days. See project details
Week8
Build & Harden AI Applications
Days 36–40 Capstone
Goal: Finish an AI application and make it safer, testable and ready to explain.
Day36
Build and test the core workflow of Mini Project 2.
Day37
Polish the project, fix failures and improve the user experience.
Day38
Identify common AI risks and add basic guardrails for unsafe or invalid inputs/outputs.
Day39
Define practical tests and explain the production concerns that matter for an AI application.
Day40
Design the capstone AI system and explain its components, flow, trade-offs and next steps.
Checkpoint: Test/harden an AI application, apply guardrails, explain production concerns and defend capstone decisions.
Capstone — a dedicated production and planning day, then you build independently and return for review after one week. See project details
How every session works
The studio pattern behind all 40 days
story
problem framing
concept
AI use
live build
analyze
experiment
streamline
viva + recap
Our AI philosophy
Students use AI to accelerate implementation, but must understand important generated code/configuration, inspect outputs, test changes, identify failures and justify decisions.
Projects
Build, ship and defend your work
Two mini projects and a market-oriented capstone. You use AI to build faster — and you explain the important generated code and decisions.
How Mini Project 1 works
Students choose one idea. The project is introduced with 30 extra minutes on the introduction day. After introduction, use two independent studio work days for implementation; these are student build days rather than new lecture sessions.
Minimum requirements
Solve a clear user problem.
Use the concepts covered before the project introduction.
Use AI for at least one research/design/build/debug/review task.
Keep an AI context/prompt log.
Demonstrate a working POC.
Explain the important generated code and one thing that was changed after analysis.
Submission checklist
Target user + clear problem
Architecture diagram
Working core flow
5 test cases
2 failure/limitation cases
README explaining technique choice
Git repository + short demo
Student can explain important code/design decisions
Pick one idea · 30 options
AI Resume Screener
Student Performance Predictor
Customer Churn Predictor
Spam Message Classifier
Support Ticket Router
Loan Eligibility Predictor
House Price Predictor
Restaurant Rating Predictor
Employee Attrition Predictor
Simple Fraud Flagging Model
Sales Lead Score Predictor
Delivery Delay Predictor
Student Attendance Risk Predictor
E-commerce Purchase Predictor
Movie Rating Predictor
Customer Complaint Classifier
Email Priority Classifier
Product Review Sentiment Analyzer
Job Description Classifier
College Admission Predictor
Retail Demand Predictor
Insurance Claim Risk Predictor
Subscription Renewal Predictor
Travel Cost Predictor
Credit Risk Demonstrator
Course Recommendation Prototype
News Category Classifier
Basic Image Classifier
Handwritten Digit Recognizer
FAQ Classifier
How Mini Project 2 works
Students choose one idea. The project is introduced with 30 extra minutes on the introduction day. After introduction, use two independent studio work days for implementation; these are student build days rather than new lecture sessions.
Minimum requirements
Solve a clear user problem.
Use the concepts covered before the project introduction.
Use AI for at least one research/design/build/debug/review task.
Keep an AI context/prompt log.
Demonstrate a working POC.
Explain the important generated code and one thing that was changed after analysis.
Submission checklist
Target user + clear problem
Architecture diagram
Working core flow
5 test cases
2 failure/limitation cases
README explaining technique choice
Git repository + short demo
Student can explain important code/design decisions
Pick one idea · 30 options
College Policy Assistant
Company HR Assistant
Course Material Q&A
Restaurant Research Agent
Travel Research Assistant
Local Business Research Assistant
Placement Preparation Agent
Scholarship Assistant
Government Scheme Information Assistant
Invoice Document Assistant
Product Manual Assistant
Real Estate Document Assistant
Legal Document Navigation
Healthcare Information Assistant
NGO Knowledge Assistant
College Admission Assistant
Library Research Agent
Startup Research Agent
Market Research Assistant
Competitor Research Assistant
E-commerce Research Agent
Event Research Assistant
Tourism Research Assistant
Financial Literacy Assistant
Agriculture Information Assistant
Customer Support Research Agent
Technical Documentation Assistant
Job Search Research Agent
Course Comparison Assistant
Multimodal Study Agent
How the capstone works
The capstone gets a dedicated production/planning day. Students then develop it independently and return for review after one week.
Minimum requirements
Solves a real problem.
Has a clear target user and business value.
Can be deployed as a live product.
Has enough functionality to demonstrate the level's skills.
Uses AI meaningfully, not as decoration.
Has a path to monetization, client delivery or portfolio value.
Review after one week
Students present a complete journey from identifying the problem
Product: target customer, problem, value proposition, workflow and adoption/payment rationale.
Your mentor has spent 15+ years architecting enterprise infrastructure and now builds agentic AI for autonomous operations, so your guidance is grounded in real engineering decisions, trade-offs and production experience.
15+ years of experience architecting scalable, secure and automated infrastructure platforms. Specialized in virtualization, cloud automation and agentic AI to drive autonomous operations at enterprise scale.