What is Oxygen
A GTM engineering workspace for early-stage B2B SaaS teams and GTM agencies.
Oxygen is a GTM engineering workspace for founders, revenue operators, GTM engineers, and agencies that need to turn GTM work into durable, inspectable systems. You build tables of accounts, contacts, leads, signups, or campaign state; add columns that enrich, score, research, or sync rows; and package repeatable motions as workflows.
Most users drive Oxygen through an AI assistant such as Claude Desktop, Claude Code, or Codex. The assistant calls Oxygen through MCP or shells out to the oxygen CLI. The web app and MCP widgets show what happened: tables, runs, credits, errors, approvals, and provenance.
Oxygen is not a generic CRM, a spreadsheet clone, or a standalone autonomous-agent runtime. Agent-like behavior in Oxygen is expressed as workflows and runs over the same workspace primitives you can inspect.
The primitives
| Primitive | What it is |
|---|---|
| Organizations | A workspace boundary for members, client work, integrations, billing, and data. |
| Workspace context | Durable company profile, ICP, positioning, assets, prompts, and GTM stack. |
| Tables | Typed GTM datasets and the audit surface for work. |
| Columns | Source/manual, formula, AI, tool, enrichment, and provider-action work. |
| Cells | Per-row outputs with status, cost, provenance, and history. |
| Workflows | Repeatable processes over tables, tools, transforms, approvals, and runs. |
| Triggers | API, cron, webhook, and event starts for workflows. |
| Modes | smoke_test, dry_run, and live execution semantics. |
| Runs | Inspectable records of work at scale. |
| Provider catalog | Runnable tools and schemas for sourcing, enrichment, CRM, outbound, and AI work. |
| Integrations | Connected provider accounts and event subscriptions. |
| Approvals | Human confirmation before paid work or external writes. |
| Spend caps | Per-run credit ceilings for paid work. |
| Billing | Credits, usage, managed provider spend, and BYOK context. |
The surfaces
| Surface | Use for |
|---|---|
| CLI | Scripts, terminal work, agency operations, and agent fallback. |
| MCP | Conversational execution from AI assistants. |
| Web app | Visual inspection, approvals, team review, and setup. |
The execution contract is API, CLI, and MCP first. The web app and widgets visualize, approve, retry, and explain the same workspace state.
Next
Quickstart installs the CLI, signs you in, picks an organization, checks context, and inspects your first table.