Install a working Chief Workshop Builder for your next launch.
Install a working Chief Workshop Builder with the nine-phase launch path, skills, and review standards already inside.
Your launch can move from the first decision to follow-up inside one connected working folder.
Disconnected launch work makes every asset carry missing context.
The plan sits in one chat.
The copy sits in another file.
The approved decisions lose their source.
The review starts from the beginning again.
A launch becomes easier to review when its plan, playbooks, voice, drafts, and decisions stay together.
One installed role plans, creates, and reviews the launch.
The agent supports the Workshop Launch System while the client keeps every final decision.
Nine phases keep the whole launch visible.
Choose
Offer
Guest Passes
Registration
Promotion
Delivery
Conversion
Testimonials
Launch Calendar
The phase path lets the agent identify where the launch is, what is approved, and what comes next.
The workshop moves from context to application.
Who
The workshop establishes who is guiding the session.
Why
The workshop makes the reason for change clear.
What
The workshop names what participants will learn.
How
The workshop teaches three or five usable steps.
Wow
The workshop supports application through practice.
Now
The workshop ends with action, feedback, and the chosen CTA.
The framework keeps the workshop focused on action instead of adding more information.
The pitch follows a documented sequence before Q&A.
The pack teaches the sequence without importing private offer material or a locked close line.
Craft controls structure. The client's voice controls expression.
Craft files
Copy, persuasion, direct-message, and voice-capture principles shape the work.
When wording conflicts, the client's captured voice wins.
Client voice
Real samples control word choice, rhythm, tone, formality, and audience language.
Generated client assets must sound like the client, never like Marc.
Verified inputs become phase assets that stay ready for review.
How to read it: the brain stores verified truth, the commands apply the method, and the client approves the result.
The agent does not need to pretend a draft is live in order to keep the launch moving.
Six commands cover setup, updates, planning, creation, review, and routing.
This command fills the client brain and opens the first real launch.
This command updates one verified brain file after something changes.
This command plans a new launch or resumes the current launch.
This command drafts the approved work product for one phase.
This command finds the highest-value correction before revision.
This command identifies the current phase and routes the next step.
The client can use a command or describe the need in plain language.
Setup reads what already exists before asking for gaps.
A new setup starts cleanly.
The interview fills the required client files one question at a time.
Existing material is read first.
The interview asks only for facts that the supplied material does not answer.
An older pack is migrated safely.
The agent backs up changed files and resumes without repeating completed questions.
Setup cannot finish until the client voice profile is grounded in real writing samples.
The first proof is a real launch plan, not a greeting.
Setup creates the first launch workspace.
The client leaves with a launch plan and a phase-status file built from verified facts, the shipped playbooks, and the captured client voice.
A usable first deliverable is the observable proof that the Chief Workshop Builder is ready to work.
Promotion runs on a proven twelve-day cadence.
The campaign has two supported depths.
The full twelve-day run suits a client who can promote daily, and the lean three-broadcast run gives each message one job across announcement, reminder, and last call.
The twelve-day run follows one arc.
It opens with a pre-launch seed and the announcement, works through teaching, desire, and objection days, and closes with a real final window and a final day.
Invitations and the page keep claims aligned.
Direct invitations go first to people with a verified connection and ask permission before any link, while the landing page stays the single source for every claim.
The pack drafts each message from approved client facts and the client's captured voice, and the client sends every one.
The calendar turns nine phases into dated actions.
One control sheet holds the whole campaign.
It records the approved workshop, targets and actuals, pages and rooms, posts and emails, direct invitations, and delivery and follow-up.
The dated source pattern anchors the schedule.
One pre-launch seed, twelve launch entries from T-12 through T-1, and the workshop day are calculated from the client's own approved date.
Five checkpoints confirm the work before it runs.
They check the campaign foundation, promotion readiness, the closing window, workshop readiness, and the follow-up review.
The client approves and makes every calendar entry, send, and live change.
Version 1 ships the complete core with no expansion packs.
The complete core is included.
Nine playbooks, six commands, craft files, the client brain, and launch folders work together.
No specialist additions ship yet.
Version 1 contains no expansion pack downloads or extra command bundles.
The core must prove useful in real launches before specialist additions earn a place.
The pack drafts. The client approves and sends.
Verified source truth stays visible throughout.
Missing proof, examples, stories, claims, or statistics remain missing or use the required placeholder.
No live action happens automatically.
The pack does not publish pages, send emails, message contacts, change checkout, or update calendars.
The Chief Workshop Builder prepares the work while the client owns every live action.
Four clear actions put the working folder in place.
Download the Workshop Launch OS zip from the install page.
Unzip it and keep the folder somewhere easy to find.
Open that exact folder in Claude Code or Codex and approve the first-use file permissions.
Say /setup and let the agent read what you already brought.
The install is confirmed when the first launch plan and phase-status file exist inside the new launch folder.
Your next launch can move through one connected workspace.
The plan keeps the launch decisions visible.
The engine creates each approved phase asset.
The review holds every draft to the same grounded standards.
The client gains a clear plan and launch assets that remain ready to approve and send.