What You’ll Learn

James starts with a product in an empty folder and one goal: get it fully ready to sell without touching the marketing himself. In this live session he runs his “build a new offer” playbook end to end — you watch it work — and hands you the workflow to steal. This walkthrough breaks down what the playbook does and how the pieces hand off.

By the end you’ll understand how a launch workflow is structured across four departments, why it matters that each one hands its output to the next, and how to document your own repeatable playbook.

The Setup: A Product With Nothing Around It

Earlier that day, James had Dean (his campus operating system orchestrator) build a product — CourseLab — from a product requirements document. Now there’s a folder with the product in it and nothing else: no sales page, no pricing, no emails, no launch. The job is the workflow that closes that gap.

He opens Claude Cowork (on Opus 4.8), says hello to Dean, and gives one instruction: run the “build a new offer” playbook for this product and get it ready to sell. Dean asks the two things he needs — the price and the sales-page URL — and starts.

“I started with a prompt. I said ‘get this ready for sale.’ It followed a workflow, a playbook, and it has me ready with a product to sell.”

What Dean Does Behind the Scenes

Before doing anything, Dean orchestrates: he reads the product, checks the available playbooks, looks at which departments and employees play into getting a product to market, builds a task list, and lines up the tools. Then he runs the playbook across four departments — some steps in sequence, some in parallel — with each department handing its output to the next.

The Four-Department Structure

💡 In Plain English: think of a launch as an assembly line. Each station adds its piece and passes the product down — nobody re-figures out what the last station already decided.

Sales. Nails the offer: what it is, the price, the product itself, and the sales copy.

Marketing. Handles the launch — the email series, the social posts, whether they’re scheduled to roll out.

Community. Figures out how to let existing members know a new product has landed and engage them around it.

Education. Covers what a buyer gets after purchase — a course, handouts, and an onboarding email sequence.

Because each department passes its results forward, the sales copy informs the emails, the emails inform the community post, and so on. The result at the end of the session: a product with a sales page, pricing, a cart entry, launch emails, social posts, community announcement, and buyer onboarding — all built, ready to sell.

The Real Lesson: Document Your Own Playbook

The takeaway isn’t “buy my thing” — it’s that you can build this yourself. James’s advice: notice the workflow you already run, and document it. What happens, when it happens, which tools you use, which steps you take. Then tell Claude or Codex: “Here’s what I do and the tools I use — build me a workflow that does this, and when I say go, run it.” It’ll start building those playbooks the way you want them.

The Takeaway

A launch is a repeatable workflow, not a scramble. Structure it across sales, marketing, community, and education, make each stage hand off to the next, and you can take a product from empty folder to ready-to-sell from a single prompt. Document your own, or install the whole operating system — which bundles this launch playbook alongside the research team, content flywheel, outbound sales, 3P teaching system, and CourseLab — at trainingsites.io/os.

Teach more, and let the agents do the rest.

This tutorial is a recap of a live workflow demo.