Cloneable repo (TS + Python)
Both languages. Same architecture. Same eval suite. Pick your side, ship the same agent.
Build an AI automation agency to $10K MRR in 90 days. Niche selection, offer design, outbound, discovery, scoping, pricing, delivery, and the agents you'll resell to clients.
You'll build a production support agent in a weekend. It cites its sources, refuses what it doesn't know, and ships behind a kill switch. The eval set catches the hallucination before the customer does. Median graduate auto-resolves 62% of tier-1 tickets. You will write code; this is not no-code.
Each lesson is a video plus a runnable repo. By the end you have an agent in production, observability wired, eval set running on every PR.
Choose the workflow and define success.
Map the actual agent loop.
Create the instructions and source rules.
Improve quality with real cases.
Prepare the team to use it.
Both languages. Same architecture. Same eval suite. Pick your side, ship the same agent.
Real-world ticket archetypes including the nasty refusals. Add your own in chapter 2.
The 1-page doc that kills bad workflows in a day. Used by every graduate before they write a line of code.
The first 10 minutes of an incident. Tested in two production fires we've shipped through.
"Killed the Zendesk queue I'd been throwing humans at for 18 months. Eval set is the thing I didn't know I was missing."
"Shipped tier-1 in 2 weekends. The refusal patterns chapter is worth the full price by itself."
One email to Deepak. No form. No follow-up. Refunded in 24 hours. The repo permissions are revoked at the same time. That's the deal.
Yes. You can. The course is the six months you'd spend learning what the second draft should have been. Pay for the shortcut or take the long way; both are valid.
The model is the easy part. What you'd be waiting on doesn't change: evals, observability, scoping. Those are the same in 12 months and the same as 5 years ago.
Watch L0 free. If it sounds like the other one, don't buy. If it sounds different, buy. If we're wrong, refund.
Chapter 3 covers the PII guardrail and the deployment patterns for VPC / Bedrock / Azure private endpoints. Patterns are model-agnostic.
Customer support agent template. Repo + eval set.
All 11 modules. 6 agents. The full curriculum.
5 seats. Vertical playbooks. Team bundle.
Most "customer support AI" demos look great in a sales deck. They look different at 2am when a customer is screenshotting your agent confidently inventing a refund policy that doesn't exist.
The hard part isn't the model. The hard part is the system around it: what it's allowed to say, what it has to cite, how it admits ignorance, how you know if it's slowly getting worse. This course is about that system.
If you can ship a support agent that grounds every answer in your real docs, refuses what it doesn't know, and reports its accuracy every day, you've solved 80% of what every customer-facing AI product needs.
The course is built so you can move at one of two paces. Pick the one that matches your week.
No. Repos in TS and Python. The TS version is the path most operators take.
Claude Sonnet by default. Swap to OpenAI / Gemini / local in 5 minutes; the code is provider-agnostic.
Per-resolution cost is about $0.01 on Sonnet with hybrid retrieval. Course materials cover both budgeting and the eval-driven cost regression catch.
Yes. Both adapters included; example wires for the Zendesk REST API + a webhook flow that doesn't require any in-app install.