How We Get Our Data
DataStackGuide analyzes historical job postings to measure hiring demand for GTM and data tools. A mention is a market signal, not proof of an active license or current open role.
The Data Pipeline
The upstream system collects job postings and exports a dated analytical snapshot for this static site. The public pipeline has four stages:
Collection
The upstream collector aggregates job postings from multiple sources. The public repository does not expose a complete source-by-source coverage audit, so source coverage remains a separate pipeline check.
Tool Detection
The exporter joins detected tool mentions to job records and maps covered tools into site categories. Ambiguous raw terms such as Warmly, Tray, and DemandTools require snippet-level verification before they belong in a clean leaderboard.
Enrichment
We normalize company names, classify roles by function and seniority, categorize company stages, extract salary data, and identify remote vs. onsite roles.
Analysis
We aggregate historical mention counts, co-occurrence patterns, dated monthly trends, salary fields, and company breakdowns. Each metric needs its own denominator.
Latest Committed Historical Export
The site build currently uses data generated on September 15, 2026. These are historical database totals. They are not a count of active listings on the day you read this page.
Four Different Denominators
What This Data Tells You
Hiring footprint. A tool mention shows that the skill or product appeared in a collected job description. It can suggest market familiarity or organizational use. It does not prove a current contract.
Relative comparisons. Counts and normalized mention share can compare covered tools within the same defined universe. Ambiguous tool names and category coverage can distort raw rankings.
Compensation context. Salary fields can describe postings with usable compensation. The figure is incomplete until the page discloses the qualifying record count, unit, geography, and date range.
Co-mentions. Co-occurrence shows that two tool names appeared in the same posting. It suggests stack adjacency but does not prove a production integration.
Company examples. Normalized company names show where a tool was mentioned in the historical data. Logos and names identify records, not endorsements.
Limitations & Caveats
We're transparent about what this data doesn't capture:
Large company bias
Bigger companies post more jobs. A 10,000-person company will generate more postings mentioning Salesforce than a 20-person startup, even though both use the tool. Our data skews toward mid-market and enterprise.
Not all tools appear in postings
Some tools (especially lightweight SaaS products) rarely show up in job descriptions. A company might use Clay or Warmly without ever mentioning it in a job posting. Our data underrepresents tools that aren't considered "skills."
Job postings lag adoption
There's a delay between a company adopting a tool and hiring for it. Fast-growing tools may be underrepresented in our current data but growing in the trend line.
Salary data is incomplete
Not all postings include salary ranges. In states without pay transparency laws, salary data is thinner. We only report salary figures when we have a meaningful sample size.
Category overlap
Many tools span multiple categories. ZoomInfo is enrichment, validation, intent data, and prospecting all at once. We handle this with multi-category tagging, but some categorization is inherently subjective.
Editorial Standards
Every tool page on DataStackGuide includes a disclosure footer noting our relationship with Verum and Provyx. Here's what guides our content:
- We don't accept payment for reviews, rankings, or placements
- Affiliate links don't influence our recommendations
- We apply the same editorial standards to our own products (Verum, Provyx) as to competitors
- Pricing information is verified directly from vendor websites and updated regularly
- We show our data sample sizes so you can judge the statistical significance
Data Updates
The latest committed export was generated on September 15, 2026. The static site can only be as fresh as its most recent successful extraction, commit, build, and deployment.
Trend comparisons use dated monthly snapshots. A page should show the relevant data date and should not label a historical cumulative count as current or active.
Questions?
If you have questions about our methodology, want to report a data error, or think we're missing a tool, email hello@datastackguide.com.