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…
Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.
$ npx -y skills add AIDevGTM/gtm-cofounder --skill 07-the-homepage --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/07-the-homepageContext preview
The summary Claude sees to decide when to auto-load this skill.
Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.
name: the-homepage description: Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.
> Write your homepage for the person who actually reads it: the **end-user developer**, not the CTO who signs the check. The developer becomes your champion and sells it internally for you.
**Use this when:** your homepage speaks to buyers/ROI, it's clever but vague about what the thing does, or a developer can't tell in 5 seconds whether to care, and can't start in 5 minutes if they do.
**Address end-user developers on the homepage; put enterprise/ROI/buyer messaging on separate pages** (enterprise, pricing, case studies). If you write the homepage for the buyer, you've written it for someone who isn't there.
1. **Hook / core message**: immediately: what *is* it? Use a category ("CI for monorepos"), a known-incumbent comparison ("a Datadog alternative"), or a plain statement. **Headline = what it is · subhead = for whom / what job.** 2. **Hero**: a real product shot; two CTAs: **Get started** (signup) *and* **Docs**. Answer "what's in it for me?" up top. Lead with the **how**, not the why. 3. **Social proof, right after the hero**: recognizable logos are the fastest credibility you have. Impressive dynamic metrics (users, stars) if you've got them. 4. **Value prop & differentiation**: why you over the 10 alternatives (see `value-prop-that-converts`). 5. **Getting started**: a huge conversion lever. Free trial, **no credit card**, quick setup. Any hard barrier sends developers straight to a competitor.
**Design:** clean typography, breathing room, no "salesy BS," minimal heavy interactions. An embedded playground / copy-pasteable snippet creates an instant *aha*.
Cross-check the copy has all six: 1. the **problem in the customer's language** (before the solution) 2. the **villain** / undeniable trend 3. **attributed proof** with numbers (name · title · company) 4. the **inciting event** / urgency 5. **social proof** (not anonymous) 6. a **low-friction path to try** (free tier · docs · GitHub)
Don't build everything. Start with: **homepage · docs · pricing · navbar (login, signup, contact, GitHub) · About** (an About page builds trust for an unknown brand). Add later, deliberately: case studies → comparison pages → blog → templates → sandbox → enterprise page.
> **Transparent pricing.** "Contact sales for pricing" reads as "expensive and slow." Show a number wherever you can.
Can a developer get value self-serve? ├─ YES → primary CTA "Get started" (signup/download) + secondary "Docs". └─ NO → primary CTA "Read the docs" / "See how it works"; don't fake a signup that dead-ends.
--- 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…