MAX-549: add /ship reel series assets

artifacts/MAX-549/proof-pack.md

@@ -0,0 +1,28 @@
+# MAX-549 proof pack
+
+## Delivered artifacts
+- Script archive: `docs/marketing/MAX-549-ship-reel-series.md`
+- Generator: `scripts/generate_max549_assets.py`
+- Reel MP4s:
+  - `artifacts/MAX-549/MAX-549-problem-agitate-solve.mp4`
+  - `artifacts/MAX-549/MAX-549-contrarian.mp4`
+  - `artifacts/MAX-549/MAX-549-specific-number.mp4`
+  - `artifacts/MAX-549/MAX-549-insider-reveal.mp4`
+  - `artifacts/MAX-549/MAX-549-testimonial.mp4`
+- Thumbnail PNGs:
+  - `artifacts/MAX-549/problem-agitate-solve-thumbnail.png`
+  - `artifacts/MAX-549/contrarian-thumbnail.png`
+  - `artifacts/MAX-549/specific-number-thumbnail.png`
+  - `artifacts/MAX-549/insider-reveal-thumbnail.png`
+  - `artifacts/MAX-549/testimonial-thumbnail.png`
+- Visual proof sheet: `artifacts/MAX-549/MAX-549-proof-sheet.png`
+
+## Coverage
+- `final_mp4_attachment`: satisfied with 5 rendered MP4 variants
+- `linear_attached_visual_proof`: ready via proof sheet + 5 thumbnails + 5 MP4s
+- `pr_url`: pending branch push and PR creation
+
+## Notes
+- Built in the correct repo: `maxtechera/ship`
+- Ticket text conflicts on archival repo (`max-techera/max-techera`), so scripts were archived in `ship` per dispatcher instruction and execution profile
+- `manychat_trigger.flow_id` is still `TBD_MAX_PROVIDES` in the ticket, so this remains an open business-side config detail, not a build blocker for the asset pack

docs/marketing/MAX-549-ship-reel-series.md

@@ -0,0 +1,73 @@
+# MAX-549 reel series scripts
+
+## CTA map
+- Primary: DM keyword `SHIP` → opt-in flow (free install guide)
+- Secondary: comment `pipeline` → reply with repo link
+- Tertiary: link in bio → `github.com/maxtechera/ship`
+
+## Variants
+### PAS (`problem-agitate-solve`)
+Hooks:
+- I lost weeks to launch chaos, then AI agents shipped it in 3 hours.
+- The problem was never building. It was the launch pipeline.
+- If your product is ready but invisible, steal this 3-hour AI launch flow.
+Script spine:
+- Hook: I launched a product with AI agents in 3 hours
+- Proof: show `/ship create` starting the coordinator and dashboard
+- Credentials: show 30+ integration preflight blocking hidden failures
+- Pipeline: idea → validate → strategy → awareness → launch → measure
+- Launch day: coordinator + content + launcher + analyst moving in parallel
+- CTA: DM SHIP for the free install guide
+
+### Contrarian (`contrarian`)
+Hooks:
+- Hot take, you do not need a bigger launch team. You need one better run command.
+- More tools will not save launch day. Better orchestration will.
+- Most founders stack apps. I stacked agents and launched faster.
+Script spine:
+- Hook: Stop hiring more tools for launch day
+- Proof: show `/ship create` starting the coordinator and dashboard
+- Credentials: show 30+ integration preflight blocking hidden failures
+- Pipeline: idea → validate → strategy → awareness → launch → measure
+- Launch day: coordinator + content + launcher + analyst moving in parallel
+- CTA: Comment pipeline and I will send the repo
+
+### Specific number (`specific-number`)
+Hooks:
+- 30 integrations. 9 agents. 3 hours. That was the entire launch stack.
+- Here is the exact AI pipeline behind a 3-hour product launch.
+- I compressed a week of GTM work into one 3-hour agent run.
+Script spine:
+- Hook: 30+ integrations checked. 9 agents running. 3 hours to launch.
+- Proof: show `/ship create` starting the coordinator and dashboard
+- Credentials: show 30+ integration preflight blocking hidden failures
+- Pipeline: idea → validate → strategy → awareness → launch → measure
+- Launch day: coordinator + content + launcher + analyst moving in parallel
+- CTA: Link in bio for github.com/maxtechera/ship
+
+### Insider reveal (`insider-reveal`)
+Hooks:
+- The secret is not the prompt. It is the launch pipeline behind the prompt.
+- Everyone shows the output. Almost nobody shows the GTM machine.
+- Behind every fast AI launch is a ruthless checklist. Here is mine.
+Script spine:
+- Hook: What the public demo does not show you
+- Proof: show `/ship create` starting the coordinator and dashboard
+- Credentials: show 30+ integration preflight blocking hidden failures
+- Pipeline: idea → validate → strategy → awareness → launch → measure
+- Launch day: coordinator + content + launcher + analyst moving in parallel
+- CTA: DM SHIP to get the install guide + repo path
+
+### Testimonial style (`testimonial`)
+Hooks:
+- Best part, it did not feel like using software. It felt like a launch team showing up.
+- I ran one command and watched a GTM team materialize.
+- If you are a solo founder, this is the closest thing to hiring a launch squad overnight.
+Script spine:
+- Hook: This felt like having a launch team on-call
+- Proof: show `/ship create` starting the coordinator and dashboard
+- Credentials: show 30+ integration preflight blocking hidden failures
+- Pipeline: idea → validate → strategy → awareness → launch → measure
+- Launch day: coordinator + content + launcher + analyst moving in parallel
+- CTA: Reply SHIP and I will send the setup guide
+