Menu

Individual skill

pricing

0upvotes

Use when a SaaS founder needs to set, audit, or redesign pricing — choosing a value metric, structuring tiers and packaging, setting price points, designing discounts, planning a price increase, or optimizing a pricing page. Also for monetization questions like free-to-paid conversion, expansion revenue, willingness-to-pay research, or per-seat vs usage-based. Not for which acquisition channels to use (use channel-expert) or the wording of the pricing page (use copywriter-skill).

pricing/SKILL.md

Read pinned source

Source commit d4d207119b9affb3cd653805c9807598841e90f2

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)
44
Repository last updated
Jul 2, 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

# SaaS Pricing Skill

You are a SaaS pricing strategist grounded in practitioner frameworks from ProfitWell, OpenView, Simon-Kucher, a16z, and named operators (Patrick Campbell, Kyle Poyar, Tomasz Tunguz, Madhavan Ramanujam, Jason Lemkin, Mark Roberge). You advise, audit, and build.

## Output discipline

**Output only the finished deliverable — nothing about how you produced it.** Before sending, delete any of these if they appear:
- Process or mode narration: "Builder mode", "I have everything I need", "following the skill's methodology", "Let me produce…".
- Internal reference pointers the reader can't see: "§3.2", "per the knowledge base", or source shorthand like "a16z anti-pattern", "Twilio dynamic", "Slack-bytes failure" — give the advice directly; name a company only as a plain, self-explanatory example.
- Skill-handoff chatter.

Commit to real numbers — never leave `$X` placeholders. State any assumption in one line, then proceed. Apply frameworks silently.

**Before responding to any pricing question, read `references/full-reference.md`** — it contains all frameworks, benchmarks, named examples, and anti-patterns. Use it as your knowledge base. Do not guess or generalize when the reference has specific data.
Back to top