Agent skill · Data & Analytics

pricing-sensitivity-model

Van Westendorp price sensitivity, computed from real survey answers — crossings found by interpolation, not read off a chart by eye. Use when someone has (or plans) the four-question pricing survey (too cheap / cheap / expensive / too expensive) and needs the optimal price point, the acceptable range, and a defensible readout. Produces OPP/IPP and the PMC–PME range, the four cumulative curves as data, and a real .xlsx with a live revenue what-if — via the bundled zero-dependency script.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorships scriptsMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill pricing-sensitivity-model --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: yes
Path: skills/pricing-sensitivity-model/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Pricing Sensitivity Model (Van Westendorp) The Van Westendorp Price Sensitivity Meter is fifty years old and still the fastest honest answer to "what should this cost?" — but most readouts are someone squinting at where four lines seem to cross. This skill computes the crossings: cumulative curves built from the actual responses, intersections found by linear interpolation, non-monotone respondents dropped and counted. ## Required Inputs - **Survey responses** — per respondent, the four classic answers as prices: *too cheap* (quality suspect), *cheap* (a bargain), *expensive* (getting dear), *too expensive* (out of the question). 20+ valid responses for a stable read; the script warns below that and refuses below 5. - **Segment splits** (optional) — the tool doesn't segment; run it per segment and compare, which is usually where the real finding is. If the survey hasn't run yet, produce the four questions verbatim and the screener instead, then stop — don't invent responses. ## Output Format 1. **The four points** — **OPP** (optimal price point: too-cheap × too-expensive crossing), **IPP** (indifference: cheap × expensive), and the acceptable range **PMC–PME**. Each with one sent

What's inside
Steps it walks through
  1. Required Inputs
  2. Output Format
  3. Programmatic Helper
  4. Quality Checks
  5. Anti-Patterns
Ships with 1 file
  • scripts/van_westendorp.py
Commands it runs
python3 scripts/van_westendorp.py analyze pricing.xlsx --responses-file survey.json
More from pm-claude-skills
All skills →
About this skill
What does the pricing-sensitivity-model skill do?

Van Westendorp price sensitivity, computed from real survey answers — crossings found by interpolation, not read off a chart by eye. Use when someone has (or plans) the four-question pricing survey (too cheap / cheap / expensive / too expensive) and needs the optimal price point, the acceptable range, and a defensible readout. Produces OPP/IPP and the PMC–PME range, the four cumulative curves as data, and a real .xlsx with a live revenue what-if — via the bundled zero-dependency script.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill pricing-sensitivity-model --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going