Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Mavera Surfaces Used
| Surface | Role |
|---|---|
Personas (POST /personas, GET /personas) | Create budget-segment personas (price-sensitive, mid-market, enterprise) |
Focus Groups (POST /focus-groups) | Run pricing sensitivity study with Slider, Likert, and Open-Ended questions |
Chat + response_format | Synthesize results into a price sensitivity report with optimal price range |
The Van Westendorp Price Sensitivity Meter uses four questions to find optimal pricing. This playbook adapts those questions to Mavera’s Slider question type, running them across budget-segment personas to produce a synthetic price sensitivity analysis.
What Value Does Mavera Add?
| Value | How |
|---|---|
| Insurance | Test pricing with 4 distinct budget segments before announcing. Catch price-perception mismatches early. |
| Opening new doors | Run pricing studies for new features, bundles, or market segments in an afternoon — no recruiting, no incentives. |
| Saving time | Traditional Van Westendorp studies take 2-4 weeks and $10K+. This runs in 30 minutes for ~300 credits. |
When to Use This
- You’re setting launch pricing for a new product or feature and need segment-specific sensitivity data.
- You’re considering a price increase and want to estimate the elasticity before announcing.
- You’re designing tiered pricing and need to validate where tier boundaries should fall.
- You’re entering a new market and need a pricing anchor based on local buyer expectations.
What You Need
| Requirement | Details |
|---|---|
| Mavera API key | Starts with mvra_live_. Get one at Developer Settings. |
| Workspace ID | From your dashboard URL (ws_...). |
| Product description | Clear description of what’s being priced (features, value prop, competitive context). |
| Price range | Reasonable min/max for the Slider questions (e.g. 500/month). |
| Credits | ~200–500 total. See Credits Estimate. |
| Python 3.8+ or Node.js 18+ | requests / openai for Python; native fetch for Node. |
The Van Westendorp Framework
The original Van Westendorp asks four questions. Mavera adapts each to a Slider question type:| Van Westendorp Question | Mavera Slider | What It Finds |
|---|---|---|
| ”At what price would this be too expensive — you wouldn’t consider buying?” | Slider: max | Upper bound (ceiling) |
| “At what price would this be expensive but worth considering?” | Slider: max | High-end acceptable range |
| ”At what price would this be a great deal — a bargain?” | Slider: max | Low-end sweet spot |
| ”At what price would this be so cheap you’d question the quality?” | Slider: max | Lower bound (floor) |
- Point of Marginal Cheapness (PMC): Where “too cheap” meets “bargain”
- Point of Marginal Expensiveness (PME): Where “too expensive” meets “expensive but worth it”
- Optimal Price Point (OPP): Where “too cheap” meets “too expensive”
- Acceptable Price Range: Between PMC and PME
Architecture
The Flow
Define your product and price range
Write a clear product description and set a realistic price range for the Slider min/max. Too narrow misses the range; too wide reduces precision.
Create 4 budget-segment personas
Build personas representing distinct budget tiers: bootstrapped startup, growth-stage, mid-market, and enterprise. Each brings a different price sensitivity.
Run the pricing Focus Group
40 respondents across 4 personas (10 per persona). 4 Van Westendorp Slider questions + 1 Likert (value-for-money) + 1 Open-Ended (pricing model preference).
Poll for completion
Pricing focus groups with 40 respondents and 6 questions typically complete in 5-10 minutes.
Calculate price sensitivity curves
Extract Slider medians and distributions. Compute the four intersection points.
Code: Full Pricing Research Pipeline
Setup
Stage 1 — Create Budget-Segment Personas
Stage 2 — Run Pricing Focus Group
Six questions: 4 Van Westendorp Sliders, 1 Likert (value-for-money), 1 Open-Ended (pricing model).Stage 3 — Calculate Price Sensitivity
Extract Slider values and compute the Van Westendorp intersection points.Stage 4 — Generate Pricing Report
Running the Full Pipeline
Example Output
Variations
Test price increases on existing customers
Test price increases on existing customers
Create personas representing your current customer base. Test the proposed increase against their current price anchor:
Feature-value analysis
Feature-value analysis
Add questions that price individual features to find which drive willingness-to-pay:
Geographic pricing
Geographic pricing
Run the same study with region-specific personas (US, EU, APAC, LATAM) to set geographic pricing:
Competitive price anchoring
Competitive price anchoring
Include competitor pricing in the context so personas anchor relative to known alternatives:
Credits Estimate
| Stage | Typical Cost | Notes |
|---|---|---|
| Create 4 personas | 0 | Persona creation is free |
| Focus Group (N=40, 6 questions) | 200–400 credits | 4 sliders + 1 likert + 1 open-ended |
| Pricing report (1 chat call) | 5–15 credits | Single structured output |
| Total | ~205–415 credits |
See Also
Focus Groups
Slider, Likert, and all 12 question types
Positioning Workshop
Test positioning alongside pricing
Market Entry Research
Research the market before pricing
Brand Perception Audit
Understand brand perception context for pricing
Persona Debate
Opposing personas evaluate pricing at different points
Credits & Budget
Track and manage credit usage