Skip to main content
skill CX Codex

first-50-users — Claude Code skill: what it does, how to install

Guides founders through direct, unscalable tactics to secure their first 50 developer users in existing discovery channels without running paid ads.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add AIDevGTM/gtm-cofounder --skill 09-first-50-users -a claude-code
Open on GitHub

What first-50-users does

This skill adapts frameworks from Adam Frankl and Jakub Czakon to steer founders away from broad posting. Before reaching product-market fit, early traction requires direct work: messaging engineers who publicly raised your problem on GitHub or Reddit, and turning early contacts into design partners.

Channel selection relies on findings in docs/gtm-cofounder/market-research.md alongside target user interviews. If that document is missing or older than a quarter, run research-the-market beforehand. Setting up a dedicated Discord server with five members is counterproductive, as an empty room signals abandonment.

The skill also checks onboarding: a developer must extract value from documentation in under an hour. When week-two retention stays near zero, pumping traffic into the product only feeds a leaky bucket.

What it helps with

  • focus outreach on one specific developer community instead of broad posting
  • identify public GitHub and Reddit discussions about your core problem
  • convert advisory board contacts into early product design partners
  • verify that new developers reach first value in under an hour from docs

Example prompts for the agent

  • Pick the best initial channel for my developer tool using docs/gtm-cofounder/market-research.md
  • Draft a direct outreach approach for developers posting about our problem on GitHub
  • Evaluate whether our onboarding flow lets developers get value within an hour

How to install first-50-users

1Skills CLI (Vercel)

npx skills add AIDevGTM/gtm-cofounder --skill 09-first-50-users -a claude-code

2Manually: put the files in place

~/.claude/skills/09-first-50-users/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/09-first-50-users/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about first-50-users

How to install first-50-users in Claude Code?

Run npx skills add AIDevGTM/gtm-cofounder --skill 09-first-50-users -a claude-code. You can also place the file directly at ~/.claude/skills/09-first-50-users/SKILL.md.

What does first-50-users do?

It structures early developer customer acquisition using targeted unscalable actions instead of paid ads or vague posting. The skill guides you to pick a single named community and turn warm contacts into initial users.

What prerequisites does first-50-users require?

It looks for docs/gtm-cofounder/market-research.md and user interview answers. If the research file is missing or more than three months old, execute research-the-market beforehand.

Source text

SKILL.md · MIT
---
name: first-50-users
description: "Get the first 50 real users through channels the user's ICP already uses. Use when the product shipped and nobody came, the user is \"posting more\" with no result, or is reaching for paid ads before product-market fit."
---

# 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. And once the first 50 are in and retention holds, the hand-to-hand work graduates: build the self-reinforcing engine in `growth-loops`.

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

You should already have two sources: the ranked watering holes in `docs/gtm-cofounder/market-research.md` (from `research-the-market`), and what real users told you in `talk-to-users` question 7 ("where do you go to stay current?"). Where they agree, that's your channel. Where they disagree, trust the users. If there's no research file yet, or it's more than a quarter old, run `research-the-market` first: picking channels from memory is how you end up "posting more" in rooms your ICP isn't in.

Rank channels by **where your specific ICP is**, and go deep on **one** before adding a second. Always by name: a specific subreddit, Discord, newsletter, or GitHub issue thread, never "Reddit" or "communities".

```
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, by name and link (from `market-research.md`, checked against `talk-to-users` Q7).
- [ ] List 20 people who publicly posted about your problem (start from "the problem in their words" in `market-research.md`). 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*).
If the first users aren't coming and you're out of channels to try, reach out to me on [LinkedIn](https://www.linkedin.com/in/devtoolgtm/).

© AIDevGTM · MIT · AIDevGTM/gtm-cofounder

Similar skills

All skills for Marketing and content →

From the same set20

founder-led-sales Walks a technical founder through the first sales conversations: spotting the champion and the budget holder, running a demo, and not losing the deal to “let me think about it”. CX Codex +1 ★ 327repo stars pricing Helps software founders choose a value metric, draw the line between free and paid tiers, and calculate subscription prices based on delivered value. CX Codex +1 ★ 327repo stars market-to-devs-sell-to-buyers Choose a go-to-market motion for a developer tool and help its users make the case for a purchase internally. Useful when free users adopt the product but paid revenue has yet to follow. CX Codex +1 ★ 327repo stars launch-it Walks you through a developer launch on Show HN, Reddit or Product Hunt so the thread earns goodwill instead of a pile-on. CX Codex +1 ★ 327repo stars time-to-first-value Map the obstacles between a developer’s first run and their first useful result. Use the skill when people try a product but fail to return. CX Codex +1 ★ 327repo stars the-homepage Audits a dev-tool landing page and reshapes it around the end-user developer instead of the buyer. Useful when the copy sounds salesy and never says what the product is. CX Codex +1 ★ 327repo stars value-prop-that-converts Rewrites developer-facing value propositions with numbers, proof, and clear category positioning. Useful when marketing copy relies on buzzwords without factual evidence. CX Codex +1 ★ 327repo stars beyond-the-wrapper Find a product’s edge beyond its model, from data and workflow to domain expertise and reliability. Useful when buyers call it a wrapper or question its accuracy. CX Codex +1 ★ 327repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor