I handed my first RevOps hire a wishlist on her first day: fix the CRM, build a forecast model, clean up lead routing, get territories sorted before the board meeting. Three weeks later almost none of it was done, she was exhausted, and I couldn't tell you what had actually improved. The problem wasn't her. It was that I'd never decided what "first" meant.
Founders spend weeks agonizing over whether to make this hire and almost none deciding what the person does once they start. That gap is where the hire either pays for itself fast or quietly stalls for a quarter.
Week 1: audit before you let them fix anything
The instinct is to point a new RevOps hire at the loudest complaint in the building. Resist it. The first week should produce a map, not a fix, because most founders are wrong about which system is actually broken versus which one is just annoying.
Have them audit four things before touching a single workflow: where leads currently get stuck between marketing and a rep touching them, how forecast numbers actually get built today (spreadsheet, gut feel, or CRM report, and how far off the last three forecasts were), what data lives in the CRM that nobody trusts enough to use, and how long it takes a new rep to become productive with the tools and process as they exist right now. This is a week of interviews and screen-shares with your reps, not dashboards. The answers almost always surprise the founder.
In my case, I assumed the CRM was the problem. The audit showed the CRM was fine; the problem was that leads sat in a shared inbox for two to four days before anyone claimed them. I would have spent the first month rebuilding the wrong system.
Week 2: fix the one thing that's bleeding deals right now
After the audit, you'll have three or four candidates for "the real problem." Pick exactly one for week two, the one closest to revenue leaking out today, not the one that's most annoying to look at. A messy CRM field structure is annoying. A four-day lead response time is a leak. Fix the leak first.
This week should end with something a rep or the founder can feel within days: leads routed automatically instead of sitting in an inbox, a single source of truth for pipeline instead of three competing spreadsheets, or a forecast built from actual stage-by-stage conversion instead of a gut number. Pick something measurable. If you can't point to a number that should move because of this week's work, it wasn't specific enough.
Weeks 3-4: build the system, not just the patch
The fix from week two will hold for a few weeks and then quietly break again unless it's turned into a system with an owner. Weeks three and four are for documentation and habit-forming, not new fires: a written playbook for the process just fixed, a recurring cadence (weekly pipeline review, monthly data-hygiene pass) that keeps it from decaying, and a dashboard that answers the three questions you as founder actually ask every week instead of the twelve metrics a generic template suggests.
This is also the point to resist scope creep from the rest of the team. Every function in the company will discover, within a month, that there's now someone who can fix their reporting problem too. Protect weeks three and four for finishing the first fix properly instead of starting five half-finished ones.
The scorecard that tells you it's working
At day 30, you should be able to answer four questions with a number, not a feeling: how long does a lead now sit before someone owns it (should be dropping, ideally to hours), how far off was the most recent forecast versus what actually closed (should be tighter than the last one before the hire started), how much of the CRM data does the sales team now actually trust enough to use without double-checking it, and can you name the one system that's now documented well enough that it survives the RevOps hire taking a week of vacation.
If you can't answer at least three of those with a real number, the first 30 days went to busywork instead of the leak that was actually costing you deals. That's a signal to reset scope with your new hire, not to wait another quarter and hope it compounds on its own.
The hire you just made is expensive enough that the first month shouldn't be spent finding out what to work on. Decide that before their start date, run the audit fast, fix the one leak that's actually costing you revenue, and turn it into a system before you let anyone hand them a second project.