Revenue Operations and Go-to-Market Alignment
What this domain tests
RevOps alignment asks whether marketing, sales, and customer success operate on one funnel definition, one data model, and one number. Questions target stage definitions, service-level agreements between functions, conversion math, pipeline coverage, capacity planning, and the mechanics of quote-to-cash.
Core rules
- One funnel, one definition. Each stage needs written exit criteria agreed by both sides of the handoff. Without shared definitions there is no shared accountability.
- SLA both directions. Marketing commits to volume and quality; sales commits to acceptance and first-touch time, with documented rejection reasons and a recycling path.
- Pipeline coverage is derived, not aspirational. Required pipeline = target ÷ win rate. Coverage of 3x–4x is typical; it rises automatically when win rates fall.
- Model the funnel as a chain. MQL → SQL → opportunity → win, each with its own conversion rate. Blended rates hide the failing step.
- Capacity planning compares ramped rep productivity against quota, accounting for ramp time and attrition.
- GTM motion per segment: product-led, sales-led, or partner-led - chosen deliberately, not layered on top of each other.
- Deal desk and CPQ own quote-to-cash integrity: approvals, discount authority, and contract terms.
Worked example
Target new ARR is $6M, historic win rate 25%, average deal $60k - so 100 wins are needed. At a 20% SQL-to-win rate that requires 500 SQLs; at 40% MQL-to-SQL conversion, 1,250 MQLs. Required pipeline is $6M ÷ 0.25 = $24M, i.e. 4x coverage. If win rate drops to 20%, 150 wins are needed: 750 SQLs, 1,875 MQLs, and required pipeline of $30M - coverage must rise to 5x. The binding constraint is qualification quality, not lead volume.
Traps
Counting pipeline without stage criteria. Using blended win rates across segments. Letting marketing count MQLs sales never touches. Treating coverage as a target rather than an output.