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

It's Monday at 9:14am. Your laptop is provisioned, your Slack handle is wrong, and someone has already added you to a calendar invite called "Q2 Renewals Sync (URGENT)" that starts in 11 minutes.

Welcome to your new Ops job.

You will inherit, on average, 14 vendor contracts you've never seen, 47 SOPs in a Notion graveyard half of which point to dead Confluence pages, a runbook last touched in 2023, and a recurring 8am Tuesday meeting whose original purpose nobody can explain. The honest first question isn't "what should I do?" It's "what should I ignore long enough to figure out what matters?"

This is the plan I wish I'd had the first time I walked into a B2B SaaS ops role with no playbook. It assumes you're a mid-senior IC reporting to a VP, you have no team yet, and you have 90 days before someone expects a real opinion.

Why 30/60/90 Beats "Hit the Ground Running"

The first auto-renewal lands in week 6. The first "this report is wrong" Slack panic hits at 4pm on a Friday in week 3. By week 8 you'll have been pulled into a politics-laden SOP rewrite that was someone else's failed project last year.

If you don't have a structure, you'll spend 90 days reacting to whichever fire is loudest. You'll close a few tickets, your VP will be vaguely pleased, and at day 91 you'll realize you have no point of view on anything.

A 30/60/90 plan does one thing: it gives you permission to not fix things in week 2. Audit before act. The new Ops hire who rearranges the furniture in week 2 loses credibility for six months. The one who shows up in week 12 with a ranked list of dead vendors and a named owner for every recurring process becomes indispensable.

Days 1–30: Audit, Don't Act

The temptation in your first month is to ship something visible. Resist it. Your job for 30 days is to build a map of the territory. Four things go on the wall.

1. Pull every vendor contract

Open a spreadsheet. You will live in this spreadsheet for two years, so name it well. The columns that matter:

Most SaaS ops folks I know find that by week 4, the gap between "active seats" and "licensed seats" alone covers 6 to 12 months of their salary in waste. That's not a brag. That's how loose most stacks are.

If finance owns the contract repository, get a read-only invite. If nobody owns it (likely), you just inherited the job of building one. Don't announce this. Just build it.

2. Map process owners

Pick the 15 to 20 recurring processes that touch revenue, customers, or money. Lead routing. Billing reconciliation. QBR prep. Onboarding handoff. Renewal forecasting. Support escalation. The CS-to-billing handoff for usage overages.

For each one, ask three people: "who actually owns this end to end?"

Half the answers will be "nobody." A quarter will be "I think Sarah?", and Sarah will tell you she does part of it. The remaining quarter will have a real owner, and that owner will be either drowning or about to leave.

This is your second deliverable. Don't fix anything yet. Just write down what you found.

3. Sit in five cross-functional meetings as a fly on the wall

Tell people you're listening, not contributing. Pick five:

1. The RevOps standup: to see how lead, opp, and pipeline data actually flow
2. The CS handoff meeting: to see what breaks when sales hands a customer over
3. The finance close: to see which manual processes still hold the books together
4. A support escalation review: to see what customers are actually angry about
5. The leadership sync: to see which metrics your VP and the CEO actually argue about

Take notes by hand. People say more in front of someone who isn't typing. The goal is to overhear what's broken, not to be told what's broken. Every team will tell you their official version of reality. The meetings will tell you the rest.

4. Identify the top 3 broken processes

By the end of week 4 you should have a ranked list. The criteria isn't "what's in the org chart." It's "what do people complain about in Slack at 6pm on Thursday."

Rank by three things: how often it breaks, how much money or trust it costs when it breaks, and how unowned it is. The unowned ones are the highest-leverage fixes, because nobody is defending the status quo.

Don't share the list yet. You'll want it for day 90.

Days 31–60: One Kill, One Fix, One Map

Month two is when you stop being the new person and start being the Ops person. You're allowed to ship, but only three things, and each one earns you a different kind of credibility.

Kill 1 dead vendor

Pick the most obviously dead tool from your audit. The criteria for "obviously dead":

• Active seat count is under 20% of licensed
• Last login by anyone was more than 90 days ago
• The original champion left the company 6+ months ago
• The renewal is more than 60 days out (so you have time to cancel cleanly)

Don't pick the politically charged one. Don't pick the one your VP's predecessor signed personally. Pick the boring obvious one and kill it. Send a 4-line email to the vendor's account manager, copy your finance partner, archive the contract.

The first time I ran a vendor audit I found a project management tool that had auto-renewed twice after its champion left the company. It was costing about $38,000 a year. The cancellation took eleven minutes. The credibility from that single move bought me six months of room to do harder things.

Fix 1 broken SOP end-to-end

Pick the one with the loudest pain, the one people genuinely complain about. Not the most strategic one. Not the prettiest one. The painful one.

Document it from start to finish. Walk it once with the people who actually do the work, not the people who designed it. Map every handoff, every tool, every place where information falls through a crack. Then write the new version: short, executable, with one named owner.

Get the owner to sign off in writing. A two-line Slack message ("yes, I own this, here's the doc") is enough. The signoff is what makes it real.

Don't try to fix two. Two is how you end up shipping nothing in month two.

Propose a process owner map to your VP

Take the process map from month one and turn it into a one-page document. Every recurring process has exactly one name next to it. For the unowned ones, propose an owner: someone whose existing job is closest, or someone who's already doing 60% of it informally.

Bring it to your VP. Don't ask permission to fix everything. Ask permission to fix the top three, with named owners, and a 90-day timeline.

Your VP probably hasn't seen the full map before. Most VPs of Ops inherit pieces and never get a complete picture. You're handing them one.

Days 61–90: Own a Metric, Present the Plan

By day 60 you've built a map, killed one thing, fixed one thing, and proposed a structure. Month three is where you bind your name to a number.

Own one process metric publicly

Pick one. Just one. Some examples that work:

• Onboarding time-to-value: days from contract signed to customer reaching their first measurable outcome
• Contract renewal lead time: days between renewal alert firing and renewal decision made
• CS-to-billing handoff SLA: hours between a CS escalation and finance acknowledging it
• Vendor stack utilization: percentage of licensed seats actually active in the last 30 days

Whichever you pick, post the current number publicly. Slack channel, dashboard, weekly digest, somewhere visible. Then post it again next week. And the week after.

The goal isn't to hit a target. The goal is to be the person whose name appears next to a number. That's how Ops people become trusted: the metric is yours, the trend is yours, and when it moves, you have an opinion about why.

Present a 90-day report

Build a short deck or doc. Five sections:

1. What I found: the audit results, in numbers (X vendors, $Y total spend, Z% utilization)
2. What I killed: the dead vendor, the dollars saved, the time it took
3. What I fixed: the SOP, who owns it now, evidence it's working
4. What's still broken: your top 3 list, ranked, with rough cost estimates
5. What I'd do next: your H2 proposal

Keep it under 10 slides or 1,500 words. This is the document your VP will forward to their boss. Make it forwardable.

Propose an H2 ops plan

Three to five initiatives. Each one has:

• A name
• An owner (you or someone you've nominated and they've agreed)
• A deadline
• An expected impact in dollars saved or hours returned

That last column is non-negotiable. "Improve vendor governance" is not an initiative. "Reduce vendor stack waste from $310k/year to $180k/year by Q4" is. The dollar figure can be approximate. Vague is the killer, not imprecise.

Bring the H2 plan to your VP at day 88. Day 90 is the formal presentation. Day 91 is when the work starts.

A Decision Framework: Kill / Fix / Leave Alone

You'll hit dozens of small decisions in your first 90 days about which fights to pick. Use this.

Kill the things that are obviously dead, cheap to remove, and have no defender. Fix the things with one clear owner where the pain is acute and the rewrite is small. Leave alone, for now, the political SOP, the report your CEO personally built, the vendor contract that's three weeks from renewal. Those are month four problems.

Real-World Landmines

Five things that will happen, in roughly this order:

1. An auto-renewal fires while you're still onboarding. A $42k contract renews in week 5 because the notice window closed in week 3. Lesson: pull renewal dates on day 2, not week 4.
2. The 4pm Friday "this report is wrong" Slack panic. Someone in leadership will spot a number that doesn't match another number. You don't own either report. You will be tagged anyway. The right move: acknowledge, ask which definition they want as canon, fix it Monday. Don't try to be a hero on Friday at 5pm.
3. The political SOP nobody will let you touch. Usually billing or pricing-related. Someone senior built it. Touching it requires their blessing. Park it. Bring it up at day 90 as part of H2.
4. The vendor whose champion left 8 months ago. They've auto-renewed twice. The renewal is in 11 days. You have to decide fast. Default to canceling unless someone steps up to defend it in writing.
5. The "can you also own X?" creep. By week 7 someone will try to hand you procurement, IT asset tracking, or all of HR ops. Politely decline anything that isn't on your VP's stated priority list. Your scope discipline in month two sets your scope for the year.

How to Tell If It's Working

By day 90, three things should be true:

• A renewal calendar exists, is shared, and someone other than you has looked at it.
• Every recurring process on your map has exactly one named owner who has acknowledged it.
• Your VP can describe your H2 priorities to their boss without asking you what they are.

If those three are true, you've done the job. The next 270 days are about execution, but the foundation is set. If any of them are still hand-wavy at day 90, that's the signal — go fix that one before you take on anything new.

Audit before you act. Kill one thing. Fix one thing. Own one number. Present the plan. The Ops Managers who do this become Directors of Operations within 18 months. The ones who skip the audit and start rearranging furniture in week 2 are still trying to recover political capital a year later.

Pick the slow path. It's faster.

Learn More

• Operations Manager Job Description
• Building Your Vendor Audit Process
• Process Owner Mapping for SaaS Ops
• Process Design and SOPs That Don't Rot
• Common Operations Manager Pitfalls