Your path through the academy

Agentic AI Automation Academy

A beginner-friendly academy for building safe agentic AI automation service offers with Claude Code, Codex, OpenClaw lab demos, templates, and a final project.

11guided modules
41implementation lessons
17student downloads
2free preview lessons
1

Start with the open lessons

Use the two free lessons to understand the service map and safe demo shape.

2

Work module by module

Open one lesson, finish the action panel, save the proof note, then continue.

3

Package one offer

Turn the saved proof into a scoped first paid-service conversation.

Objective

Each module states what the student should be able to explain, build, or decide.

Practice

Lessons point toward a concrete demo, workbook entry, package, sales asset, or delivery step.

Proof

Checkpoints and final-project artifacts make progress visible before the student moves on.

Learning path

Modules, proof points, and lesson access

Module 1

Free Preview

Use two complete lessons to map a buyer workflow and sketch a safe demo before deciding whether to enroll.

2 lessons2 available
Outcome

You will build a first service map: one business type, one repeated workflow pain, one safer assistant output, one human approval boundary, and one plain-English offer sentence.

Module proof

Your fake inquiry, demo output shape, safety note, and one-sentence business explanation.

Recall check

Without rereading, write the main decision, artifact, or boundary you can now explain from Free Preview.

Module 2

Start Here

Choose a first-offer goal, learn the course rhythm, and start the artifact trail that becomes your final project.

1 lesson0 available1 paid
Outcome

You will understand the course path, the workbook, and the final project before you start.

Module proof

Your rough Final Project Snapshot.

Recall check

Without rereading, write the main decision, artifact, or boundary you can now explain from Start Here.

Module 3

Agentic AI Service Foundations

Understand what a buyer is paying for, how the tool stack supports the work, and where safety and client-trust boundaries begin.

3 lessons0 available3 paid
Outcome

You will describe your agentic AI automation service in business language.

Module proof

Your safety boundary and client trust sentence.

Recall check

Without rereading, write the main decision, artifact, or boundary you can now explain from Agentic AI Service Foundations.

Module 4

Claude/Codex Setup And OpenClaw Lab

Prepare the tools, verify a local lab, build a fake-data demo, troubleshoot it, and document a client-safe boundary.

12 lessons0 available12 paid
Outcome

You will explain OpenClaw in beginner language and understand the setup path.

Module proof

A short checkpoint note naming the completed proof, any blocker, and the artifact you will carry into the final project.

Recall check

Without rereading, write the main decision, artifact, or boundary you can now explain from Claude/Codex Setup And OpenClaw Lab.

Module 5

Choose A Sellable AI Service

Compare beginner-friendly offers, choose a reachable niche, and identify one repeated workflow worth improving.

3 lessons0 available3 paid
Outcome

You will choose a realistic beginner offer.

Module proof

Workflow pain map.

Recall check

Without rereading, write the main decision, artifact, or boundary you can now explain from Choose A Sellable AI Service.

Module 6

Build Your First Agentic AI Systems

Build lead, inbox, FAQ, and reporting assistants, then turn the strongest result into a reviewable demo portfolio.

5 lessons0 available5 paid

Module 7

Package And Price The Service

Define deliverables and exclusions, practice a starter price, write a simple proposal, and pass the package checkpoint.

4 lessons0 available4 paid
Outcome

You will package your demo as a bounded beginner service.

Module proof

A short checkpoint note naming the completed proof, any blocker, and the artifact you will carry into the final project.

Recall check

Without rereading, write the main decision, artifact, or boundary you can now explain from Package And Price The Service.

Module 8

Sell The Agentic AI Offer

Build a focused prospect list, write honest outreach, run discovery, and handle objections without risky promises.

4 lessons0 available4 paid
Outcome

You will build the first outreach list.

Module proof

Objection response sheet.

Recall check

Without rereading, write the main decision, artifact, or boundary you can now explain from Sell The Agentic AI Offer.

Module 9

Delivery, Handoff, And Next Offers

Onboard, test, hand off, support, identify a sensible next offer, and assemble the final buyer-readable project.

5 lessons0 available5 paid

Module 10

Optional: Client Apps, Hosting, And Domains

An optional path for turning a proven workflow into a small client app. Students describe the buyer result while Codex handles Supabase, the app build, Vercel hosting, and later domain setup under human approval.

5 lessons0 available5 paid

Module 11

Optional: Faceless YouTube Service Workflow

An optional money path for using Codex to research original topics, create reviewed production packets, organize a client dashboard, and sell a bounded service without promising views or monetization.

4 lessons0 available4 paid

Keep it simple

One lesson, one artifact, one next step.

The course contains a lot of support material, but the path stays simple: open the next lesson, follow the start panel, save one buyer-readable proof note, and keep moving.

Go to next lesson
Optional guidanceBuyer path, tool guide, and starter offersOpen this after you choose a module or when you need help packaging the work.

Learning experience

Built like a guided apprenticeship, not a video dump.

The academy uses practice-first lesson design, visible progress, artifact checkpoints, and screenshot-backed agent workflows so beginners always know what to do, what to save, and what not to overpromise.

First-week momentum

Start with small practice loops

The first lessons ask for short, concrete work: a service map, fake-data demo sketch, setup note, and first evidence artifact.

Artifact-based lessons

Every lesson produces proof

Students save a decision, checklist, test note, demo output, proposal section, or handoff artifact that feeds the final project.

Visible progress

The app always shows the next move

Dashboard progress, module proof points, lesson checkpoints, and completion states reduce uncertainty while the student works.

Claude + Codex workflow

Agents are taught as operating skills

Claude Code and Codex sit at the center: explore, plan, implement, review, test, document, and keep the human in control.

Screenshot-backed learning

Visual proof beats tool hype

OpenClaw remains the practical lab for selected demos, supported by owner-created screenshots, safe captures, and official source notes.

Accessible review

Readable, repeatable lesson structure

Each lesson uses the same brief, mission, workbench, resource kit, reading, and completion flow so students can scan instead of hunt.

Clarity loop

Confusion gets captured before completion

Lessons end with a final clarity check that asks students to explain the move, verify the proof, and route precise blockers to support.

Commercial course map

How the modules become a first paid offer.

The academy is organized as a project-based path: students choose a buyer pain, use Claude Code and Codex to build reviewable proof, use OpenClaw for safe lab evidence where useful, and turn the work into one small scoped offer.

Buyer workflow

Every module names the operational result a buyer can understand before tools are discussed.

Agent proof

Claude Code plans context and Codex inspects artifacts, tests, docs, and handoff quality.

Safe offer

Proof stays scoped, fake-data friendly, human-approved, and clear about what is not promised.

01Inspect

Free Preview

See the service category and test whether agentic AI automation is worth learning before paying.

Claude/Codex move
Use Claude Code for the service map and Codex for a quick review of what the demo must prove.
Proof to save
Service map and first sellable demo sketch
Money action
Name one workflow a small business might pay to have inspected, cleaned up, or automated.

OpenClaw appears as optional lab proof, not the only way to learn the commercial skill.

Open module
02Orient

Start Here

Set the working rhythm: one lesson, one artifact, one buyer-readable proof point.

Claude/Codex move
Use Claude Code to plan the lesson outcome and Codex to check the saved artifact for gaps.
Proof to save
Course-use plan and artifact habit
Money action
Choose the weekly cadence that gets a real offer artifact finished instead of collecting notes.

Keep OpenClaw as the fake-data lab where risky claims can be tested safely.

Open module
03Position

Agentic AI Service Foundations

Understand what buyers actually buy: clearer workflows, faster follow-up, safer handoff, and usable proof.

Claude/Codex move
Use Claude Code to compare service angles and Codex to pressure-test the operational steps.
Proof to save
Buyer pain, trust boundary, and service map
Money action
Pick the smallest credible service result you can explain without income promises.

Use OpenClaw examples only where a fake-data automation lab makes the value concrete.

Open module
04Set Up

Claude/Codex Setup And OpenClaw Lab

Create a working agentic AI lab so future demos can be shown safely and repeatably.

Claude/Codex move
Use Claude Code for setup planning and troubleshooting notes; use Codex to inspect commands, docs, and setup proof.
Proof to save
Working lab, setup receipts, and first safe demo
Money action
Turn the setup into proof that you can configure, test, and explain a client-safe workflow.

OpenClaw is the controlled demo environment for screenshots, fake-data workflows, and setup confidence.

Open module
05Choose

Choose A Sellable AI Service

Select a niche, painful workflow, and service lane that can be sold as a small scoped pilot.

Claude/Codex move
Use Claude Code to compare niches and Codex to inspect the workflow for missing data, permissions, and handoff steps.
Proof to save
Niche choice, painful workflow, and offer angle
Money action
Write the first buyer-safe offer sentence with a narrow result and clear exclusions.

Use OpenClaw only when it helps demonstrate the selected workflow with fake data.

Open module
06Build

Build Your First Agentic AI Systems

Create small demos for lead follow-up, inbox triage, FAQ support, reporting, and portfolio proof.

Claude/Codex move
Use Claude Code to design each workflow and Codex to review outputs, edge cases, test notes, and reusable assets.
Proof to save
Demo portfolio with tests and captions
Money action
Pick the strongest demo and translate it into a paid pilot conversation.

OpenClaw supplies the lab workflows and screenshots while student-facing claims stay grounded in fake-data proof.

Open module
07Package

Package And Price The Service

Turn the strongest demo into deliverables, scope, price logic, review boundaries, and a simple proposal.

Claude/Codex move
Use Claude Code to shape the package and Codex to inspect proposal clarity, missing risks, and handoff steps.
Proof to save
Package, price notes, and simple proposal
Money action
Prepare the first scoped offer without promising revenue, savings, or fully autonomous decisions.

Use OpenClaw screenshots as supporting proof only when they make the package easier to trust.

Open module
08Sell

Sell The Agentic AI Offer

Start honest conversations with prospects using proof, discovery questions, and a low-pressure next step.

Claude/Codex move
Use Claude Code to adapt outreach to buyer context and Codex to inspect scripts for hype, vagueness, and unsafe claims.
Proof to save
Prospect list, outreach script, discovery notes, and objection answers
Money action
Ask for one review call or paid pilot conversation, not a broad automation transformation.

Use OpenClaw lab proof as a demonstration aid only after the buyer pain is clear.

Open module
09Deliver

Delivery, Handoff, And Next Offers

Onboard, test, hand off, and identify the next safe offer after the first project is delivered.

Claude/Codex move
Use Claude Code to prepare handoff docs and Codex to inspect test coverage, risks, and acceptance notes.
Proof to save
Client onboarding, test notes, handoff, and final project
Money action
Use delivery proof to propose the next small improvement only after the first scope is reviewed.

Keep OpenClaw as the demo/control environment while client work uses approved tools, data, and human review.

Open module
10Step 10

Optional: Client Apps, Hosting, And Domains

An optional path for turning a proven workflow into a small client app. Students describe the buyer result while Codex handles Supabase, the app build, Vercel hosting, and later domain setup under human approval.

Claude/Codex move
Use Claude Code for planning and Codex for inspection, testing, or reusable assets before saving proof.
Proof to save
Saved module artifact
Money action
Translate the module output into one buyer-safe next step.

Use OpenClaw only when a fake-data lab makes the lesson proof clearer.

Open module
11Step 11

Optional: Faceless YouTube Service Workflow

An optional money path for using Codex to research original topics, create reviewed production packets, organize a client dashboard, and sell a bounded service without promising views or monetization.

Claude/Codex move
Use Claude Code for planning and Codex for inspection, testing, or reusable assets before saving proof.
Proof to save
Saved module artifact
Money action
Translate the module output into one buyer-safe next step.

Use OpenClaw only when a fake-data lab makes the lesson proof clearer.

Open module

This commercial map is a work path, not an income claim: students build scoped proof, use fake data where needed, keep humans in approval, and make careful buyer-safe offers.

Market proof board

Students learn the tools buyers are already curious about.

The course should feel like an investment in marketable agentic AI skills: Claude Code for planning and buyer language, Codex for build/review/test evidence, and OpenClaw for selected fake-data lab proof.

$49.99 into a proof stackNo income promise. The point is to leave with assets a buyer can inspect.
Official Claude Code desktop workflow screenshot from Anthropic showing parallel coding tasks.Official Anthropic product image

Claude Code

Claude Code turns messy buyer problems into a plan.

Use Claude Code to read the workflow, clarify the buyer pain, define the safe scope, and turn the idea into language a prospect can understand.

Proof students build

Buyer workflow map, safe scope note, and first offer sentence.

Official Codex app screenshot from OpenAI showing a project sidebar, active thread, and review pane.Official OpenAI Codex app image

Codex

Codex turns the plan into reviewable delivery evidence.

Use Codex to create, inspect, test, and document the implementation so a buyer sees more than a prompt: they see a deliverable with checks.

Proof students build

Prototype note, test evidence, review summary, and handoff checklist.

Academy-owned OpenClaw gateway dashboard check used as a clean lab proof example.Academy-owned lab capture based on OpenClaw docs

OpenClaw

OpenClaw makes selected demos visible in a fake-data lab.

Use OpenClaw when a visible dashboard or gateway run makes the Claude/Codex plan easier to trust without exposing client data.

Proof students build

Sanitized lab screenshot, source note, approval boundary, and no-live-data disclaimer.

Official screenshots are references, not endorsements. Paid course screenshots should be owner-captured, source-noted, scrubbed, and kept private unless explicitly approved for public use.

Proof standards and screenshot sourcesOptional buyer trust review

Visual evidence roadmap

Screenshots should become buyer proof, not tool hype.

Every lesson has a planned screenshot, owned visual, or diagram target so students can show what Claude Code, Codex, and OpenClaw helped them inspect, build, verify, or safely demo.

48/48lessons mapped to visual proof
29official references
21clean demo screenshots
45owned/diagram paths
38high-priority proof points

Start from a trusted source

Use official Claude Code, Codex, or OpenClaw references as context.

Capture one lesson action

Show one plan, review, demo output, or decision students can repeat.

Scrub private context

Hide keys, emails, customer names, paths, billing, repositories, and tokens.

Caption it for a buyer

Name the workflow pain, proof, approval point, and boundary.

high

Build Your First Sellable Demo

Students understand what a safe demo output looks like before connecting any real account.

Agentic AI Automation Academyacademy-ownedAcademy generated or owner-created democourse diagram
Open visuals
high

The Agentic AI Service Map

A beginner can see exactly how a vague AI-agent idea becomes one narrow service offer.

Agentic AI Automation Academyacademy-ownedAcademy generated diagramcourse diagram
Open visuals
high

Build The Faceless Production Workflow In Codex

Students understand Codex as the production command center for documents, checklists, review, and optional app/dashboard scaffolding.

Academy generated diagramcourse diagramOpenAIofficial reference
Preview lesson

Use official web sources as references, owner-created captures for course proof, and generated diagrams when a real screenshot would leak private data or distract from the buyer-facing workflow.

29official reference mappings for source notes and current workflow language.
21clean fake-data screenshots marked for owner capture before publishing.
45owned diagrams used when real screenshots would leak private context.
48/48lessons mapped to a visual proof plan in the course media catalog.

The full source trail is maintained in the visual catalog and lesson-level proof panels. Official references are not endorsements; production lesson media should be academy-owned, source-noted, and scrubbed before paid-course use.

Tool tracks

Choose the path that matches why you came here.

Claude Code and Codex are the primary operating skills. OpenClaw stays visible as the applied lab where selected automation proof becomes concrete.

Buyer category

Agentic AI service path

Map one painful workflow into one safe buyer-readable service offer.

Start
Free service map lesson
Proof
Workflow map, approval boundary, service artifact.
Money angle
Sell the outcome before naming the tools.
Primary operator skill

Claude Code path

Use Claude Code for orientation, setup reasoning, planning, checks, and implementation notes.

Start
Setup basics lesson
Proof
Setup note, blocker log, checked commands.
Money angle
Show inspected work, not a magic-button promise.
Primary build/review skill

Codex path

Use Codex for implementation, review, tests, docs, and reviewable demo evidence.

Start
Free sellable demo lesson
Proof
Review checklist, test log, docs note.
Money angle
Turn build quality into a scoped offer.
Applied lab proof

OpenClaw lab path

Use OpenClaw as the visible gateway and dashboard lab for selected fake-data demos.

Start
Gateway orientation lesson
Proof
Gateway check, dashboard proof, safe screenshot.
Money angle
Make the service concrete without live-risk promises.

Agentic stack

Market the whole agentic AI stack, not just one tool.

The academy leads with Claude Code and Codex as the coding-agent operating skills students can market, then uses OpenClaw as a practical automation lab where selected workflows become visible proof.

Market language

Agentic AI services

Students learn to sell workflow improvement: one painful process, one useful assistant output, one human approval point.

Primary coding-agent workflow

Claude Code

Claude Code is taught as a core operating skill for reading codebases, planning changes, fixing errors, running checks, and reviewing diffs under user control.

Primary coding-agent workflow

Codex

Codex is taught as a core build, review, testing, documentation, and multi-agent workflow skill for turning ideas into inspected software changes.

Applied automation lab

OpenClaw

OpenClaw stays in the course as a practical lab surface for selected workflow demos, gateway checks, dashboard evidence, and channel decisions.

Starter offer menu

Five starter offers students can build toward without promising outcomes.

Use these as concrete paths through the lessons: each offer starts with a buyer pain, turns Claude Code and Codex work into proof, and uses OpenClaw only when fake-data lab evidence makes the service easier to trust.

Buyer pain first

Start from a repeated workflow pain a business owner can recognize without tool vocabulary.

Claude Code plans

Use Claude Code for workflow logic, scope, buyer language, and approval boundaries.

Codex inspects

Use Codex to review artifacts, tests, templates, documentation, and handoff quality.

Proof stays safe

OpenClaw proof is fake-data lab evidence, never a claim of guaranteed client results.

Local service owner with missed web, SMS, or email leads

Lead follow-up pilot

Good leads arrive, but replies are slow, inconsistent, or too hard to inspect.

Starter paid scope
Map the follow-up workflow, draft safer reply logic, test fake examples, and hand over a review checklist.
Proof to build
Before/after lead reply demo, approval boundary, test notes, and one buyer-readable proof screenshot.
Paid ask
Ask for a small paid workflow review or pilot after showing the fake-data proof and exclusions.
Claude Code

Use Claude Code to plan the lead journey, edge cases, approval rules, and plain-language service promise.

Codex

Use Codex to inspect the follow-up artifact, test cases, reusable checklist, and handoff notes.

OpenClaw

Use OpenClaw only as a fake-data lab run when a visible follow-up demo makes the workflow easier to trust.

No automatic live sending, no client-result guarantee, and no private lead data in screenshots.

Open first proof lesson
Founder, ops lead, or support owner drowning in repeated messages

Inbox triage cleanup

Important requests get buried because inbox categories, urgency, and handoff rules are unclear.

Starter paid scope
Document the inbox categories, draft triage rules, test sample messages, and create a human-review handoff.
Proof to build
Triage matrix, fake inbox examples, risk notes, and a handoff checklist a buyer can inspect.
Paid ask
Ask for a paid inbox workflow audit or first-pass triage setup with human approval kept in place.
Claude Code

Use Claude Code to clarify the buyer categories, approval points, escalation risks, and exclusion list.

Codex

Use Codex to review the triage checklist for missing states, unsafe assumptions, and reusable structure.

OpenClaw

Use OpenClaw as a controlled channel demo only when fake messages can prove the rule set safely.

No live inbox access in early proof, no hidden automation, and no promise that every message will be handled.

Open first proof lesson
Course creator, SaaS founder, or service business with repeated support questions

FAQ support assistant

The same answers are rewritten manually, but the team cannot risk inaccurate or overconfident replies.

Starter paid scope
Collect repeated questions, draft answer boundaries, test answer quality, and create a review-ready support sheet.
Proof to build
FAQ map, answer-quality rubric, unsafe-answer examples, and a support handoff note.
Paid ask
Ask for a paid FAQ cleanup sprint or support-response prototype, not a promise of autonomous support.
Claude Code

Use Claude Code to turn messy support questions into answer rules, tone constraints, and reviewer prompts.

Codex

Use Codex to inspect the FAQ asset, edge cases, missing disclaimers, and implementation checklist.

OpenClaw

Use OpenClaw lab proof only if a fake support conversation helps demonstrate review flow.

Agency owner, operator, or manager who needs clearer recurring updates

Weekly report pack

Weekly updates take too long and still miss decisions, blockers, or next actions.

Starter paid scope
Design a report template, define inputs, test example outputs, and prepare a review checklist.
Proof to build
Report outline, sample weekly summary, source checklist, and buyer review questions.
Paid ask
Ask for a paid reporting-template setup or first monthly reporting sprint after the buyer approves inputs.
Claude Code

Use Claude Code to define the report narrative, audience, decision points, and questions for missing context.

Codex

Use Codex to inspect the template, calculations or source notes, formatting consistency, and repeatability.

OpenClaw

Use OpenClaw only if a fake workflow run makes the recurring-report path visible.

No hidden data scraping, no unverifiable metrics, and no claim that reports prove business growth.

Open first proof lesson
Small team that wants AI help but does not know what is safe to automate first

Workflow proof audit

The team has tool interest, but no clear workflow, approval boundary, or proof that a pilot is safe.

Starter paid scope
Interview the workflow, map the risk boundary, create one fake-data proof, and recommend the first small pilot.
Proof to build
Service map, safety boundary, demo evidence board, and a one-page pilot recommendation.
Paid ask
Ask for a paid audit and pilot recommendation before offering implementation work.
Claude Code

Use Claude Code to plan discovery questions, summarize workflow pain, and critique the pilot scope.

Codex

Use Codex to review the evidence board, documentation, missing risks, and reusable audit checklist.

OpenClaw

Use OpenClaw as one proof source only if a dashboard or fake-data run helps the audit feel concrete.

No broad transformation promise, no live-data testing, and no revenue or client acquisition guarantee.

Open first proof lesson

These are practice-to-offer paths, not income claims. Students should sell scoped audits, setup help, templates, and fake-data demos only after the buyer understands the boundaries.