You are the person three teams ask for a number, and you know the number is not clean. Last quarter the board pack and the CRM disagreed, and the reconciliation cost you two evenings. Now a well-meaning leader suggests the obvious fix: point an agent at the CRM and let it clean up. This lesson is the answer you give.
Everything this module uses came in the practice pack from the course page; if you have not downloaded it and unzipped it into your course folder, do that first.
What you will be able to do
- Score three hygiene tasks on the five-factor fit test and say which two you would hand over today.
- Say why the third stays human, even though it is the most tedious.
- Choose between a file export and a live CRM connector, and defend the choice in one sentence.
Three hygiene tasks, three different answers
"Clean up the CRM" is not one task. It is at least three, and they score differently. Run them through the Module 3 fit test: Volume, Checkability, Judgment density, Cost of being wrong, Specification cost, each 1 to 5. A low Checkability score is a veto, whatever the rest say.
| Count the defects | Find duplicate candidates | Choose which duplicate survives | |
|---|---|---|---|
| Volume | 5. Three files, 1,747 rows in the shipped set | 5. Every account against every other | 3. Fifteen or twenty decisions a month |
| Checkability | 5. Every count is reproducible from the export | 4. Every candidate pair can be read by a human | 1. No file says which record is right |
| Judgment density | 1. None, once the definitions exist | 2. Low, once the rule exists | 5. High, and most of it is outside the CRM |
| Cost of being wrong | 2. A wrong count is embarrassing and reversible | 2. A wrong candidate is rejected at review | 5. A wrong merge destroys history for two teams |
| Specification cost | 2. Twenty minutes if you know your fields | 3. An hour to write the rule properly | 5. You cannot write down what "right" means |
| Verdict | Hand it over | Hand it over, with a review band | Keep it human. The agent proposes, a person decides |
Row counts: accounts.csv 308, contacts.csv 911, opportunities.csv 528 in the shipped Talvera dataset (DATA-DICTIONARY.md in your pack's data folder). Together: 1,747.
The third column is the lesson. Which duplicate survives depends on things the export cannot see: which record billing points at, where support's tickets sit, whether the rep on one is mid-negotiation. Checkability scores 1, and that is a veto. The agent brings you the pair and the evidence. You make the call.
Work from an export first, connect later
Two ways to give an agent CRM data: a file export in a folder you granted, or a connector wired to the live system. Connectors are MCP servers wired to your tools, and installing a plugin can add one.
For a first hygiene pass, use the export. Three reasons your CRM owner will accept:
- A snapshot you can reconcile against. Re-run the same brief on the same file next week: any difference is your brief, not the data moving under you. That is what makes checking possible.
- No write path. Cowork reads, creates and modifies files only inside the folders you grant it. A CSV in
10-data/cannot become a CRM record by accident. No such guarantee exists once a connector with write scope is authorised. - Read-only blast radius. You get to be wrong for free until the rules are right.
Default: export to 10-data/, output to 30-output/hygiene/, connector later or never.
Treat any CRM connector as writes-to-system until you have read its permission screen yourself. Our fact base names Gmail, Google Drive, Slack and a Zoom connector, and does not enumerate CRM connectors, so this course cannot tell you what yours can do. Write down what it can read and write, and put that line in your data-boundary.md from Module 2.
Worth knowing: a large export consumes allowance quickly, because complex multi-step work uses materially more than chat, out of a pool shared with chat and Claude Code. One batched monthly pass is cheaper than a live connection you poke at all week. And no trigger fires when a record changes, so a hygiene pass is a cadence whatever you connect. Module 8 designs the cadence.
Try this now
- Point Cowork at your
revenue-workspace/from Module 2, not at Downloads. Downloads also holds a compensation spreadsheet, and the directory boundary is the real boundary.- Copy
accounts.csv,contacts.csv,opportunities.csvfrom your pack's data folder into10-data/. Nothing else goes there.- Before any analysis, paste this and read the answer.
Read every CSV in 10-data/. For each file, report: filename, row count,
column names in order, and the first two data rows verbatim.
Do not clean, interpret or summarise anything. Do not write any file.
What you should see: accounts.csv 308 rows, contacts.csv 911, opportunities.csv 528. You asked for an inventory first on purpose: proof the agent sees what you think it sees. If a count differs from what your CRM export tool reported, stop. You have an encoding problem, a quoting problem or the wrong file, and every later number inherits it. Thirty seconds, and the cheapest tripwire in this course.
What you keep
Nothing yet. Two decisions, written at the top of 40-reference/field-policy.md, which you start next lesson:
- Source: file export, refreshed monthly, in
10-data/. Connector status: not authorised. - Never delegated: the survivor decision on a duplicate merge. Reason: no source of truth exists in the export, so the decision cannot be checked.
That second line belongs in your Module 3 delegation-policy.md too.
Check yourself
- Your VP asks why the agent cannot just fix the duplicates it can obviously see. Answer in two sentences, using the fit test.
- A colleague says the export route is slower because you re-export every month. Name what the export buys you that the connector does not, and say whether you would trade it.
- You are handed a connector already authorised with write scope. What do you do first, and what do you write down?
Where this goes next
L5.2 turns "count the defects" into a brief that gives the same answer every month, which means naming the defect classes first. Part A of the exercise sheet in labs/LAB-05 of your practice pack (start with its README) runs the full pass on this dataset. TL-OPS-2, in your pack under labs/track-labs, is where a RevOps learner takes the workflow to a controlled write with a tested reversal.