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.
The Scenario
Pricing is one of the hardest go-to-market decisions. Ask a budget buyer and they’ll say it’s too expensive. Ask a premium buyer and they’ll say it’s reasonable. The truth lives in the tension between them. This playbook creates two opposing personas and runs them through the same Focus Group evaluating your product at multiple price points. The output is a structured price-sensitivity analysis from opposing perspectives.Mavera-only workflow. No conjoint analysis software, no survey panels, no incentive budgets. Just Mavera’s Personas, Focus Groups, and Chat surfaces.
When to Use This
- Pre-launch pricing decisions — find the range that maximizes both WTP and adoption.
- Tier structure design — which features justify premium vs standard pricing?
- Price increase planning — simulate reactions from loyal customers and price-sensitive prospects.
- Competitive pricing — test your price against a competitor’s with opposing buyer mindsets.
- Freemium vs paid debates — let opposing personas argue for and against free tiers.
Architecture
| Mavera Surface | Role in Pipeline |
|---|---|
Personas (POST /personas) | Create opposing buyer archetypes |
Focus Groups (POST /focus-groups) | Both personas evaluate the product at 4 price points |
| Chat (OpenAI-compatible) | Synthesize opposing viewpoints into a recommendation |
What You Need
| Requirement | Details |
|---|---|
| Mavera API key | Starts with mvra_live_. Get one at Developer Settings. |
| Python 3.8+ or Node.js 18+ | requests for Python; native fetch for Node. |
| Credits | ~85–205 total. See Credits Estimate. |
Step 1 — Create Opposing Personas
The key is making these genuinely opposed — not just different price preferences, but different value frameworks.Step 2 — Define Product and Price Points
Step 3 — Run the Debate Focus Group
Both personas participate in the same group. Questions surface the tension between their opposing value frameworks.Step 4 — Parse the Debate
Separate responses by persona type and display side by side.Step 5 — Generate Pricing Recommendation
Example Output
Variations
Add a 'Pragmatic Middle' persona
Add a 'Pragmatic Middle' persona
Test specific feature bundles per tier
Test specific feature bundles per tier
Iterate with refined price points
Iterate with refined price points
After the first debate narrows the range, test smaller increments:
Use Mave for competitive benchmarking first
Use Mave for competitive benchmarking first
Industry-specific opposing personas
Industry-specific opposing personas
Credits Estimate
| Operation | Typical Cost | Notes |
|---|---|---|
| Persona creation (×2) | 0–10 | One-time; reuse across runs |
| Focus Group (2 personas, 10 respondents, 8 questions) | 80–180 | Primary cost driver |
| Chat recommendation | 5–15 | Single synthesis call |
| Total | ~85–205 |
What’s Next
Industry Panel Simulation
Expand from 2 opposing personas to 10 buying-committee members
Message Testing Matrix
Test which messaging angle works best at each price point
Pricing Research
Full Van Westendorp analysis with persona segments
Generational Content Testing
How pricing perception varies across age demographics
Persona Selection Guide
Choose the right persona types for your research goal
Credits & Budget
Pre-flight checks and usage tracking