AutoClaw Marketing Plan — Apr–May 2026

Based on: SCQH (2026-03-19), Q2 execution plan (2026-03-20), Upwork demand analysis (2026-04-01), and site/content state as of Apr 2, 2026.

Goal: Build the AutoClaw site into a credible public surface for the OpenClaw ecosystem. Drive ecosystem traction (GitHub stars, inbound interest, real deployments) through content — not through paid channels or product announcements.

---

Where we are now (Apr 2)

Site: autoclaw.sh is live — Astro static site on Cloudflare Pages, PostHog analytics running.

Live playbooks (4):

• Deploying OpenClaw on Cloudflare
• Running OpenClaw locally
• Stabilizing a deployment
• Choosing infrastructure

Draft playbooks (5 — written, not yet published):

• OpenClaw vs Claude Code (autonomous agents)
• Secure private deployment
• Email integration
• CRM integration
• Multi-agent workflows

Examples (1):

• openclaw-aaas — multi-tenant reference deployment on Cloudflare Workers

Flagship article draft:

• drafts/2026-04-01-open-source-playbook-for-openclaw-deployment.md — "What We Learned Building an OpenClaw AaaS Prototype" — ready for review and publish on datopian.com

Upwork demand analysis:

• drafts/2026-04-01-openclaw-upwork-demand/ — 326 labeled jobs, demand-ranked topic list across setup, integrations, workflow, and debugging categories

What we don't have yet:

• Any distribution (no posts, no links, no traffic)
• Templates or scaffold
• CLI

---

Direction: two-phase approach

Phase 1 — Content-first (Apr 2–18)

Publish all draft playbooks. Add high-demand playbooks from Upwork analysis. Get the existing flagship article out. Begin lightweight distribution.

No templates, no CLI yet. Content only.

Phase 2 — Templates (Apr 19 – May 16)

Introduce a scaffold template: a starter repo that provisions a new OpenClaw deployment with sane defaults. Add a "Templates" section to autoclaw.sh alongside Playbooks and Examples.

---

Phase 1 in detail (Apr 2–18)

Flagship article

Already drafted: drafts/2026-04-01-open-source-playbook-for-openclaw-deployment.md

Working title options:

1. "Toward an Open Source Playbook for OpenClaw Deployment" ← cleanest for HN
2. "What We Learned Building an OpenClaw AaaS Prototype"
3. "From OpenClaw AaaS to an Open Source Agent Deployment Playbook"

The draft covers: why we built a prototype → what we learned → the sharp edges (billing, memory, sandboxing, observability) → why an open playbook is the right next step → invitation to the community.

Action: review draft, finalize title, publish on datopian.com/blog. Link from autoclaw.sh.

Target: published by Apr 9.

Playbooks to publish

Priority driven by: existing drafts first, then Upwork demand signal.

Publish from existing drafts:

Write new — top Upwork gaps:

That takes live playbooks from 4 → 13 by Apr 18.

Deliberately deferred (address in Phase 2+):

• Windows / WSL / Ubuntu setup (16 mentions) — real demand but lower priority
• Slack integration (25), Teams/Azure (21), SMS (15) — integration-specific, write when demand justifies
• Browser automation (29) — technically complex, needs real reference

Distribution — Phase 1

Each piece gets distributed once it's live. Don't batch.

Reddit rules: clean URLs, no UTM. Post from a personal account as "I wrote this", not the brand account.

Subreddits — tiered:

Tier 1 — OpenClaw-specific (post everything relevant here):

• r/openclaw
• r/clawdbot
• r/openclawinstall
• r/openclawusecases

These are the highest-value channels. High-intent audience already stuck on exactly the problems our playbooks solve. Two modes: (1) post new playbooks as standalone posts; (2) find existing threads where people are stuck and answer with a link to the relevant playbook — not spam, genuine contribution.

Tier 2 — post only when directly relevant:

• r/ClaudeCode — for the OpenClaw vs Claude Code playbook specifically
• r/selfhosted — for infrastructure/deployment content (Hetzner, Cloudflare, choosing-infrastructure)
• r/LocalLLaMA — only if content touches local model inference (Ollama playbook)
• r/n8n — for the n8n integration playbook specifically

Tier 3 — skip:

• r/claude, r/claudeAI — too broad, wrong audience
• r/ChatGPT, r/OpenAI, r/Gemini — enormous communities, strict self-promo rules, AutoClaw audience is a tiny fraction, not worth the noise

r/autoclaw — don't create yet. An empty subreddit looks worse than no subreddit. Create it only when people are organically asking "is there a community for AutoClaw?" — that's the right trigger.

Not yet: paid promotion, newsletter, Instagram.

---

Phase 2 in detail (Apr 19 – May 16)

Templates

Ship a starter template: a minimal, working OpenClaw deployment that someone can clone, configure, and push to Cloudflare in under 30 minutes.

Form factor: Start with a GitHub template repo (fastest to ship, no npm publishing required). Decide after Phase 2 whether usage signal justifies building a full npm create autoclaw@latest scaffold.

Template scope (minimum):

• Cloudflare Workers + D1 + Queues config
• wrangler.toml with sensible defaults
• Environment variable scaffold
• Deploy script / Makefile
• Clear README with step-by-step

Site update: Add a "Templates" section to autoclaw.sh. Signal-row style matching Playbooks/Examples.

Playbooks — Phase 2

Continuing from Upwork backlog + deeper technical content:

Datopian blog post #2

"Deploy OpenClaw in 30 minutes: our starter template" — announce the template, walk through what it gives you out of the box, link to GitHub.

Distribution — Phase 2

• LinkedIn + X: template launch post
• Reddit r/selfhosted: template announcement (communities love "here's a starter repo")
• Hacker News: "Show HN: AutoClaw — open deployment reference for OpenClaw agents" — the template section is the hook; this is the main HN moment

---

YouTube — parallel track from Phase 1

YouTube is activated early, but treated as a skill-building track rather than a distribution channel in Phase 1. Views will be near zero in weeks 1–4 regardless of quality — that's fine. The goal is reps.

Why start early:

• YouTube is a search engine. "How to install OpenClaw on Mac" gets typed into YouTube, not just Google. Text playbooks don't compete there.
• The Upwork demand list is a pre-validated YouTube keyword list. High-intent viewers are already searching for exactly these topics.
• Getting reps in early compounds. Starting in Phase 3 means 6–8 weeks of delayed learning on production workflow, pacing, and on-camera comfort.

Format (Phase 1): screen recording + narration only. No camera, no editing beyond basic cuts. Each video is effectively the matching playbook in video form — the text is already the script.

Pace: 1 video per week. Don't let it crowd out the playbook work — text ships faster and has more distribution options in Phase 1.

Phase 1 videos (start here — easiest to record):

Phase 2 videos (once production workflow is understood):

Distribution decision point (end of Phase 2): after 6+ videos, review watch time and search traffic. If any video is getting organic search views, increase production cadence and start cross-posting to LinkedIn/X. If not, investigate format before scaling.

What to avoid:

• Don't invest in production quality before you know what format this audience responds to.
• Don't start a YouTube channel and go dark for 3 weeks. Consistency matters more than launch timing. If weekly pace isn't sustainable, drop to biweekly before skipping.

---

What we're not doing (Apr–May)

• No paid ads
• No influencer outreach
• No newsletter (not enough audience yet — revisit after Phase 2)
• No Instagram
• No CLI (Phase 3)
• No outbound client services marketing — let the content generate inbound

---

Success metrics

Stars are the lagging indicator. Inbound inquiries are the early signal that the content is landing.

---

Content calendar

---

Key decisions to revisit

1. HN timing: Only post when the content is genuinely strong. Review the flagship article draft carefully before submitting — a weak HN post burns credibility.

2. Template form factor: GitHub template repo first. Decide after Phase 2 if npm create autoclaw@latest is worth building.

3. Newsletter: If traffic and inbound are above threshold by May 16, add a lightweight email signup to the site. Don't start earlier.

4. YouTube distribution: YouTube is activated in Phase 1 as a skill-building track (1 video/week, screen recording only). At end of Phase 2 — after 6+ videos — review watch time data and decide whether to scale cadence and push distribution. Don't invest in production quality before knowing what format the audience responds to.

---

Content backlog (deferred)

From Upwork demand analysis — topics to address after May 16:

• OpenClaw + Slack integration (25 mentions)
• OpenClaw + Microsoft Teams / Azure Bot (21 mentions)
• How to fix gateway / connectivity issues (20 mentions)
• OpenClaw for lead generation / prospecting (20 mentions)
• OpenClaw for real estate workflows (18 mentions)
• OpenClaw on Windows / WSL / Ubuntu (16 mentions)
• OpenClaw + SMS workflows (15 mentions)
• OpenClaw + browser automation (29 mentions — needs real reference)
• Business automation patterns by vertical (marketing, sales, e-commerce, legal)

---

Created: 2026-04-02