Start with the smallest useful Build

Find the first artifact your work actually needs.

This diagnostic helps you choose a Practical AI Workbench Build without understanding the whole curriculum first. Pick the bottleneck you feel now, choose the safest first artifact, and start with one Build, preview, bundle, or workshop path.

Use when You know the problem, not the Build
Default first test Make Your Work Legible
Buying rule One Build, one artifact
Boundary No private files needed to choose

Choose By Current Bottleneck

The best starting class is the one that makes this week easier. Do not buy the full path because it sounds complete; buy the first artifact you can use.

You need both better prompts and cleaner context.

Start with: Starter Bundle.

First artifact: prompt pack plus context packet with a bridge prompt.

You keep re-explaining active work.

Start with: AI-Ready Work OS.

First artifact: one-lane Work OS charter and assistant handoff test.

One recurring task might deserve a helper.

Start with: Basic Agents.

First artifact: First Agent Pack with role, permissions, tests, and receipt.

A repeated process needs a reviewed path.

Start with: Agentic Workflows.

First artifact: workflow SOP, gates, eval set, and run receipt.

You need to teach or facilitate this with people.

Start with: Workshops and Enablement or a live workshop inquiry.

First artifact: workshop promise, run of show, workbook, rubric, and follow-up plan.

You want to see what the Builds produce.

Start with: Artifact Gallery.

First artifact: compare prompt pack, context packet, Work OS, surface map, agent pack, workflow SOP, and live-session artifact examples.

Routing Table

Use this table if you are comparing two or three options. The right answer is usually the smallest Build that produces a useful artifact without extra explanation.

What You SayLikely StartYou Leave WithStop If
"My AI answers are weak."Prompt FoundationsPrompt pack and review habit.Your daily prompts now work.
"My files and notes are messy."Make Your Work LegibleContext packet and cleanup receipt.One cleanup habit solves the current problem.
"Both prompts and files are the problem."Starter BundlePrompt pack, context packet, and bridge prompt.The foundation pair is enough for now.
"I keep repeating the same project context."AI-Ready Work OSWork OS charter and source map.The operating layer reduces re-explaining.
"I do not know which tool fits which job."AI Surfaces and HarnessesSurface map and harness handoff.You only needed routing clarity.
"I want a recurring helper."Basic AgentsAgent charter, permissions, test set, and receipt.The task is not actually helper-shaped.
"I need a repeatable process."Agentic WorkflowsSOP, gates, eval set, and run receipt.One reviewed run is enough.
"I need a room or team to learn this."Live workshop pathParticipant artifact and implementation next step.A self-paced Build would solve the problem.

When A Bundle Makes Sense

Bundles should reduce friction, not add pressure. Use a larger offer only when the buyer can name why one Build is too small.

Starter Bundle

Choose this when weak prompts and messy source material are both active problems.

  • Prompt Foundations
  • Make Your Work Legible
  • Bridge guide joining the two artifacts

Founding Lifetime Access

Choose lifetime access only when you already know you want the full six-Build path instead of one focused artifact this week.

  • All six self-paced Builds stay visible and available individually.
  • Lifetime access includes the six Builds and future updates to those self-paced rooms.
  • Start with Prompt Foundations, Make Your Work Legible, or the Starter Bundle.
Do not overbuy: if one $49 Build gives you a useful artifact this week, that is a valid stopping point.

Safe First Artifact

Every starting path should use low-risk material first. The program is practical, but it is not a reason to paste private, regulated, client, student, HR, legal, financial, medical, or confidential material into a tool without permission and a safe environment.

Use

Fictional examples, redacted samples, public material, folder listings, file names, notes you own, and low-stakes drafts.

Avoid First

Private client files, student records, HR issues, medical details, legal strategy, payment data, credentials, or confidential business material.

Review

Keep human review in the loop before using, sending, publishing, automating, or relying on an AI-assisted output.