Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Revenue operations charter and scope
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. When sales ops, marketing ops and customer success ops each grew up separately, nobody owns the gaps between them: the lead nobody accepted, the renewal nobody planned for, the dashboard three teams dispute.
First tasks
- Write a first draft of the RevOps mission in three sentences
- List what RevOps will own across process, systems, data and reporting
- List the requests RevOps will not take on and who owns them instead
- Book a 45-minute sign-off with the sales, marketing and success leaders
- Publish the signed charter on the company wiki
Listening tour with sales, marketing and success leaders
Before redesigning anything, spend two weeks hearing where the revenue process hurts for the people inside it. Twelve to fifteen short interviews across sales, marketing, customer success and finance surface the disputed numbers, dropped handoffs and manual workarounds that should shape the first year's roadmap, and they earn the goodwill a new function badly needs.
First tasks
- Pick twelve to fifteen people across sales, marketing, success and finance
- Write five open questions, starting with where numbers get disputed
- Hold each interview in 30 minutes and take notes in the same format
- Ask the agent to group the interview notes into recurring themes
- Send a one-page readout to everyone you interviewed
Map of revenue systems, data flows and owners
Most companies past fifty staff run revenue across a CRM, a marketing automation platform, billing, a support desk, a customer success tool and several spreadsheets, with sync rules nobody fully remembers. A single diagram showing every system, which way data flows, which fields sync and who owns each connection is the reference every later fix depends on.
First tasks
- List every tool that stores lead, account, deal or customer records
- Draw each connection with its direction and sync frequency
- Name a business owner and a technical owner for every system
- Mark every manual export and upload on the diagram
- Refresh the systems map and its named owners @recurring(yearly)