00-start-here
Interview the user once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a…
Measure GTM with the metrics that matter (net developer retention, DREAM funnel) instead of vanity numbers. Use when the user has dashboards full of stars and pageviews but can't tell if go-to-market is working, or is optimizing acquisition over a leaky bucket.
$ npx -y skills add AIDevGTM/gtm-cofounder --skill 15-know-if-its-working --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/15-know-if-its-workingContext preview
The summary Claude sees to decide when to auto-load this skill.
Measure GTM with the metrics that matter (net developer retention, DREAM funnel) instead of vanity numbers. Use when the user has dashboards full of stars and pageviews but can't tell if go-to-market is working, or is optimizing acquisition over a leaky bucket.
name: know-if-its-working description: Measure GTM with the metrics that matter (net developer retention, DREAM funnel) instead of vanity numbers. Use when the user has dashboards full of stars and pageviews but can't tell if go-to-market is working, or is optimizing acquisition over a leaky bucket.
> The only early metric that matters is **net developer retention**. Without it, you're not running a funnel; you're running a colander.
**Use this when:** you're tracking GitHub stars and pageviews and still can't answer "is GTM working?", or you're pouring effort into acquisition while new users quietly churn.
Acquisition is worthless if users don't come back. Prove **retention** first; only then does spending on **acquisition** make sense. Most early founders optimize the top of the funnel while the bottom leaks. Fix that order.
> Of all the developers who first used the product in **Month 1**, how many used it in **Month 2? Month 3?**
Measure one honest number per stage, not pageviews, not stars.
| Stage | The metric that counts | |---|---| | **Discovery** | unique human visitors / month | | **Research** | newsletter subs + community joins + follows | | **Evaluation** | free-tier signups / downloads / active free users | | **Activation** | monthly active users · frequency · session depth | | **Membership** | community members *actively* posting & answering |
**The gate before all of it, the weekend test:** can a new developer get to first value **over a weekend from docs + Stack Overflow, no support call?** Time-to-value target: **< 1 hour ideal, 1 day max.** If Evaluation/Activation fails here, no channel work will save you.
Developer marketing is **hard to attribute and that's normal.** A dev sees your HN post, reads a tutorial, lurks for two months, then signs up direct.
Is month-2 cohort retention healthy (users come back)?
├─ NO → STOP optimizing acquisition. Fix Evaluation/Activation (the weekend test, time-to-value).
└─ YES → is a channel reliably producing retained users?
├─ YES → pour more in (and only now consider paid to amplify).
└─ NO → go back to first-50-users; find the channel before scaling spend.--- 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](https://thedevtoolgtmcompany.com).
#1 Product of The Day @ Product Hunt. The GTM co-founder you don't have. Open-source GTM Agent Skills for developer tools and AI products, for founders, GTM hires, and founding AEs: positioning, first users, launch, pricing. Sharpened by Frankl & Czakon. MIT.
Repo: AIDevGTM/gtm-cofounder
Interview the user once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a…
After the founder brief, turn it into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the…
Define a real ICP and the developer personas in the sale. Use when the user says the product is \"for developers,\" can't name who would say no, or is…
Run developer customer discovery via a Technical Advisory Board (TAB). Use when the user has never interviewed a user who isn't a friend, is inventing…
Build a positioning and narrative where the developer is the hero and a real trend is the villain. Use when the messaging describes the product instead of the…
Position an AI product when everyone claims AI and skeptics call it \"just a wrapper.\" Find the real wedge (data, workflow, trust, domain), make reliability…