$0 Distribution Playbook: 12 Channels, 30 Days to 650+ Installs

The $0 Distribution Playbook: 12 Channels, 30 Days, Real Numbers

Launching an open-source project with no marketing budget and no existing audience is a challenge many developers face. William, the creator of aicraft-code-review, tackled this head-on. His project, an open-source MCP server designed for code review with features like OWASP scanning, N+1 detection, and style rule enforcement for platforms like Claude Code, Cursor, and Cline, achieved over 650 PyPI installs, gained 12 Product Hunt followers, and secured listings in five directories within its first month – all without spending a dime on marketing. This playbook details the exact channels used, their effort-to-reach ranking, and crucial lessons learned.

Channel Breakdown: Effort vs. Reach

The core of this strategy lies in maximizing reach for minimal effort. William ranked his distribution channels based on this principle. The goal was to identify the most efficient paths to visibility and adoption.

Top Tier: High Reach, Low Effort

PyPI (Python Package Index): This was the most impactful channel, yielding over 650 installs. The effort was minimal: a single afternoon to configure pyproject.toml, build the wheel, and upload using twine. This demonstrates the power of leveraging existing developer ecosystems.

Smithery: This platform offers a live listing with no cost. The setup involved a quick deployment process, integrating the project into a known developer tool directory.

Mid Tier: Moderate Effort, Growing Reach

GitHub Topics: Adding relevant topics to the repository (`python`, `code-review`, `mcp-server`, `developer-tools`, `ai-coding-assistant`) increased discoverability within the GitHub ecosystem. This requires understanding SEO within the platform and consistent tagging.

Hacker News: A single post to Hacker News generated significant traffic and discussion. The key was crafting a compelling title and engaging with comments. While not guaranteed, a well-timed and relevant post can be a massive lever.

Awesome Lists: Being added to relevant "Awesome" lists on GitHub (curated lists of great resources) provided sustained, high-quality traffic. This often requires outreach or having someone in the community nominate the project.

Product Hunt: While the direct follower count was modest (12), the launch on Product Hunt provided initial visibility and drove some traffic. The effort involved preparing assets and coordinating the launch day.

Lower Tier: Higher Effort, Specific Reach

Reddit: Posting in relevant subreddits like r/Python, r/programming, and r/OpenSource generated discussion and some installs. Success here depends on adhering to subreddit rules and providing genuine value, not just self-promotion. The effort is moderate due to needing tailored posts for each community.

Discord Communities: Engaging in relevant developer and AI communities on Discord provided direct interaction. The effort is high because it requires genuine participation and finding the right channels to share the project without being spammy.

X (Twitter): Organic posts on X provided some visibility, but the reach was limited without a pre-existing following or engagement strategy. This channel requires consistent effort and understanding of platform algorithms.

Dev.to: Publishing an article on Dev.to, similar to this one, serves as a content marketing play. It requires writing a detailed piece and can drive traffic over time, but the immediate impact is often lower than direct platform listings.

LinkedIn: Sharing updates on LinkedIn yielded minimal results, suggesting the platform is less effective for direct open-source tool adoption compared to developer-centric platforms.

Indie Hackers: While not directly resulting in installs, sharing the journey on Indie Hackers provided valuable feedback and connections with other founders.

What Didn't Work (Or Worked Less)

Not every channel delivered proportional results for the effort invested. LinkedIn, for instance, provided minimal traction. While X (Twitter) can be powerful, organic reach without a strategy or following is a slow burn. The key takeaway is that direct integration into developer workflows (like PyPI) and community hubs (like Hacker News, Reddit) offer the most efficient path to early adoption for tools like aicraft-code-review.

The surprising detail here is not the low cost, but the sheer variety of channels that can be leveraged even with zero budget. Many developers assume significant marketing spend is necessary for visibility. This playbook shows that strategic use of existing platforms and communities can be incredibly effective.

The Path Forward

With a solid foundation of 650+ installs and growing awareness, the next steps involve building on this momentum. Continued engagement on channels like GitHub, Hacker News, and relevant subreddits, alongside seeking additions to more "Awesome" lists, will be crucial. The focus remains on providing value to developers and fostering a community around the project.

If you're a developer looking to distribute an open-source tool, consider this playbook. Prioritize platforms where your target audience already lives and works. PyPI, GitHub, and developer forums should be your first stops. The $0 distribution is not only possible but achievable with a smart, channel-aware strategy.