Install
$ agentstack add mcp-fayerman-source-startup-growth-playbook ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Startup Growth Playbook
Distribution-first marketing strategies for AI-era startups. Clone into any project directory and let an LLM agent auto-generate and execute a marketing plan from the codebase.
Quick Start
cd your-startup-project/
git clone https://github.com/fayerman-source/startup-growth-playbook.git marketing/
Then tell your LLM agent:
> Read marketing/AGENT.md and follow the protocol.
The agent will:
- Discover — scan your codebase to understand the product, niche, and audience
- Select — pick the best 2-3 strategies from the playbook
- Plan — generate a tailored
plan.mdwith real tasks and metrics - Execute — produce marketing artifacts (content, SEO pages, outreach, etc.)
- Handoff — when the next step requires app-code changes or live rollout, generate an implementation-ready handoff instead of endlessly expanding docs
No manual setup. No forms to fill in. The protocol bootstraps from your code.
What's Inside
| File | Purpose | |---|---| | AGENT.md | Self-bootstrapping protocol — the agent reads this first | | playbook.md | 8 distribution strategies with implementation steps and agent tasks | | startup-template.md | Plan structure (used by the agent, not by you) |
The 8 Strategies
- MCP Servers — let AI assistants sell for you
- Programmatic SEO — generate thousands of keyword-targeted pages
- Free Tool — build a grader/calculator as top-of-funnel
- Answer Engine Optimization — be the source ChatGPT and Perplexity cite
- Viral Artifacts — make product outputs shareable
- Newsletter Acquisition — buy an audience for $5-20K instead of building from zero
- Content Repurposing — one pillar piece becomes 50+ across channels
- Parallel Instagram Reels Content Engine — high-volume meme-remix short-form video across parallel Instagram accounts for consumer mobile apps (5-6 month grind; credit: Caleb Dean / Runify, via Superwall Podcast; primary-source analysis in [research/runify-content-engine-analysis.md](research/runify-content-engine-analysis.md))
Output Structure
The agent commits marketing artifacts to subdirectories:
marketing/
plan.md — tailored marketing plan (auto-generated)
content/ — tweets, LinkedIn posts, newsletters, blog posts
seo/ — keyword research, page templates, generated pages
tools/ — free tool specs or source code
outreach/ — newsletter targets, DM templates
aeo/ — FAQ content, schema markup
artifacts/ — viral artifact designs, share copy
Important Boundary
By default, this playbook is designed to generate and organize marketing work inside marketing/.
If the next valuable step requires:
- publishing pages in the real app
- wiring homepage or product UX changes
- implementing share flows
- adding analytics
- submitting sitemaps or checking live behavior
the agent should switch from content generation to an implementation handoff unless the user explicitly asks it to modify the product code.
Source
Strategies 1-7 are derived from Greg Isenberg's Startup Ideas Podcast. Strategy 8 is informed by Caleb Dean's public account of Runify, including the Superwall Podcast with Joseph Choy.
License
MIT
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: fayerman-source
- Source: fayerman-source/startup-growth-playbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.