RevOps Manager onboarding plan
RevOps sits between sales, marketing and customer success, and inherits their data problems. Onboarding should map definitions and the CRM setup before any tool changes.
What good onboarding achieves
Own the revenue data model, funnel definitions and reporting so sales, marketing and CS work from the same numbers.
Week one example
- Day 1: CRM admin access; meet sales, marketing and CS leads.
- Day 2: CRM data model: objects, fields, stages and automations.
- Day 3: Funnel and metric definitions currently in use.
- Day 4: Tool stack and integrations around the CRM.
- Day 5: Known reporting pain points from each team.
30/60/90 progression
- Day 30: Has documented the data model and agreed funnel definitions.
- Day 60: Owns revenue reporting and the forecast process mechanics.
- Day 90: Has fixed one high-impact data or process issue.
People to meet (examples)
- Head of sales
- Marketing lead
- CS lead
- Finance contact
Systems to learn (examples)
- CRM (admin level)
- Marketing automation
- Customer success tool
- BI or reporting tool
Manager checkpoints
- Week 1: pain points summary
- Day 30: definitions agreed
- Day 60: reporting ownership
- Day 90: fix delivered
Common mistakes
- Changing CRM setup before documenting it
- No agreed definitions across teams
- Admin access granted with no change process
- Serving one team's needs only
Checklist
- CRM admin access
- Data model documented
- Definitions reviewed
- Integrations mapped
- Team pain points collected
- Change process agreed
- Reporting handed over
- Priorities agreed