30-60-90 day plan for revenue operations managers
On this page
- What does revenue operations own that sales operations does not?
- What does the 30-60-90 day plan look like?
- Why does the definitions document come first?
- Which compliance duties live in the revenue systems?
- Which numbers should a new RevOps manager baseline?
- What does "on track" look like at day 30, 60 and 90?
- A filled example
- How should the hiring manager use this plan in the final interview?
- What should the hiring manager ask at the check-ins?
- What the hiring manager owes a new RevOps manager
- Common mistakes
- Adapting the plan
- Questions people ask
A 30-60-90 day plan for a new revenue operations manager should map every revenue system, data flow and funnel definition in the first 30 days, get one set of definitions signed by marketing, sales, customer success and finance and fix the worst data leaks in days 31-60, and run the revenue reporting rhythm with a 12-month systems roadmap by day 90. RevOps owns the shared data model across the customer lifecycle, so it is also where opt-outs, text consent and privacy requests either reach every system or fall through. Those rules are summarized below with their sources, as of October 2026.
This page is for the CRO, CFO or head of sales or marketing hiring a revenue operations manager. If the role supports only the sales team, the 30-60-90 day plan for sales operations managers fits better; the 30-60-90 day plan for VPs of sales shows the forecast and capacity work RevOps will feed.
What does revenue operations own that sales operations does not?
| Area | Sales operations | Revenue operations |
|---|---|---|
| Scope | The sales team | Marketing, sales and customer success together |
| Definitions | Opportunity stages and forecast categories | The whole funnel, from first touch to renewal and expansion |
| Systems | CRM configuration for sales | CRM, marketing automation, billing, customer success tools and how they connect |
| Reporting | Pipeline and forecast | One revenue dashboard: acquisition, conversion, retention, expansion |
| Planning | Territories, quotas, commission administration | Inputs to company planning with finance, plus the systems roadmap and budget |
What does the 30-60-90 day plan look like?
30-60-90 day plan — [Name], Revenue Operations Manager, [company]
Reports to: [CRO / CFO / COO] Start date: [date]
Teams supported: marketing [N], sales [N], customer success [N]
Systems: CRM [name], marketing automation [name], billing [name],
customer success [name], BI [name]
Planning dates: [quarter close, annual planning]
DAYS 1-30 — Map the systems, the data and the definitions
Goals:
- One-to-one with the heads of marketing, sales, customer success
and finance, and with the admin of each system
- Draw the system map: every tool, owner, renewal date, seats in
use, and how data moves between tools
- Write down every funnel definition in use (lead, qualified lead,
opportunity, closed, churned, expansion) and where they conflict
- Trace [10] customers from first touch to renewal across systems
- Baseline data quality on open pipeline and active accounts
- Check how opt-outs, text consent and privacy requests move
between systems
Deliverables by day 30:
- System and data-flow map with renewal dates
- Definitions gap list and data-quality baseline
DAYS 31-60 — One set of definitions; fix the leaks
Goals:
- Agree one funnel definitions document with the heads of
marketing, sales, customer success and finance
- Fix the top data-quality issue at its source: required fields,
routing rules or an integration
- Close any gap in opt-out or deletion handling between systems
- Rebuild the core dashboard on the agreed definitions
- Set one intake process for system and report requests
Deliverables by day 60:
- Signed definitions document
- Dashboard leaders use in the weekly meeting
DAYS 61-90 — Run the revenue rhythm
Goals:
- Supply the inputs for the forecast call and the quarterly
business review
- Present a 12-month systems roadmap: renewals, consolidation,
integrations, budget
- Support planning with finance: capacity, territories, targets
Deliverables by day 90:
- Roadmap approved by the [CRO / CFO]
- The quarter's numbers reported on the agreed definitions
Check-ins: weekly with [manager]; day 30, 60 and 90 reviews.Why does the definitions document come first?
Most revenue arguments are definition arguments. Marketing counts a qualified lead when a score passes a threshold; sales counts it when a rep accepts it; finance counts revenue when it is billed. Until one document says what each stage means, who moves a record into it, and which system is the source of truth, every dashboard will be disputed. A definitions document can be short. The entries below are examples of the format, not recommended definitions.
| Stage (example only) | Definition (example only) | Who sets it | Source of truth |
|---|---|---|---|
| Qualified lead | Fits the target profile and asked for contact | Marketing automation rule, reviewed monthly | Marketing automation |
| Sales-accepted lead | A rep has reviewed it and agreed to work it | The rep, within an agreed response time | CRM |
| Opportunity | A meeting held and a defined buying need recorded | The rep, with manager review | CRM |
| Closed won | Contract signed | Deal desk or finance | CRM, reconciled to billing |
| Churned | Contract ended without renewal | Customer success, confirmed by finance | Billing |
Which compliance duties live in the revenue systems?
Legal sets the policy; RevOps makes every system follow it. The items below are checked against the official text as of October 2026. Which apply depends on the business; this is not legal advice.
| Duty | What the systems must do | Source |
|---|---|---|
| Email opt-outs | Honor a marketing email opt-out within 10 business days; the company stays responsible when another tool or vendor sends for it, so the suppression list has to reach every sending system | FTC CAN-SPAM guide |
| Text and call consent | Record prior express written consent before telemarketing calls or texts sent with an autodialer or prerecorded voice to wireless numbers, and keep the record with the contact | 47 CFR 64.1200(a)(2) |
| Privacy request timing (California) | Confirm receipt of a request to delete or know within 10 business days and respond within 45 calendar days, extendable once to 90 with notice | CCPA regulations, section 7021 |
| Deletion reaching vendors (California) | Delete from existing systems and notify service providers and contractors to delete what they collected under contract, and notify third parties the data was sold or shared with, unless that proves impossible or involves disproportionate effort | CCPA regulations, section 7022 |
| Opt-out of sale or sharing (California) | Stop selling or sharing as soon as feasibly possible and no later than 15 business days after the request | CCPA regulations, section 7026 |
The California rows apply only to businesses the CCPA covers. The practical test in month one is simple: submit an opt-out and a test deletion request through the public channels, then check every system on the map to see where the record still sits.
Which numbers should a new RevOps manager baseline?
| Area | Example measures (examples only) |
|---|---|
| Data quality | Open opportunities with a past close date or no next step; duplicate accounts; contacts with no owner |
| Funnel | Conversion between each agreed stage; time in stage |
| Pipeline | Coverage of next quarter's target; forecast against actual for recent quarters |
| Retention | Gross and net revenue retention, calculated the way finance calculates them |
| Systems | Tool spend, seats paid versus active, renewal dates in the next two quarters |
What does "on track" look like at day 30, 60 and 90?
| Checkpoint | On track | Worth a direct conversation |
|---|---|---|
| Day 30 | System map complete with renewal dates; definitions conflicts written down; opt-out and deletion paths tested | Has started building dashboards before the definitions are known |
| Day 60 | Definitions signed by all four leaders; one data-quality fix made at the source | Data cleaned by hand with no change to how it is entered |
| Day 90 | Leaders use one dashboard in the weekly meeting; roadmap approved | Each team still brings its own numbers; roadmap is a list of tool requests |
A filled example
RevOps manager: Aisha Rahman (invented), first revenue operations hire at a 250-person subscription software company, reporting to the CFO.
Day 30: The system map showed three tools that could send email, and only one received the unsubscribe list. Marketing, sales and finance used three different definitions of a new customer, so their monthly numbers never matched. A test deletion request reached the CRM but not the enrichment vendor.
Day 60: The suppression list now synced to all three sending tools, and counsel updated the deletion procedure to include the vendor. The four leaders signed a two-page definitions document. Close dates in the past became impossible to save on open opportunities.
Day 90: The weekly revenue meeting used one dashboard. The roadmap retired one of the three email tools at its renewal and moved its budget to a billing integration.
How should the hiring manager use this plan in the final interview?
Give finalists the same brief: a simplified system list, two conflicting funnel reports and one known problem. Score the plan with the rubric in how to evaluate a 30-60-90 day plan in an interview. Strong plans map before they build and get definitions signed before dashboards. Questions that test it:
- "Marketing and sales report different pipeline numbers for the same quarter. Where do you start?"
- "A customer asks us to delete their data. Walk me through every system you would check."
- "Three teams each want a new tool this quarter. How do you decide?"
- "How would you know whether a data-quality fix worked?"
What should the hiring manager ask at the check-ins?
- Day 30: Where do our systems disagree, and why? What did the opt-out and deletion tests show?
- Day 60: Have all four leaders signed the definitions? Which fix changed how data is entered?
- Day 90: Which meeting runs on your dashboard? What does the roadmap retire or renew?
What the hiring manager owes a new RevOps manager
- Admin access to every revenue system, and the contracts with their renewal dates.
- Time from the heads of marketing, sales, customer success and finance for the definitions.
- Authority to make fields required and change routing, within an agreed change process.
- A named contact in legal for opt-out, consent and privacy requests.
Common mistakes
- Building dashboards first. Numbers on disputed definitions get disputed faster.
- Cleaning data by hand. It looks better for a month and then decays; fix the entry point.
- Taking every request. Without an intake process, RevOps becomes a queue of one-off reports.
- Assuming tools share opt-outs. Each integration has to be checked; the rules apply to the company, not the tool.
Adapting the plan
- Product-led companies: add product usage data and the hand-raise from free to paid to the system map and the definitions.
- Heavy renewal business: weight the plan toward renewal forecasting with customer success; the 30-60-90 day plan for customer success managers shows what they track.
- Analyst-heavy team: the 30-60-90 day plan for data analysts and the plan for business analysts show the ramp for the people who will build the reports.
The general 30-60-90 day plan template for new hires covers the structure for any role.
Questions people ask
What should a revenue operations manager do in the first 30 days?
Meet the heads of marketing, sales, customer success and finance and the admins of each system, map every revenue tool with its owner, renewal date and data flows, write down every funnel stage definition in use and where they conflict, trace a sample of customers from first touch to renewal, and baseline data quality. Also check how opt-outs and privacy requests move between systems.
What is the difference between revenue operations and sales operations in a 30-60-90 day plan?
A sales operations manager supports the sales team: territories, quotas, commission administration, CRM hygiene for sales and the forecast call. A revenue operations manager owns the shared data model and systems across marketing, sales and customer success: one funnel definition, the integrations between CRM, marketing automation and billing, the dashboards leaders use and the systems roadmap.
Which compliance tasks does revenue operations handle?
Usually the system side: making sure an email opt-out reaches every sending tool in time for the FTC's 10-business-day rule under CAN-SPAM, that text consent is recorded before automated marketing texts, and, for businesses covered by California's CCPA, that deletion requests reach service providers and opt-outs of sale or sharing are applied within the regulation's time limits. Legal decides the policy; RevOps makes the systems follow it. This is not legal advice.
What should a RevOps manager deliver by day 90?
A funnel definitions document signed by the heads of marketing, sales, customer success and finance, a core dashboard built on it, the inputs for the forecast and quarterly business review, and a 12-month systems roadmap with renewals, consolidation and budget.