For logistics SaaS

The agentic GTM platform for logistics SaaS teams

Operators in freight do not read email at a desk. They answer the phone between problems, which changes both the list and the cadence you build.

try
Start freeRead the docs

Freight is a market of extremes. A carrier with eight trucks and one with eight hundred are both transportation companies, and only one of them has the problem your software solves. Working that out on the call is an expensive way to qualify a market.

Most of the evidence is public. Company sites state fleet and facility counts, listings carry an address per terminal, and dispatcher hiring shows which operators are growing. Collected into columns, that becomes a size band before anyone picks up a phone.

Who this is for
Seed to Series A logistics software companies selling to carriers, brokers, third party logistics providers, or warehouse operators. Four to fifty people, founder led.
What it looks like today
Fleet size, dock count, and lane coverage decide whether an account can use your product, and none of them are fields in a sales database. So teams buy a list of transportation companies and discover the sizing problem one call at a time.
What changes
Sizing happens before the call. Public listings, company sites, and hiring activity produce a size estimate per row, so the list is banded before a single number gets dialed.

Example searches

Ask for it the way you'd say it

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

  • Size before you dial

    find trucking and 3pl companies in the southeast and estimate how many trucks they run

    The estimate arrives with the page it came from, so a rep can sanity check an account in seconds before calling.

  • Operators adding capacity

    which of these companies posted dispatcher or driver roles in the last month

    Postings attach to the account with dates, so a company scaling up is separable from one that always has ads open.

  • The operations owner

    find the operations manager or owner at each of these carriers with a mobile number

    Numbers land per row with their type, so a calling list is built from the accounts that are genuinely reachable.

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.

  • Band the market by size

    Carriers and brokers split into size bands before anyone contacts them.

    1. Tables
    2. Records
    3. Tags
    1. 1Source operators by region, then read sites and listings for fleet and facility counts.
    2. 2Band the rows and promote only the bands your product actually fits.
    oxygen tables query

  • Growth signals from hiring

    A short list of operators adding capacity right now.

    1. Signals
    2. Tables
    3. Sequences
    1. 1Run a hiring search scoped to your banded accounts so dispatcher, driver, and warehouse postings land in their own table.
    2. 2Enroll the accounts with fresh postings ahead of everything else.
    oxygen signals search run

  • Phone first, email second

    A calling list with numbers, plus an email step for accounts without one.

    1. Tables
    2. Sequences
    3. Messages
    1. 1Run the phone and email waterfalls, reading the cost preview before approving.
    2. 2Build one cadence with call tasks and email steps, and log every outcome.
    oxygen find phone

Capabilities

What you get

  • Sizing as a column

    Fleet counts, terminals, and facility mentions come off public pages into numeric columns, so a list can be banded before anybody works it.

  • Calls and emails in one cadence

    A sequence can mix call tasks with email steps, so the channel that actually works in this market is part of the motion rather than beside it.

  • Costs with a ceiling

    Managed phone and email finders bill only when they return a value. Email checks bill even on a miss, including checks of guessed addresses on rows without a LinkedIn URL. Every run you start carries a credit ceiling.

  • One workspace, one meter

    Sourcing, enrichment, the CRM, sequences, and reporting share a database and a credit balance, so there is nothing to reconcile between vendors.

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
  • Pipedrive
  • n8n
  • Google Sheets

Data sources

Data sources and CRM connections

  • Op

    Open Web Ninja

    Business listings by city and category, which is how terminals and warehouses become rows with addresses.

  • TheirStack

    Postings for dispatchers, drivers, and warehouse staff, the most honest public signal of capacity growth.

  • People Data Labs

    Company records for the operators large enough to have one, used to sanity check the size bands.

  • Blitz API

    Finds the operations owner at a carrier or broker instead of a shared dispatch inbox.

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

  • Fleet numbers on a company website are marketing copy and can be years old. Use them to band accounts, not to price a deal, and confirm the real number on the first call.

FAQ

Questions people ask first

Can we estimate fleet size without buying a data feed?
Often, yes. Company sites, listings, and job ads together give a defensible band. It is an estimate, and the cell keeps the page behind it so a rep can judge it rather than trust it blindly.
Our motion is phone first. Does that fit?
It does. A sequence can carry call tasks alongside email steps, and outcomes log against the account, so the calling list and the email list are one list rather than two.
Do owner operators belong on the list at all?
Usually not, and banding is how you exclude them cheaply. Filtering before enrichment means you never pay to look up a contact at an account you were never going to sell to.
What happens to a number that turns out to be wrong?
It stays visible with its source and the run that produced it, so you can see which lane found it. Corrections are written to the record instead of quietly overwriting the history.
Can we track terminals as well as companies?
Yes. Locations can be rows related to the company record, which matters when the buying decision sits at a terminal rather than at a head office.
How long does a first list take to build?
An afternoon for a region, most of it spent waiting on runs. Sourcing and site reading happen in the background as durable runs, so you can close the tab and read results later.

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