TechByHeart Kochi · AIS

Agentic AI and Automation Specialist

Eight weeks: understand AI, set up a real workshop on your laptop, then ship a website, an AI chatbot and three working apps — no coding needed.

2 months · 8 weeks · 2 stages · No coding required

For: 18+ · job seekers and graduating students — zero coding background

What you'll be able to do

✓No coding needed — build and launch real websites, apps and bots with AI
✓8 weeks, 8 products: site, poster & reel, AI chatbot, CRM, agents, tracker
✓Finish with a live portfolio, a demo video and the CAIS certificate

What it costs, honestly: a Claude Pro subscription (about €20 a month — yours, and it outlives the course), and nothing else — every other tool, including the AI model your Week 7 chatbot runs on, has a free tier or free monthly credit that covers the course. A domain of your own (about €12 a year) is optional.

Ask for a place →

Places are confirmed by TechByHeart. The whole syllabus is below — read it first.

Every module, in order

A clear step forward, every module.

Stage 1

Foundations & First Ships

Meet AI, set up your workshop, and ship your first website and media — weeks 1 to 4.

Week 1 · Meet AI

Lesson 1

What Is AI, Really?

Brilliant — and Confidently Wrong
Software That Learned From Examples
How an AI Model Is Trained
Why Answers Change Every Time
Hallucination: Confidently Wrong
Catch It Lying: The Three-Step Check
Where It's Weak, Precisely
Does It Remember You?
How AI, Machine Learning and LLMs Fit Together
The Companies That Build AI
Why Now, Exactly?
AI Was Already in Your Day
From Passenger to Driver

ShipsA one-line explanation of AI you could tell your family, your three rules for trusting AI, and five interview-ready terms: LLM, knowledge cutoff, hallucination, generative AI, open vs closed models.

Lesson 2

Talk to It & Make Things

The Cover Letter That Said Nothing
Context: What the AI Can Actually See
Context Isn't Just Text
The Four Elements of a Good Prompt
Iterating: Talk Back, Don't Start a New Chat
The Bonus Element — Persona: Give It a Job
How Hard Should It Think?
Make the Job Permanent
Chat Tools and Building Tools
Prompting for Pictures: Subject, Style, Mood, Light
Prompting for Video: The Picture Learns to Move
Your Media Budget

ShipsA weak prompt rebuilt with the four elements — with visibly better output — plus your first AI image set and your first short video.

Lesson 3

Tokens, Limits & Models

The Night Lena's Chat Went Quiet
Claude, Claude Code — and Why This Lesson Comes First
What a Token Is
Your Language Changes the Count
Count Any Line Yourself
Tokens Aren't Only Text
Why Long Chats Slowly Get Expensive
Start Fresh Without Losing the Thread
Your Limit Refills — Like a Daily Data Pack
Limit Hit? The 7pm Kit
App, Model, Plan: Three Different Things
Every AI App Has the Same Three Parts
Choosing the Engine
The Five Habits That Save Tokens
The Lines Lena Types Every Single Time
Your Chats and Your Privacy

ShipsYour fuel card: your token counts in two languages, your engine rule, the hand-over note you'll reuse, the habits you'll keep and your own 7pm-kit move — in your own words.

Week 2 · How Software Actually Works

Lesson 1

How Software Is Actually Built

The Four Parts of Software: Always the Same Shape
The Frontend — Everything You Can Point At
The Backend — The Part You Cannot Point At
Programming Languages: Which One Does Which Job
What an API Actually Is
The Database: Where the Information Lives
One Tap Through All Four Parts
The Development Loop: How Real Teams Make Software
Building With Claude Code: The Same Loop, Fewer People
Debugging: Why These Words Save You Whole Evenings
Next: The Two Halves, Up Close

ShipsThree apps you use daily drawn as four-part diagrams, one tap traced end to end with what breaks at each stop, and the words for every step of the build loop — the vocabulary you will debug in for the rest of the course.

Lesson 2

The Frontend: What the Visitor Sees

HTML, CSS and JavaScript: Three Languages, Three Jobs
The Browser's Inspect Tool: See Any Page's Three Files
Frameworks and Components: The Tools on Top
UI Design Rules: What Separates Good From Merely Working
Loading, Empty and Error Screens: The Three Nobody Builds
Forms People Actually Finish
Speed and Accessibility: Fast and Kind
Design References: Steal Like a Professional
Getting Found, Getting Shared: SEO and the Preview Card
The Two-Minute Page Review

ShipsYour Page Judge report: three real sites put through the two-minute pass — timed on a phone on mobile data, tabbed with no mouse, the heaviest picture found, a loading, empty or broken screen quoted, the WhatsApp card checked — one first fix each, plus a screenshot of a real site's heading changed to your name.

Lesson 3

Backend, APIs & Data

The Backend: Where the Decisions Are Made
Backend Languages: What Each Is Known For
An API Is a Menu
Status Codes: The Number That Comes Back
JSON: The Shape Answers Arrive In
The APIs Your Products Will Call
Webhooks: Being Told Instead of Asking
The Wiring: API, MCP, Connector, Plugin
A Connector at Work: One Question's Trip
Plugins: Several Pieces in One Box
Four Kinds of Database: One for Each Job
Tables, Rows and Keys
Why a Database and Not Just a Spreadsheet?
The Rules of a Backend Worth Trusting
A Real API Reply, Up Close

ShipsYour API Console notes: two real services asked and read properly — the number, the time, the one value a page would show — a 404, a 400 and a 401 caused on purpose, a 429 and a 503 read without causing them, Corner Coffee's customers and bookings tables with a key each and one link, and a Python test script waiting for Week 3 · Lesson 3.

Week 3 · System Design & Your Dev Setup

Lesson 1

System Design & DNS

System Design: One System, Built Brick by Brick
The CAP Theorem: You Get Two of Three
Building Blocks: Five Boxes, Opened Only When It Hurts
Cloud Providers: What the Cloud Actually Sells You
Architecture Habits: Scalable, Secure and Cheap Together
DNS: How a Name Finds Your Site
Six Tool Names Worth Remembering
Next: Your Own Machine

ShipsYour design notes: seven products blueprinted, the one brick that fitted one product and was refused for another, a real website's DNS read row by row — where its site lives, where its mail goes, who answers for its name — and Corner Coffee's site planned at three sizes, starting with an honest "nothing yet".

Lesson 2

Meet Claude Code: Set Up & Explore

Claude Code: The Coding Agent You Will Build With
Before You Start: What You Need Today
Install Claude Desktop: From Download to App
Sign In to Claude: The Account That Has Your Pro
Say Hello: Claude Code Writes Its First File
The Claude Desktop Demo: The App, Corner by Corner
Settings: Every Page, and the Switches to Leave Alone
The Code Tab: Every Button on Claude Code
Project Folders: What “Project” Means in Claude Code
Why Claude Code Spends Faster Than Chat
Claude Code Best Practices: The Habits Before Any Real Job
First Real Job: Clean Your PC
Beyond Downloads: Where the Rest of the Disk Goes
Where Your Space Hides: Six Places on Every Laptop
Your Storage Screen: Where to Look on a Mac and on Windows
The Disk Map: Safe to Clear, Copy First or Leave Alone
Next: Your Work Gets a History

ShipsClaude Code running on your own laptop, your own app checked before the job (Pro plan, usage credits off, Manual mode), and a clean-up report from your first real job — with nothing lost.

Lesson 3

Version Control & How Teams Work

Version Control: The Problem It Solves
Commits: Save Points With a Reason
Branches and Pull Requests: Nobody Edits main
Merge Conflicts: A Question, Not an Error
Git and GitHub: One Tool, Many Hosts
Your GitHub Account: Five Boxes and a Code
A GitHub Repository, Room by Room
GitHub Actions: A Robot That Checks Every Push
Python and Node.js: The Two Engines
The Secrets Rule: Keys Never Get Pushed
Access Tokens: Where a Key Comes From
Push and Pull From Claude Code: The Daily Routine
The README Skill: A Standard That Checks Itself
GitHub Across the Course: What You Will Use Later
Next Lesson: Cloud Accounts

Shipshello-skillkraft, public on your GitHub: a history of commits with real notes, a pull request you merged, a conflict you answered, and a protected main — checked live.

Week 4 · The Cloud & Your First Ship

Lesson 1

Cloud Accounts & Where Software Lives

The Cloud: Somebody Else's Computer, in a Real City
Deploy: The Moment Your Code Goes Live
Cloud Accounts: Every Service Is an Appliance on Your Meter
Free Tiers: What “Free” Really Means
Regions: The City Your Code Sits In
Account Security: Four Switches on Day One
The Google Cloud Console: A Guided Tour
Your Account Map: Who Holds What
Next Lesson: Directing Claude Code

ShipsThe accounts this course runs on, opened and hardened: two-step on, recovery codes safe, a budget alert armed, regions chosen on purpose and written down, six Google Cloud console jobs practised, and a private account map in your password manager (only its summary with no emails is shared).

Lesson 2

Directing Claude Code: Build What You Meant

Directing Claude Code: Same Tool, Two Different Pages
The Brief: A Five-Line Prompt That Stops the Guessing
Your Calls and Its Calls: What a Brief Must Decide
Handing Over Context: What Claude Code Can and Can't See
Done Checks: Say What Finished Looks Like
Plan Mode: Nothing Changes Until You Approve
Claude Code in the Desktop App: A Guided Tour
Slices: Build a Little, Check, Save, Repeat
CLAUDE.md: The Memory File for Your Project
Markdown (.md): The Four Files Every Project Keeps
Undo: Two Ways Back When a Change Goes Wrong
Reading the Diff: Check Every Change Before You Keep It
Proof of Done: Ask for Evidence, Not Promises
Context Hygiene: Keep the Conversation Clean
From Repeated Brief to Skill: Save a Job You Keep Asking For
Next Lesson: Ship Your First Website

ShipsAn about-me page on hello-skillkraft that you directed: a five-line brief, a CLAUDE.md, an approved plan, three slices with a commit each, two undo drills, and a director's report with your proof.

Lesson 3

Ship Your First Website

A Website: A File a Browser Draws
The Request Journey: How a Visitor Reaches Your Site
Deploying: From Localhost to a Link Anyone Can Open
The Ship Loop: Six Steps You'll Repeat for Every Site
Website Styles: Name the Look You Want
Website Imagery: Six Honest Options
Your Project Folder: One Folder, One Product
The Starter Brief: Describe It Once, Well
Reviewing the Preview: Worst Problem First
Iterating: Symptom, Then the Change You Want
Your Repo: The Project's Copy on GitHub
Free Hosts: Which One Can Receive Your Form?
Push, README, Deploy: What the Host Does
The Netlify Dashboard: A Guided Tour
The Phone Test: Shipped Means a Stranger Can Use It
Website Traffic: Where Visitors Come From
Conversion: The Three-Second Test
Feedback: Show It to One Person Tonight
Next Lesson: Media Models & Script Craft

ShipsA live website at a real URL you can text to anyone, with a working form, plus a public repo that meets the README standard.

Stage 2 · CAIS

Products & Launch

Media and a brand that brings customers, one real web app with a CRM behind it, an AI chatbot, agents and automations, what the cloud charges and how it gets broken into, then your capstone — weeks 5 to 8.

Week 5 · The Creative Studio

Lesson 1

Media Models & Script Craft

Media Models: Six Credits, Zero Reel
Three Machines, Three Jobs
Makers and Workshops: The Names Worth Knowing
A Video Is 120 Guesses in a Row
Carved Out of Noise: Why Words Go On Top
Write the Script Before You Spend Anything
The Hook: The First Second Does Half the Work
Shot Sizes: The Camera Words for Your Shot List
Posters That Work From Across the Street
Four Tells of Fake-Looking AI Video
Choose One Voice and Keep It
Script First: Lena's Second Try
Media Craft: Three Things to Remember
Video Credits: Your Budget This Week
Next Lesson: Make the Poster & the Reel

ShipsA two-column script with a shot list for a real subject, plus one chosen ElevenLabs voice you'll keep for everything.

Lesson 2

Make the Poster & the Reel

Poster and Reel: A Poster You Have to Squint At
The Poster: Art First, Words After
Type the Message Yourself
The Reel: Stills First, Then Movement
Ask for One Gentle Motion
The Editing Screen in Three Words
Two Habits From the Cutting Room
Captions and Voice Go On Last
Four Checks Before Anything Goes Out
Put Both on Your Site
Art First: Lena's Second Try
Paid Work: What You Just Learned to Charge For
Poster and Reel: Three Things to Remember
Video Credits: What Today Costs
Next Lesson: Brand & Social

ShipsA print-ready poster and a 15–30 second voiced reel, both live on your website.

Lesson 3

Brand & Social: Turn Your Media Into Customers

Brand: The Promise Customers Recognise
The Brand Kit: Five Things on One Board
Building the Brand Kit With AI in One Hour
Social Commerce: Where Your Customers Actually Are
Content Pillars and the 30-Day Calendar
Repurposing: One Reel, Ten Posts
The Scroll-Stopping Post: Hook, Call to Action, Timing
Social Media Automation: Let AI Do the Busywork
The Funnel: Reading the Numbers From Reach to Orders
Boosting a Post: The €20 Test
Honest Marketing: What's Allowed in Europe
Personal Branding: LinkedIn for Job Seekers
Pricing a Social Media Package
Next Lesson: Web App with CRM

ShipsA brand kit for a real business (name line, three colours, two fonts, a logo mark, a voice guide) saved in Canva, a 30-day content calendar, one reel turned into three more posts, a WhatsApp Business profile with a catalogue item and quick replies, the first post scheduled, and your own work posted on LinkedIn — plus, a week later, one number you read and one change you made because of it.

Week 6 · Web App with CRM

Lesson 1

Web App with CRM · Database to Frontend

Database to Frontend: Two Guests, One Table
Static or Dynamic: Does It Remember?
Your Stack: The Four Parts Get Real Names
The Real Build: A Restaurant That Takes Its Own Bookings
The Bookings Table: Columns Come From Questions
Caching: How Fresh Does Each Copy Need to Be?
The Booking's Trip: Write the Row First
Debugging the Trip: Four Places One Click Can Break
The Reference and the Token: Letting a Guest Back In
Resend: Email Your Product Sends Itself
API Keys: Your Laptop, Vercel, Never the Repo
The Vercel Dashboard: A Guided Tour
Immersive Scroll: The Face a Client Pays For
Spam Bots: A Public Form Meets the Public
The Spec: Four Answers You Write Yourself
Plan Mode: Judge the Plan Before Any Code
The Customer Walkthrough: Verify Like a Customer
Row First: Lena's Second Saturday
Database to Frontend: Three Things to Remember
Next Lesson: Web App with CRM · The Client's Back Office

ShipsA live site for a real business that takes and stores enquiries, emails the customer back, and looks like work somebody commissioned.

Lesson 2

Web App with CRM · The Client's Back Office

Follow-Ups: Who Did I Promise to Call Back?
Front Door, Back Office: One App, Two Doors
CRM: Three Lists That Point at Each Other
Sheet or Back Office: One Shows, One Works
The Back Office Screen: Three Parts, One Number
Authentication: What a Login Actually Is
The Privacy Test: A Stranger, Logged Out
Production Quality: Fail Politely, Leave a Trail
The Door Policy: Spec the Doors Before You Build
Building in Slices: Lock First, Chart Last
The Walkthrough: Prove It From Your Phone
The Handover: The Part Nobody Teaches
Follow-Up Done: Lena Hands Over the Keys
The Client's Back Office: Three Things to Remember
Your Portfolio Shelf: Three Products, One Address
Next Lesson: Build Your AI Chatbot

ShipsA working CRM behind a real login, on the same pipeline as the site — leads list, mark-as-handled, one honest chart, an export button, and a handover the owner can actually run.

Week 7 · Agents & Automation

Lesson 1

Build Your AI Chatbot

AI Chatbot: A Website That Talks Back
The Chat Widget: Two Parts in the Page, One Behind It
The Job Description: Rules a Bot Never Forgets
Rules That Hold: Exact Words Beat Virtue Words
Pasting Everything: Why It Stops Working
Grounding and RAG: Facts Before the Model Speaks
The Index: Cutting Your Pages Into Pieces
Embeddings: A Map Where Meanings Sit Close
Hybrid Search: Meaning Plus Keywords
The Fact Sheet: When Answers Come Out Thin
Hugging Face: Renting the Brain Per Answer
The Token: A Secret That Never Touches the Page
Code Checks: The Prompt Asks, the Code Makes Sure
The Message Tool: From Answering to Doing
Testing: Attack It Yourself, Then Hand It to a Stranger
Failed Tests: Fix the Content, Never the Check
Back to Omar: Asked at 11pm, Delivered to Alfama
AI Chatbot: Four Numbers to Remember
Next Lesson: Agents, Revealed

ShipsA live AI receptionist on the student's own site — it searches the business's own pages, answers only from them with sources, holds its rules under attack, takes a message for the owner that lands in the CRM only when the visitor taps Send, and keeps the token out of the page.

Lesson 2

Agents, Revealed

Leads at Corner Coffee: 14 Messages, One Big Order
Agents vs Chatbots: One Answers, One Finishes
The Agent Loop: Plan, Act, Check, Repeat
Tools and Skills: The Agent's Hands, Leash and Backpack
Subagents: The Agent That Hires Help
Agents in the Wild: The Ones You Already Meet
Claude Cowork: The Second Agent You Already Own
Session Memory: What an Agent Remembers
Stuck Loops: When the Agent Goes in Circles
The Honest Rule: When an Agent Is Overkill
Lead Triage: The Agent You Build Today
Visual Automation: The Loop, Drawn as Boxes
Session Logs: Read One Like a Manager
The Claude Agent SDK: The Kit Behind Claude Code
Open-Model Agents: Run the Loop Yourself
Lead Triage, Done: Omar Gets His Call
Agents: Three Things to Remember
Next Lesson: Automation — Work That Runs Itself

ShipsA lead-triage agent you designed and ran in Claude Code — every lead sorted hot, warm or cold with a reason, reply drafts that had to ask before they were written, one reply you sent yourself, and the run's log labelled beat by beat. Plus your form feeding a Make scenario, and your first Cowork document.

Lesson 3

Automation: Work That Runs Itself

Automation: 6:50, and One Order Missing
Anatomy of an Automation: Trigger, Steps, Result, Check
Triggers: The Clock, an Event, or Your Own Hand
Automation Tools: Two Families
Choosing the Tool: Judgement, or Exactly the Same?
The Brief: Six Answers Before You Build
Scheduled Tasks: Claude on a Timetable
Scheduled Task Setup: Corner Coffee's Morning Orders
Draft, Don't Send: Trust Is Earned One Message at a Time
Safe to Repeat: What If It Runs Twice?
Silent Failure: When Automations Break, Nobody Hears It
Failure Alarms: Make Failure Loud
Selling Automations: What Small Businesses Pay For
Run Costs: Every Run Spends Something
Automation at Work: Lena's First 6:30 Run
Automation: Three Things to Remember
Next Lesson: Your Agentic Job Tracker

ShipsA Claude scheduled task with a written six-answer brief, tested by hand twice before it got its timetable, that drafts and never sends. Plus a Make flow — form → Google Sheet row → email — with a filter, broken once on purpose and fixed, and one line from each run history.

Week 8 · Projects, Cost & Launch

Lesson 1

Your Agentic Job Tracker

Job Tracker: Twenty-Three Applications, One Missed Follow-Up
Pipeline Stages: Build for the Customer You Know Best
Follow-Up Rules: Most Applications Die of Silence
Tracker, Agent, Clock: Where Your Agent Gets a Real Job
Scheduled Jobs: Code That Runs on a Clock
Cron Lines: Five Fields, in Plain Words
The Morning Brief: Rules Find, the Model Writes
Tracker Pro: Pick Your Features
Backups: Your Data Is Real Now
Staging: Don't Experiment on the Tool You Depend On
Dogfooding: Use What You Build, Daily
The 7:00 Email: Lena's First Calm Monday
The Job Tracker: Three Things to Remember
Next Lesson: Cloud Cost & Security

ShipsA deployed tracker you will actually use — pipeline, contacts, stats — with an agent that reads it every morning and sends you the short list of what needs doing, and a CSV backup habit started.

Lesson 2

Cloud Cost & Security

Cost and Security: Two Bills in One Week
The Google Cloud Console: Your Account's Control Room
The Four Meters: Reading a Real Cloud Bill
Billed for Existing: What Counts While You Sleep
FinOps: Five Habits That Keep the Bill Small
Budget Alerts: A Tripwire, Not a Wall
Break-ins: Every Open Door Started as a Shortcut
Leaked Keys: One Revoke Kills Every Copy
Least Privilege: The Smallest Job, the Smallest Blast
Service Accounts: Make the Sheet Robot Properly
AWS and Azure: Same Moves, Different Names
The Account Audit: A Monthly Round Before Launch
A Calm Control Room: Lena's Last Check Before Launch
Cost and Security: Three Things to Remember
Next Lesson: Launch Day — Ship Your Own Product

ShipsA cost-and-vulnerability board for your own cloud account, kept private: what you run, what it costs, and the doors you found open and closed. You share only its summary: the doors you closed, and a count of the rest.

Lesson 3

Launch Day: Ship Your Own Product

The Capstone: Writing the Prompt Is the Test
Bring Your Own Idea: Three Checks Before Any Tokens
Capstone Rules: Your Past Repos Are the Library
The Portfolio: Eight Products, Proven Honestly
The Demo Film: One Minute of Real Screens
The Pitch: Sixty Seconds, Out Loud
Launch-Ready: What Public Products Carry
The Certificate: A Human Checks Your Work
Your First Client: Where to Look, What to Charge
The Case Study: One Honest Story, Four Uses
Launch Day: Three Things to Remember
After the Course: The Loop Keeps Running

ShipsYour capstone, your portfolio updated to all eight products (five live links, three honest proof cards), a one-minute demo film, your pitch and a case study — sent for CAIS review.

Ready to start?

Ask for a place