For productivity SaaS

The agentic GTM platform for productivity SaaS teams

Productivity SaaS teams win outbound by testing small segments one at a time, because a horizontal product has no natural list. On a paid plan, OXYGEN's AI agent builds each test list as its own table, and the replies show which segment wins.

try
Start freeRead the docs

The hard part for a horizontal tool is choosing, not sending. Any list can be justified, so a first campaign often becomes a thousand companies of no particular kind, with replies that show no pattern.

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
The GTM (go-to-market) team at a productivity SaaS company with a proven horizontal tool. It sells docs, project tracking, scheduling, team chat, or workflow software as a subscription. Two or more sellers take it to the accounts a signup alone does not win.
What it looks like today
Everyone is a prospect, so nobody is. The list becomes every company of a certain size and the copy turns generic. The campaign teaches you nothing, because it held no hypothesis to disprove.
What changes
You define wedges and test them. Three small lists built on different criteria, three versions of the copy, and one workspace that holds each wedge's replies, costs and outcomes.

Example searches

Ask for it the way you'd say it

Each example is a request in plain words, with what it returns underneath.

  • 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 tag each table, so every segment keeps its own list instead of blending into one campaign.

  • Team shape as well as 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. 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 compare.

    1. Tables
    2. Tags
    3. Sequences
    1. 1Build one table per hypothesis and tag each table with its segment.
    2. 2Run each as its own sequence and read each sequence's analytics.
    oxygen tables tag

  • 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 ideal customer profile (ICP) into the company profile.
    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. 2Remove the rows of anyone you are already talking to, then enroll the table in a short referral sequence.
    oxygen people search run

Capabilities

What you get

  • Segments you can compare

    Tags separate the wedges across tables, sequences, and email 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 company profile. A later AI column reads it when you map the profile in, so the learning outlives the person who found it.

  • 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 every enrichment or AI run you start carries a credit ceiling. A wedge that fails costs a few hours, not a quarter.

Instead of

The stack this replaces

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

Data sources

Data sources and CRM connections

  • TheirStack

    Finds companies by the tools their job postings name, such as a project tool you integrate with.

  • LeadMagic

    Scans a company's website for the tools it loads when job postings name none. It helps when a wedge's tool shows on the site, such as a support chat widget.

  • Blitz API

    Company size, industry and open roles by title, the base layer for each wedge, plus the operations lead or chief of staff.

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

  • 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 joins one wedge's table and sequence, and filters the inbox to its email replies; tag LinkedIn replies yourself. Each sequence's stats show sends, replies and reply rate, while the tag index only counts what carries each label.
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 as well as new logos?
Yes. Existing customers are records, so other departments at those companies can be sourced, enriched and enrolled like any other list. Enrollment does not skip everyone you are already talking to, so remove their rows from the table before you enroll 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?
Tables, sequence drafts and workflows cost nothing to build. Searches, enrichment and AI columns draw credits, and a new workspace starts with a small one-time grant. A run you start in a table shows its cost first; the AI agent reports it afterwards. Connecting a mailbox or LinkedIn account to send from needs a paid plan, and so does chatting with OXYGEN's AI agent once onboarding ends.

Put your GTM motion on one stack

Sign up free with a one-time credit grant, and an in-app AI agent researches your company and proposes your first plays. Pick a plan, and it sources the buyers, writes the sequence, and enrolls them. Connect the mailbox or LinkedIn account it sends from, and it is ready to send.

Start freeSee pricing