AI 30 CLIENT RECORD
Your work. Your builds. What changes.

Keep one shared document for your 30-day program. Give your coach access using your organization's usual sharing controls. Update it together as the work moves forward. Keep approved source files in their original location and link to them here.

Start with your outcome, starting point, and current build. Add the rest as the work progresses.

PARTICIPANT AND PROGRAM
Participant:
Coach:
Program start date:
Program end date:
Time available to build and review:
Last updated:

1. WHAT WOULD MAKE THESE 30 DAYS WORTHWHILE?
The recurring work I want help with:
The outcome that matters to me:
Agents or workflows I already use:
What works today, and what still needs attention:
What I want to build, improve, or connect next:

2. STARTING POINT
Workflow being measured:
Comparable work samples and dates:
How often this work happens:
Current hands-on effort per run:
Current quality, corrections, or missed steps:
Evidence links:
Success measure and target agreed with my coach:
How and when we'll measure again:

3. AUTOMATION ROADMAP
Add one entry per opportunity. Rank by useful impact, feasibility, available information, and review effort. Agree on priorities and co-building scope with your coach. Keep adding opportunities as you learn.

Opportunity:
Build, improve, connect, or defer:
Why it matters and how often it happens:
Expected benefit (an estimate until measured):
Available sources and tools:
Access or other dependencies:
Build and review effort:
Priority and reason:
Status (backlog / agreed / building / in review / in use / paused / deferred):
Owner:
Next action and date:

4. CURRENT BUILD
Copy this section for each workflow you build or improve.

Workflow and purpose:
Build or improve an existing agent:
Trigger and frequency:
Inputs and approved source links:
Expected output:
What a good result must include:
What it must not do:
Tools, models, and integrations:
Allowed access and actions:
Actions that require human approval:
Stop rules, failure handling, and recovery:
Working instructions or Skill link and version:
Relevant lesson or example:
Participant next action and date:
Coach next action and date:
Current blocker and owner:

5. RUNS, FEEDBACK, AND CHECKS
Add an entry for each reviewed run. Test on a fresh comparable example before keeping a change.

Run date and instructions version:
Input and output links:
Reviewer:
Quality checks and result:
Hands-on time, including prompting, review, and corrections:
What needed correcting:
Lesson saved in the instructions:
What changed on the next run:
Human decision (keep / revise / pause):
Remaining issues and owner:

6. COACHING UPDATE
Add an entry whenever you work with your coach.

Date:
What changed since the last update:
What we reviewed and decided:
What is blocked and who can resolve it:
Participant next action and date:
Coach next action and date:
Next review point agreed together:

7. RESULTS AT DAY 30
Workflows in use and evidence links:
Comparable before-and-after samples and dates:
Starting effort and current effort on the same basis:
Prompting, review, correction, and maintenance effort included:
Quality and reliability compared with the starting point:
Actual tool and operating costs:
Measured benefit, separate from estimates:
Any comparison with the $2,500 program investment (state assumptions):
What improved:
What did not improve or is still unproven:
What I can run, review, and improve myself:
What still needs support:

8. TOOLS AND MAINTENANCE (AI BILL OF MATERIALS)
Keep an entry for each workflow.

Workflow and owner:
Tools, models, and subscriptions:
Instructions or Skill location and version:
Data sources, access, and permissions:
Quality checks and human approval points:
Usage, subscription costs, and limits:
Support or maintenance owner:
Review schedule and what triggers a recheck:
How to pause the workflow, remove access, and recover:
Dependencies on personal accounts or devices:

9. KEEP BUILDING
Next opportunities on the roadmap:
What to maintain or revisit:
Next question or build to bring to the AI Mastermind:
Next action, owner, and date:

Your program includes one year of continuation support in the weekly AI Mastermind. Included OpenAI, Anthropic, and Gemini API usage covers the 30-day program. API usage afterward and other tool subscriptions are separate. Identify ongoing access, ownership, and costs with your coach before the program ends.

Program scope: There is no program cap on agents created using the process. We agree on co-building scope together. Completed builds depend on complexity, available tools and information, and participation.

Delivery guide: https://www.technical-leaders.com/ai-30/program
AI 30 offer: https://www.technical-leaders.com/ai-30