Reference · A1 definitional volume
RevOps
11 terms. Revenue operations, systems, and data.
RevOps · 11
- Data Enrichmentenrichment, waterfall enrichment Augmenting contact/account records with data from multiple providers (a 'waterfall' tries sources in sequence) to improve targeting and personalization. C6
- GTM Engineergo-to-market engineer A technical revenue role that builds and automates the systems powering outbound: ICP data pipelines, enrichment, lead routing, signal-to-action workflows, and tool integrations. Builds the machine SDRs used to run by hand. C6
- Lead Routinground-robin routing, lead assignment Automated logic that assigns inbound leads to the right rep based on territory, segment, or availability. C6
- Marketing OperationsMOps The function managing the systems, processes, and data that power marketing campaign execution and reporting. C6
- Operating Cadenceoperating rhythm The recurring meeting/review structure (weekly forecast, pipeline review, QBR) that keeps the GTM engine accountable. C6
- QBRQuarterly Business Review A periodic review of performance against targets across the revenue org (and sometimes with customers). C6
- Revenue OperationsRevOps The function aligning sales, marketing, customer success, and finance around shared processes, data, and the analytics layer — designing the dashboards and rules that run the GTM engine. C6
- Rules of Engagement The agreed rules governing who works which leads/accounts and how handoffs occur, preventing conflict and leakage. C6
- Signal-to-Actionsignal-based selling Workflows that detect an intent signal (job change, site visit, surge) and automatically trigger a personalized outreach action. C6
- SLAService Level Agreement A committed standard between teams or vendor and customer — e.g. marketing-to-sales lead-response time, or support resolution times. C6
- Stage Definitions Explicit, enforced criteria for what each pipeline stage means, so forecasts are consistent and deals don't get stuck or skipped. C6