OXYGENOXYGEN

What they run

Technographic signals on the stack a company runs

Knowing a company runs the tool you integrate with, or the competitor you displace, changes the first sentence of the email. Detection is the cheap part. Noticing the change is the valuable part.

try
Start freeRead the docs

Technographics get sold as a filter and then used as a snapshot. A vendor says a company runs a tool, you build a list around it, and six months later a good part of that list is wrong because tools get swapped and no database was told.

Two different things live here, and only one of them is finished. Detection answers what a company runs today, read from its public footprint and from the tools its job posts name. The change is what you actually want, and today it comes from comparison: the detection column keeps its run history, so this week's value sitting beside last week's is how an addition or a disappearance surfaces. No technology event type is registered yet, so nothing fires on its own.

Example searches

Ask for it the way you'd say it

Every search below runs on the same hosted Tables, with the cost previewed before anything is spent.

  • 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 a call

    tell me when a company in our market adds or drops a tool in our category

    Two runs of the same column is how a change shows up, with the earlier value still on the cell.

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.

  • Every account running your integration

    Accounts where the integration story is true get a different opening line from everyone else.

    1. Signals
    2. Tables
    3. Sequences
    1. 1Run detection across the account table and keep the technologies that matter to your pitch.
    2. 2Enroll only the matching rows, with the detected tool named in the first line.
    oxygen signals search run

  • A displacement list from one competitor

    Companies running the product you replace become a working segment instead of an anecdote.

    1. Signals
    2. Tables
    3. Records
    1. 1Filter the detections down to the competitor you win against most reliably, then read the count.
    2. 2Promote the qualified accounts and record the competitor on the company record.
    oxygen tables query

  • Act on the change, not the state

    A tool appearing or disappearing produces a note worth reading within days rather than quarters.

    1. Tables
    2. Workflows
    3. Messages
    1. 1Schedule the detection column so it reruns on a cadence, each delivery under a ceiling you approved.
    2. 2Compare the new value against the one already on the cell, then queue a draft for a person to read.
    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. Storing both means one feed yields a list and a trigger instead of only a list.

  • Evidence you can quote

    A detection carries where it was seen. Being able to name the source 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

    Category, technology, and company filters narrow the feed before it costs anything, which keeps a broad detection pass from becoming a broad bill.

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 and the registry it is not yet part of, branching on a change belongs to Workflows, and a reply in the thread it starts is Messages.

Data sources

What the data actually comes from

Every value lands with its provider and cost recorded on the cell.

  • PredictLeads

    The default technology lane: dated detections per company, and the source of the appeared-or-disappeared question.

  • TheirStack

    The named alternative, and the only lane crossing technology adoption with hiring for that technology in one request.

  • BuiltWith

    A free preflight rather than a detection lane. It resolves a technology label to its canonical form, because a wrong slug returns quietly empty.

  • Crustdata

    Also outside the default technology chain. Name it deliberately when a detection needs the company's size and stage beside it.

Run these on Oxygen's managed credits, or connect your own provider keys and pay the vendor directly — the same columns, the same runs, the same provenance either way. See every integration.

Limits

Where this stops

  • Detection sees the public surface only. Internal tools, anything behind a login, and a decision that has not shipped stay invisible, so an absence of evidence is not evidence of absence.
  • A change needs two runs to exist. The first detection is only a state, so schedule the column before you promise anybody an alert when a competitor's script disappears.

FAQ

Questions people ask first

How accurate is technology detection?
Good on what a website exposes, weaker on anything internal. Treat a detection as strong evidence for the opening line of an email, not as a fact you would assert back to the customer.
What exactly counts as a stack signal?
The change, mostly. A tool appearing or disappearing between two runs is a reason to write this month, where a static attribute is not. Today that comparison is yours to make on the row, since the registry holds no technology type for anything to fire on.
Can I combine this with hiring evidence?
Yes, and the pair is usually stronger. A team posting for an engineer who knows a tool, at a company where that tool is already detected, beats either fact standing on its own.
Does a detection reach my CRM?
Only if you promote it. The detection sits on the working row until you write it onto the company record, which is an explicit step with the run that produced it recorded beside it.
How far back does the history go?
As far back as your own runs, plus whatever history the source reports on a detection. The value a run wrote stays on the cell with that run, so a correction reads as a change rather than as a silent overwrite of what you believed last month.
What if the company is not a fit yet?
The detection is still worth keeping. Accounts drift into an ICP over time, and having the stack history already attached is what makes that shift easy to notice later on.

Run technographic signals on the stack a company runs on 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.

Start freeSee pricing