What they run
Technographic signals on the stack a company runs
Detect the tech stack a company runs, with the dates each tool was first and last seen. Seeing a tool you integrate with, or a competitor you displace, changes the first line of the email.
Technographics get sold as a filter and then used as a snapshot. A vendor says a company runs a tool, and you build a list around it. Tools get swapped, so that list goes out of date while it sits.
Two things live here, and only one is finished. Detection answers what a company runs today, from its public footprint and the tools its job posts name. The change is what you want, and today it comes from comparing runs: a detection column keeps its recent history. No technology event type exists yet, so nothing fires on its own.
Example searches
Ask for it the way you'd say it
Each example is a request in plain words, with what it returns underneath.
Companies running your integration
which accounts in this table already use a warehouse we can plug straight into
Detection lands per row, so the integration story gets written only where it happens to be true.
Displacement candidates
find companies showing a competitor's script on their public website
A competitor's presence is evidence you can name in a first line, not a guess dressed up as research.
Stack changes worth an email
tell me when an account in this table adds or drops a tool in our category
Two runs of the same column show a change: the cell holds the new value, and its recent history keeps the one before. Nothing alerts you yet.
Plays
Three motions you can run this week
Each one is a chain of OXYGEN primitives: the same hosted objects your workspace already has, composed.
Accounts already running your integration
Accounts where the integration story is true get a different opening line from everyone else.
- 1Search the market for companies running the tool you integrate with. Without --last-days, it finds only companies first seen using it in the last 30 days, so pass --last-days 3650 to include long-time users.
- 2Find the decision makers at each matching company, add their work emails, then enroll that people table with the detected tool in the first line.
oxygen signals search runA displacement list from one competitor
Companies running the product you replace become a working segment instead of an anecdote.
- 1Filter the detections down to the competitor you win against most reliably, then read the count.
- 2Promote the qualified accounts and record the competitor on the company record.
oxygen tables queryAct on the change, not the state
A tool appearing or disappearing gives you a reason to write within weeks rather than quarters.
- 1Add a PredictLeads detection column and schedule it with --force, which reruns filled rows, under a credit ceiling. A repeat lookup within 30 days can return the stored result, so space runs over 30 days apart.
- 2Within a week of each run, compare each new value with the previous one in the cell's history. Then email that account's contact from Messages and approve the preview before it sends.
oxygen tables schedule set
Capabilities
What you get
Detection and change kept apart
What a company runs today and the week that changed are different facts. Keeping both gives you a list and a reason to write.
Evidence you can quote
A detection carries the dates the source first and last saw the tool. Naming that evidence in an email is the difference between research and a lucky guess.
Detection where the work is
The result is a column on the account row, so scoring, filtering, and enrollment read it directly. Crossing it with hiring or funding means joining columns in a table you own.
Filters before the spend
The default lane, the first source a search tries, narrows on one technology and a first-seen window; TheirStack also filters on company country. Planning, which is free, quotes the credits and names any filter a lane drops.
Boundaries
What Signals does not own
A detection is Tables work: a column on the account row with its own run history. Signals owns the search that produced it. Branching on a change belongs to Workflows, and a reply in the thread it starts is Messages.
Data sources
Data sources and CRM connections
PredictLeadsThe default lane for technology search. Each detection carries the dates the tool was first and last seen on the company.
TheirStackThe named alternative, filtering on technology and company country. Its free catalog lookup turns your wording into the exact label first.
CrustdataOutside the default technology chain. Name it on your own Crustdata key when a detection needs the company's size and stage beside it.
Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.
Limits
Where this stops
- Detection reads the public footprint and job posts. An internal tool nobody hires for, anything behind a login, and a purchase not yet live stay invisible, so an empty result proves nothing.
- One run already shows when each tool was first and last seen. A script that vanishes afterwards shows only on a later run, so schedule the column with --force to catch removals.
FAQ
Questions people ask first
How accurate is technology detection?
How do I act on a tech stack change signal?
Can I combine this with hiring evidence?
Does a detection reach my CRM?
How far back does the history go?
What if the company is not a fit yet?
Try Signals in your own workspace
Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.