Episode Details

What's up everyone, today we have the pleasure of sitting down with Keith Jones, Head of GTM Systems at OpenAI.

Summary: Keith's GTM systems team at OpenAI got split across 2 orgs, ran into the most wildly practical cost center problem imaginable, and ended up proving exactly why distributed systems teams at high-velocity companies don't work. In this episode, he walks through the full restructuring journey, explains why "be close to the money" now means be close to the budget rather than the revenue motion, and breaks down Symphony and harness engineering — the open-source agentic code orchestration tools his team built to ship production-ready GTM changes without going to the nth degree of "write this Apex class." He also has a filter for separating human candidates from AI-generated applications that is simple, specific, and immediately usable. If you run a GTM systems team, build one, or just want to understand what operating at 10x growth actually requires, this one is worth your time.

About Keith Jones

Keith Jones is the Head of GTM Systems at OpenAI, where he leads the team responsible for the tools, platforms, and technical infrastructure behind the company's go-to-market motion. He began his career across sales ops and marketing ops roles before joining Mural, where he built and led the GTM Systems function. He later served as Senior Director and Analyst at Gartner, covering revenue technology, before moving to OpenAI. Keith joins this episode as a technologist and practitioner; the views and opinions he expresses are his own and do not represent OpenAI.

What Separates GTM Ops from GTM Systems

The naming debate in martech ops has been running so long it's almost a genre. Marketing ops, revenue ops, GTM ops, GTM systems — the titles keep multiplying and nobody agrees on where one ends and the other begins. If you're in this function, you've had the conversation. In job interviews. In org design meetings. In budget justifications. It goes nowhere, and it keeps happening.

Keith has a more useful framing. When he first came on the show, he drew a clean line. GTM ops handles process design, training, and the frontline support that keeps the humans in your GTM org running. GTM systems owns the tools, the technical infrastructure, the back-end work: Salesforce, integrations, scaling, the stack. That line still holds. But he's added something that makes it more useful than a job description.

They're the ones in the room with every sales segment leader, every functional head, absorbing what the business actually needs and translating it into something buildable. Without that translation layer, a systems team is guessing. And guessing at OpenAI's pace doesn't go well.

At OpenAI, both functions have kept evolving alongside the company. Denise Dresser came in as CRO with a complete vision for reshaping the go-to-market org. B2B marketing got folded in. The company launched ads. The org changed repeatedly and fast. Through all of it, the underlying logic held: GTM ops partners with the business, GTM systems delivers what that partnership requires.

As for the labels, Keith's position is that they're the wrong thing to anchor on. At OpenAI, the specific titles of marketing ops or rev ops matter less than who owns the stakeholder work and who owns the technical delivery. The names on the teams are almost secondary. The friction comes from not having clarity on which team does which job and what flows between them. Most organizations that treat these two functions as interchangeable tend to find out why that's a problem the hard way.

The clean requirements that GTM ops provides to GTM systems aren't a process nicety. They're what keeps a systems team from building the wrong thing at the wrong pace.

Key takeaway: Draw a line in your own org between who owns stakeholder requirements and who owns technical delivery. If one person or team is carrying bot