AIDevGTM/gtm-cofounder

Learn to position an AI product to overcome the "just a wrapper" objection. Focus on real differentiators like data, workflow, and trust, and craft messaging that puts the problem first, not the AI.

Structure a dev-tool homepage that converts developers into champions. Use when the landing page speaks to buyers, reads as salesy, buries the product, or lacks a clear start.

Helps founders find the first 50 real users by going where their ICP already discovers tools. Use it after launch when posting more, community-building, or ads are not producing users.

Build authority by teaching the problem space, not announcing features. Use when the founder finds 'marketing' distasteful and does none, publishes only product updates, or wants a sustainable content and GitHub-README strategy that developers actually respect.

Coach technical founders through selling: finding champions and buyers, running sales conversations, demoing use cases, handling stalls, and closing first paying customers. For founders who've never sold and need to turn free users into revenue.

Measure GTM effectiveness using net developer retention and the DREAM funnel instead of vanity metrics like stars and pageviews. Use when dashboards are full but you can’t tell if your go-to-market is actually working.

Plan a developer-focused launch for Show HN, Reddit, or Product Hunt that earns goodwill. Avoid common mistakes like hype titles and astroturfing with proven frameworks.

Re-scans named competitors and the market category for changes since the founder's brief, surfacing positioning threats or opportunities and updating documentation accordingly. Use when a rival rebrands, a new tool appears, or market shifts are sensed.

Turn developer love into revenue by enabling champions and choosing a GTM model. Use when developers adopt the free tier but nobody pays, when the founder is cold-selling the VP instead of arming the developer, or when picking between open-source, PLG, inbound, and sales-led.

Build a compelling narrative for developer tools by positioning the developer as the hero and a market trend as the villain. Ideal when your messaging feels interchangeable or lacks urgency.

Guides founders to determine product pricing by defining value metrics, packaging tiers, and finding the right number based on evidence, not fear. Use when stuck on pricing decisions or overcoming the belief that developers won't pay.

Stress-tests AI-written GTM deliverables (positioning, homepage, pricing, etc.) against quality standards as a skeptical gate, so only proven work reaches the founder. Use before presenting work or when the founder questions its strength.

Interview the founder once to create a founder brief that other GTM skills use as context, ensuring advice is specific to their real product, ICP, market, and stage. Use this first to avoid generic guidance.

Diagnoses a founder's GTM bottleneck and generates a prioritized, stage-aware roadmap saved as a living document. Use it to turn scattered tactics into a clear plan and always know the next move.

Run developer customer discovery via a Technical Advisory Board (TAB). Use when the founder has never interviewed a user who isn't a friend, is inventing messaging in isolation, or is guessing at the roadmap instead of hearing the pain firsthand.

Optimize your dev tool's first-run experience to get developers to their first real win quickly. Reduces friction so they activate and return.

Write developer value propositions that are specific, provable, and free of puffery. Use when messaging leans on vague claims like 'powerful' or 'seamless,' lacks proof, or tries to address both developers and buyers with one line.

Define a real ICP and the developer personas in the sale. Use when the founder says the product is "for developers," can't name who would say no, or is marketing to whoever holds the budget instead of who actually adopts.