Revenue Operations

SalesOps optimizes the sales process (pipeline, forecasting, territory management, compensation). MarketingOps manages marketing tools, campaigns, and lead generation workflows. RevOps sits above both, creating a unified revenue system: single CRM, integrated data, shared metrics (pipeline, revenue, forecasts). The key insight is that isolated operations create data gaps — marketing passes leads with insufficient qualification, sales lacks context on campaign sources, CS doesn't see the revenue impact. RevOps enforces integration: marketing/sales handoff SLAs, unified lead scoring, shared dashboards, coordinated territory planning. Without RevOps, you have three separate tools and three versions of truth. With RevOps, you have one revenue engine.

Start with historical accuracy: look back 12 months, categorize closed deals by deal size, sales cycle length, and outcome. Build a simple model: forecast = (pipeline in stage X) × (historical close rate for stage X). Layer in seasonality (enterprise budgets Q4, SMB spends H2), product changes (price increases lower velocity), and sales rep skill (A-players close 30% faster). Validate weekly: compare forecast vs actual, find error patterns (forecasts too optimistic = bad deal qualification, forecast too conservative = sales rep hesitation). Use tools like Clari (AI-powered) or Tableau + dbt for manual modeling. Most common mistake: extrapolating pipeline without considering conversion rates — $5M pipeline looks great until you realize your close rate is 10% (only $500K actual revenue). Forecast = realistic pipeline × realistic close rate, not just raw pipeline.

Rules-based (A-lead = $1M+ company + decision-maker + 3+ touches this month) is transparent but slow to maintain. Behavioral (ML on historical wins) scales but feels like a black box. Best practice: hybrid model. Start rules-based with clear criteria (company size, industry, role match), then layer behavioral signals (email opens, content engagement, website visits). Use LeanData or Marketo for automation. Mistake to avoid: scoring on activity alone (10 emails = sales-ready lead) — high activity from irrelevant personas wastes sales time. Audit your model monthly: score the last 20 closed-won deals (what did they have in common?) vs 20 closed-lost deals (what red flags did we miss?). If top-scoring leads have low conversion, your model is wrong.

Sales comp plans directly impact RevOps data quality. If reps are paid on ARR signed, they'll front-load deals (Jan ≠ true revenue). If paid on revenue recognized, they'll avoid multi-year deals. If paid on quota attainment, they'll dump deals at EOQ (artificial spikes). Common solution: base salary (70%) + commission on actual revenue recognized (20%) + bonus on quota/growth (10%). Use tiered accelerators (ex: 1.5x commission over 120% quota) to align with business goals. Automate comp calculations from CRM data (Salesforce → dbt → Tableau) to avoid manual error and enable transparency. Most critical: involve RevOps early when designing the plan. Post-launch compensation disputes (reps claim they hit quota, finance disagreed) become RevOps problems — you have to mediate with the CRM.

Executive dashboard (CEO/board): (1) ARR/MRR actual vs forecast, (2) Net Revenue Retention, (3) CAC Payback, (4) Sales Efficiency (Magic Number: new ARR / S&M spend). Sales ops dashboard (team view): (1) Pipeline by stage + age, (2) Win rate by stage/rep/product, (3) Sales cycle duration (trending), (4) Quota attainment %, (5) Forecast accuracy (vs last month). Marketing/RevOps alignment dashboard: (1) Leads generated → Sales-qualified leads, (2) Lead-to-deal conversion, (3) CAC by source, (4) Influence (first-touch, multi-touch, closed-loop). Avoid vanity metrics (total pipeline, number of calls, email sends) — they don't predict revenue. Update weekly, not monthly. If your dashboards are stale by Tuesday, nobody will trust them for forecasting.

Yes, but it doesn't have to be perfect. Start with the 20% of data that matters: company name, contact role/seniority, pipeline stage, deal size, deal age. Enforce standards on new records (validation rules in Salesforce), then gradually clean historical data. Use LeanData or Data.com to dedupe companies and verify contact roles. Most common pitfall: standardizing too early (spending 3 months cleaning data before you've aligned with sales) vs too late (implementing a tool stack on messy data, then discovering you can't migrate). Phase it: Month 1 = new-record standards + CRM training, Month 2-3 = automated data cleanup (fuzzy matching, duplicate flagging), Month 4+ = optimize stage definitions and close rates. Your RevOps tech stack is only as good as the data it runs on — if sales reps skip pipeline updates, even Clari can't help.

Salesforce if you need flexibility, scale, or have complex custom requirements (enterprise SaaS, $100M+ ARR). HubSpot if you're <$10M ARR, need speed-to-value, or want an all-in-one suite (CRM + marketing + CS in one UI). Specialized tools (Clari for forecasting, Gong for call intelligence, Outreach for sequences) layer on top of your core CRM to add capability — don't replace the CRM. Most common mistake: tool stack bloat (Salesforce + Hubspot + Clari + Salesloft + Gong + 5 other platforms = integration nightmare, $50k/year). Better: core CRM + 2-3 specialized tools + single data warehouse (Snowflake/BigQuery) for reporting. Before buying anything, ask: 'Can Salesforce/HubSpot + dbt + Tableau solve this problem?' Usually yes.