Jarvis is the north star. The path there includes lots of smaller wins — most people need these before a full assistant.
What "build anything" actually means here
| You can build | Example |
|---|---|
| Tools | Text analyser, content generator, CLI helper on your machine |
| Automations | Monitor a site, draft emails, alert when something changes |
| Websites | Shop site, landing page, own-your-site demos like on /demos |
| Desktop apps | Private "ChatGPT" with your rules — offline-capable |
| Agents | AI that plans steps, uses tools, checks its work (with guardrails) |
| Voice / phone | Receptionist-style workflows (later modules — real cost and compliance) |
You won't build all of this in week one. You will build something real early in the paid path — then stack skills.
How this connects to your toolkit
Your Lesson 11 card says which rented app when for quick jobs today.
The build path says: for jobs you run every week, stop re-prompting in four browsers — own the workflow.
| Today (rented) | Tomorrow (build) |
|---|---|
| Flash-day posts in ChatGPT | Small tool or template you reuse |
| Client email tone in Claude | Assistant that knows your business voice |
| Research report in Gemini | RAG over your files on your machine |
Honest ceiling
- APIs, hosting, domains still cost money when you build
- You're not becoming a career developer — you're learning to direct and ship with AI (the course promise — not a CS career path)
- Red-tier data still doesn't belong in cloud chat — building on your PC is how you fix that for sensitive work
My first ever "build" wasn't Jarvis — it was a scrappy little script that saved me twenty minutes on a Tuesday. Stack up enough of those and the full assistant starts to make sense. Don't sit around waiting for perfect.
Continue — receipts, not hype.