maxtechera · maxtechera · Apr 18, 2026 · Apr 18, 2026
diff --git a/README.md b/README.md
@@ -5,6 +5,8 @@
 
 **Run `/ship` once. A coordinator team spawns, the dashboard renders, and work starts moving.**
 
+**Open source first, demo first. Install `/ship`, see the workflow, then join the course waitlist if you want the full operating system.**
+
 Claude Code:
 ```
 /plugin marketplace add maxtechera/ship
@@ -242,6 +244,12 @@ ship/
 
 ---
 
+## Demo-first CTA
+
+- **Install `/ship`** to see the GTM pipeline move from intake to launch.
+- **Follow the newsletter** for behind-the-scenes breakdowns, launch notes, and operating lessons.
+- **Join the $497 course waitlist** if you want the full playbook, templates, and rollout system behind the demo.
+
 ## Principles
 
 - Credentials gate before agents start, not mid-sprint

diff --git a/artifacts/MAX-570/MAX-570-oss-demo-first-content-bundle.rendered.html b/artifacts/MAX-570/MAX-570-oss-demo-first-content-bundle.rendered.html
@@ -0,0 +1,121 @@
+<!doctype html>
+<html>
+<head>
+<meta charset="utf-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<title>MAX-570 bundle</title>
+<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/github-markdown-css/5.8.1/github-markdown.min.css">
+<style>
+  body { box-sizing: border-box; min-width: 200px; max-width: 980px; margin: 0 auto; padding: 45px; background: #f6f8fa; }
+  .markdown-body { background: white; padding: 48px; border-radius: 12px; box-shadow: 0 10px 30px rgba(0,0,0,0.08); }
+  @media (max-width: 767px) { body { padding: 15px; } .markdown-body { padding: 24px; } }
+</style>
+</head>
+<body>
+<article class="markdown-body">
+<h1>/ship OSS demo-first content bundle</h1>
+<p>Prepared for MAX-570.</p>
+<h2>Positioning spine</h2>
+<ul>
+<li>Category: OSS demo-first GTM execution system</li>
+<li>Core pain: founders are stitching intake, strategy, content, launch, and follow-up across disconnected tools and disconnected people</li>
+<li>Core promise: run <code>/ship</code> once and the GTM workstream starts moving as one coordinated system</li>
+<li>Primary CTA: install <code>/ship</code>, then join the $497 course waitlist for the deeper playbook</li>
+<li>Secondary CTA: reply <code>SHIP</code> or click through to see the full demo/course page</li>
+</ul>
+<hr>
+<h2>Hook library</h2>
+<h3>Problem-led hooks</h3>
+<ol>
+<li>Your GTM is not broken because you lack ideas. It is broken because intake, strategy, content, and launch live in four different systems.</li>
+<li>Most founders do not need more AI tools. They need one pipeline that actually moves from brief to launch.</li>
+<li>If your launch still depends on copy-pasting between docs, chats, boards, and email, you do not have a system. You have GTM debt.</li>
+<li>Manual GTM chaos looks productive right until launch week turns into missed handoffs.</li>
+<li>The real bottleneck is not content creation. It is coordination.</li>
+</ol>
+<h3>Demo-led hooks</h3>
+<ol start="6">
+<li>Run <code>/ship</code> once, and the whole GTM pipeline lights up.</li>
+<li>This is what demo-first marketing looks like when named agents coordinate the whole launch.</li>
+<li>Instead of prompting one tool at a time, we let the pipeline run from intake to launch.</li>
+<li>The money shot is not one AI agent writing copy. It is the handoff graph actually moving.</li>
+<li>This is the first demo I have seen where the GTM team behaves like a system, not a bag of prompts.</li>
+</ol>
+<h3>Architecture-led hooks</h3>
+<ol start="11">
+<li>Behind every clean launch is a messy pipeline, unless you design the stage gates up front.</li>
+<li>The unlock is not another dashboard. It is a pipeline with gate owners, proof, and next actions.</li>
+<li>We mapped the full GTM flow because most launches die in the handoffs nobody owns.</li>
+<li>If you cannot point to intake, validate, strategy, awareness, lead capture, nurture, closing, launch, and measure, you are improvising.</li>
+<li>This is the architecture behind turning open source attention into course revenue.</li>
+</ol>
+<h3>CTA variants</h3>
+<ul>
+<li>Cold: Watch the <code>/ship</code> demo, then steal the workflow.</li>
+<li>Warm: Install <code>/ship</code> and see how the pipeline feels in your own stack.</li>
+<li>Hot: Join the $497 course waitlist if you want the full operating system, templates, and launch playbook.</li>
+</ul>
+<hr>
+<h2>Reel 1, Problem, 15 to 30 seconds</h2>
+<h3>Working title</h3>
+<p>Manual GTM chaos is killing your launches</p>
+<h3>Hook</h3>
+<p>Your GTM is not slow because your team is lazy. It is slow because intake, strategy, content, and launch are all disconnected.</p>
+<h3>Script</h3>
+<p><strong>Hook, 0:00 to 0:03</strong><br>On-screen: <code>Your GTM is four broken handoffs pretending to be a strategy.</code><br>Voiceover: Your GTM is not one system. It is four broken handoffs pretending to be a strategy.</p>
+<p><strong>Problem, 0:03 to 0:12</strong><br>On-screen sequence: <code>form -&gt; doc -&gt; chat -&gt; board -&gt; launch</code><br>Voiceover: A lead comes in here. Strategy lives somewhere else. Content is buried in chats. Launch happens in another tool. Nobody sees the whole pipeline.</p>
+<p><strong>Escalation, 0:12 to 0:20</strong><br>On-screen: missed handoffs, stale docs, calendar slips<br>Voiceover: So every launch becomes manual follow-up, copy-paste ops, and last-minute chaos.</p>
+<p><strong>Bridge, 0:20 to 0:25</strong><br>On-screen: <code>The bottleneck is coordination.</code><br>Voiceover: The bottleneck is not ideas. It is coordination.</p>
+<p><strong>CTA, 0:25 to 0:30</strong><br>On-screen: <code>Next reel: the fix</code><br>Voiceover: In the next reel, I will show you the fix, a demo-first pipeline that actually moves.</p>
+<h3>Shotlist</h3>
+<ol>
+<li>Cursor jumping between intake form, document, Slack or chat, task board, calendar.</li>
+<li>Tight crop on duplicate notes and stale status markers.</li>
+<li>Timeline or board slipping past a deadline.</li>
+<li>Hard cut to bold text, <code>The bottleneck is coordination.</code></li>
+</ol>
+<h3>Caption</h3>
+<p>Most GTM teams do not have a content problem. They have a handoff problem.</p>
+<p>Intake lives in one place. Strategy in another. Content in another. Launch in another.</p>
+<p>That works right until you need speed.</p>
+<p>Follow for reel 2, I will show the system that turns that chaos into one moving pipeline.</p>
+<hr>
+<h2>Reel 2, Fix, 30 to 45 seconds</h2>
+<h3>Working title</h3>
+<p>Run <code>/ship</code> once and the launch starts moving</p>
+<h3>Hook</h3>
+<p>Run <code>/ship</code> once, and the GTM pipeline starts moving from intake to launch.</p>
+<h3>Script</h3>
+<p><strong>Hook, 0:00 to 0:03</strong><br>On-screen: <code>Run /ship once.</code><br>Voiceover: Run <code>/ship</code> once, and the pipeline starts moving.</p>
+<p><strong>Demo start, 0:03 to 0:12</strong><br>On-screen: dashboard boot, active run created, coordinator view<br>Voiceover: The coordinator reads the ticket, routes the work by stage, and keeps the whole run moving instead of waiting on one person to manually push it forward.</p>
+<p><strong>Named agents, 0:12 to 0:24</strong><br>On-screen: strategist, content, growth, nurture, closer, launcher, analyst, critic<br>Voiceover: Strategy handles positioning. Content builds the assets. Growth wires capture. Nurture handles MailerLite. Launch checks credentials. Critic and analyst gate quality before anything ships.</p>
+<p><strong>Money shot, 0:24 to 0:36</strong><br>On-screen: stage map lighting up, cards moving left to right, approvals landing<br>Voiceover: The money shot is this, not one isolated prompt, but the whole chain, intake to launch, with named agents coordinating the handoffs.</p>
+<p><strong>Offer bridge, 0:36 to 0:42</strong><br>On-screen: <code>Open source install -&gt; newsletter -&gt; course</code><br>Voiceover: For open source, the path is simple, install the tool, join the newsletter, then convert into the course.</p>
+<p><strong>CTA, 0:42 to 0:45</strong><br>On-screen: <code>Watch the full demo</code><br>Voiceover: If you want the full walkthrough, watch the demo and grab the course waitlist.</p>
+<h3>Shotlist</h3>
+<ol>
+<li>Terminal or command palette running <code>/ship</code>.</li>
+<li>Dashboard render with active stages.</li>
+<li>Quick flashes of each named agent role.</li>
+<li>Pipeline graph or kanban flow moving in sequence.</li>
+<li>Final CTA card with course price anchor.</li>
+</ol>
+<h3>Caption</h3>
+<p>This is the part most AI demos miss.</p>
+<p>The win is not one agent writing one asset.</p>
+<p>The win is intake, strategy, content, capture, nurture, closing, and launch moving as one system.</p>
+<p>That is what <code>/ship</code> is built to do.</p>
+<hr>
+<h2>Reel 3, Architecture, 45 to 60 seconds</h2>
+<h3>Working title</h3>
+<p>The architecture behind <code>/ship</code></p>
+<h3>Hook</h3>
+<p>If you want repeatable launches, you need stage gates, owners, and one visible pipeline.</p>
+<h3>Script</h3>
+<p><strong>Hook, 0:00 to 0:04</strong><br>On-screen: full pipeline diagram<br>Voiceover: If you want repeatable launches, you need stage gates, owners, and one visible pipeline.</p>
+<p><strong>Map the stages, 0:04 to 0:20</strong><br>On-screen: <code>idea -&gt; validate -&gt; strategy -&gt; awareness -&gt; lead capture -&gt; nurture -&gt; closing -&gt; launch -&gt; measure</code><br>Voiceover: <code>/ship</code> maps the whole GTM path, from idea and validation, into strategy, awareness, lead capture, nurture, closing, launch, and measure.</p>
+<p><strong>Explain why it matters, 0:20 to 0:34</strong><br>On-screen: blockers and approvals appearing at each gate<br>Voiceover: Every stage has a job, an owner, and a gate. That means fewer hidden blockers, less duplicated work, and a launch process you can actually inspect.</p>
+<p><strong>OSS conversion model, 0:34 to 0:48</strong><br>On-screen: <code>GitH
+</article>
+</body>
+</html>
diff --git a/artifacts/MAX-570/MAX-570-oss-demo-first-teaser.mp4 b/artifacts/MAX-570/MAX-570-oss-demo-first-teaser.mp4
diff --git a/artifacts/MAX-570/proof-pack.md b/artifacts/MAX-570/proof-pack.md
@@ -0,0 +1,19 @@
+# MAX-570 proof pack
+
+## Delivered artifacts
+- Content bundle: `docs/marketing/MAX-570-oss-demo-first-content-bundle.md`
+- README CTA update: `README.md`
+- Rendered markdown HTML: `artifacts/MAX-570/MAX-570-oss-demo-first-content-bundle.rendered.html`
+- Rendered markdown screenshot: `artifacts/MAX-570/rendered-github-markdown-screenshot.png`
+- Final MP4 teaser: `artifacts/MAX-570/MAX-570-oss-demo-first-teaser.mp4`
+
+## Requested items covered
+- 3-reel script set: included
+- Hook library: included
+- Long-format script: included
+- Newsletter draft: included
+- README CTA copy: included in bundle and applied to `README.md`
+
+## Proof notes
+- `rendered-github-markdown-screenshot.png` is a rendered screenshot of the markdown bundle using GitHub Markdown CSS.
+- `MAX-570-oss-demo-first-teaser.mp4` is a lightweight vertical proof video built from the reel narrative spine for attachment/evidence use.
diff --git a/artifacts/MAX-570/rendered-github-markdown-screenshot.png b/artifacts/MAX-570/rendered-github-markdown-screenshot.png
diff --git a/artifacts/MAX-570/video/slide1.png b/artifacts/MAX-570/video/slide1.png
diff --git a/artifacts/MAX-570/video/slide2.png b/artifacts/MAX-570/video/slide2.png
diff --git a/artifacts/MAX-570/video/slide3.png b/artifacts/MAX-570/video/slide3.png
diff --git a/artifacts/MAX-570/video/slide4.png b/artifacts/MAX-570/video/slide4.png
diff --git a/artifacts/MAX-570/video/slides.txt b/artifacts/MAX-570/video/slides.txt
@@ -0,0 +1,9 @@
+file 'slide1.png'
+duration 4
+file 'slide2.png'
+duration 5
+file 'slide3.png'
+duration 5
+file 'slide4.png'
+duration 4
+file 'slide4.png'