RevOps getting started

Use this before auditing fields, reviewing duplicates, or building a forecast.

Map objects and reports

Ask for the CRM in use, the objects that matter (accounts, contacts, leads, deals), a recent export of each, the field definitions, the current stage rules, the routing rules, and the reports the team reads every week. For each export record the date, object, filter, row count, and currency.

Ask who owns the CRM, who owns each report, and which reports go to the board or to finance. Note fields that no one can define and reports that no one reads.

Set the working rules

Agree who approves a merge, a deletion, a reassignment, a field change, a new stage rule, and a change to routing. Agree how missing values are shown in reports (blank, not guessed) and which date the forecast uses. Record who may call a deal commit and who signs off the forecast number.

Return the setup brief

Give the user:

1. Objects, exports, and row counts in scope, with export dates.
2. Fields that are empty, undefined, or used in more than one way.
3. Current stages and routing rules, with known gaps.
4. Reports that depend on weak fields, and who reads them.
5. The first three pieces of work, with reasons.

Never fill a missing value with a guess. Do not merge, delete, reassign, or edit CRM records; propose each change for the system owner to make.