OXYGENOXYGEN

For HR tech

GTM infrastructure for HR tech startups

Hiring volume is the buying signal for nearly everything you sell. The job is watching it continuously instead of buying a list once a quarter.

try
Start freeRead the docs

Almost everything in HR tech gets bought when something breaks under growth. Twenty hires with no onboarding process. A first recruiter. Payroll in a second country. The account was not a prospect last quarter and may not be one next quarter.

Freshness is therefore the whole game. Postings land as dated rows, a scheduled run rebuilds this week's working set, and the sequence enrolls from that view. When a trigger expires the account leaves the view instead of sitting in a spring export.

Who this is for
Seed to Series A HR software companies: applicant tracking, onboarding, payroll, performance, or benefits. Four to fifty people, revenue owned by a founder or first sales hire.
What it looks like today
Headcount data goes stale in weeks. A list bought in January describes a company that finished hiring in February, and the sequencer keeps writing because nothing told it the trigger expired.
What changes
Postings and headcount movement arrive as dated events on the account. The list becomes a view over that stream, so the companies you contact this week are the ones under pressure this week.

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.

  • Hiring faster than they can cope

    which companies under 200 people opened more than fifteen roles in the last thirty days

    Posting counts come back with dates, so a steady hirer and a company that opened a floodgate are separable.

  • The first people hire

    tell me when a company on my list posts their first hr or people operations role

    The posting attaches to the account as an event, so the trigger is still there when you follow up in six weeks.

  • Who owns this budget here

    find the head of people or the coo at each of these companies with a verified email

    At companies too small for a people team the lookup returns the operator who owns it, and says which.

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.

  • Hiring velocity as the list

    A working list rebuilt from this week's postings instead of last quarter's export.

    1. Signals
    2. Tables
    3. Sequences
    1. 1Pull postings for your segment into a table and put the run on a schedule.
    2. 2Filter to the volume band that signals real pain, then enroll the fresh rows.
    oxygen tables schedule set

  • Find the owner before the team exists

    A named contact at companies that have no HR leader yet.

    1. Tables
    2. Records
    3. Sequences
    1. 1Look up the people lead, falling back to the operations owner where none exists.
    2. 2Verify the address, then enroll on a cadence that suits a team of six.
    oxygen find email

  • Stop working triggers that expired

    Enrollment ends when the hiring stops, without anyone remembering to check.

    1. Tables
    2. Workflows
    3. Sequences
    1. 1Refresh the postings table on a schedule so an account that has gone quiet for a month falls out of the filtered view.
    2. 2Have a cron workflow read that view and remove the stale rows from the campaign they were enrolled in.
    oxygen workflows apply

Capabilities

What you get

  • A list that refreshes itself

    A scheduled run rebuilds the working table from current postings, so nobody is working a trigger that went cold two months ago.

  • Roles mapped onto companies

    Postings resolve onto the account, so you read the department a company is staffing rather than a raw feed of disconnected job titles.

  • One place for the reply

    Email, LinkedIn, and WhatsApp conversations land in the same inbox and attach to the account, so a warm answer is never stranded in a personal mailbox.

  • Build free, pay to send

    Tables, the CRM, workflows, and sequence drafts are unmetered. Connecting a sending mailbox and dispatching from it is what needs a plan.

Instead of

The stack this replaces

Native, on one contract and one credit balance — not another tab wired to the last one.

  • Clay
  • Apollo
  • Lemlist
  • HubSpot
  • n8n
  • Airtable

Data sources

What the data actually comes from

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

  • TheirStack

    Job postings with dates and departments, the raw material behind every hiring trigger on this page.

  • PredictLeads

    Company events including hiring bursts and funding, so a posting spike arrives with context beside it.

  • People Data Labs

    Headcount and firmographics, used to band accounts by size before anything is spent on contacts.

  • Blitz API

    Resolves the people or operations owner, including at companies with no HR title at all.

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

  • A posting is evidence of intent, not proof of budget. Some of what you see is a backfill or an evergreen ad open for a year, so rank on volume and confirm it on the call.

FAQ

Questions people ask first

How fresh is the posting data?
Fresh enough for a weekly cycle, and dated so you can judge. Each posting row carries the date it was seen, which makes the window your choice: seven days, or sixty for a slower motion.
Can we watch a fixed account list instead of the whole market?
Yes, and once you have a target list that is the better setup. You name the accounts, the run watches only those, and a new posting shows up on a company you already know.
What if the company has no HR leader?
Then the buyer is the founder or the operations lead, and the lookup should ask for that. The table records the title it found, so you can write to those two readers differently.
Does this replace our sequencer?
It can. Cadence, enrollment, sender rotation, and suppression live here, and answers come back into the same workspace. Teams often keep the old tool a while and move campaigns across one at a time.
How do we avoid contacting the same company twice?
Suppression is workspace wide rather than per campaign. A domain or person you exclude stays excluded everywhere, and a reply from anyone at an account stops the cadence aimed at it.
What does a run actually cost?
You see it before it happens. Sourcing and reading postings are metered, contact lookups bill on a hit rather than an attempt, and each run states its scope and ceiling first.

Put your GTM motion on one stack

Sign up, get a working workspace with a one-time credit grant, and run the first play end to end without wiring five tools together.

Start freeSee pricing