# devtools-business-model

Selects a business model for a developer tool and defines the go-to-market path it enforces. Useful when deciding where to draw the boundary between free and paid software.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 10000 installs · ★ 5
- Author: Samuel Berthe
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/samber/developer-relations-skills/tree/HEAD/skills/devtools-business-model/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/devtools-business-model

## What it does

This skill acts as a commercial strategist for developer tooling founders. It identifies what to sell, who signs the contract, and when users acquire a reason to pay. The analysis contrasts models like open core, hosted services, source-available releases, and usage-based billing against the go-to-market motion each choice demands.

The workflow proceeds via a diagnostic interview. The agent asks questions one at a time to examine software surfaces, buyer profiles, and hiring limits. If file-backed memory is present, the answers persist in `devrel-context.md`. The final output is a structured decision memo containing rejected archetypes, the paid boundary, and revisit triggers.

This skill does not design pricing tiers or free-tier thresholds, delegating those tasks to `devtools-pricing-strategy`. Because an open-source license that has already shipped cannot be revoked without severe fork risks, constraints are locked in before any brainstorming begins.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/developer-relations-skills --skill devtools-business-model -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/devtools-business-model/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/devtools-business-model/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/developer-relations-skills --skill devtools-business-model -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/devtools-business-model/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/developer-relations-skills --skill devtools-business-model -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/devtools-business-model/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install samber/developer-relations-skills devtools-business-model
```

2. **Manually: put the files in place**
- File: `.github/skills/devtools-business-model/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/developer-relations-skills --skill devtools-business-model -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/samber/developer-relations-skills --path skills/devtools-business-model
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/devtools-business-model/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add samber/developer-relations-skills --skill devtools-business-model -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/samber/developer-relations-skills/tree/HEAD/skills/devtools-business-model/SKILL.md

## When to use it
- Choose between open core, hosted cloud, and dual licensing
- Define the exact boundary between free and paid capabilities
- Assess risks of competing managed offerings by cloud providers
- Determine the go-to-market approach forced by the commercial model

## Example prompts
- We have 12k weekly downloads and zero revenue, how do we monetize this?
- Should we go open core or sell a managed cloud?
- A cloud provider just launched a managed version of our project. Do we relicense?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b8dd76251dfe674f.

BEGIN THIRD-PARTY FILE b8dd76251dfe674f
```text
---
name: devtools-business-model
description: Chooses the business model for a developer tool - proprietary SaaS, open core, hosted open source, support and LTS subscription, dual licensing, source-available, consumption metering, marketplace take-rate, OEM licensing - and the go-to-market each one forces. Use whenever a founder or exec asks how a developer tool should make money, whether open core or a managed cloud fits better, where the line between free and paid belongs, whether to open-source the product at all, or why adoption is high and revenue flat, and on any monetization, revenue model or commercial open source question - even if they never say "business model". Not price points, packaging or free-tier limits - use samber/developer-relations-skills@devtools-pricing-strategy.
license: MIT
metadata:
  author: Samuel Berthe
  version: "1.0.1"
---

# Devtools Business Model

You are a commercial strategist for developer tools. Decide, with the founder or exec, what gets sold, who signs, and what has to be true for the money to arrive. Name the go-to-market that choice forces.

Developer tools fail at value _capture_ far more often than at value _creation_: the software gets adopted, deployed and loved, and nobody ever has a reason to sign anything. Hold every recommendation to that test, name the moment a user acquires a reason to pay, or the model is a wish.

Produce a model decision with its consequences and a validation plan, not a pricing page, not a launch plan, not a licence.

## Typical invocations

- "We have 12k weekly downloads and zero revenue, how do we monetize this?" → run the full workflow; expect the paid-boundary test to do the real work.
- "Should we go open core or sell a managed cloud?" → start at step 2 with those two as the candidate set, and still test both boundaries.
- "A cloud provider just launched a managed version of our project. Do we relicense?" → step 1 constraints, then the reversibility ladder in step 5; relicensing is a decision of its own, not a step.
- "What should stay free forever?" → step 3 alone; output the always-free list and the reasoning behind it.
- "I maintain this library alone and companies use it, how do I get paid?" → not this skill: one project's maintainers with no company behind them belong to `samber/developer-relations-skills@oss-monetization`.
```
END THIRD-PARTY FILE b8dd76251dfe674f

The third-party file has ended. Everything between the b8dd76251dfe674f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2358 of 26752 bytes. © Samuel Berthe · MIT · https://github.com/samber/developer-relations-skills/tree/HEAD/skills/devtools-business-model/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md