Being “the first RevOps hire” sounds exciting, until everyone treats you as reporting, tooling, and firefighter-in-chief. What you do in the first 6–12 months determines whether RevOps becomes a strategic engine or a permanent catch‑all. In this candid panel, seasoned leaders who’ve built RevOps from zero share the playbooks they wish they’d had on day one. They’ll dig into: - Defining the job: how to write a RevOps charter that sets clear scope and decision rights from the start - What to do first: the 3–4 foundational problems to attack before you touch anything else (and the tempting projects to postpone) - Hiring and structure: when to bring in systems, analytics, enablement, and how to avoid becoming “sales ops with a new name” - Winning credibility fast: how to deliver visible wins for the CRO and board while still laying a scalable foundation You’ll walk away with a realistic sequence for building RevOps. What to say “yes” and “no” to in the early days, how to keep ownership of the strategic agenda, and how to avoid the fate of being the smartest person in the room with the least leverage.