Your First 30/60/90 Days as a New MOps Manager

Day one. You log into Marketo and the dashboard says 847 active lists, 312 smart campaigns, and a "Master Suppression List" last updated 14 months ago. You scroll to the sync queue and there are 2,400 records stuck in a failed-sync state going back to last September. Your new CMO wants a "marketing attribution dashboard by Q3." Your director of demand gen wants a leads-by-source report by Friday. Sales ops just slacked you about a routing rule that's been sending all enterprise leads to a rep who left the company in February.

This guide is what to do instead of panicking.

Why the First 90 Days Are Different for MOps

In most ops roles, the first 90 days are about learning the team, the goals, and the metrics. In Marketing Ops, you're inheriting a tech stack that's been duct-taped together by two or three predecessors, each of whom solved a different fire and left their fix in production. There's no documentation, the Confluence page is a year out of date, and the person who actually understood the lead scoring model left in 2024.

Most MOps hires fail in the first 90 days for one reason: they try to redesign the lead flow in week two. They walk in, see the chaos, propose a CDP migration, and lose all credibility before they've shipped a single fix. The new MOps Manager who proposes a CDP migration in month two gets ignored. The one who quietly deletes 400 stale lists and shows the CMO a $14K/year API cost reduction gets handed the H2 roadmap.

The job in your first 90 days is not to fix the system. It's to document what you inherited, ship three visible cleanup wins, and earn the right to propose strategy. Here's how the timeline breaks down.

Days 1-30: Audit Everything, Change Nothing

This is the hardest part of the plan because you'll be itching to fix things. Don't. Your only output for the first month is a documented audit. If anyone asks why you haven't shipped anything, the answer is: "I'm five weeks out from being able to make changes I won't have to undo. I'd rather be slow once than fast and wrong."

Here's the actual audit checklist.

MAP audit

Open your marketing automation platform (Marketo, HubSpot, Pardot, whatever you inherited) and document five things:

Active smart lists vs. orphaned lists. Pull a count. The first instance I inherited had 1,140 active smart lists, of which only 312 were referenced by any active program or campaign. The rest were orphans built for one-off campaigns three years ago.
Active programs. How many are firing this quarter? How many are paused? How many are "active" but haven't sent in 12+ months?
Sync errors in the last 30 days. Marketo, HubSpot, and Pardot all log sync failures. Pull the count. If it's over 100, you have a real problem.
API call usage vs. limit. Most B2B SaaS companies are at 60-85% of their daily API allocation and don't know it. If you're at 90%+, that's a budget conversation, not a tech problem.
Webhook health. Every webhook firing today, with last-success timestamp.

CRM sync health

Run these queries in Salesforce (or HubSpot CRM, or whatever you're synced to):

Failed syncs in the last 30 days, by error type, not just count
Duplicate rate per record type (leads, contacts, accounts). The benchmark is under 3% for healthy instances; most B2B SaaS companies are at 8-12% on the lead object.
Field mismatches, fields that exist on the CRM side but aren't mapped, and vice versa. These are how silent data loss happens.
Records with sync paused. Most teams have hundreds of records flagged "do not sync" and nobody remembers why.

Form library inventory

Pull every active form in your MAP. For each one:

Is it referenced by an active campaign or landing page?
Does it have hidden field population working (UTM, lead source, original referrer)?
When was it last submitted?

Most form libraries have 40-60% orphans. The first instance I audited had 287 active forms; only 94 had been submitted in the last six months.

List hygiene snapshot

Document your sender reputation baseline:

Engaged vs. unengaged ratio (opened or clicked in last 90 days)
Hard bounce rate in the last six months
Role-based email count (info@, sales@, support@). These tank deliverability.
Suppression list health. Is it being used by every send program, or just some?

Routing rule documentation

This is the single highest-leverage thing you'll do in month one. Open LeanData (or Chili Piper, or your native CRM rules) and draw the actual flowchart, not the one in Confluence. They will not match. Walk the flow on paper:

What fires first when a lead comes in?
What conditions trigger which assignment?
What happens when a routing condition fails?
Where do unassigned leads go to die?

Then book 20 minutes with the SDR manager and walk them through your version. They'll correct three or four things you got wrong because they live with the flow daily. Now you have the real flowchart.

By day 30, you have a 12-page audit doc. Don't share it yet. You're going to use it to pick your first three wins.

Days 31-60: Three Visible Wins

Now you ship. The goal is three cleanup wins with measurable before/after numbers. Not strategy. Not redesign. Cleanup.

Win 1: Kill one dead nurture

Find the nurture program with the worst engagement metrics. Every B2B SaaS instance I've inherited has at least one. It's the one with 0.4% click-through rate that's been running for 18 months because nobody wanted to be the person who turned it off. Pull the numbers:

Active recipients on the program
Email volume per month
Click-through rate, reply rate, unsubscribe rate
Unsubscribes attributed to this program in the last six months

Walk it to your manager with the numbers and one sentence: "I'd like to pause this for 60 days and measure pipeline impact. If pipeline is unchanged, we kill it permanently. The deliverability lift alone is worth running the test." You'll get yes 95% of the time. When you turn it off and unsubscribes drop 12% the next week, you have your first proof point.

Win 2: Fix one routing rule

You documented the routing flow in month one. You found at least one rule that's broken. Maybe it's the round-robin that's been sending all enterprise leads to the rep who left in February. Maybe it's the geo rule that's routing UK leads to the US queue. Maybe it's the SLA escalation that's been escalating to a manager's old email address.

Pick the one that's hurting pipeline most visibly and fix it. Document the before state, ship the fix, measure for two weeks, and write a one-paragraph summary: "Before this fix, 23 enterprise leads in Q1 were assigned to a rep no longer at the company. Median time-to-first-touch on enterprise was 41 hours. After the fix, median is 6.2 hours and assignment is verified daily."

That paragraph is gold. Save it. You'll use it in your 90-day report.

Win 3: Deduplicate one segment

Pick one segment (usually MQLs from the last 90 days) and run a real dedupe pass. Match on email domain plus name, then on email plus company, then on phone plus company. Most B2B SaaS instances have 8-15% phantom MQLs in any given quarter. The first instance I cleaned up had 2,847 MQLs in the last 90 days; 312 of them were duplicates of leads that already existed as contacts under a parent account. That's an 11% phantom rate.

Document the before count, document the after count, document what it means for the funnel math. If your team has been reporting MQL→SQL conversion of 22% and 11% of MQLs were phantoms, your real conversion was 19.6%. That's not a bad headline. That's the truth, and it changes how you forecast.

By day 60, you have three shipped wins, each with before/after numbers. Now you've earned the right to propose something bigger.

Days 61-90: Own a Metric, Earn the Roadmap

The last 30 days are about positioning yourself as the person who owns a number, presents the truth, and proposes a plan. Three deliverables.

Own one data hygiene metric publicly

Pick one and put it in your weekly update, every week, forever:

Duplicates per 1,000 records (target: under 30)
Sync failure rate (target: under 1%)
% leads with valid UTM source (target: over 85%)
Active forms with broken hidden fields (target: 0)

Just one. Not four. One number you'll publish weekly, defend in QBRs, and own as the "MOps health" line item. The reason this works: most ops people own outcomes (pipeline, conversion). Hygiene metrics are leading indicators that nobody else is watching, and when you own the leading indicator, you become the person whose work prevents fires instead of fighting them.

Present the 90-day report

One page. Three sections.

What I found. Five bullets, each with a number. ("847 active smart lists, 740+ orphaned. 11% MQL duplicate rate. 312 enterprise leads routed to inactive reps in Q1.")
What I fixed. Three bullets, each with before/after numbers. ("Killed Nurture Program X, and unsubscribes dropped 12%. Fixed enterprise routing, so time-to-touch went 41hr to 6.2hr. Deduplicated MQL segment, removing 312 phantom records, so real MQL→SQL conversion is 19.6% not 22%.")
What it cost the business. Translate to dollars where you can. API cost reduction from killing the dead nurture, pipeline value of leads now reaching reps, hours of SDR time saved.

Send it to your CMO and the VP of Sales the same day. Do not soften the numbers. The audience for this doc is people who've been told the funnel is healthy and will be quietly relieved that someone finally measured it.

Propose the H2 plan

Three priorities. Not 12. Each tied to a revenue impact you can defend.

A good H2 proposal looks like: "1. Migrate the lead scoring model from rule-based to engagement-weighted. Current model passes ~60% of MQLs that don't match ICP, projected MQL→SQL lift of 8 points if we tighten. 2. Implement form-level UTM enforcement. Current state is 67% of inbound leads have valid UTM, target is 90%, and this is the only blocker to closed-won attribution by source. 3. Build the MOps health dashboard, with weekly publication of dupe rate, sync failures, and routing SLA, owned by MOps."

A bad H2 proposal looks like: "Migrate to a CDP." You don't have permission to propose that yet. You will in nine months, after another quarter of hygiene wins.

Common Pitfalls

A short list of mistakes I've watched smart MOps people make in their first 90 days.

Promising attribution dashboards in week 4. Attribution is a six-month build with cooperation from sales ops, finance, and engineering. If you commit to a dashboard before you understand the data state, you'll either ship something wrong or miss the deadline. Either way you lose credibility.

Touching the lead scoring model before you understand it. Lead scoring is the most political artifact in any B2B SaaS marketing org because it determines who gets paid. Don't touch it for 90 days. Just document how it works.

Going to the CMO with problems instead of fixes already shipped. "I found 740 orphan lists" is a complaint. "I deleted 740 orphan lists, the API budget is now 22% under cap, here's what we can spend that on" is a win. Same finding, different framing, completely different career trajectory.

Treating Confluence as truth. It isn't. Walk the flow with the SDR who lives in it. Talk to the demand gen manager who built the campaign. Ask the rep what actually happens when a lead comes in. The system is what people experience, not what's documented.

Templates and Scripts You'll Need

A few I recommend keeping in a "MOps essentials" doc from day one.

The "I'm not changing X yet, here's why" script. When the CMO asks you to redesign the lead flow in week two, the answer is: "I'd like to wait six weeks before changing the routing logic. My audit is showing two upstream issues that would make a routing redesign land badly. Let me document those, fix them, then redesign with clean data. Six weeks instead of two months saved by going slow."

The audit one-pager. Five sections, max one page each. MAP audit, CRM sync, form library, list hygiene, routing flow. Include numbers, not adjectives.

The exec one-pager. Used at day 90, then quarterly forever. Three sections: state of the system (with numbers), what shipped this quarter (with before/after), what's next (with revenue impact).

The H2 roadmap proposal. Three priorities. Each one paragraph. Each paragraph ends with the metric that will move and the dollar value of that movement.

Measuring Success

You've executed this plan well if, at day 90:

You can draw the lead flow on a whiteboard from memory.
You've shipped three cleanup wins, each with before/after numbers a CFO would accept.
Sales leadership knows your name for a good reason. Specifically, the SDR manager has stopped slacking you about broken routing because you fixed the worst rule and documented the rest.
You own a public hygiene metric and it's in the weekly leadership update.
The CMO has read your 90-day report and asked you to expand the H2 proposal.

If three of those five are true, you're doing fine. If all five are true, you're on the path to senior MOps manager in 12-18 months.

The MOps job is not glamorous. It's pipes, plumbing, and patience. But the people who run the audit before they run the redesign are the ones who get to design the next system. The ones who skip the audit get fired in month nine when their CDP migration breaks the sync to Salesforce.

Be the first kind.

Marketing Ops Playbooks