Upcoming RevOps Masterclass: The Next Evolution of the Revenue Operator
RevOps existed to fix a silo problem. Marketing Ops, Sales Ops, CS Ops and GTM Systems each owned a slice of a customer journey the customer never split up, so the industry merged them. That worked. What it produced is a job description no single person can hold: set the operating strategy, design the system, and build it, all at once. So the hire lands, delivers the third they are naturally best at, and the other two quietly go undone for two years.
The GTM Engineer title showed up because that is what happens when one part of a role outgrows the generalist holding it. Two more are coming. Alex Biale and Rhys Williams walk through the three paths the role is splitting into, why this is not a return to silos, and how to sequence the hires so you are not rebuilding in a year.
What you will leave with:
A working definition of the three roles — GTM Ops Strategist, GTM Ops Architect, GTM Engineer — and what each one actually decides
The scorecard we use to find which altitude is unowned on a RevOps team, and how to score a candidate with it
A hiring sequence tied to operating maturity, including why the architect seat almost always comes before the engineer seat
Who this is for:
CROs, VPs of RevOps, and heads of GTM Ops at $5M–$100M ARR B2B SaaS companies who are about to write a RevOps job description, or who already hired one person and cannot work out why nothing compounds. Not useful if you are a two-person GTM team, or if you are shopping for tool recommendations.
Your hosts:
Alex Biale, Co-Founder at Domestique. Leads the demand and commercial GTM practice, and spends most of his time on operating model and role design for Series A to D SaaS teams.
Rhys Williams, Co-Founder at Domestique. Owns FinOps and BizOps, and works primarily on where RevOps work should sit inside a company and who should own it.
Register here
08/19 12p MT
