For SDR leaders
Run an SDR team on one inspectable pipeline
Two reps, four mailboxes and a spreadsheet nobody trusts. The fix is one pipeline where the list, the senders and the replies share a database.
An outbound team of three breaks on coordination, not on effort. Two reps work the same account from different exports. A mailbox quietly starts bouncing. Somebody writes to a customer who churned last month. Buying another sequencer does not fix any of that.
Sequences own the parts that have to be central: cadence, enrollment, sender rotation, daily limits, suppression and reply-stop. A sender profile groups each rep's mailboxes and accounts under one name and picture, so a step goes out from whoever signs it.
- Who this is for
- The person running a small outbound team at a four to fifty person B2B SaaS company: a head of sales with two reps, or a founder just past the first SDR hire.
- What it looks like today
- Coordination eats the week. Lists get copied, two reps work the same account, a mailbox degrades unnoticed, and a churned customer gets a cold email. The sequencer knows none of it.
- What changes
- Cadence, enrollment, sender rotation, suppression and reply-stop are enforced centrally rather than remembered. Ownership is a field on one shared list, and replies land in a single store.
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.
Split a list between reps
take these accounts, give half to each rep, and make sure neither one touches the other half
Ownership is a field on the row, so enrollment filters on it rather than on two files.
Which mailbox is about to fail
which of my sending mailboxes are bouncing or dropped out of warmup this week
Sender health sorts worst first, with the pause state and the reason attached to each row.
Protect the customer list
suppress everyone at a company we already sell to before this campaign starts sending
Suppression matches address, domain and company, and applies to every sequence at once.
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.
One list, two reps, two identities
Each step sends from the rep who owns the account, under their own limits.
- 1Set an owner column, then build a sender profile per rep with their mailboxes.
- 2Enroll filtered by owner so the from name and the reply thread match.
oxygen senders profiles createDeliverability as a standing check
A bouncing mailbox pauses before a bad domain becomes the team's problem.
- 1Attach domains and mailboxes here, keep warmup on, read the health list weekly.
- 2Let thresholds pause a sender, then rotate capacity to the healthy mailboxes.
oxygen mailboxes healthReplies that end in a stage
Every answer is triaged and written back to the record, not left in a mailbox.
- 1Work the merged inbox in bulk, label the buckets, archive the noise.
- 2Log the outcome on the person and the deal so the pipeline view stays honest.
oxygen inbox bulk
Capabilities
What you get
Suppression that covers everyone
Do-not-contact lists match at address, domain and company level and apply to every sequence at once. A rep cannot escape them with a fresh campaign.
Per-rep identities, one shared list
A sender profile groups one person's mailboxes, LinkedIn account and WhatsApp number under one name and picture, so a list can go out as three people.
One inbox across three channels
Email, LinkedIn and WhatsApp replies land in one thread store with labels and bulk actions, so triage is a single session instead of four tabs.
Sending infrastructure on one bill
Domains, mailboxes, warmup and monitoring are bought and run here. A LinkedIn or WhatsApp sending seat is $30 per month with no per-action charge.
Instead of
The stack this replaces
Native, on one contract and one credit balance — not another tab wired to the last one.
- Instantly
- Smartlead
- Lemlist
- Apollo
- Clay
- HubSpot
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.
Blitz API
Heads the work-email chain, keeping the metered lanes behind it idle.
LeadMagic
Fills the gaps the first lane leaves, including mobiles worth a call.
MillionVerifier
Grades each address before enrollment, so a bad list is caught at build time.
Instantly
Keeps an existing campaign workspace usable while the list and suppression move over.
People Data Labs
Supplies the firmographics a rep filters on before deciding where the week goes.
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
- Sending from your own identity needs a paid plan and a connected mailbox. Building a list and previewing a cadence is free; enrichment draws credits, and dispatch is the purchase.
- Warmup and monitoring reduce risk, they do not remove it. A new domain still needs ramp time, and a bad list damages a sender whoever sends it.
FAQ
Questions people ask first
Can two reps work the same list without colliding?
What happens to a mailbox that starts bouncing?
Do LinkedIn steps carry a per-action cost?
How do we move off the sequencer we use now?
Where do replies actually live?
Can I see what a rep sent without asking them?
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.