revops-leader-onboarding-coach

Coach a newly-hired RevOps leader through their first 90 days. RevOps is one of the most ill-defined senior roles in B2B SaaS — sometimes it's "Salesforce admin team that grew up", sometimes it's "Chief of Staff to the CRO", sometimes it's "the analytics function that lives between marketing and sales." First-90-day decisions about scope, focus, and stakeholder relationships set the trajectory.

This is parallel to chief-of-staff-onboarding-coach in role-ambiguity, but with a sharper functional center (revenue tech stack, data, process automation).

When to engage

Trigger when:

• "I start as VP RevOps next week, first 90 days plan"
• "Inherited a RevOps team of 8; what's the first thing to fix?"
• "Forecast accuracy is broken; I'm being hired to fix it"
• "We have Salesforce, HubSpot, Outreach, Gong, ZoomInfo, ChurnZero, ChiliPiper — and they don't talk to each other"
• "My boss is the CRO but the CFO wants more from the role"
• "RevOps is being expanded from Sales Ops to revenue operations — what should I prioritize?"

Do not engage for: pure Salesforce administrator roles (different scope), pure marketing operations roles (different focus), or strategic-function/Chief of Staff coaching (use chief-of-staff-onboarding-coach).

Step 0: Disambiguate the role

RevOps spans 5 archetypes; figure out which one you're actually in.

The 5 RevOps archetypes

1. Automation-led (most common at Series B-D). Primary goal: keep the tech stack running, automate routine work, build workflows. CRM admin + marketing-ops admin + integrations. Strong technical center.

2. Data-led (common at Series C+). Primary goal: revenue analytics, dashboards, attribution, forecast accuracy. Heavy SQL / data-warehouse / BI work. Cross-functional reporting.

3. Strategy-led (less common, more senior). Primary goal: go-to-market strategy support, territory design, comp-plan design, capacity planning. Closer to "Chief of Staff to CRO."

4. Process-led (common in mid-market enterprise). Primary goal: deal-desk, contract operations, RFP support, pricing approvals, quote-to-cash discipline.

5. Hybrid (most actual roles). Primary 1-2 archetypes + secondary support for others.

The CRO (or CFO/CEO if RevOps reports there) often hasn't articulated which archetype they want. The first job is to make this explicit and aligned.

Disambiguation conversation with the principal

Within first 7 days, schedule 60-90 min deep dive:

• "What does RevOps look like 6 months from now if I'm wildly successful?"
• "What's the most-broken thing today that I should prioritize?"
• "Which of these would you de-prioritize: forecasting, territory design, automation, attribution, deal desk?"
• "What did the previous RevOps leader do well / not well?"
• "What's our budget for RevOps headcount + tools next year?"
• "Where does the line sit between RevOps and Sales Management?" (Critical — see below.)
• "Will I have direct reports? Now or later?"

Walk away with one-page memo: archetype, top 3 outcomes for first 6 months, principal expectations, success metrics.

Step 1: Principal stakeholder map

RevOps reports vary, and each reporting line shapes priorities.

Reporting to CRO (most common, ~60%)

• Priority: sales-team productivity, forecast accuracy, pipeline hygiene, comp.
• Risk: Marketing Ops and CS Ops feel orphaned.
• Strength: tight feedback loop with sales leadership.

Reporting to CFO (~20%)

• Priority: revenue accuracy, deal-desk discipline, contract operations, ASC 606.
• Risk: cultural distance from sales reps; perceived as compliance function.
• Strength: budget influence, finance-aligned analytics.

Reporting to CEO (~10%)

• Priority: cross-functional revenue strategy, exec-level analytics.
• Risk: stretched too thin; lacks operational depth.
• Strength: org-wide credibility.

Reporting to COO (~10%)

• Priority: revenue + delivery + customer success operational integration.
• Risk: revenue-specific issues compete with broader ops priorities.
• Strength: full operational view.

Whichever line you're in, build relationships across the others. RevOps without strong cross-functional ties is dead.

Step 2: First 30 days — Listen

The single most-leveraged 30 days you'll have. Don't waste it acting.

Stakeholder interviews (45 min each)

Schedule with:

• CRO (multiple times)
• VP Sales
• VP Marketing
• VP Customer Success
• CFO
• CIO / Head of IT
• Top 5 sales reps (volunteer or random sample)
• 2-3 sales managers
• 2-3 marketing operations managers / lifecycle marketers
• 2-3 CSMs
• Existing RevOps team (1:1 with each direct, plus skip-levels)

Standard questions:

• "What's working well in revenue operations today?"
• "What's broken or stuck?"
• "What does great support from RevOps look like for you?"
• "Where are you blocked by other functions today?"
• "What's the dashboard / report you wish you had?"
• "What's the manual process you wish was automated?"
• "What's your honest take on the previous RevOps approach?"

Document review

• Last 4 quarters of forecasts: what was forecast, what shipped, what was the variance?
• Pipeline-stage definitions and exit criteria.
• Lead-routing rules.
• Comp-plan documents.
• Territory definitions and quota assignments.
• Attribution model (if any).
• Deal-desk process documentation.
• Customer-segmentation framework (ICP, accounts, segments).

Tech-stack audit

• CRM: license count, customizations, integration list.
• Marketing automation: instance health, campaign hygiene.
• Sales engagement (Outreach/Salesloft/Apollo/etc.): rep adoption, sequence library.
• Conversation intelligence (Gong/Chorus/Avoma): coverage, signal use.
• Data sources / warehouse: BigQuery / Snowflake / Redshift; what's loaded, what's not.
• BI tool (Looker / Tableau / Mode / etc.): dashboards, usage.
• Dialer / phone (Aircall, RingCentral): rep usage.
• Scheduling (ChiliPiper, Calendly, HubSpot): meeting flows.
• Data enrichment (ZoomInfo, Clearbit, Apollo): list quality.
• CS platform (Gainsight, ChurnZero, Catalyst, Vitally): coverage, health-score logic.
• Documentation / quote-to-cash (Salesforce CPQ, DealHub, PandaDoc, Conga): contract flow.
• AI tools (Clari, Aviso, BoostUp, etc.): forecasting / coaching.

Data audit

• CRM hygiene: how many records, missing-fields percentage, duplicate rate.
• Lead-routing accuracy: are leads landing where they should?
• Pipeline-stage discipline: do reps follow stage exit criteria?
• Forecast methodology: rep commits + AI signals + management adjustments?
• Attribution: is there a model? Is it trusted? Are there multi-touch / first-touch / last-touch debates?

You're looking for the 1-3 most-broken things to focus on in the first 90 days. Most companies have 5-10; you can't fix all of them in 90 days.

Step 3: First 90 days quick wins

Pick the top 3-5 quick wins. Don't aim for perfection; aim for momentum.

Common high-leverage quick wins

1. Forecast accuracy improvement. Tighten the methodology, add deal-stage exit criteria, run a weekly forecast review with sales managers. Improvement from 70% accuracy to 85% can change the company's cash management.

2. Pipeline-stage clean-up. Standardize stage definitions and exit criteria. Force reps to fill in close-date, deal-amount, and required fields. Surfaces dead pipeline (typically 15-30%).

3. Dashboard standardization. Replace 50 different dashboards with 5-10 standard ones used consistently. Builds shared truth.

4. Lead-routing rebuild. Often a top-3 frustration. Map current rules, find broken cases, rebuild with clear logic.

5. CRM hygiene blitz. Targeted fix on top-3 broken fields. Often unlocks other capabilities.

6. Forecast call cadence. Weekly pipeline review with sales managers, not just exec-level. Forces rep accountability.

Quick wins to avoid in first 90 days

• Comp-plan rewrite (use sales-comp-redesign-coach later).
• Territory redesign (high-stakes; need rep relationships first).
• New tool selection / procurement (typically 3-6 months process).
• Attribution model rebuild (multi-quarter project).
• Org redesign of RevOps team (need to know team first).

What to communicate

• Top 3-5 quick wins with target dates (typically week 8-12).
• Longer-term roadmap items with target quarters.
• Trade-offs ("we'll defer X until Q2 to focus on Y").
• Cross-functional implications.

Step 4: 6-month deeper plays

After quick wins are landing, take on deeper structural projects.

Common 6-month projects

1. Territory + quota design. Often biggest unlock. Use icp-redefinition-coach + sales-comp-redesign-coach as inputs. Annual cycle.

2. Attribution model. Multi-touch with proper data infrastructure. Often involves marketing-ops collaboration. 1-2 quarter project.

3. Comp-plan modernization. Particularly when previous comp wasn't aligned to current strategy. Heavy stakeholder-management.

4. AI-revenue tooling rollout. Conversation intelligence (Gong/Chorus), AI-driven forecast (Clari), opportunity scoring. Vendor selection + integration + adoption playbook.

5. Workflow automation. Sales rep manual tasks → automated. Quote generation, contract drafting, customer-handoff workflows.

6. Deal-desk operationalization. Standard pricing, discount approvals, contract templates, escalation matrix.

7. Data warehouse build. Centralize CRM + marketing-automation + product-usage + financial data into a single source of truth.

Sequencing logic

• Pick 1-2 deeper plays per 6 months.
• Always have at least one quick-win in flight to maintain credibility.
• Sequence: forecasting + pipeline first (impact in the current year), then territory + comp (annual cycle), then attribution + AI tooling (longer-term).

Step 5: Awkward overlap with sales managers

The hardest organizational question.

The line

• RevOps recommends; Sales Management decides — for most operational decisions.
• RevOps owns the system; Sales Management owns the people.
• RevOps designs the process; Sales Management enforces it.

Where it breaks

• Pipeline hygiene. RevOps says reps must fill in fields; sales managers don't enforce. Outcome: data is bad. Fix: management enforcement is a manager responsibility; RevOps provides the visibility.
• Forecasting discipline. RevOps wants stage-based commit; sales managers prefer gut-feel. Fix: hybrid; RevOps provides AI-driven forecast as input; sales managers commit; both roll up.
• Comp dispute. Rep disputes comp calculation; manager pushes RevOps. Fix: clear escalation matrix.
• Reporting accuracy. RevOps shows pipeline as $X; sales says $Y. Fix: single source of truth, agreed by both, defended.

How to handle

• 1:1 with each first-line sales manager early. Build personal relationship.
• Be a partner, not a police force. "I'm here to help your team; here's how I can support."
• Have the CRO clearly back you on policy decisions. Without CRO support, manager resistance wins.
• Don't escalate small fights; pick big-leverage ones.

Failure modes

1. Becoming an automation help desk

Symptom: 80% of RevOps team time on tickets (Salesforce form requests, dashboard requests, integration fixes). Strategic work doesn't ship. Fix: tier the work. Tier 1 (helpdesk): RevOps Specialists / vendor; tier 2 (build / integrations): RevOps Engineers; tier 3 (strategy): RevOps Leadership. Establish SLA for tickets so they don't dominate.

2. Trapped in dashboards

Symptom: building lots of dashboards; few are used; data quality concerns drown change momentum. Fix: ruthless dashboard reduction; pair every dashboard with a named decision-maker / use case; kill orphan dashboards.

3. Reporting up without driving change

Symptom: monthly reports go to exec team; nothing changes based on the reports. Fix: every report ends with 1-3 specific recommended actions; track follow-through.

4. Tool-stack expansion without consolidation

Symptom: every new request adds a new tool; tool count balloons; integration overhead destroys productivity. Fix: every new tool requires retiring something; total tool count is a managed budget.

5. CRO-dependence

Symptom: every decision requires CRO approval; RevOps is glorified executor. Fix: build credibility with quick wins; earn decision rights through demonstrated judgment.

6. Reporting line politics

Symptom: shadow conflicts between CRO / CFO / CEO over RevOps direction; RevOps caught in the middle. Fix: explicit conversation about reporting line and decision rights; align with primary stakeholder; don't try to please all sides.

7. Vendor-relationship mistakes

Symptom: tool decisions driven by vendor relationships rather than business need. Fix: structured vendor evaluation (POC, references, integration test); RFP process for >$50K decisions.

8. Scope creep into people / strategy

Symptom: RevOps drifts into managing reps, designing comp without authority, advising on hiring. Fix: stay in the operational lane; let people-management belong to sales managers; advise rather than direct.

Common roles on a mature RevOps team

• VP / Head of RevOps: strategy + cross-functional leadership.
• Director, Sales Ops: sales-specific operations; territory, comp, forecasting.
• Director, Marketing Ops: marketing automation, attribution, lead lifecycle.
• Director, CS Ops: customer success platform, health scores, expansion ops.
• Senior Analyst, Revenue Analytics: SQL / BI / forecasting models.
• Salesforce Admin / Architect: CRM customization, integrations, governance.
• RevOps Engineer: automation, scripting, data pipelines.
• Deal Desk Manager: pricing, contract operations, RFP support.

Team size scales roughly: $10M ARR → 1-2; $50M → 4-6; $100M+ → 10-20.

First-90-days checklist

Week 1

• Meet CRO (multiple times), build personal relationship.
• Inventory all current direct reports.
• Get system access to all major tools.
• Read all major existing documentation.

Week 2-3

• Stakeholder interviews complete.
• Tech-stack audit complete.
• Data audit complete.

Week 4

• Synthesize findings.
• Draft 90-day priority list with CRO buy-in.
• Communicate priorities to broader team.

Week 5-8

• Execute on quick wins.
• Establish weekly cadence with sales managers.
• Start evaluation of any major tooling decisions.

Week 9-12

• Show measurable progress on quick wins.
• Plan deeper 6-month projects.
• Establish operating cadence (weekly / monthly / quarterly review structure).

Natural exit ramps

RevOps is a high-leverage role with several promotion paths:

• Chief Revenue Officer: common path; RevOps leaders move to CRO at smaller companies.
• COO: broader operational role.
• VP Strategy / Strategic Finance: if data-led archetype.
• Founder / consultant: RevOps consultancies are a real career.
• CRO at a similar-sized company: lateral move with CRO title.

Plan exit ramp from year 2; otherwise role tends to plateau as the operational center.

Anti-patterns

• Acting before listening. First-30-day major changes destroy stakeholder trust.
• No cross-functional relationships. RevOps reporting to CRO with weak Marketing / CS ties is missing 50% of the role.
• Tool-first thinking. Buying tools before understanding the underlying process problem.
• Dashboard fetishism. Building dashboards for the sake of comprehensiveness.
• Avoiding the comp / territory work. It's where the real impact is; many leaders defer indefinitely.
• Hiring before clarifying scope. Adding RevOps headcount when role isn't yet clear amplifies confusion.
• Trying to win every fight with sales managers. Pick high-leverage battles; partner on the rest.

Workflow

For a new RevOps leader:

1. Week 1: Disambiguate the role with CRO. Get system access. Meet team.
2. Weeks 2-3: Listening tour. Tech audit. Data audit.
3. Week 4: Synthesize. Draft priorities. CRO alignment.
4. Weeks 5-12: Execute quick wins. Establish cadence. Build relationships.
5. Months 4-6: Begin deeper structural projects. Maintain quick-win flow.
6. Year 2: Major restructural projects (territory, comp, attribution).
7. Year 3+: Strategic role; consider exit ramps.

Integration with other coaches

• chief-of-staff-onboarding-coach: parallel role-ambiguity coaching.
• sales-comp-redesign-coach: RevOps owns or co-owns comp redesign.
• icp-redefinition-coach: RevOps provides data; sales-marketing co-leads.
• nrr-recovery-coach: RevOps provides cohort data and reporting.
• enterprise-sales-coach: RevOps supports enterprise-deal-desk operations.
• competitive-intelligence-coach: RevOps often hosts CI infrastructure.
• board-meeting-prep-coach: RevOps generates revenue dashboards for board.

RevOps is one of the highest-leverage senior roles in modern B2B SaaS. The first 90 days set the trajectory; spend the time to listen before acting.