Revenue Operations Setup

A RevOps charter, one glossary of lifecycle terms, a system of record for every metric, agreed handoffs and a monthly revenue council, so sales, marketing and success work from the same numbers.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Revenue Operations Setup, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

206

Starter tasks

💼 Sales & Revenue

Revenue Operations Setup

Aligning sales, marketing and customer success data, definitions and handoffs under one revenue operations function that owns process, systems and reporting.

  1. Revenue operations charter and scope
  2. Listening tour with sales, marketing and success leaders
  3. Map of revenue systems, data flows and owners
  4. Cross-team revenue data audit
  5. Shared glossary of revenue lifecycle terms
  6. Customer lifecycle stage model from lead to renewal
  7. System of record for each revenue metric
  8. Deciding where revenue operations reports
  9. Baseline revenue metrics pack
  10. RevOps request intake and prioritisation rules
  11. Weekly RevOps request triage
  12. Monthly revenue council with sales, marketing and success
  13. Monthly bookings and ARR reconciliation with finance
  14. Handoff service levels between revenue teams
  15. Monthly customer count match across systems
  16. Quarterly revenue metrics pack for leadership
  17. Change control for revenue definitions
  18. Quarterly RevOps roadmap planning
  19. Monthly churn and contraction reason review
  20. Annual go-to-market planning calendar
  21. Recurring revenue metrics fluency
  22. Funnel and bowtie conversion maths
  23. Revenue data modelling basics
  24. SQL for revenue reporting
  25. Revenue recognition basics for operations staff
  26. Change management for revenue process rollouts
  27. Lead acceptance and recycle agreement with marketing
  28. Sales to customer success handoff package
  29. Choosing an attribution model with marketing and finance
  30. Customer identity key across CRM, billing and support
  31. One revenue dashboard of record
  32. Warehouse or in-app reporting decision
  33. Deciding who owns renewals
  34. Retiring shadow revenue spreadsheets
  35. Customer health score inputs for the success team
  36. Launching revenue operations to the company
  37. Board meeting revenue metrics section
  38. Lifecycle stage model go-live
  39. New fiscal year revenue systems rollover
  40. Cross-team readiness for a pricing change
  41. ARR bridge for a fundraise or audit
  42. Hiring the first revenue operations analyst
  43. Revenue operations as a sales manager's side duty
  44. Merging sales, marketing and success ops teams
  45. Aligning revenue definitions after an acquisition
  46. Multi-region revenue operations rules
  47. Revenue data stewardship council
  48. Cohort net revenue retention analysis
  49. Usage-based revenue data model
  50. Partner-sourced revenue tracking

Where it starts.

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)

Make it yours.

Install Revenue Operations Setup, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.