# Expertron AI Agent Mastery — source-based adaptation brief

## Approved direction
Use the supplied mentor materials as the teaching foundation, preserving concepts and day sequence while expressing them in Expertron's voice. User states mentor has permitted reuse. Do not substitute an unrelated curriculum. Do not transfer the mentor's personal claims, testimonials, cohort dates, agent deployments or commercial guarantees to Expertron.

Standalone site: aiagentmastery.expertronhq.com. Landing page at /; login, dashboard, daily lessons, replays, resources, assignments and progress stay on this subdomain. Do not route learning to academy.expertronhq.com.

## Reviewed sources
- Day 1 Foundations: /root/.hermes/cache/documents/doc_c27841936b16_AI_Agents_Mastery_Day1_Foundations.pptx
- Day 2 Build: /root/.hermes/cache/documents/doc_54e7bf0ee235_AI_Agents_Mastery_Day2_Build.pptx
- Day 3 Monetise & Implement: /root/.hermes/cache/documents/doc_d11688575f51_AMM_Day3_Monetise_Implement.pptx
- Workflow reference PDF: /root/.hermes/cache/documents/doc_3f6202ca2c44_AI_Agents_Mastery_VIP_50_Workflows_Resource.pdf
Review scope: extracted slide text, supplied speaker notes and PDF text. Visual layouts and embedded graphics have not been audited. Slide decks guide live demos; they do not contain a full technical installation manual.

## Day 1 — Understand agents and delegate effectively
Source: Foundations slides 1–25.
Preserve: using AI vs directing a system; AI, agents, workflow and cron vocabulary; goal/context/reasoning/tools/action/feedback; delegation and orchestrator mindset; agent types; business use cases; beginner mistakes; simple architecture and agent loop demo; safe exploration of tools; meeting-to-action example.
Exercises: identify five tasks worth delegating, then choose one painful recurring task with clear input and output.
Completion evidence proposed for dashboard: submit the selected task, desired outcome, relevant context and approval limits. This is a proposed assessment, not a claim it was in the original dashboard.
Do not market Day 1 as a full agent build: source slide 21 explicitly places building on Day 2.

## Day 2 — Set up the workspace and build workflows
Source: Build slides 1–16.
Preserve: installation vs workflow value; AWS/Ubuntu → Hermes → model provider → Telegram setup map; role-specific agent workspace; screen-share workshop format.
Live demonstrations in source order:
1. Post-meeting action extraction from notes/transcript.
2. Student-success reminders and follow-up.
3. Proposal drafting and follow-up, with response notification.
4. Scheduled morning briefing using messages/calendar/tasks.
5. Repurpose long-form material into platform-specific drafts.
Preparation for Day 3: deploy the agent, list three priority workflows, prepare a business-context document (business, voice, services, customers, standards).
Completion evidence proposed: setup status and blocker log, business-context document and workflow shortlist. Students need not individually complete every demonstrated workflow on Day 2.
Missing source: separately referenced AWS/Hermes setup guide and live demonstration recordings. Request if available; otherwise develop and test a current supplementary guide, clearly labelled as newly prepared.

## Day 3 — Monetise and implement
Source: Monetise & Implement slides 1–27.
Preserve six routes: deploy in own business; agency implementation (done-for-you, setup/retainer, consulting); freelance builds; productised packages; affiliate/referral partnerships; workflow/template products.
Preserve value-based positioning, measurement, warm-network demo approach, honest proof collection, clear scope and follow-through.
Implementation: deployment catch-up, Telegram/model connectivity, first workflow, optional second workflow, end-to-end testing, troubleshooting and next-action commitments.
Completion evidence proposed: one working workflow demonstration with test input/output, limits and approval checks; one selected commercial route and next-step plan. Treat successful deployment as a learning target dependent on readiness and access, not a guarantee for every attendee.

## Resource library
Preserve the PDF's workflow concepts and build checklist: goal, context, input, tools, output, approval, feedback. Retain categories: sales/lead generation; content/marketing; student success/community; admin/operations; client delivery; finance/reporting; productised workflows/templates. Retain recommended starting workflows and the 30-day implementation framework as reference, not promises of client acquisition.
Potential dashboard presentation: searchable workflow cards with source number, business problem, suitable users, inputs, tools, steps, approval boundary and test checklist. PDF suggestions are build outlines, not already implemented automations.

## Corrections without changing the teaching concept
- Reframe source pricing bands, revenue examples, savings and profit margins as illustrative teaching examples, not Expertron prices, verified market rates or guaranteed income. Include subscription, hosting, maintenance and support costs; capacity created is not necessarily cash revenue.
- Verify current AWS eligibility, hosting costs, model access and Hermes setup commands before teaching; avoid unconditional free-tier claims.
- Distinguish scheduled cron triggers from event triggers: an action immediately after a call normally requires an event/webhook or polling workflow, not merely a clock schedule.
- Resolve different proposal reminder examples (Day 2 deck: days 2/5/10; PDF: days 1/3/7/14) with one explicitly illustrative cadence. Neither supersedes Expertron's client-service SOP.
- Retain human approval for commercial commitments and outbound publishing, secure authentication, consent and opt-outs; never teach blind autonomous proposal pricing or unrestricted messaging.
- Replace Kenny/Zubby personal stories with labelled sample scenarios or genuinely verified Babajide/Lucy examples. Do not relabel personal proof as Expertron proof.
- Workshop slide 21's duration heading and individual time blocks need reconciliation before a timed facilitator plan is finalised.

## Website changes now required
Replace the earlier generic curriculum with Foundations → Build → Monetise & Implement. Replace the external academy section with the masterclass's own student portal. Include the actual workflow demonstrations and resource-library concept. Keep date, fee, access duration, certificate requirements and final package inclusions unconfirmed until approved. Do not publish or activate checkout as part of materials review.