RevOps audit checklist: what to check and how to prioritise fixes
A practical RevOps audit checklist covering people, processes, systems, and data. Collect evidence, prioritise findings, and assign the next action.
Haris Odobasic writes about revenue operations, go-to-market strategy, and the systems behind growth.

Haris is a revenue leader with experience driving growth and operational improvements at public and private technology companies. His work connects go-to-market strategy with the systems and processes needed to put it into practice.
At Revenue Wizards, his published writing covers AI and revenue operations, go-to-market engineering, team structure, and the choices companies face when building their revenue operations function.
A practical RevOps audit checklist covering people, processes, systems, and data. Collect evidence, prioritise findings, and assign the next action.
What revenue operations means for an AI-native company, why starting fresh is an advantage, and which foundations to put in place before automating.
A view towards 2027: as AI takes on more revenue work, RevOps needs to own the definitions, permissions and feedback that make that work useful.
If you already run RevOps work through your own agents in Claude, Five Dots does not replace that setup. It adds a method and a knowledge base drawn from more than 100 RevOps projects, and it keeps growing.
Eight problems that stall AI rollouts, from licences that change nothing to pilots stopped by security. Most come down to process, data and ownership, including where the company’s knowledge should live.
We planted 11 problems in a dummy company's sales pipeline and had Claude Opus 5.5 audit it 20 times, alone and with Five Dots. With Five Dots it found 94% of them, against 65%.
How to set up Claude as the revenue operations system of your company: strategy first, one neutral data store, a semantic layer, clean data, then automation, Slack and the CRM question.