agentleFS
AIDevGTMAIDevGTM/gtm-cofounder/skills/11-market-to-devs-sell-to-buyers/SKILL.md

market-to-devs-sell-to-buyers

Skill340 starsChanged 3 months agoMITView on GitHub

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 user is cold-selling the VP instead of arming the developer, or when picking between open-source, PLG, inbound, and sales-led.

The file

Files
SKILL.md

Market to devs, sell to buyers

The developer who adopts your tool is almost never the person who pays for it. Win the developer's heart; then hand them the ammunition to win the budget conversation for you.

Use this when: you have stars, signups, and a beloved free tier, and a revenue line of zero.

The core idea (Czakon)

Market to developers, sell to decision-makers. Developers evaluate and adopt; buyers (CTO/VP/procurement) approve money. Your growth engine is the developer champion who sells internally, so your job is to make them look smart to their boss.

Framework: GTM models that work (Czakon)

Pick the one that fits your product and ICP; don't run all four half-heartedly.

ModelFits whenThe motion
Open sourceinfra/dev-tool, trust & inspectability matterOSS core → adoption → paid cloud/enterprise
PLG / self-servefast time-to-value, dev = buyer for small teamsfree tier → usage → expand → sales-assist on big accounts
Inboundyou can own the problem's content/SEOeducate on the problem → capture → nurture
Sales-led / ABMhigh ACV, complex enterprise, few big logostarget named accounts, land via a dev champion

Most dev tools are PLG + a sales-assist overlay for the accounts worth a human.

Framework: enable the champion (Czakon + Frankl)

Give the developer what they need to sell up:

  • The Kairos case for their boss (weeks off a release cycle, risk reduced), see value-prop-that-converts.
  • A one-pager / ROI snippet they can paste into an internal thread.
  • Security/compliance answers the buyer will ask (SOC 2, data handling), the CTO's real fears.
  • Proof: attributed results from peers at comparable companies.

Persona → sale map (Frankl): Alpha Dev finds & advocates → VPE/SRE validate feasibility → Empowered CTO approves budget → procurement handles terms (late, enterprise only). A complex sale needs a "what's in it for me" for each. Nail one persona and you get great meetings and no decisions.

Decision tree: when to introduce paid

Has the developer hit real, repeated value (Activation)?
├─ NO  → too early. Gating now kills adoption. Keep delivering value.
└─ YES → is this a small team (dev controls spend)?
         ├─ YES → self-serve upgrade in-product; keep it frictionless.
         └─ NO  → trigger sales-assist: help the champion build the internal case.

Close your first $1M yourself. Don't hand off sales before you've done it. Teaching a rep is far harder than teaching a founder who's felt the objections firsthand (Frankl).

Mistakes that look reasonable

  • Expecting developers to have budget: the Alpha Dev loves you and cannot pay you.
  • Gating value too early: a paywall before the aha moment converts curiosity into a bounce.
  • Cold-selling the VP: bypassing the champion; the buyer trusts their engineer, not your email.
  • No champion enablement: the developer wants to buy but has nothing to bring to their boss.
  • Four GTM models at 10% each: pick one primary motion and commit.

Your next 30 minutes

  • Name your model (OSS / PLG / inbound / sales-led) and the one you'll commit to first.
  • Identify your happiest free user → that's a champion. Ask what their boss would need to approve budget.
  • Build the champion's one-pager: Kairos case + proof + security answers.
  • Define the Activation moment that must happen before you ever mention paid.

Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). Choosing a GTM model is a bet you live with for years. If you want to talk it through, reach out to me on LinkedIn.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.