Revenue Operations Architect — GTM Systems Builder

Ovii's Interpretation of the Role

The Revenue Operations Architect will design, build, and own end‑to‑end GTM systems—from forecasting engines to AI‑driven deal desks—while delivering reliable executive dashboards for a fast‑growing B2B SaaS AI company.

Role Snapshot

• Design and ship GTM forecasting and deal‑desk engines
• Create territory, quota, and capacity‑planning models
• Architect AI‑enabled GTM agents and signal pipelines
• Deliver live executive dashboards for pipeline health
• Own cross‑functional GTM projects from concept to launch

Must-Have Requirements

• Salesforce
• Gong
• Claude (LLM tooling)
• Forecasting & routing logic design
• RevOps
• GTM engineering
• sales strategy

Nice-to-Have Signals

• CPQ / Salesforce architecture depth
• Outbound data infrastructure (enrichment, sequencing, intent)
• Enterprise sales motion and complex‑deal support
• CPQ/Salesforce architecture
• Outbound data infrastructure
• Enterprise sales motion

Work Setup

• Location: United States, United States
• Work mode: REMOTE
• Remote scope: COUNTRY_RESTRICTED
• Remote countries: United States
• Employment type: Full-Time

Not Specified in JD

• Salary range
• Visa sponsorship
• Travel requirement
• Security clearance
• Coding test

What You'll Likely Work On

• Build a high‑accuracy forecast engine using Gong and Salesforce data
• Implement a deal‑desk with pricing guardrails, discount authority, and quote governance
• Develop territory and quota models with capacity planning and clean routing logic
• Create AI‑driven GTM agents that surface product usage and intent signals to BDRs and AEs
• Produce a live CRO dashboard covering pipeline coverage, conversion, ramp velocity, NRR, and forecast accuracy
• Lead end‑to‑end GTM projects such as pricing changes, new‑segment launches, and cross‑functional initiatives

Good Fit If You Have

• Thrives in zero‑to‑one, builder‑first environments
• Enjoys influencing change‑resistant sellers through proven value
• Has a bias toward shipping, tight scoping, and closing loops