Menu

Individual skill

dev-tool-pricing

0upvotes

Use this skill when setting or fixing the price of a developer tool or technical product: choosing the value metric, drawing the free-to-paid line, structuring tiers, and finding the actual number. Produces a value metric, a packaging model, and a defensible price grounded in evidence. Triggers on "what should I charge", "how do I price this", "free vs paid", "pricing tiers", "value metric", "usage-based vs per-seat", "we're too cheap", "developers won't pay", "should I charge yet".

skills/shane-oconnor/dev-tool-pricing/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Applies when you are guessing at a price, priced on a gut feeling and feel stuck, don't know where the free line goes, or believe your users won't pay so you never charge. Produces a value metric, a free-to-paid packaging model, and a defensible number, from evidence rather than fear.

## The three decisions, in order

Most founders skip to the third and wonder why nothing converts.

1. **Value metric** — what you charge *per*. The most important call; get it wrong and no tier structure saves you.
2. **Packaging** — what is free, paid, and enterprise, and what triggers the upgrade.
3. **The number** — the actual price on each tier.

Price against the value the customer receives, never against your cost or your fear. Your infrastructure bill is a floor, not a strategy.

## Are you ready to price?
Back to top