OXYGENOXYGEN

For productivity SaaS

GTM infrastructure for productivity SaaS teams

A horizontal product has no natural list, which is why a first outbound attempt usually fails. The fix is segments you can test one at a time.

try
Start freeRead the docs

The hardest problem for a horizontal tool is not sending, it is choosing. Any list can be justified, which is why most first campaigns are a thousand companies of no particular kind and a reply pile with no pattern in it anywhere.

Treat it as an experiment instead. A wedge is a hypothesis: this size, this team shape, this tool already in place. Build three of them as small tables, tag them, run them separately, and let the workspace say which one earned another week.

Who this is for
Seed to Series A companies selling a horizontal tool: docs, project tracking, scheduling, internal communication, or workflow software. Four to fifty people, founder led growth.
What it looks like today
Everyone is a prospect, so nobody is. The list ends up being all companies of a certain size, the copy ends up generic, and the campaign teaches you nothing because there was no hypothesis in it to disprove.
What changes
You define wedges and test them. Three small lists built on different criteria, three versions of the copy, and one place where the replies, costs, and outcomes can be compared honestly.

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.

  • One wedge, one list

    find companies with between 50 and 200 people that already run a project tool we integrate with

    One query builds one table. Run it again per wedge and each segment keeps its own list and its own tag instead of blending into one campaign.

  • Team shape, not just size

    find companies between 50 and 200 people with more than five project manager roles open

    Role counts arrive as columns, so a team shape hypothesis becomes a filter you can state precisely.

  • Who owns internal tooling

    find the operations lead or chief of staff at each of these companies with an email

    Internal tooling has no standard owner at this size, so plan on two names per account: the operations lead who feels the problem and whoever signs off on the spend.

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.

  • Wedge test

    Three small segments run separately, with results you can actually compare.

    1. Tables
    2. Tags
    3. Sequences
    1. 1Build one table per hypothesis and tag every row with its segment.
    2. 2Run each as its own sequence and read the outcomes per tag.
    oxygen tags list

  • Promote the wedge that works

    The segment that replied becomes your real account list.

    1. Tables
    2. Records
    3. Knowledge Graph
    1. 1Promote the winning rows into accounts and write that ICP into the wiki.
    2. 2Rebuild the next list from the written definition rather than from instinct.
    oxygen knowledge profile update

  • Expand inside the accounts you win

    Second and third teams inside a customer, found deliberately.

    1. Records
    2. Tables
    3. Sequences
    1. 1List the other departments at your existing customers as rows in a table.
    2. 2Enroll a short referral cadence, suppressing anyone already in a thread.
    oxygen people search run

Capabilities

What you get

  • Segments you can actually compare

    Tags separate the wedges across tables, sequences, and replies, so an experiment reads as a result instead of an average across everything you sent.

  • A definition that outlives the test

    The ICP that wins goes into the workspace wiki and later runs read it, so the learning is reused rather than remembered by one person.

  • Expansion treated like pipeline

    Existing customers are records, so a second team inside an account is a row somebody can work, not an idea raised once in a meeting.

  • Cheap to be wrong

    Small test lists cost little to build and the spend is previewed, so an unproductive wedge costs a few hours rather than a quarter.

Instead of

The stack this replaces

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

  • Clay
  • Apollo
  • Instantly
  • HubSpot
  • Airtable
  • Zapier

Data sources

What the data actually comes from

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

  • People Data Labs

    Firmographics and headcount, the base layer for cutting a horizontal market into testable segments.

  • TheirStack

    Job postings, which reveal team shape: how many project managers, operations people, or engineers a company hires.

  • BuiltWith

    Technology detected on a domain, useful for a wedge defined by a tool a company already runs.

  • Blitz API

    Finds the operations owner or chief of staff, who buys internal tooling at this size of company.

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 hundred row test tells you whether a wedge is obviously wrong, not whether it is right. Treat an early result as a reason to run a larger version, not as proof that a segment works.

FAQ

Questions people ask first

How small can a test list be?
A hundred rows is enough to see whether the copy lands and the targeting is coherent. Smaller than that and you are learning about individual accounts rather than about a segment.
How do we compare two segments fairly?
Tag them and run each wedge as its own sequence. The tag is what joins one wedge's table, its sequence, and the conversations it produced, and the per sequence analytics are where sends, answers, and costs are read back. The tag index reports how much is carrying each label, not how each label performed.
When should we stop testing and commit?
When one wedge keeps producing conversations that sound the same. That repetition is the real signal, and it is easier to notice when the replies sit beside the list that produced them.
Can we use this for expansion, not just new logos?
Yes. Existing customers are records, so other departments at those companies can be sourced, enriched, and enrolled like any other list, with suppression keeping live threads out of it.
Does a horizontal product need a different setup?
Only in how you build lists. The primitives are identical, but you will spend more time on segmentation and tags and less time staring at one enormous table.
What does a first month cost?
Building costs nothing and three hundred enriched rows is a small spend. A workspace starts with 10,000 credits, and Starter is $99 a month if you decide to start sending.

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