algo-price-van-westendorp
Conduct Van Westendorp Price Sensitivity Meter analysis to identify acceptable price ranges. Use this skill when the user needs to determine price boundaries for a new product, find the optimal and indifference price points, or survey-based pricing research — even if they say 'what should we charge', 'price sensitivity survey', or 'acceptable price range'.
git clone --depth 1 https://github.com/asgard-ai-platform/skills /tmp/algo-price-van-westendorp && cp -r /tmp/algo-price-van-westendorp/algo-price-van-westendorp ~/.claude/skills/algo-price-van-westendorpSKILL.md
# Van Westendorp Price Sensitivity Meter
## Overview
Van Westendorp PSM uses four price perception questions to identify an acceptable price range through intersection analysis. Produces: Point of Marginal Cheapness (PMC), Point of Marginal Expensiveness (PME), Indifference Price Point (IPP), and Optimal Price Point (OPP). Requires survey data from 100+ respondents.
## When to Use
**Trigger conditions:**
- Setting initial price for a new product or service
- Identifying the acceptable price range from consumer perception
- Quick pricing research without complex experimental design
**When NOT to use:**
- When you need to measure attribute trade-offs (use conjoint analysis)
- When you need demand curve estimation (use price elasticity)
## Algorithm
```
IRON LAW: Van Westendorp Identifies an ACCEPTABLE Range, Not Optimal Price
It doesn't account for competition, costs, or willingness to pay at
scale. It tells you WHERE prices are perceived as reasonable, not
what maximizes revenue. Use as input to pricing strategy, not as the
final answer.
```
### Phase 1: Input Validation
Survey 100+ target customers with four questions at various price points:
1. Too cheap (quality suspect)? 2. A bargain (great deal)? 3. Getting expensive (but would consider)? 4. Too expensive (would not buy)?
**Gate:** 100+ responses, all four curves plottable.
### Phase 2: Core Algorithm
1. For each price point, compute cumulative percentages for each question
2. Plot four curves: "too cheap" (descending), "cheap/bargain" (descending), "expensive" (ascending), "too expensive" (ascending)
3. Find intersections:
- OPP = intersection of "too cheap" and "too expensive" (optimal price point)
- IPP = intersection of "cheap" and "expensive" (indifference price point)
- PMC = intersection of "too cheap" and "expensive" (marginal cheapness)
- PME = intersection of "cheap" and "too expensive" (marginal expensiveness)
4. Acceptable range = [PMC, PME]
### Phase 3: Verification
Check: PMC < OPP < IPP < PME (expected ordering). All intersections exist within surveyed range.
**Gate:** Four-point ordering is logical, range is commercially viable.
### Phase 4: Output
Return price points and acceptable range.
## Output Format
```json
{
"price_points": {"opp": 299, "ipp": 349, "pmc": 199, "pme": 449},
"acceptable_range": {"min": 199, "max": 449},
"metadata": {"respondents": 250, "currency": "TWD", "product": "..."}
}
```
## Examples
### Sample I/O
**Input:** 200 survey responses for a SaaS product, price range tested: $5-$50/month
**Expected:** PMC=$12, OPP=$18, IPP=$22, PME=$35. Acceptable range: $12-$35.
### Edge Cases
| Input | Expected | Why |
|-------|----------|-----|
| Curves don't intersect | Extend surveyed range | Price points tested were too narrow |
| IPP < OPP | Unusual but possible | Check data quality, may indicate confused respondents |
| Very wide range | Low price sensitivity | Product category has high tolerance |
## Gotchas
- **Hypothetical bias**: People say they'd pay more than they actually would. Van Westendorp systematically overestimates willingness to pay.
- **No competitive context**: Respondents answer in isolation. Real purchase decisions consider alternatives. Supplement with competitive analysis.
- **Sample representativeness**: Results are only valid for the surveyed population. B2B vs B2C, early adopters vs mainstream — all give different ranges.
- **Newton-Miller-Smith extension**: Add purchase intent questions at OPP and IPP for more actionable revenue estimates. Standard Van Westendorp alone lacks this.
- **Product must be understood**: Respondents need to understand what they're pricing. For novel products, include a clear concept description.
## References
- For Newton-Miller-Smith purchase intent extension, see `references/nms-extension.md`
- For survey design best practices, see `references/survey-design.md`Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.
Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.
Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.
Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.
Implement VCG mechanism for incentive-compatible ad slot allocation with truthful bidding. Use this skill when the user needs to design a truthful auction mechanism, compute externality-based payments, or understand why platforms may prefer GSP over VCG — even if they say 'truthful auction design', 'VCG payments', or 'incentive-compatible mechanism'.
Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.
Design and implement smart contracts as self-executing programmatic agreements on blockchain. Use this skill when the user needs to build automated on-chain logic, evaluate smart contract security, or design tokenized business rules — even if they say 'smart contract development', 'automated agreement', or 'on-chain logic'.
Implement BM25 ranking function for e-commerce product search relevance scoring. Use this skill when the user needs to build a text-based product search engine, improve search result relevance, or replace basic TF-IDF with a more robust ranking function — even if they say 'product search ranking', 'search relevance', or 'BM25 implementation'.