Develop a B2B pricing strategy: value metrics, packaging, discounting policy,…
- User
Develop a B2B pricing strategy: value metrics, packaging, discounting policy, willingness-to-pay research, pricing experiments, and governance. Provide a step-by-step playbook and guardrails to avoid common traps.
Assistant
This is a comprehensive request for a B2B pricing strategy playbook. Let me structure this thoroughly, covering all the requested areas:
- Value Metrics - how to identify and select the right pricing dimensions
- Packaging - how to structure tiers and bundles
- Discounting Policy - frameworks for when/how to discount
- Willingness-to-Pay Research - methodologies to understand price sensitivity
- Pricing Experiments - how to test pricing safely
- Governance - who owns pricing decisions and how
Plus common traps and guardrails throughout.
Let me create a detailed, practical playbook that a B2B company could actually implement.
I should structure this as:
- Executive overview
- Each major section with step-by-step guidance
- Templates and frameworks where helpful
- Common traps and guardrails for each section
- Implementation timeline
- Key metrics to track
Let me make this extremely practical and comprehensive. # B2B Pricing Strategy Playbook
Executive Summary
This playbook provides a comprehensive framework for developing, implementing, and governing B2B pricing. It's designed to be actionable whether you're pricing a new product or restructuring existing pricing.
Table of Contents
- Value Metrics: Finding Your Pricing Dimension
- Packaging Strategy: Structuring Your Offer
- Willingness-to-Pay Research
- Pricing Experiments
- Discounting Policy
- Pricing Governance
- Common Traps & Guardrails
- Implementation Roadmap
1. Value Metrics
What is a Value Metric?
A value metric is the unit by which you charge customers. It should scale with the value customers receive and align company growth with customer success.
Step-by-Step Process
Step 1.1: Map Customer Value Drivers
┌─────────────────────────────────────────────────────────────────┐ │ VALUE DRIVER MAPPING │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ Customer Goal ──► Your Solution ──► Measurable Outcome │ │ │ │ Examples: │ │ • "Close more deals" → CRM → Revenue influenced │ │ • "Reduce support costs" → Helpdesk → Tickets deflected │ │ • "Ship faster" → CI/CD tool → Deployments/month │ │ • "Manage risk" → Compliance tool → Assets monitored │ │ │ └─────────────────────────────────────────────────────────────────┘Exercise Template:
Customer Job-to-be-Done How We Help Value Created Potential Metric Step 1.2: Evaluate Candidate Metrics
Score each potential metric against these criteria (1-5 scale):
Criteria Description Weight Value Alignment Does usage correlate with value received? 25% Predictability Can customers forecast their costs? 20% Scalability Does it grow naturally with customer success? 20% Measurability Can you track it accurately? 15% Simplicity Is it easy to understand and explain? 15% Defensibility Is it hard for customers to game? 5% Scoring Matrix:
VALUE METRIC EVALUATION Metric Val Pred Scale Meas Simp Def TOTAL ───────────────────────────────────────────────────────────── Per user/seat 4 5 3 5 5 4 4.15 Per transaction 5 2 5 5 3 4 3.95 Per API call 3 2 4 5 4 3 3.35 Per GB stored 3 4 4 5 4 3 3.70 Per revenue % 5 3 5 3 4 2 4.00 Flat platform fee 2 5 1 5 5 5 3.30Step 1.3: Test Metric with Customer Interviews
Interview Script:
PART 1: Value Understanding "Walk me through how you measure success with [product category]?" "What would make this solution 10x more valuable to you?" "How do you justify software purchases internally?" PART 2: Metric Reaction "If we priced based on [metric], how would that feel?" "Could you predict your costs month-to-month?" "Does this feel fair relative to value received?" PART 3: Budget Dynamics "Who controls the budget for this?" "Is this OpEx or CapEx for you?" "Do you prefer predictable flat fees or variable usage-based?"Step 1.4: Choose Primary and Secondary Metrics
┌─────────────────────────────────────────────────────────────────┐ │ METRIC ARCHITECTURE │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ PRIMARY METRIC (determines tier/base price) │ │ └── Usually: users, revenue processed, core usage unit │ │ │ │ SECONDARY METRICS (create expansion opportunities) │ │ └── Usually: storage, API calls, advanced features │ │ │ │ Example - Project Management Tool: │ │ • Primary: Number of users │ │ • Secondary: Storage (GB), Guests, Automations/month │ │ │ └─────────────────────────────────────────────────────────────────┘Value Metric Guardrails
Trap Guardrail Choosing a metric customers can't predict Offer cost calculators and billing alerts Metric that punishes success (charges more when it works) Ensure value grows faster than cost Too many metrics (bill shock, complexity) Maximum 3 metrics in pricing model Metric that doesn't scale with company size Test with 10x customer scenarios
2. Packaging Strategy
Step-by-Step Process
Step 2.1: Define Your Packaging Goals
┌─────────────────────────────────────────────────────────────────┐ │ PACKAGING OBJECTIVES │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ □ Capture different willingness-to-pay segments │ │ □ Create clear upgrade paths (land and expand) │ │ □ Simplify buying decision │ │ □ Differentiate from competitors │ │ □ Align with sales motion (self-serve vs. sales-assisted) │ │ □ Enable rapid time-to-value for new customers │ │ │ └─────────────────────────────────────────────────────────────────┘Step 2.2: Segment Your Customer Base
Create a 2x2 or segmentation matrix:
COMPANY SIZE Small/Mid │ Enterprise ───────────────────────────────────── Simple │ STARTER │ TEAM │ Use │ Self-serve │ Sales-assist │ Case │ $0-500/mo │ $500-5K/mo │ ─────────────│────────────────│───────────────────│ Complex │ PRO │ ENTERPRISE │ Use │ Self-serve │ Sales-led │ Case │ $200-2K/mo │ $5K-100K+/mo │ ─────────────────────────────────────────────────────Step 2.3: Design Your Tier Structure
The "Good-Better-Best" Framework:
┌────────────────┬────────────────┬────────────────┬────────────────┐ │ │ STARTER │ PRO │ ENTERPRISE │ │ │ (Acquire) │ (Convert) │ (Expand) │ ├────────────────┼────────────────┼────────────────┼────────────────┤ │ Target │ Individual/ │ Growing teams │ Large orgs │ │ │ small teams │ │ │ ├────────────────┼────────────────┼────────────────┼────────────────┤ │ Price Point │ Free or low │ Sweet spot │ Premium │ │ │ (decoy/hook) │ (volume) │ (margin) │ ├────────────────┼────────────────┼────────────────┼────────────────┤ │ Sales Motion │ Self-serve │ Product-led │ Sales-led │ │ │ │ + light sales │ │ ├────────────────┼────────────────┼────────────────┼────────────────┤ │ Features │ Core value │ Collaboration │ Control & │ │ Theme │ only │ & productivity │ customization │ ├────────────────┼────────────────┼────────────────┼────────────────┤ │ Key Features │ • Basic func. │ • Integrations │ • SSO/SAML │ │ │ • Limited │ • Reporting │ • Custom SLAs │ │ │ users/usage │ • Team mgmt │ • Dedicated │ │ │ │ • API access │ support │ │ │ │ │ • Audit logs │ └────────────────┴────────────────┴────────────────┴────────────────┘Step 2.4: Design Feature Fences
Feature fences are the reasons customers upgrade. They should be:
NATURAL FENCES (Best) • Team size grows → need more seats • Data volume grows → need more storage • Business scales → hit usage limits CAPABILITY FENCES (Good) • Advanced integrations • Better reporting/analytics • Automation features ARTIFICIAL FENCES (Use Carefully) • Support response time • API rate limits • Export capabilities AVOID • Features that feel punitive • Fences that fragment core workflows • Anything that damages user experience significantlyStep 2.5: Create Add-Ons Strategy
┌─────────────────────────────────────────────────────────────────┐ │ ADD-ON ARCHITECTURE │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ ALWAYS ADD-ONS (Never in base tiers) │ │ • Premium support/SLAs │ │ • Custom implementation services │ │ • Highly specialized features (<20% adoption potential) │ │ │ │ TIER-LOCKED ADD-ONS (Available only at higher tiers) │ │ • Advanced security features │ │ • Enterprise integrations │ │ │ │ UNIVERSAL ADD-ONS (Available to all tiers) │ │ • Additional capacity (users, storage, API calls) │ │ • Training and certification │ │ │ └─────────────────────────────────────────────────────────────────┘Packaging Guardrails
Trap Guardrail Too many tiers (>4 creates confusion) Maximum 4 tiers (often 3 is ideal) Hollow starter tier Ensure real value in lowest tier Feature overload in pricing page Maximum 10 feature rows on comparison "Contact us" with no anchor Always show starting prices or ranges
3. Willingness-to-Pay Research
Research Methods Overview
┌─────────────────────────────────────────────────────────────────┐ │ WTP RESEARCH METHODS │ ├──────────────────┬──────────────────────────────────────────────┤ │ METHOD │ BEST FOR │ ACCURACY │ ├──────────────────┼────────────────────────────┼─────────────────┤ │ Van Westendorp │ New products, ranges │ Medium │ │ Gabor-Granger │ Specific price points │ Medium-High │ │ Conjoint │ Feature/price trade-offs │ High │ │ Monadic Testing │ A/B price validation │ High │ │ Economic Value │ Value-based pricing │ Context-dep. │ │ Win/Loss Data │ Competitive intelligence │ High (actual) │ │ Expert Interview │ Enterprise deals │ Medium │ └──────────────────┴────────────────────────────┴─────────────────┘Step-by-Step Process
Step 3.1: Van Westendorp Price Sensitivity Meter
Ask these four questions:
Q1: "At what price would you consider [product] to be so expensive that you would not consider buying it?" (Too Expensive) Q2: "At what price would you consider [product] to be priced so low that you would feel the quality couldn't be very good?" (Too Cheap) Q3: "At what price would you consider [product] starting to get expensive, but you still might consider buying it?" (Expensive) Q4: "At what price would you consider [product] to be a bargain— a great buy for the money?" (Cheap/Bargain)Analysis:
PRICE ($) │ 400 │ ╱ Too Expensive │ ╱ 300 │ ╱ ╲ Expensive │ ╱ ╲ 200 │─ ─ ─ ─ ─ ─ ─ ─ ─ X ─ ─ ─ ─ ─ ─ ─ ─ X ─ ─ Optimal Range │ ╱ │ ╲ 100 │ ╱ │ ╲ Cheap │ ╱ │ ╲ 0 │─────╱────────────┼───────────────────────╲── └──────────────────┴─────────────────────────► % Respondents OPP IDP OPP = Optimal Price Point (intersection of Too Cheap & Too Expensive) IDP = Indifference Price Point (intersection of Cheap & Expensive) Acceptable Range = Between these intersectionsStep 3.2: Gabor-Granger Direct Pricing
Process:
┌─────────────────────────────────────────────────────────────────┐ │ GABOR-GRANGER FLOW │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ 1. Show product description at MEDIUM price │ │ └─► "Would you buy at $X?" │ │ │ │ 2. If YES → Show HIGHER price │ │ If NO → Show LOWER price │ │ │ │ 3. Continue until boundaries found │ │ │ │ 4. Calculate: │ │ • % who would buy at each price point │ │ • Revenue-maximizing price (Price × Purchase Intent) │ │ │ └─────────────────────────────────────────────────────────────────┘Output Example:
Price Purchase Intent Revenue Index $99 82% 81.18 $149 68% 101.32 $199 51% 101.49 ← Optimal $249 34% 84.66 $299 21% 62.79 Step 3.3: Conjoint Analysis (Advanced)
When to use: You need to understand trade-offs between features AND price.
Setup:
STEP 1: Define Attributes and Levels Attribute Levels ───────────────────────────────────────── Price $99, $199, $299, $399 Users 5, 25, 100, Unlimited Storage 10GB, 100GB, 1TB Support Email, Chat, Phone, Dedicated Integrations Basic (5), Pro (25), All (100+) STEP 2: Create Choice Tasks "Which option would you choose?" ┌─────────────┬─────────────┬─────────────┐ │ Option A │ Option B │ Option C │ ├─────────────┼─────────────┼─────────────┤ │ $199/mo │ $299/mo │ $399/mo │ │ 25 users │ 100 users │ Unlimited │ │ 100GB │ 100GB │ 1TB │ │ Email │ Chat │ Dedicated │ │ Basic integ.│ Pro integ. │ All integ. │ ├─────────────┼─────────────┼─────────────┤ │ [ ] │ [ ] │ [ ] │ └─────────────┴─────────────┴─────────────┘ STEP 3: Analyze Part-Worth Utilities Determine how much each feature level contributes to preference, and convert to dollar values.Sample Output:
FEATURE VALUE ANALYSIS (Willingness to Pay) Feature Value Add ──────────────────────────────────── +75 users +$85/mo +900GB storage +$45/mo Phone support upgrade +$62/mo All integrations +$38/mo → Insight: Users value seats > support > storage > integrationsStep 3.4: Economic Value Analysis
Framework:
ECONOMIC VALUE TO CUSTOMER (EVC) ┌─────────────────────────────────────────────────────────────────┐ │ │ │ ┌───────────────────┐ │ │ │ DIFFERENTIATION │ ← Value of unique benefits │ │ │ VALUE │ vs. next best alternative │ │ ├───────────────────┤ │ │ │ │ │ │ │ REFERENCE │ ← Price of next best │ │ │ VALUE │ alternative │ │ │ │ │ │ └───────────────────┘ │ │ │ │ │ ▼ │ │ TOTAL ECONOMIC VALUE │ │ (Maximum rational price) │ │ │ └─────────────────────────────────────────────────────────────────┘Calculation Template:
ECONOMIC VALUE CALCULATION 1. REFERENCE VALUE Next best alternative: [Competitor X] Their price: $500/month 2. DIFFERENTIATION VALUE (Positive) + Time savings: 10 hrs/mo × $75/hr = $750 + Error reduction: 5% × $10K impact = $500 + Productivity gain: 15% × $2K salary = $300 ───────────────────────────────────────────── Total positive differentiation: $1,550/mo 3. DIFFERENTIATION VALUE (Negative) - Learning curve: 5 hrs × $75/hr ÷ 12mo = ($31) - Missing feature: -$100/mo value gap ───────────────────────────────────────────── Total negative differentiation: ($131/mo) 4. TOTAL ECONOMIC VALUE $500 + $1,550 - $131 = $1,919/month 5. TARGET PRICE (Capture 30-50% of differentiation) $500 + ($1,419 × 40%) = $1,068/monthStep 3.5: Win/Loss Analysis for Pricing Intelligence
Data Collection Template:
WIN/LOSS PRICING DEBRIEF Deal ID: ________ Size: $________ Outcome: Win / Loss 1. Price Discussion □ Price was never a concern □ Price was discussed but not a blocker □ Price required significant negotiation □ Price was primary objection 2. If LOST on price: □ Lost to competitor at lower price → Competitor: ________ Price: $________ □ Lost to "do nothing" / budget constraints □ Lost to internal build 3. Discount requested: ________% Discount given: ________% 4. Features most valued in pricing discussion: ________________________________________________ 5. Would we have won at our price with different: □ Packaging (different features included) □ Contract terms (longer term, different billing) □ Payment structure □ No—price was simply too highWTP Research Guardrails
Trap Guardrail Survey respondents say higher prices than they'd actually pay Discount stated WTP by 20-30% Only researching prospects (not actual buyers) Include 50%+ current customers Asking about price without context Always show value proposition first Small sample size Minimum n=100 per segment Leading questions Use third-party or neutral facilitator
4. Pricing Experiments
Step-by-Step Process
Step 4.1: Choose Your Experiment Type
┌─────────────────────────────────────────────────────────────────┐ │ PRICING EXPERIMENT TYPES │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ GEOGRAPHIC TESTING │ │ • Different prices in different regions │ │ • Pros: Clean separation, real purchase data │ │ • Cons: Exchange rates, cultural differences │ │ │ │ COHORT TESTING │ │ • Different prices for new signups in different time periods │ │ • Pros: Simple, no simultaneous different prices │ │ • Cons: External factors, small samples │ │ │ │ A/B TESTING (Careful!) │ │ • Random assignment to price variants │ │ • Pros: Statistical rigor │ │ • Cons: Ethical concerns, customer discovery risk │ │ │ │ FEATURE/PACKAGE TESTING │ │ • Same price, different packaging │ │ • Pros: Low risk, high learning │ │ • Cons: Doesn't directly test price elasticity │ │ │ │ LANDING PAGE TESTING │ │ • Test conversion at different displayed prices │ │ • Measure: Clicks to pricing page, demo requests │ │ • Pros: Safe (no actual different prices charged) │ │ • Cons: Top of funnel only │ │ │ └─────────────────────────────────────────────────────────────────┘Step 4.2: Design Your Experiment
Experiment Design Template:
PRICING EXPERIMENT BRIEF Hypothesis: ________________________________________________ "We believe [change] will result in [outcome] because [reasoning]" Example: "We believe increasing Pro tier from $49 to $79 will increase revenue per account by 20%+ with less than 10% decrease in conversion rate because WTP research showed strong demand at higher price points." Metric(s): □ Primary: ______________________________________________ □ Secondary: ____________________________________________ □ Guardrail (must not worsen): __________________________ Population: □ New customers only □ Existing customers □ Both □ Segment: ____________________________________________ □ Geography: __________________________________________ Duration: _______ weeks Sample size needed: _______ per variant (use power calculator) Variants: Control: _______________________________________________ Treatment: _____________________________________________ Success criteria: ________________________________________ Rollback trigger: ________________________________________Step 4.3: Calculate Required Sample Size
SAMPLE SIZE CALCULATION Baseline conversion rate: 5% Minimum detectable effect: 20% relative change (5% → 6%) Statistical significance: 95% Statistical power: 80% Formula (simplified): n = 16 × p × (1-p) / (MDE)² Where: p = baseline conversion (0.05) MDE = minimum detectable effect (0.01 or 1pp) n = 16 × 0.05 × 0.95 / (0.01)² n = 7,600 per variant → NEED: ~15,000 total visitors for meaningful resultsStep 4.4: Run Ethically and Safely
Ethical Pricing Experiment Framework:
┌─────────────────────────────────────────────────────────────────┐ │ ETHICAL TESTING GUIDELINES │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ DO: │ │ ✓ Test with new customers who have no existing expectation │ │ ✓ Honor any price a customer sees if they purchase │ │ ✓ Test completely new products or packages │ │ ✓ Use geographic testing (real market differences) │ │ ✓ Test landing page behavior without checkout completion │ │ ✓ Offer grandfathering for existing customers on price hikes │ │ │ │ DON'T: │ │ ✗ Show different prices to same customer on different visits │ │ ✗ Use demographic data to show different prices │ │ ✗ Test prices on existing customers without clear reason │ │ ✗ Refuse to honor a seen price │ │ ✗ Create unreasonable price variance (100%+ difference) │ │ │ └─────────────────────────────────────────────────────────────────┘Step 4.5: Analyze and Decide
Analysis Framework:
EXPERIMENT ANALYSIS TEMPLATE Results Summary: Control Treatment Difference ───────────────────────────────────────────────────────── Sample size 4,521 4,489 Conversions 227 196 Conversion rate 5.02% 4.37% -13.0% Stat. significance p = 0.04 ARPU $142 $178 +25.4% Revenue per visitor $7.13 $7.78 +9.1% Stat. significance p = 0.11 Analysis: ┌─────────────────────────────────────────────────────────────────┐ │ Higher price decreased conversion but increased ARPU │ │ Net revenue impact: +9.1% (not statistically significant) │ │ Need more data OR accept directional learning │ └─────────────────────────────────────────────────────────────────┘ Decision: □ Roll out treatment (clear winner) □ Extend experiment (need more data) □ Roll back to control (clear loser) □ Iterate and test new variant (inconclusive, new hypothesis)Pricing Experiment Guardrails
Trap Guardrail Running tests without sufficient sample Pre-calculate sample size; wait for significance Creating PR/social media risk Cap price variant differences at 30% Stopping tests early on exciting results Pre-commit to duration regardless of interim results Ignoring long-term metrics Track cohort retention + LTV, not just conversion Testing too many things One variable per test; use sequential testing
5. Discounting Policy
Step-by-Step Process
Step 5.1: Define Discount Philosophy
┌─────────────────────────────────────────────────────────────────┐ │ DISCOUNT PHILOSOPHY │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ "Discounts are earned, not given." │ │ │ │ Principles: │ │ 1. Every discount must be exchanged for specific value │ │ 2. Discount authority must be clearly defined │ │ 3. All discounts must be documented and analyzed │ │ 4. Standard discounts should be rare and transparent │ │ 5. Discounting trains customers; be careful what you teach │ │ │ └─────────────────────────────────────────────────────────────────┘Step 5.2: Create Discount Menu
Approved Discount Reasons:
STANDARD DISCOUNT TIERS TIER 1: Rep Discretion (up to 10%) Reason Max Discount ────────────────────────────────────────────── Annual prepay (vs. monthly) 10% Multi-year commitment 10% additional per year Competitive displacement 10% TIER 2: Manager Approval (11-20%) Reason Max Discount ────────────────────────────────────────────── Strategic account potential 15% Case study commitment 10% Partner referral 15% Nonprofit/education 20% TIER 3: VP/C-Level Approval (21-30%) Reason Max Discount ────────────────────────────────────────────── Lighthouse logo (top 50 brand) 25% Platform expansion commitment 25% Volume commit (50+ seats) 20% TIER 4: Exceptional (>30%)—CEO Only Reason Max Discount ────────────────────────────────────────────── Strategic partnership 40% Industry breakthrough account 35% NOTE: Discounts should stack to maximum 35% (except Tier 4 exceptional circumstances)Step 5.3: Design "Give-Get" Framework
Every discount requires something in return:
GIVE-GET DISCOUNT MATRIX Customer Gets │ Customer Gives ───────────────────────────────────────────────────── 10% off │ Annual prepay │ OR 2-year commitment │ OR Logo rights ───────────────────────────────────────────────────── 15% off │ Annual prepay + case study │ OR 3-year commitment │ OR Reference + speaking engagement ───────────────────────────────────────────────────── 20% off │ Annual prepay + 2yr + case study │ OR Multi-product commit │ OR Executive sponsor access ───────────────────────────────────────────────────── 25%+ off │ All of the above │ + Strategic partnership terms │ + Advisory board participation ─────────────────────────────────────────────────────Step 5.4: Create Approval Workflow
DISCOUNT APPROVAL WORKFLOW ┌─────────────────────────────────────────────────────────────────┐ │ │ │ Deal registered Discount Submit for │ │ in CRM requested approval │ │ │ │ │ │ │ ▼ ▼ ▼ │ │ ┌─────────┐ ┌──────────┐ ┌───────────┐ │ │ │ 0-10% │───YES────►│ Auto- │ │ System │ │ │ │ │ │ approved │ │ routes │ │ │ └─────────┘ └──────────┘ │ to right │ │ │ │ │ approver │ │ │ NO └───────────┘ │ │ │ │ │ │ ▼ ▼ │ │ ┌──────────┐ ┌──────────┐ │ │ │ 11-20% │────────────────────────────►│ Manager │ │ │ └──────────┘ │ Review │ │ │ │ └──────────┘ │ │ NO │ │ │ │ ▼ │ │ ▼ ┌──────────┐ │ │ ┌──────────┐ │ Deal Desk│ │ │ │ 21-30% │────────────────────────────►│ Review │ │ │ └──────────┘ └──────────┘ │ │ │ │ │ │ NO ▼ │ │ │ ┌──────────┐ │ │ ▼ │ VP/CRO │ │ │ ┌──────────┐ │ Approval │ │ │ │ >30% │────────────────────────────►│ │ │ │ └──────────┘ └──────────┘ │ │ │ │ │ ┌─────┴─────┐ │ │ ▼ ▼ │ │ Approved Rejected │ │ │ └─────────────────────────────────────────────────────────────────┘Step 5.5: Monitor and Enforce
Discount Health Dashboard:
MONTHLY DISCOUNT METRICS Target Actual Status ────────────────────────────────────────────────────── % deals with any discount <40% 47% ⚠️ Average discount given <12% 14% ⚠️ Discount by rep (std dev) <5% 8% 🔴 Deals at max discount <5% 12% 🔴 Time to approval (days) <2 1.4 ✅ DISCOUNT BY SEGMENT ───────────────────────────── Enterprise (>$50K ACV) 18% Mid-Market ($15-50K) 12% SMB (<$15K) 6% DISCOUNT BY REP (Quartile Analysis) ─────────────────────────────────────────────────── Rep Avg Discount Win Rate Concern ─────────────────────────────────────────────────── Sarah K. 8% 34% — John M. 11% 31% — Pat L. 22% 28% 🔴 Investigate Amy R. 9% 36% —Discount Policy Guardrails
Trap Guardrail Discounts become expected Never discount same customer twice for same reason End-of-quarter "fire sales" Cap monthly discount deals at 25% of pipeline Reps racing to discount floor Track correlation between discount and win rate Discount creep over time Annual audit with baseline reset Strategic discount abuse Require executives to justify "strategic" quarterly
6. Pricing Governance
Step-by-Step Process
Step 6.1: Define Pricing Ownership (RACI)
PRICING RACI MATRIX Activity │ Product │ Finance │ Sales │ Marketing │ CEO ────────────────────────────┼─────────┼─────────┼───────┼───────────┼───── Set list prices │ A │ C │ C │ I │ R Define packaging/tiers │ R │ C │ C │ C │ A Approve new product pricing │ R │ C │ C │ I │ A Approve standard discounts │ I │ R │ A │ I │ C Approve exception discounts │ I │ C │ R │ I │ A Geographic pricing │ C │ R │ C │ I │ A Price change communication │ C │ I │ C │ R │ A Contract term approval │ I │ C │ R │ I │ A Annual pricing review │ R │ R │ C │ C │ A R = Responsible A = Accountable C = Consulted I = InformedStep 6.2: Establish Pricing Committee
┌─────────────────────────────────────────────────────────────────┐ │ PRICING COMMITTEE CHARTER │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ PURPOSE: │ │ Cross-functional body to make and review pricing decisions │ │ │ │ MEMBERS: │ │ • CPO or VP Product (Chair) │ │ • CFO or VP Finance │ │ • CRO or VP Sales │ │ • VP Marketing │ │ • Deal Desk Lead │ │ │ │ CADENCE: │ │ • Monthly: Review metrics, approve adjustments │ │ • Quarterly: Strategic review, competitive analysis │ │ • Annual: Full pricing architecture review │ │ │ │ AUTHORITY: │ │ • Approve pricing changes up to 25% impact on revenue │ │ • Recommend larger changes to executive team │ │ • Set and revise discount policy │ │ • Adjudicate exception requests │ │ │ │ DECISION PROCESS: │ │ • Quorum: 3 of 5 members │ │ • Decisions by consensus; if split, Chair decides │ │ • Reversible decisions: <24hr; irreversible: 1 week review │ │ │ └─────────────────────────────────────────────────────────────────┘Step 6.3: Create Pricing Change Process
PRICING CHANGE WORKFLOW ┌─────────────────────────────────────────────────────────────────┐ │ │ │ PRICING CHANGE REQUEST │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ 1. PROPOSAL (Requestor) │ │ │ │ • Business case (why change needed) │ │ │ │ • Financial model (revenue/margin impact) │ │ │ │ • Competitive context │ │ │ │ • Customer impact analysis │ │ │ │ • Implementation requirements │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ 2. ANALYSIS (Finance + Deal Desk) │ │ │ │ • Model scenarios (best/base/worst) │ │ │ │ • Elasticity assumptions │ │ │ │ • Cannibalization risk │ │ │ │ • Operational readiness │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ 3. REVIEW (Pricing Committee) │ │ │ │ • Approve / Reject / Modify │ │ │ │ • If approved, set launch date │ │ │ │ • Define success metrics │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ 4. COMMUNICATION PLAN (Marketing + Sales) │ │ │ │ • Internal enablement (2 weeks before) │ │ │ │ • Customer notification (if existing affected) │ │ │ │ • Public announcement │ │ │ │ • Sales tool updates │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ 5. IMPLEMENTATION (Product + Ops) │ │ │ │ • System updates (billing, CPQ) │ │ │ │ • Website/marketing updates │ │ │ │ • Grandfathering logic (if applicable) │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ 6. MONITOR (Finance + Product) │ │ │ │ • Weekly tracking for first month │ │ │ │ • 30/60/90 day reviews │ │ │ │ • Post-implementation review │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────┘Step 6.4: Build Pricing Documentation
Required Documentation:
PRICING DOCUMENTATION CHECKLIST □ MASTER PRICE LIST • All products, SKUs, and price points • Effective dates and version history • Currency/regional variations □ RATE CARD • Sales-facing price sheet • Volume tiers and discount structure • Terms and conditions summary □ DISCOUNT POLICY • Approved discount reasons • Approval thresholds and process • Give-get requirements □ COMPETITIVE PRICE SHEETS • Key competitor pricing • Feature comparison at price points • Win/loss pricing insights □ PRICING FAQ • Common customer questions • Objection handling scripts • Edge case guidance □ CHANGE LOG • Historical pricing changes • Rationale for each change • Impact analysisStep 6.5: Set Up Pricing Health Metrics
PRICING HEALTH SCORECARD ACQUISITION METRICS ─────────────────────────────────────────────────────────────── Metric Target Actual Trend Status ─────────────────────────────────────────────────────────────── ASP (Average Selling $45K $42K ↓ ⚠️ Price) Price realization >92% 88% ↓ 🔴 (actual/list) Conversion rate 5.5% 5.2% → ⚠️ Sales cycle (days) 45 52 ↑ ⚠️ RETENTION & EXPANSION METRICS ─────────────────────────────────────────────────────────────── Net Revenue Retention >110% 108% ↓ ⚠️ Gross Revenue Retention >90% 91% → ✅ Expansion Revenue % 25% 22% ↓ ⚠️ Price increase accept. >85% 79% ↓ 🔴 PROFITABILITY METRICS ─────────────────────────────────────────────────────────────── Gross Margin >75% 77% → ✅ CAC Payback (months) <18 16 ↓ ✅ LTV:CAC Ratio >3:1 3.2:1 → ✅ OPERATIONAL METRICS ─────────────────────────────────────────────────────────────── Pricing errors/month <5 3 ↓ ✅ Discount approval time <48hr 36hr ↓ ✅ Price-related churn <2% 1.8% → ✅Governance Guardrails
Trap Guardrail Pricing by committee (slow, conservative) Clear decision rights; Chair breaks ties Pricing changes without communication 2-week minimum internal enablement "Emergency" price changes bypassing process Define what qualifies as emergency (<1% of changes) Tribal knowledge only All pricing in documented, version-controlled system Set and forget Mandatory annual pricing architecture review
7. Common Traps & Guardrails
Comprehensive Trap Reference
┌─────────────────────────────────────────────────────────────────┐ │ PRICING TRAPS MATRIX │ ├───────────────────────────────────────────────────────────────── │ │ │ │ CATEGORY: PSYCHOLOGY TRAPS │ │ ───────────────────────────────────────────────────────────── │ │ TRAP: Anchoring on cost, not value │ │ SIGN: Pricing discussions start with "our costs are..." │ │ FIX: Always start with customer value; cost is floor only │ │ │ │ TRAP: Fear of losing deals │ │ SIGN: High discount rates, low price realization │ │ FIX: Track win rate vs. discount correlation; usually weak │ │ │ │ TRAP: Round number bias │ │ SIGN: All prices end in 00 or 99 │ │ FIX: Use charm pricing ($X97) or prestige ($X00) deliberately │ │ │ │ CATEGORY: STRATEGY TRAPS │ │ ───────────────────────────────────────────────────────────── │ │ TRAP: Race to the bottom │ │ SIGN: Matching every competitor price cut │ │ FIX: Compete on value, not price; differentiate │ │ │ │ TRAP: One-size-fits-all pricing │ │ SIGN: Same price/package for all segments │ │ FIX: Segment by WTP; create tiered packaging │ │ │ │ TRAP: Leaving money on the table │ │ SIGN: Very high win rates (>40%), no pushback on price │ │ FIX: Test higher prices; you're probably underpriced │ │ │ │ TRAP: Pricing too high for market entry │ │ SIGN: Extremely long sales cycles, low conversion │ │ FIX: Re-research WTP; consider freemium for adoption │ │ │ │ CATEGORY: OPERATIONAL TRAPS │ │ ───────────────────────────────────────────────────────────── │ │ TRAP: Unpredictable bills (usage pricing) │ │ SIGN: Customer complaints, high churn after first bill │ │ FIX: Add caps, alerts, forecasting tools │ │ │ │ TRAP: Complex pricing page │ │ SIGN: High drop-off on pricing page, "call us" requests │ │ FIX: Simplify to 3-4 tiers; max 10 feature rows │ │ │ │ TRAP: Stale pricing │ │ SIGN: No price changes in 2+ years; margins shrinking │ │ FIX: Annual pricing review; track cost/value changes │ │ │ │ CATEGORY: DISCOUNT TRAPS │ │ ───────────────────────────────────────────────────────────── │ │ TRAP: Discount addiction │ │ SIGN: >50% of deals have discounts; customers expect them │ │ FIX: Strict approval process; rep compensation adjustment │ │ │ │ TRAP: End-of-quarter desperation │ │ SIGN: Deep discounts spike in final week of quarter │ │ FIX: Cap discount deals; don't reward quarter-end heroics │ │ │ │ TRAP: Rogue discounting │ │ SIGN: Wide variance in discounts by rep; no documentation │ │ FIX: System-enforced approval workflow; regular audits │ │ │ └─────────────────────────────────────────────────────────────────┘Warning Signs Dashboard
Monthly Review Checklist:
PRICING HEALTH WARNING SIGNS Check each month—if 3+ are true, pricing review needed: □ Win rates increased >10% (likely underpriced) □ Win rates decreased >10% (likely overpriced or value issue) □ Average discount increased >2 percentage points □ Churn mentions "price" in top 3 reasons □ Expansion revenue declining as % of existing base □ Competitors significantly changed pricing □ >20% of deals require exception approval □ Sales cycle length increased >20% □ Customer complaints about pricing complexity increased □ Gross margin decreased >3 percentage points
8. Implementation Roadmap
12-Week Pricing Transformation
WEEK 1-2: FOUNDATION ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Workstream: Discovery & Data ┌────────────────────────────────────────────────────────────┐ │ □ Collect current pricing documentation │ │ □ Pull historical deal data (prices, discounts, outcomes) │ │ □ Interview 5 sales reps on pricing challenges │ │ □ Interview 5 recent customers on pricing experience │ │ □ Analyze competitor pricing (public + intel) │ │ □ Review win/loss data for pricing mentions │ └────────────────────────────────────────────────────────────┘ Deliverable: Pricing Diagnostic Report WEEK 3-4: VALUE & WILLINGNESS TO PAY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Workstream: Research ┌────────────────────────────────────────────────────────────┐ │ □ Map value drivers by segment │ │ □ Conduct Van Westendorp survey (n=100+) │ │ □ Complete 10 customer depth interviews │ │ □ Calculate economic value for key use cases │ │ □ Segment analysis (who values what?) │ └────────────────────────────────────────────────────────────┘ Deliverable: WTP Research Report & Segmentation WEEK 5-6: STRATEGY DESIGN ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Workstream: Pricing Architecture ┌────────────────────────────────────────────────────────────┐ │ □ Select value metric(s) │ │ □ Design package tiers (3-4) │ │ □ Define feature fences │ │ □ Set price points for each tier │ │ □ Create add-on strategy │ │ □ Model revenue scenarios (3 scenarios) │ └────────────────────────────────────────────────────────────┘ Deliverable: Draft Pricing Architecture WEEK 7-8: TESTING & VALIDATION ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Workstream: Experiments ┌────────────────────────────────────────────────────────────┐ │ □ Design pricing experiment(s) │ │ □ Build landing page variants │ │ □ Launch limited test (geography or cohort) │ │ □ Collect qualitative feedback │ │ □ Present draft to sales team for input │ │ □ Iterate based on findings │ └────────────────────────────────────────────────────────────┘ Deliverable: Validated Pricing Recommendation WEEK 9-10: GOVERNANCE & POLICY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Workstream: Operations ┌────────────────────────────────────────────────────────────┐ │ □ Write discount policy document │ │ □ Design approval workflows │ │ □ Configure CPQ/billing systems │ │ □ Establish Pricing Committee charter │ │ □ Create pricing documentation │ │ □ Build health metrics dashboard │ └────────────────────────────────────────────────────────────┘ Deliverable: Governance Framework & Systems WEEK 11-12: LAUNCH PREPARATION ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Workstream: Enablement & Communication ┌────────────────────────────────────────────────────────────┐ │ □ Create sales enablement materials │ │ □ Train sales team (2 sessions) │ │ □ Update website and marketing materials │ │ □ Prepare customer communication (if needed) │ │ □ Set grandfathering rules (existing customers) │ │ □ Define 30/60/90 day review checkpoints │ │ □ Go-live! │ └────────────────────────────────────────────────────────────┘ Deliverables: Enablement Complete, Launch POST-LAUNCH: MONITORING ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Week 13-16: Daily/weekly tracking Week 17-20: Adjustments based on data Week 24: Full post-launch reviewOngoing Rhythm
PRICING GOVERNANCE CALENDAR WEEKLY (Deal Desk) • Exception discount review • Pipeline pricing analysis • Competitive pricing intel MONTHLY (Pricing Committee) • Metrics review • Discount health check • Experiment readouts • Policy adjustment votes QUARTERLY (Leadership) • Strategic pricing review • Competitive positioning • Segment performance • Roadmap alignment ANNUALLY (Full Team) • Complete pricing architecture review • Customer WTP refresh research • Multi-year pricing strategy • Policy and documentation audit
Quick Reference Card
┌─────────────────────────────────────────────────────────────────┐ │ B2B PRICING CHEAT SHEET │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ VALUE METRIC: Choose based on value alignment, predictability, │ │ scalability. Test with real customer conversations. │ │ │ │ PACKAGING: 3-4 tiers max. Good-Better-Best. Clear upgrade │ │ triggers. Hollow tiers kill conversion. │ │ │ │ WTP RESEARCH: Van Westendorp for ranges, Gabor-Granger for │ │ points, Conjoint for trade-offs. Discount stated WTP 20-30%. │ │ │ │ EXPERIMENTS: Test safely (new customers, geographic). Honor │ │ any price shown. Pre-calculate sample sizes. │ │ │ │ DISCOUNTS: Every discount = give-get. Clear approval tiers. │ │ Track by rep. Never discount same customer twice same reason. │ │ │ │ GOVERNANCE: Clear RACI. Monthly committee. Document │ │ everything. Annual full review. │ │ │ │ RED FLAGS: Win rate >40%, discount >20% avg, no price │ │ changes in 2 years, wide rep variance. │ │ │ └─────────────────────────────────────────────────────────────────┘
This playbook should give you a complete framework for building and managing B2B pricing. Start with the diagnostic (Week 1-2), then work through systematically. Pricing is never "done"—build the governance muscle to iterate continuously.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.