Home/Methodology
DATA METHODOLOGY

Where Our Pricing Data Comes From — and Why You Can Trust It

Every benchmark report we deliver is built on verified, anonymized transaction data from real enterprise procurement teams. Here is exactly how we collect it, clean it, and make it usable.

10,000+ Transactions 30-Deal Minimum Cohort Quarterly Updates Analyst-Verified
Data analyst reviewing large-scale enterprise contract pricing data on multiple screens
THE PROBLEM WE SOLVE

Pricing Data That Doesn't Exist Anywhere Else

Enterprise software pricing is deliberately opaque. Vendors publish list prices, but actual transaction prices — the numbers that reflect real negotiating leverage — are almost never disclosed.

Analyst firms publish "price ranges" based on interviews and surveys. Consultants share anecdotes from their prior engagements. Neither provides the statistical rigor needed to anchor a serious negotiation.

VendorBenchmark aggregates actual executed transactions. Not surveys. Not interviews. Not estimates. Real enterprise deals, submitted by the procurement teams who signed them, normalized across a methodology that makes them comparable to your situation.

The result: when you benchmark an Oracle Database renewal, you're seeing discount percentile data derived from dozens of comparable Oracle transactions closed in the past 18 months — not an analyst's best guess.

DATA SOURCES

Three Channels. One Verified Database.

Our transaction data comes from procurement teams, not vendors. That distinction matters for everything that follows.

SOURCE 01
Direct Procurement Submissions
Enterprise procurement teams submit their executed or in-negotiation contract data directly through the platform, typically in exchange for benchmark credits. All submissions are anonymized before analysis.
47%
of total data points
SOURCE 02
PE Portfolio Company Network
Private equity operating partners who use the platform for portfolio-wide software cost optimization contribute anonymized transaction data across multiple portfolio companies and procurement cycles.
31%
of total data points
SOURCE 03
Research Partner Contributions
Enterprise procurement associations, CFO networks, and technology industry research groups who partner with VendorBenchmark contribute aggregated, pre-anonymized transaction data to expand coverage.
22%
of total data points
NORMALIZATION METHODOLOGY

How Raw Transactions Become Comparable Benchmarks

A $3M Oracle deal closed by a Fortune 100 bank is not directly comparable to a $500K Oracle deal at a mid-market manufacturer. Our normalization pipeline makes them comparable — or excludes them from the same cohort.

Core principle: A benchmark is only useful if it reflects transactions that are genuinely comparable to yours. We would rather exclude data than include transactions that distort your percentile position. This is why we maintain minimum cohort sizes and why some niche products have limited benchmark availability.

01
Transaction Intake & Anonymization
Raw transaction data enters the pipeline stripped of all identifying information. What remains: vendor name, product/SKU, volume tier, deal type (renewal/new/expansion), effective date, term length, list price, and negotiated price. No company name. No account IDs. No contact information.
02
Volume-Tier Normalization
We normalize price-per-unit figures to account for volume discount curves. An enterprise purchasing 5,000 Oracle licenses will structurally receive better pricing than one purchasing 200 licenses — so these are never compared directly. Transactions are bucketed into volume tiers before any discount percentile calculation.
03
Industry & Use-Case Segmentation
Financial services firms, healthcare organizations, and manufacturing companies often receive different vendor pricing due to regulatory requirements, competitive landscape, and procurement sophistication. We segment cohorts by industry vertical and use-case type to ensure comparisons reflect relevant market context.
04
Deal-Type Classification
Renewal pricing, new purchase pricing, and expansion pricing carry structurally different discount profiles. A vendor will offer 35% off list on a competitive new logo deal and 8% off on a renewal where there's no credible alternative. We never mix renewal and competitive new purchase data in the same percentile range.
05
Recency Weighting
Pricing market conditions change — sometimes rapidly. An Oracle Java licensing deal from 2022 is less representative than one from Q4 2025. We apply recency weighting that reduces the influence of transactions older than 18 months and excludes transactions older than 36 months entirely from live benchmarks.
06
Minimum Cohort Enforcement
We require a minimum of 30 comparable, normalized transactions before publishing any benchmark percentile. Below this threshold, statistical confidence is insufficient to anchor a negotiation. Vendors or products that don't meet this minimum show "Limited Data" status rather than unreliable percentiles.
07
Analyst Review & Outlier Removal
Every benchmark cohort is reviewed quarterly by a senior analyst. Statistical outliers (transactions more than 2.5 standard deviations from the cohort mean) are flagged for investigation before inclusion. Anomalous data points — often the result of one-time strategic deals or data entry errors — are excluded.
BENCHMARK OUTPUT

What a Benchmark Report Actually Shows

A simplified illustration of the percentile data format. Real reports include additional filters, cohort details, and negotiation guidance.

EXAMPLE BENCHMARK — ORACLE DATABASE ENTERPRISE EDITION Renewal · 1,000–5,000 Named User Plus Licenses · Financial Services · 2024–2025 Transactions
DISCOUNT RANGE (OFF LIST) COHORT: 84 TRANSACTIONS
P10: 14% discount · P25: 28% · P50: 41% · P75: 56% · P90: 67%
SUPPORT & MAINTENANCE DISCOUNT COHORT: 84 TRANSACTIONS
P10: 0% · P25: 8% · P50: 18% · P75: 29% · P90: 37%
TOTAL CONTRACT VALUE REDUCTION FROM LIST VS. YOUR PROPOSAL POSITION
YOUR POSITION: 62nd percentile — you are paying more than 62% of comparable deals

Illustrative example only. Real benchmark outputs contain additional product-line breakdowns, deal structure analysis, multi-year term comparisons, and negotiation recommendations. Percentile data is updated quarterly.

QUALITY CONTROLS

What Keeps the Data Accurate Over Time

Quarterly Cohort Refresh
All benchmark cohorts are refreshed quarterly. New transactions are added, outdated transactions are aged out or removed, and recency weights are recalculated. This keeps benchmark data relevant to current market conditions rather than historical averages.
Analyst Validation Layer
No benchmark data goes live without review by a senior analyst with direct procurement experience in that vendor category. Automated statistical flags are reviewed by humans before any cohort update is published to the platform.
Feedback Loop from Active Negotiations
When customers use our benchmark data in live negotiations and share the outcome, we feed that result back into the cohort. This creates a closed loop that validates our percentile accuracy in real-world conditions — and flags any drift between our benchmarks and current vendor behavior.
No Vendor Input in Methodology
We have never accepted input from any software vendor into our normalization methodology. No vendor has reviewed, approved, or influenced how we calculate their benchmark data. Our methodology is designed by procurement professionals for procurement professionals.
SEE IT IN ACTION

Run a Live Benchmark on Your Vendor Proposal

Start with 3 free benchmark reports. No credit card. Submit your Oracle, Microsoft, AWS, or any other vendor proposal and see exactly where your pricing stands against the market.

Start Free Trial Submit a Proposal