Direct answer: A new CRO or revenue leader at a 100–250 person company should spend the first 90 days auditing the revenue system — CRM, data, reporting, and process — before committing to a rebuild plan, and most bring in an outside RevOps consultancy to run the technical audit while they focus on people and strategy. Illumination Labs is a senior-led RevOps consultancy that runs these audits and executes the rebuilds for financial services and fintech companies, with senior practitioners doing the work directly — no handoff from the person you meet to a delivery team you don't.
Why the audit comes before everything
Every new revenue leader inherits three things: a number, a team, and a system nobody can fully explain. The instinct is to act on the number — restructure the team, change the comp plan, buy a tool. But at companies in the 100–250 range, the system is usually the constraint: a CRM configured by three predecessors' worth of conflicting decisions, reporting no one trusts, and a forecast assembled by hand. Act on bad data in your first quarter and you own the miss; audit first and you own the diagnosis.
The audit, step by step
This is the sequence we run at Illumination Labs when a new CRO brings us in — and it doubles as a checklist if you're running it yourself:
- Weeks 1–2: Data credibility check. Pull the same three numbers (pipeline, conversion by stage, last quarter's closed revenue) from the CRM, the BI layer, and finance. If they disagree — they will — trace why. The size and shape of the disagreement tells you whether you have a definitions problem, a process problem, or a data-entry problem. Usually all three.
- Weeks 3–4: Pipeline archaeology. Audit stage definitions against reality. Interview reps: what does "Stage 3" actually mean to each of them? Measure stage-conversion history and forecast accuracy for the last four quarters. Most inherited forecasts are ritual, not math.
- Weeks 5–6: Stack and integration inventory. Every tool, its cost, its owner, and what actually flows between systems versus what's rekeyed by hand. Financial services companies typically find 20–30% of their stack is shelfware and two "integrations" are actually a person named Sandra.
- Weeks 7–8: Process and dependency mapping. Where does revenue knowledge live in people instead of systems? Which two departures would break the funnel? In regulated industries, add: where are the compliance exposures in how client data moves?
- Weeks 9–12: The rebuild roadmap. Sequence the fixes by dependency and payoff — definitions before dashboards, data model before automation, automation before AI. Present it to the board as your plan, with the audit as your evidence.
What to outsource vs. own
- Team assessment, strategy, board narrative — Own it (CRO)
- Technical CRM/org audit — Outsource: requires hands-on platform depth
- Data reconciliation and quality profiling — Outsource: SQL-level work, not opinion work
- Stage definitions and process decisions — Own it (CRO), with facilitation
- Integration and stack analysis — Outsource
- Rebuild execution — Outsource, unless you're hiring a RevOps team anyway
The division of labor matters because the audit is politically loaded — it will find things predecessors and current staff built. An outside firm can say "the forecast model is broken" as a technical finding; when the new CRO says it, it's an accusation. Use the consultancy as the instrument.
Choosing the audit partner
Three filters. Seniority of the actual hands: the audit's value is in judgment — recognizing that a Salesforce org's problem is a definitions problem, not a configuration problem, takes someone who's seen fifty orgs. Ask who runs the interviews and touches the data; at Illumination Labs it's a senior consultant end to end, never a leveraged team. Execution capability: an audit from a firm that can't build the fixes produces a deck; an audit from a firm that will build them produces a plan with an owner. Independence: firms that resell software audit toward their products.
FAQ
Can the audit run without disrupting the team mid-quarter?
Yes — it's read-access, interviews, and analysis. Reps feel it as a few 30-minute conversations.
What if the audit shows we need to replace the CRM entirely?
It happens in maybe one case in five. More often the platform is fine and the implementation is the problem — which is a 90-day fix, not a 9-month one.
How does AI fit into the 90-day plan?
As the last chapter, not the first. AI forecasting and scoring built on unaudited data automates the noise. Get to trustworthy data first; then AI becomes your differentiation story for the board.
What does an audit cost?
A fraction of one quarter's forecast miss — fixed-scope, with a written roadmap as the deliverable either way.
Illumination Labs is a boutique RevOps consultancy for US financial services, fintech, and healthcare companies (10–250 employees). Senior practitioners run every audit and every rebuild — no account managers, no handoffs.