Next Move Marketing

Next-Move Marketing

How to market the /next-move prediction pipeline to developers. This skill covers positioning, messaging, content strategy, distribution, demos, and the playbook for getting the first 1,000 users — inspired by what worked for Cursor, Copilot, and the best developer tools.

Core insight: Developer tools sell on demonstrated capability, not promises. Cursor reached $100M ARR with zero marketing spend. The entire budget was product and demos. Next-move must follow the same playbook: show a developer their own repo being analyzed, and the product sells itself.

When to Use

Use for:

• Planning a next-move launch or content push
• Writing blog posts, tweets, or demos that showcase next-move
• Deciding between distribution channels (where to post)
• Crafting messaging for landing pages and README
• Evaluating pricing models and freemium strategy
• Creating "show don't tell" demo content

Do NOT use for:

• Defining customer personas -> use next-move-customer-persona
• Competitive landscape mapping -> use competitive-cartographer
• WinDAGs-wide ecosystem promotion -> use claude-ecosystem-promoter
• Pricing and business model analysis -> use indie-monetization-strategist

Positioning: The One-Sentence Pitch

For developers: "AI that reads your codebase and tells you exactly what to work on next."

For the ADHD community: "Never waste another hour deciding what to code. Just ask."

For consultants: "Walk into any repo cold and know the highest-impact thing to fix in 30 seconds."

Technical positioning: "/next-move is a 5-agent meta-DAG that analyzes your project context — git history, file structure, test coverage, dependency health, TODO comments — and recommends the highest-impact next action as an executable DAG of skills."

Positioning Against Alternatives

The Demo-First Marketing Playbook

Principle: Show, Don't Tell

Developer marketing has one iron law: if you can't demo it in 60 seconds, you can't sell it. Next-move's advantage is that the demo is the product experience. The viewer watches their own problem being solved in real time.

The Canonical Demo Script (60 seconds)

[Terminal opens. Real repo visible.]
$ wg next-move

Analyzing project context...
  - 847 files across 12 packages
  - 34 open TODOs, 7 marked FIXME
  - Test coverage: 72% (down from 78% last week)
  - 3 stale branches with unmerged work
  - Auth middleware has known vulnerability (CVE-2026-1234)

Your highest-impact next move:

  Fix auth middleware vulnerability (CVE-2026-1234)
  Impact: CRITICAL — blocks security audit and 2 downstream features
  Estimated effort: 45 minutes
  Skill: security-auditor + api-architect
  Confidence: 0.91

  Ready-to-execute DAG:
    Wave 0: [research-cve-details]
    Wave 1: [patch-session-handler, update-middleware-tests]
    Wave 2: [integration-test, security-scan]

  Run this DAG? [Y/n]

Why this demo works:

1. Real repo, real data — not a toy example
2. Identifies something the developer knows they should fix but hasn't
3. Provides a specific, actionable plan — not vague advice
4. Shows estimated effort — reduces fear of commitment
5. Offers immediate execution — zero friction from insight to action

Demo Variations by Channel

Content Strategy: The 12-Week Launch Calendar

Phase 1: Seed (Weeks 1-4) — Build credibility before asking for attention

Phase 2: Grow (Weeks 5-8) — Demos and community engagement

Phase 3: Convert (Weeks 9-12) — Drive installation and usage

Distribution Channels Ranked by ROI

Tier 1: High-intent, zero cost

Tier 2: Medium effort, high credibility

Tier 3: Strategic, longer timeline

Messaging Framework

Headlines (A/B test these)

Problem-led:

• "Stop wasting 30 minutes deciding what to code"
• "Your repo already knows what needs attention"
• "The hardest bug is deciding which bug to fix first"

Solution-led:

• "AI that reads your codebase and tells you what to work on next"
• "wg next-move — one command, instant clarity"
• "Every morning starts with a plan. Automatically."

Outcome-led:

• "Ship 2x faster by eliminating decision paralysis"
• "From 'I don't know where to start' to 'I'm already building' in 30 seconds"
• "What if you never had to decide what to code again?"

ADHD-specific (use with care — authentic only):

• "Built by a developer who was tired of staring at his repo for 20 minutes every morning"
• "Task initiation is the hardest part. We automated it."
• "Your executive function called in sick. next-move showed up instead."

Messaging Do's and Don'ts

Pricing Model Options

Option A: next-move is free forever (recommended for launch)

Rationale: Next-move is the acquisition channel for WinDAGs. The prediction is free. Executing the suggested DAG requires WinDAGs (free tier for small DAGs, paid for larger orchestrations).

Funnel: Free prediction -> "Run this DAG?" -> WinDAGs free tier -> WinDAGs Pro

Precedent: Cursor's free tier (2,000 completions) is the on-ramp to $20/mo Pro.

Option B: Freemium predictions

3 free next-move predictions per week. Unlimited with WinDAGs Pro ($20-40/mo).

Risk: Artificial friction on the acquisition channel. Reduces word-of-mouth.

Option C: next-move as standalone product

$5-10/mo for unlimited predictions. Separate from WinDAGs.

Risk: Splits the brand. Creates confusion about what WinDAGs is.

Recommendation: Option A. Make next-move free, make it amazing, let it be the reason people discover WinDAGs. The monetization happens when they want to execute the DAG, not when they want to see it.

The "Zero Marketing Spend" Playbook

Cursor reached $100M ARR with zero marketing budget. Their playbook is directly applicable:

1. Product IS the marketing: Every wg next-move invocation is a marketing event. If the output is good, users screenshot it and share it. Build for shareability.

2. Ship weekly, talk about it: Every new next-move capability (new analysis dimension, better skill matching, cross-repo support) is a content opportunity. Announce on Twitter, show the diff.

3. Engage authentically: Reply to every tweet that mentions WinDAGs or next-move. Answer every HN comment. Be present in Discord. This does not scale, and that is the point — it builds trust.

4. Let power users evangelize: Identify the 10 most active users and give them early access to features. They become volunteer advocates.

5. Compound content: Every blog post builds on the last. Week 1's "How I Use AI to Decide What to Code" links to Week 4's "Why ADHD Developers Need This" which links to Week 10's "What We Learned from 500 Predictions." The corpus becomes an SEO moat.

Metrics That Matter

Launch metrics (first 90 days)

Growth metrics (month 4-12)

Anti-Patterns

• Do not launch with a waitlist. Developer tools with waitlists signal "we're not ready." Just ship it.
• Do not write marketing copy that sounds like marketing copy. Developers can smell it. Write like an engineer explaining what they built and why.
• Do not lead with the Windows 3.11 aesthetic in marketing. It's a delightful surprise when people discover it, not a selling point in the headline.
• Do not create a Product Hunt launch as the primary strategy. Product Hunt is a vanity metric — the Hacker News and Reddit developer communities have higher conversion rates.
• Do not market next-move and WinDAGs as the same thing. "AI that tells you what to do" and "AI that does it" are different value propositions for different moments. Market them distinctly even if they live in the same CLI.
• Do not make the first demo a video. Make it a GIF or terminal recording — developers want to see output, not listen to a voiceover.
• Do not target enterprise marketing channels before nailing the solo developer experience. Enterprise follows individual adoption in developer tools, not the other way around.

Quality Checklist

• Positioning statement is one sentence that a developer can repeat to a friend
• Demo script takes under 60 seconds and uses a real repo
• Content calendar has at least 8 weeks of planned content
• Distribution channels are ranked by expected ROI with specific tactics
• Messaging framework includes problem-led, solution-led, and outcome-led variants
• Pricing recommendation is justified with precedent from other dev tools
• Metrics are specific, time-bound, and tied to business outcomes
• Anti-patterns protect against the most common developer tool marketing mistakes
• Zero marketing spend playbook is actionable without hiring