If it is not on the charter, it is not in the quarter.

Diagnosis is not commitment. A referee, a seam, a dictionary, and a tool freeze are raw material. They become an operating system only when a sponsor can repeat, in one breath, who is accountable, which three things move, and what the company will stop.

That is a ninety-day mandate. It is not a program office, a six-month roadmap, or a requisition you hide behind.

You need a named sponsor, a reporting line for the referee, a charter signed or dated this week, and one shared revenue goal — one sentence all three functions ladder to, not fourteen KPIs. Missing any of those is a reason not to launch.

Days 1–30 diagnose: enough of a path map to find leaks, a data snapshot against the draft dictionary, the stack inventory, the top five leaks, baselines for the few numbers you will live with.

Days 31–60 stabilize: freeze the dictionary with Finance on the page, run the one handoff SLA, inspect pipeline weekly inside the system of record, and put one executive view in the room.

Days 61–90 institutionalize: a cadence, change control for definitions, one strategic output the sponsor can use — coverage, capacity, or forecast reliability — and a keep, kill, or hire decision at day 90, not at day 5.

This is not automatically a new department. An early company needs one senior generalist or a fractional lead plus the charter. A scaling company needs a head of RevOps and one or two specialists already in the building. A complex company needs a central referee with embedded ops — still one dictionary.

Do not open a requisition to avoid naming the person who already sits closest to the work. Do not dump the hat on a CRM admin and call it strategy. Name an interim or do not start the clock.

Five decisions: sponsor, reporting line, three workstreams, who does the work, and two or three habits that die. Extra dashboards. Vanity MQL targets. Forecasts in a spreadsheet. Tool buys without review.

If a decision will not land, write the blocker. Do not invent a sixth workstream to hide it. If everything is RevOps, nothing is.

Put day 30, 60, and 90 on the sponsor’s calendar before anyone leaves the room. A mandate without those three meetings is a memo. Parallel old dashboards during transition are how day 90 looks like day 0.