For fractional GTM
The stack a fractional GTM consultant brings along
You are hired for a quarter and judged on what still works in the third one. That argues for infrastructure you can hand over, not a document.
Fractional work has a structural problem that talent does not fix. What you create is a system, and a system built inside somebody else's tool subscriptions cannot travel. By the third client you are rebuilding the same scoring logic for the third time and charging for it once.
Here the motion is packageable. A table set, its columns, and the workflow around them export as a blueprint and apply into a fresh workspace, where you adapt instead of rebuild. What the client knows goes into their own wiki pages, so a drafting prompt reads a written source rather than your memory of the kickoff.
- Who this is for
- A fractional GTM lead, RevOps consultant, or independent operator working with three to six B2B SaaS companies at once. Paid for judgment, not for plumbing.
- What it looks like today
- Every engagement restarts from zero. You rebuild the list logic inside whatever the client already bought, the reasoning stays in your head, and the motion ends when the contract does.
- What changes
- The motion becomes an artifact. A working setup exports and applies into the next workspace, the reasoning lives in the client's own wiki, and you leave a hosted workflow with a readable run log.
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.
Onboarding week one
read this company's site and write their positioning, ICP, and disqualifiers into the workspace
Pages land revisioned, linked, and searchable, so the next prompt or column can name the one it should read.
Testing the thesis
how many companies in this segment are hiring for the role my client's product removes
Hiring posts arrive as a filterable column, so the thesis is a number before it is a slide.
Reusing last quarter
run the same qualification steps i built for the other client against this list
The applied bundle brings the columns and the workflow; you change the prompt, not the plumbing.
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.
Package the motion, then apply it
A proven table set and workflow installed into a new client workspace in minutes.
- 1Export the blueprint from the engagement where the motion already works.
- 2Preflight it against the new workspace, apply, then adapt prompts to their offer.
oxygen blueprints exportWrite the client's context down once
Scoring and drafting columns point at one written description of the business instead of your memory.
- 1Fill the company profile, ICP, offers, and disqualifiers as sourced pages.
- 2Point scoring and drafting columns at that context so the reasoning is inspectable.
oxygen knowledge page upsertLeave a workflow, not a handover doc
The automation keeps running after you go, with a run log the client can read.
- 1Move the recurring steps into a hosted workflow with a schedule and approvals.
- 2Walk them through one run timeline so a failure has somewhere to be seen.
oxygen workflows apply
Capabilities
What you get
A motion you can carry
Export a working table set, its columns, and the workflow around them, then apply the bundle in the next client workspace. The judgment travels; the rebuild does not.
Context that outlives you
Profile, ICP, positioning, offers, and disqualifiers live as versioned, linked pages in the client's own workspace. Point a scoring or drafting prompt at the page it should read, and the run records what it used.
Automation the client can read
A hosted workflow shows its triggers, steps, retries, approvals, and every run it has made. Handover is a walkthrough of a live system.
Separate workspaces, one bill
Each client keeps its own workspace and data. If you carry the subscription, one plan can pay for several of them with spend attributed per workspace.
Instead of
The stack this replaces
Native, on one contract and one credit balance — not another tab wired to the last one.
- Clay
- n8n
- Zapier
- Notion
- Airtable
- Make
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.
People Data Labs
Firmographics for sizing a market before a client commits to a segment.
TheirStack
Job postings and the tools named inside them, the fastest read on what a market buys.
Blitz API
Resolves the contact behind an account once the segment has been chosen.
Exa
Grounds research columns in fetched pages, so a claim points at a source.
Firecrawl
Reads the client's own site and competitor pages into the workspace as rows.
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
- A blueprint carries structure, not data. Columns, prompts, and workflow steps travel between workspaces; rows, credentials, connected accounts, and provider keys stay put.
- A page grounds the prompt you point at it, but canonical voice and positioning changes pass an approval queue. That is deliberate: an approved message cannot be rewritten by a run.
FAQ
Questions people ask first
Can I reuse a setup across clients?
Who owns the workspace when I leave?
Does the client have to buy anything on day one?
How does the AI know anything about this client?
Does this replace the automation tool they run?
Can I work from a terminal instead of the app?
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.