For outbound agencies
Run every client's outbound from one workspace set
You are not short of tools. You are short of a way to run twelve clients without twelve subscriptions and twelve places to look.
An agency rarely fails on copy. It fails on operations. Your twelfth client needs the same eight setup steps as your first, and by then nobody remembers which mailbox belongs to which logo.
A workspace is one client's copy of the stack. Any workspace on a paid plan can be the billing owner for the others its admins run, and the linked ones share its credit pool. Inside each, Tables hold the list, Sequences own the cadence and senders, Messages hold the replies.
- Who this is for
- A cold-email agency running campaigns for five to twenty B2B clients at once. Two to fifteen operators, and a delivery promise that has to hold every month.
- What it looks like today
- Every client arrives with its own sequencer seat, list tool, spreadsheet, and domain bill. None of it joins up, so the Monday answer gets rebuilt from four screens.
- What changes
- One plan covers every client workspace. Credits come from a shared pool with a per-client cap, spend is attributed by workspace before you invoice, and the client gets a login instead of a slide.
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.
Where the credits went
show me what each client workspace spent this month and on what
Usage splits by sub-workspace, so the number you invoice is the number you can show.
A new client's first list
build 400 companies in this niche and find the head of sales at each
The sourcing plan returns the filters and a cost band before a paid row runs.
Senders that need attention
which mailboxes in this client's workspace are unhealthy or paused right now
Health ranks worst first inside the workspace you opened, with the bounce evidence attached. A roster-wide view means switching client and reading it again.
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.
Stand up a client from the last one
A new client running the motion that already works, without rebuilding it.
- 1Export the blueprint from the account that performs and apply it next door.
- 2Fill the ICP, offer, and disqualifiers once, then point the drafting prompts at those pages.
oxygen blueprints applySending infrastructure per client
Domains, mailboxes, and warmup that belong to one client, not a shared pool.
- 1Buy or connect domains and mailboxes inside that client's own workspace.
- 2Read sender health worst first, then open the evidence behind a pause.
oxygen mailboxes healthGive the client a login, not a deck
The client reviews the list and signs off the launch, with a timestamp.
- 1Invite them on the restricted role: read, comment, decide what is theirs.
- 2Gate the launch so a sequence cannot start until that person approves.
oxygen approvals gate set
Capabilities
What you get
One plan across client workspaces
A paid workspace can pay for the others its admins administer. They inherit the plan and share one credit pool, one level deep, and detach whenever you say so.
Spend attributed per client
Usage breaks down by sub-workspace, and an optional monthly cap stops one client's enrichment run eating the pool everyone else works from.
Domains and ramp per client
Buy or connect a client's sending domains inside their own workspace, and let each mailbox ramp on the schedule that account earned. Volume rises where one client's history supports it, not on a roster average.
A login that cannot spend
The restricted client role reads, comments, and decides what is assigned to it. It cannot launch a sequence, move a gate, or draw a credit.
Instead of
The stack this replaces
Native, on one contract and one credit balance — not another tab wired to the last one.
- Clay
- Instantly
- Smartlead
- HubSpot
- Airtable
- n8n
- Zapier
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.
Blitz API
Profile and company scraping, and the head lane of the work-email chain, so the metered lanes behind it stay idle.
LeadMagic
Runs on the rows the first lane left blank, and releases the charge when it comes back empty.
MillionVerifier
Grades every address found, so a client domain does not learn by bouncing.
BounceBan
Takes the accept-all verdicts only, so the deeper check is paid on catch-alls.
Mailforge
Managed cold-email domains and mailboxes, inside the client workspace.
Instantly
Keeps a client already sending there reachable while the program moves.
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
- Shared billing is exactly one level deep. A billing owner cannot itself be paid for by a third workspace, so a holding structure needs a plan at each tier.
- Client collaboration is in beta and enabled per workspace in settings. The CLI, the MCP tools, and the emailed approval link work without it.
FAQ
Questions people ask first
Do I need a subscription per client?
How do I stop one client burning the pool?
Can a client see the work safely?
Do bounces cross between client domains?
Who keeps the workspace after the engagement?
What does an agency pay to start?
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.