Green & Rao (conjoint) · Louviere (MaxDiff) · Ramanujam
4 · Conjoint / MaxDiff — what goes in which tier
| Method | What it does | Use it to |
| Choice-based conjoint (CBC) | Show bundles (features × price), force trade-off choices, estimate part-worth utility per feature. WTP for attribute = utility ÷ price-coefficient | Decide tier-movers vs table stakes; simulate share/revenue under a proposed line-up |
| MaxDiff (best–worst) | Cheaper, no price; ranks features by relative importance | Triage the feature list when you only need "what do they value most?" |
Use MaxDiff to triage the feature list, conjoint to price the bundle. Map outputs to Ramanujam's three buckets:
Leaders
High WTP + tier-mover — lead the tier, charge for it.
Fillers
Low WTP — round out the tier, don't build the story on them.
Killers
Negative part-worth or "expected free" — never bundle a Killer with a Leader.
Ramanujam · Campbell (value metric)
6 · Tier architecture — Good / Better / Best
Inter-tier ratio ~1 : 2.5–3 : 5 (directional). With Better = $199 → Good ≈ $79 (the "1"), Best ≈ $399–$499 ($79 × 5 ≈ $395, rounded to an anchor).
Good
$79/mo
the "1"
Entry — charm-priced for self-serve.
Most popular
Better
$199/mo
~2.5–3×
Center-stage default — the triangulated price.
Best
$399–499/mo
~5×
Anchors the page — list first / most-prominent.
Want a higher Best ($499–$599)? Fine — but that's stretching above 5× as a deliberate anchor (read it as ~1 : 2.5–3 : 5–6); don't present it as a clean 5× derivation, because it isn't.
- Anchoring — list Best first / most-prominent so it sets the reference and makes Better look reasonable.
- Center-stage — make Better the highlighted "most popular"; most buyers pick the middle when one is framed as default.
- Decoy (asymmetric dominance) — a tier clearly dominated by Better pushes choice toward it; use sparingly, never deceptively.
Round vs charm: charm ($199, $49) signals value / deal — self-serve, monthly, B2C. Round ($200, $2,000, $50k) signals quality / trust / premium — B2B annual, sales-led. Match the signal to the buyer.
Each tier needs a value metric (Campbell) — the unit that scales with delivered value (seats, events, GB, resolved tasks). The bill should grow as the customer succeeds.
7 · Price fences — let segments self-sort without arbitrage
A fence is a rule that keeps a low-WTP buyer from taking the high-WTP price. Three families:
| Fence | Mechanism | Examples | Watch-out |
| Feature / product | capability gating | advanced analytics, SSO/SAML, API limits, SLA, audit logs | gate SSO behind premium only when moving up-market — "SSO is table stakes" is survivorship bias |
| Usage / metric | quantity of the value metric | seats, events, rows, storage, calls, environments | the metric must be one the buyer equates with "more value," and hard to game / under-report |
| Segment / identity | who or how they buy | student / nonprofit / region / PPP, channel, annual vs monthly, volume | needs verification + must be defensible; geographic fences invite grey-market arbitrage |
Rule: a fence is legitimate only if the lower-WTP segment can't easily jump it and the gating tracks real value — not artificial crippling (which becomes a Killer).