Pricing Splunk's New B2B Service
You are a Product Manager evaluating how to price a new observability or security analytics service for a mid-size technology customer. Outline a rigorous enterprise pricing approach.
Constraints & Assumptions
-
Assume a B2B enterprise or mid-market sales motion with procurement, discounting, pilots, and renewals.
-
The service has meaningful infrastructure and support costs, so gross margin matters.
-
Pricing should align with customer value, not only internal cost.
-
Avoid unfair or opaque experiments that would damage trust with customers.
Clarifying Questions to Ask
-
What is the primary use case: observability, security analytics, compliance, data platform, or incident response?
-
What usage dimension best reflects customer value, such as data volume, hosts, events, users, retention, or alerts?
-
Is the product sold standalone, bundled with existing Splunk products, or attached as an add-on?
-
Are we optimizing for adoption, revenue, margin, expansion, or strategic account penetration?
Part 1 - Customer Segmentation
Explain how you would segment customers and identify willingness to pay.
What This Part Should Cover
-
Segments by company size, data volume, use case, maturity, risk, compliance, buying center, and urgency.
-
Personas such as SRE, SecOps, platform engineering, admins, finance, and procurement.
-
Price fences that separate segments without creating bespoke complexity.
Part 2 - Value-Based Versus Cost-Plus Pricing
Compare value-based and cost-plus pricing and explain how you would use both.
What This Part Should Cover
-
Value-based anchor from ROI, willingness to pay, and customer outcomes.
-
Cost-plus floor from COGS, support load, and target gross margin.
-
A pricing corridor that includes competitive benchmarks and discount policy.
Part 3 - Competitive Landscape
Describe how you would benchmark competitors and differentiate the offering.
What This Part Should Cover
-
Competitor value metrics, list prices, packaging, retention, SLAs, support, and overage policies.
-
Differentiation through lower total cost of ownership, faster MTTR, better detections, compliance, or simpler operations.
-
How to avoid apples-to-oranges confusion in sales conversations.
Part 4 - Packaging Tiers
Design good, better, and best packaging tiers with value metrics and add-ons.
What This Part Should Cover
-
A fair value metric and clear tier step-ups.
-
Included usage, retention, advanced features, support levels, security features, and add-ons.
-
Overage policy, usage alerts, annual commitments, volume discounts, and expansion paths.
Part 5 - Research and Experiments
Explain which research and experiments you would run to validate and iterate on pricing.
What This Part Should Cover
-
Customer interviews, ROI modeling, Van Westendorp, Gabor-Granger, conjoint, pilot bundles, quote analytics, and win-loss analysis.
-
Guardrails around fairness, contract stability, sales enablement, and legal review.
-
Post-launch monitoring of win rate, discounting, price realization, NRR, churn, COGS, and support burden.
What a Strong Answer Covers
-
Pricing that balances customer value, margin, market reality, and simplicity.
-
A clear value metric and packaging strategy.
-
Ethical validation methods and a plan to iterate after launch.
Follow-up Questions
-
What value metric would you choose first and why?
-
How would you prevent bill shock?
-
What would you do if competitors price by host while you price by data volume?
-
How would you set discount guardrails for sales?
-
Which pricing metric would you monitor weekly after launch?