TheirStack tells you which companies use a technology by reading their job postings. This guide is for the sales operations lead or engineer who relies on it and is weighing other sources. It explains the two ways technographic data is produced, from postings and from websites, shows what each reveals, and gives a query that tests one against the other.
TheirStack is built for prospecting from postings. Its catalogue, which its website puts at more than 30,000 technologies, includes programming languages, databases and ERP systems. It gathers postings from job boards as well as company sites, with history that its documentation dates to 2021, and its job records include the description. It has a web app that its pricing page says you can start for free, webhooks and datasets in Parquet. Fokals delivers both kinds of evidence on one company index: the technologies detected on each company's website, with a dated event for every adoption and removal, and the tools named in the roles each company publishes.
What TheirStack offers, as documented
TheirStack's documentation describes a database of job postings and technographics for sales and marketing teams, with three kinds of signal: hiring, technology use and pain points. Its site also offers buying intents, topics it identifies in what companies are hiring for. Postings come from what the job data page calls job boards, company websites and applicant tracking systems. A company enters the database when one of its postings is collected, and the company data page says the record is then enriched with firmographic, financial and technographic data, among them industry, employee count, estimated revenue and funding.
Its documentation lists four ways to use the data: a web app, an API, webhooks that depend on a saved search, and datasets in CSV or Parquet, delivered as a link to an S3 bucket. The pricing page sells the app by packs of company credits and the API by credits, in packs or on a monthly subscription, and directs dataset buyers to its sales team.
Two ways to know what a company runs
From job postings. TheirStack's page on how it sources technology data says it reads the title, the description and the URL of each posting, and takes a mention of a technology as a hint that the company uses it. A confidence score of low, medium or high weighs the number of mentions, their frequency against similar technologies, where the mention sits and how recent it is. The same page states the limit of the method: a company that uses a technology without naming it in a posting, or that is not hiring, does not appear under it.
From the website. Fokals detects technologies from page content, scripts, network requests, response headers and DNS records, as the article on how we detect technologies explains. Each technology carries its first-seen and last-seen dates, and every adoption and removal is a dated event. A detection is evidence of presence on the company's website, and it holds whether or not the company is hiring.
| From job postings | From the website | |
|---|---|---|
| Evidence | A posting names the technology | The technology is detected in page content, scripts, network requests, response headers or DNS records |
| Shows | Tools staff are asked to know, including databases, languages and internal systems | The customer-facing stack: advertising, analytics, commerce, CRM and marketing tools, and the services a domain's records reveal |
| Reaches | Companies that are hiring and name the tool | Every company website in the index, whether or not the company is hiring |
| What a date means | When a posting named it | When the technology was first seen on the site, and when it was last seen |
| When a tool is dropped | Postings stop naming it | The removal is recorded as a dated event |
In Fokals data the two kinds of evidence sit side by side on one company ID. Technology Stack, in the marketing stack dataset, holds the technologies detected on each company's website, in a curated catalogue across 68 categories from advertising and analytics to commerce, CRM and infrastructure. Job Postings, in the hiring dataset, carries the tools named in each role, with labels for tool families that include Salesforce, SAP, Snowflake and AWS.
TheirStack and Fokals side by side
The TheirStack column repeats what the pages linked above state.
| TheirStack | Fokals | |
|---|---|---|
| Scope | Job postings, technographics inferred from them, buying intents and company records | Technographic, hiring, intent and announcement data on one company index, with weekly Market Series |
| Sources | Job boards, company websites and applicant tracking systems | First-party company sources and public records, processed in-house |
| Technology catalogue | More than 30,000 technologies, as its site states | A curated catalogue for website detection, from advertising and analytics to commerce, CRM and infrastructure, and the tools named in each job posting |
| Job data | Postings with their descriptions, from 195 countries as its documentation states | Every role a company publishes, labelled by job function, seniority and ten role flags, with location, work mode, advertised pay and the tools named |
| Delivery | Web app, API, webhooks, and datasets in CSV or Parquet by S3 link | REST API and bulk exports in JSON, JSON Lines or CSV, with a signed-in dashboard for browsing |
| Licensing | Credit packs for the app, credit packs or a monthly subscription for the API, datasets through sales | Written agreement for internal use, embedding in a product or redistribution |
A worked check: do postings and the website agree?
You can test the two kinds of evidence against each other on Fokals data alone, which shows what each method tells you about the same companies. Take a tool that both datasets carry. Salesforce is one: it is detected on websites in Technology Stack and named in roles in Job Postings.
-- Postgres syntax. labels is the JSON object delivered with each posting.
with named as (
select distinct company_id
from job_postings
where closed_at is null
and labels ->> 'tool_salesforce' = 'true'
),
seen as (
select distinct company_id
from company_technologies
where technology = 'salesforce' -- confirm the id against technology_name
and missing_since is null
)
select
coalesce(n.company_id, s.company_id) as company_id,
n.company_id is not null as named_in_postings,
s.company_id is not null as seen_on_website
from named n
full join seen s on s.company_id = n.company_id;Read the result as three groups.
- Named and seen. Two separate public facts agree. This is the group to trust for a list of companies that use the tool.
- Named only. The tool is in use inside the company, or the role is being hired to introduce it. The posting is the evidence, and it sits on the same company ID as the website record.
- Seen only. The tool is on the site and no open posting asks for it. This group includes every company that is not hiring, and website detection is what finds it.
Count the three groups for the technologies you sell around before you choose a method. Databases and programming languages are named in postings, the evidence on which TheirStack's catalogue is built. Customer-facing tools sit in the first and third groups, where website detection adds the date a tool arrived and the date it left, as events in Technology Changes.
An illustrative case: Acme Robotics, an invented company, has two open postings that name Salesforce and no Salesforce detection in Technology Stack. That is the second group. The reading is that Acme Robotics asks its staff to know the tool, and a later detection or posting will date the next step. The guides to finding accounts by the technology they run and timing outreach with hiring signals build lists on each kind of evidence.
Hiring signals: the text or the labels
The same difference shapes hiring signals. TheirStack's datasets carry the description, and its Job Postings API page describes filters on job, company and technology fields, so a signal can start from the words of the posting. In Fokals data a signal starts from structure. Every posting is labelled by job function, seniority and ten role flags under a named, frozen version, and the flags mark the roles a seller looks for: a role that selects tools, starts a new initiative, builds a team or replaces a vendor.
-- open roles in performance marketing that choose tools, seen opening
select company_id, title, url, first_seen_at
from job_postings
where closed_at is null
and labels ->> 'job_function' = 'marketing_performance'
and labels ->> 'selects_tools' = 'true'
and not found_on_first_read;A label groups roles that employers word differently, so one filter finds the role whatever its title says, and the frozen version keeps that filter stable from week to week. The last line of the query keeps roles that were observed to open, so the first-seen date is the date of the signal. A signal that depends on one specific phrase, such as a regulation or a piece of equipment, starts from the description text, which TheirStack's datasets carry.
Other alternatives to TheirStack
- PredictLeads collects technologies from both kinds of evidence: script tags, DNS records, IP ranges and cookies as well as job descriptions.
- BuiltWith reports the technologies websites are built with, and its API page offers current and historical technology data for a domain. The guide to BuiltWith alternatives covers website detection in more depth.
- Coresignal sells jobs data merged from job boards, company websites and applicant tracking systems, beside company and employee data.
- LinkUp sources job openings directly from employer websites every day and sells them as job market data.
Frequently asked questions
How does TheirStack detect the technologies a company uses?
From job postings. Its documentation says it reads the title, description and URL of each posting and treats a mention of a technology as a sign that the company uses it, with a confidence score of low, medium or high. It also states that a company that does not name a technology in its postings, or is not hiring, will not appear under it.
What is the difference between technographic data from job postings and from websites?
Postings reveal the tools a company asks its staff to know, including databases, programming languages and internal systems, for companies that are hiring and name them. Website detection reveals the customer-facing stack, such as advertising, analytics and commerce tools, for every company with a website, with the date each tool arrived and the date it left. Fokals delivers both on one company ID. Test both on your own target technologies before you choose.
What does Fokals deliver for each job posting?
Every role a company publishes, with its title, location and work mode, labelled by job function, seniority and ten role flags, with advertised pay on one annual US-dollar scale and the tools the role names. Labels are produced under a named, frozen version, so a filter built on them stays stable. Hiring Activity adds daily open, new and closed postings for each company. TheirStack's datasets carry the description text of each posting.
Can I find companies by technology with Fokals?
Yes. Technology Stack lists each company and the technologies detected on its website, with first-seen and last-seen dates, and Technology Changes records every adoption and removal as a dated event. Job Postings adds the tools named in each role, so a tool a company asks its staff to know appears on the same company ID. Listed companies carry their ticker, ISIN, LEI and FIGI, and a brand carries the identifiers of its listed parent.
How is Fokals licensed, and how do I try it on my accounts?
By written agreement for internal use, embedding in a product or redistribution. Sample data for the companies you track is sent on request with the data dictionary and methodology. Data reaches you by REST API or bulk file, and a signed-in dashboard lets you browse it. TheirStack's pricing page invites you to sign up and start for free.
The queries and code on this page are examples to adapt. Test them in your own environment before you rely on them.
What this page says about the products it names was checked against their public documentation on 4 October 2026. Product and company names are trademarks of their owners. Fokals is not affiliated with them or endorsed by them.