Appearance

RevenueOps Manager JD teardown ​

If your RevenueOps Manager JD reads like “fix the mess,” you are about to hire into ambiguity.

What this JD is really asking for (in outcomes) ​

Within 90 days, the role must make the revenue engine measurable and reviewable:

  • One shared pipeline definition language
  • Cleaner lifecycle stage discipline
  • A KPI tree leadership can trust

Common failure modes (patterns) ​

  1. “Own RevOps” without naming KPIs (pipeline velocity, win rate, CAC payback, forecast accuracy)
  2. “Improve forecasting” without stage definitions + enforcement
  3. “Fix attribution” without instrumentation scope
  4. “Partner with teams” without explicit interfaces (M→S, S→CS, S→Finance)
  5. Mixing IC build work with director-level governance

Fixes (paste-ready) ​

Replace “responsibilities” with owned outcomes:

  • Own a KPI tree that ties pipeline → bookings → cash.
  • Own lifecycle stage definitions and the enforcement cadence.
  • Own routing rules and hygiene SLAs (duplicates, enrichment, attribution).

Add constraints:

  • Stack (CRM/MAP/BI)
  • Team size and decision rights
  • Budget authority (if any)

Interview plan preview (3 exercises) ​

  • 90-day operating plan: show cadence, definitions, KPIs, first fixes.
  • Lifecycle stage audit: identify 10 common errors and how you would prevent them.
  • KPI tree build: map KPI → inputs → owners → instrumentation.

Next move ​