Choose a workshop people can understand.
“For the title, you’ll want to make it as attractive and easy to understand as possible.”Workshop Launch System, Creating your Workshop Offer
Meet your Chief Workshop Builder
Run your whole workshop launch with one agent.
Meet your Chief Workshop Builder, an installed working agent that knows the Workshop Launch System and keeps your launch moving from the first idea to follow-up.
It helps you plan the workshop, draft each asset, and review your work against the method while learning your business and voice. You stay in control because it drafts and reviews, while you approve and send.
Set aside one focused sitting for setup, with your business material and two or three real writing samples ready.
Install a working Chief Workshop Builder with the nine-phase launch path, commands, and review standards already inside.
9Workshop launch phases inside one connected path
6Installed commands for setup, planning, creation, review, and navigation
4Client brain files for business, voice, tools, and workshop history
0Assets sent, scheduled, or published without your approval
01
A normal AI chat starts over. This pack keeps the whole launch connected.
The difference comes from an installed brain, a small set of files that remember your business, plus nine playbooks, a craft library of writing rules, a voice profile, and six commands that stay with the project.
Normal AI chat
The context starts over each timeYou explain the audience, offer, tools, and launch status again in each conversation.
The method gets guessed from scratchWorkshop choices, promotion, delivery, and conversion can follow a different standard each time.
The client's voice can drift between draftsWording sounds generic when the AI has no verified client voice profile to read.
The launch drafts sit in separate chatsPlans, assets, approvals, and phase status can disappear across unrelated chats.
Workshop Launch OS
The client brain stays currentFour setup-filled files hold verified facts about your business, voice, tools, and workshop history.
The workshop method stays visible throughoutNine playbooks guide the path from workshop choice through the launch calendar.
Your voice controls the wordingThe craft rules shape the structure while your captured voice shapes the words, rhythm, and tone.
Every launch has a homeThe plan, phase status, drafts, reviews, and approval evidence stay inside one launch folder.
02
The method connects the workshop idea, the teaching, and the next step.
These blocks come from the Workshop Launch System source curriculum. The installed agent turns them into planning checkpoints, creation rules, and review checks.
Teach through six connected sections.
The delivery outline moves through Who, Why, What, How, Wow, and Now. The main teaching stays within three or five supported steps so participants can follow and apply it.
Workshop Launch System, Delivering your WorkshopFollow up without becoming pushy.
“My rule of thumb is I’ll remind a maximum of 3 times over 3 days.”Workshop Launch System, Promoting your Workshop
CLIENT FACTS + VOICE
BRAIN + NINE PLAYBOOKS
SIX COMMANDS
PLANS + DRAFTS FOR REVIEW
How to read it: Your verified facts and writing samples shape the client brain, the playbooks and craft guide the six commands, and every result stays with your launch until you approve and send it.
Playbook 05 Promotion remains a DRAFT until its Kit email sequence source material is imported.
Playbook 09 Launch Calendar remains a DRAFT until its Notion launch calendar document is imported.
03
Five honest steps take you from the download to your first real launch plan.
To get started, you download one zip, unzip it, and open that folder in your AI tool. Version 1 includes no expansion packs, so every included workflow already lives inside the core folder.
Version 1.0.0
Download the complete Workshop Launch OS.
The zip file contains the client brain, nine playbooks, shared craft library version 1.0, launch folders, and all six commands.
Smoke-tested as version 1.0.0.Install and open your chosen AI tool.
Use Claude, Claude Code, or Codex, set up so it can open a folder of files on your computer. Keep the project on a computer you can return to for each launch.
Download and unzip the archive.
Keep the complete WorkshopLaunchOS folder together because the brain, commands, and launch files work as one installed project.
Open the exact folder and say start.
Open the unzipped WorkshopLaunchOS folder in your AI tool, then say start or run /setup. Setup reads what is already there before asking about missing information, one question at a time.
Bring your facts and writing samples.
Give the agent your business and offer material, audience notes, workshop history, tool choices, and two or three real writing samples. Setup uses the material you can verify and marks anything unknown instead of guessing.
Review the first real launch plan.
Setup creates a launch folder with a usable launch plan and a nine-phase status record. You approve or correct the plan before the agent drafts any asset for use.
The first time you run it, your AI will ask for permission to read and write files in this folder. That is normal, so approve it and carry on.
Keep the unzipped folder somewhere easy, and open that exact folder in your AI tool. If the pack sits buried inside another folder, your agent cannot see it.
If you use the Claude desktop app, add the pack folder as a project first, then talk to it there.
This release was smoke-tested in Codex from a fresh install through setup, planning, asset creation, and review. The folder includes matching instruction files for both Codex and Claude, so both tools follow the same rules. Your approval is still required before any file is changed or anything goes live.
04
You will know the install worked when the first real launch plan lands.
A welcome message is not enough. You know it worked when the client brain is filled in and two launch files appear, grounded in your facts and captured voice.
Setup completes the four client brain files.
Your client profile, voice profile, tool stack, and workshop history should contain verified client information or clearly marked unknowns.
First working signal
Your launch folder contains
launch-plan.md and phase-status.md, with one next action waiting for your approval.
05
This works best when you bring real material and keep the final decisions.
The agent can plan, draft, and review the work. It cannot replace the facts, examples, judgment, or approval that belong to you.
Who this is for and what you need to begin.
- You have a workshop topic or audience problem you can responsibly help with.
- You can provide your offer, audience notes, tools, workshop material, and real writing samples.
- You want help across planning, registration, promotion, delivery, conversion, and follow-up.
- You are willing to review and approve every final asset before it is used.
Do not use this as a hands-free launch system.
- It will not invent proof, examples, quotes, stories, results, personalization, or statistics.
- It will not connect to live tools, schedule messages, send emails, publish pages, or change a checkout.
- It will not final-pass the missing Promotion or Launch Calendar source details while those playbooks remain drafts.
- It will not imitate Marc when the asset must sound like your business.
06
Six commands keep the launch moving without making you memorize the whole system.
You can use an exact command or describe what you need in plain language. The installed agent sends the request to the correct workflow.
Set up your Workshop Launch OS
/setup
It fills the four client brain files and opens a real launch folder with a usable plan and phase record.
Trigger: “start” or “run setup.”
Use it when starting fresh, bringing existing material, or upgrading an older folder.
Refresh one client file with evidence
/refresh
It backs up and updates one verified client brain file, then reports the exact change and supporting evidence.
Trigger: “refresh my brain” or “my offer changed.”
Use it when your business, audience, tools, workshop history, or voice changes after setup.
Plan or resume a launch
/launch-planner
It creates or updates one complete launch plan and its nine-phase status record from verified facts.
Trigger: “plan my workshop launch” or “what should happen next?”
Use it when choosing the workshop, setting the date, resolving dependencies, or approving the next action.
Create one complete phase asset
/launch-engine
It drafts one client-review asset for one launch phase by using the matching playbook, craft, facts, and client voice.
Trigger: “draft my workshop asset” or “create the next phase asset.”
Use it for titles, registration copy, promotion, direct messages, delivery outlines, pitches, or testimonial requests.
Review and tighten the work
/launch-review
It reviews client-written or agent-written work, names one highest-value correction, and waits for authorization before revising.
Trigger: “review my workshop” or “tighten what you wrote.”
Use it before you approve a title, page, email, direct message, outline, pitch, or calendar.
Find your place in the launch
/router
It reads the launch state, identifies the active phase and blocker, and gives you one next action with the exact command.
Trigger: “where am I in my launch?” or “what do I do next?”
Use it when you need phase navigation, a status summary, or help choosing the correct command.
07
Keep the client brain current so the drafts stay useful.
Your business, tools, workshop history, and voice can change after setup. Update the source of truth instead of correcting the same outdated fact in every draft.
08
A few honest answers can make the first run much easier.
The pack works from real files and plain conversation. It stays useful by being clear about what it can and cannot do.
Can I bring old workshop documents and launch material?
Yes. Setup reads what you provide first, maps verified material into the client brain, and asks only about the missing information.
Can I use Notion, Google Docs, or another tool?
Yes, when you export, paste, or place the relevant material inside the project. The pack does not connect to, change, or publish inside your live tools.
Can I use Codex instead of Claude?
Yes. This release was smoke-tested in Codex from a fresh install through setup, planning, asset creation, and review. The folder includes matching instruction files for both Codex and Claude, so both tools follow the same rules. Your approval is still required before any file is changed or anything goes live.
Is my data private inside the pack?
The pack does not transmit data on its own. Your AI tool handles whatever you share under its own settings and terms, so use the same care you would use for any client or business material.
What should I do if setup stops or something breaks?
Open the same folder and ask the agent to resume setup. The pack keeps a record of your progress, so completed answers and backups are not lost. If you still need help, book a call with Master Implementers.
Where does the Workshop Launch System training fit?
Use the Workshop Launch System training when you want the teaching behind the workflow. The installed pack helps you apply that method to your own launch, and no classroom URL is stored inside the product.
09
Later additions will follow real client use and complete source material.
Version 1 includes no expansion packs. These three ideas are reserved for later consideration and are not present in this release.
Physical-workshop pack
This specialist pack is not included in version 1.
Paid-ads promotion pack
This specialist pack is not included in version 1.
High-ticket pitch pack
This specialist pack is not included in version 1.