AgentStack
SKILL verified MIT Self-run

First 50 Users

skill-aidevgtm-gtm-cofounder-first-50-users · by AIDevGTM

Get the first 50 real users through channels the founder's ICP already uses. Use when the product shipped and nobody came, the founder is "posting more" with no result, or is reaching for paid ads before product-market fit.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-aidevgtm-gtm-cofounder-first-50-users

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README — it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-aidevgtm-gtm-cofounder-first-50-users)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.

Preview Execution monitoring

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 →
Are you the author of First 50 Users? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Your first 50 users

> You don't get your first 50 users by posting more. You get them by going where your users already discover tools, and, at the start, by doing things that don't scale.

Use this when: you launched to silence, you're spraying every channel hoping one works, or you're about to buy ads to fix a problem ads can't fix.

The core idea

Every developer audience has an existing technology-discovery loop: the specific places they already go to find new tools. Your job isn't to invent demand; it's to position yourself inside that loop. And your first cohort is hand-to-hand: the TAB members from talk-to-users are your first users.

Framework: the top of the DREAM funnel (Frankl)

  • Discovery: be where developers look: the communities, newsletters, influencers, and searches your ICP already uses. Metric: unique humans, not pageviews.
  • Research: give the interested dev a next step before they forget you: newsletter, Discord, free tier, docs. Developers can sit in Research for months, so sustain the relationship.

Then Evaluation decides everything (see know-if-its-working): can a new dev get value over a weekend, from docs and Stack Overflow, with no support call? If not, more traffic just fills a leaky bucket.

Framework: channels by stage (Czakon)

Pre-PMF (you are here for the first 50): unscalable, direct, high-touch.

  • The people who posted about the problem (HN/Reddit/GitHub issues/X), DM them, personally.
  • Your TAB → convert to design partners / first users.
  • Founder posting genuinely useful things where the ICP hangs out (not "we launched!").
  • One deep launch (see launch-it), not ten shallow ones.

Post-PMF (later): content/SEO, community, dev-influencer partnerships, then paid to amplify what already converts, never to discover it.

How to pick the channel (don't do all of them)

From talk-to-users question 7 ("where do you go to stay current?"), you already have the answer. Rank channels by where your specific ICP is, and go deep on one before adding a second.

Is your ICP concentrated somewhere specific (a subreddit, a Discord, a conference, a tag)?
├─ YES → go all-in there first. Depth beats spread at 0→50.
└─ NO  → your ICP may be too broad → tighten it in `who-is-this-for`.

Mistakes that look reasonable

  • "Post more": volume without a channel thesis is noise.
  • Paid ads pre-PMF: you'll pay to accelerate a message that doesn't convert yet.
  • Building a community at 5 users: a Discord with 3 lurkers is a graveyard that signals "dead." Wait for real traction.
  • Optimizing acquisition over a leaky bucket: if week-2 retention is near zero, fix Evaluation/Activation first.
  • Launching ten times, shallow: one well-prepared launch > ten "we shipped X" tweets.

Your next 30 minutes

  • [ ] Write down the 3 exact places your ICP discovers tools (pull from talk-to-users Q7).
  • [ ] List 20 people who publicly posted about your problem. DM 5 today, helpful, not pitchy.
  • [ ] Turn your best 5 TAB members into your first 5 users this week.
  • [ ] Confirm a new user can hit first value in under an hour. If not, that's the real priority.

Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). When a framework can't make the call, that's what a human is for: The DevTool GTM Company.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.