What you'll be able to do after this guide: add logging to every agent so you can see where prospects are lost, tell a quiet day from a broken agent, and spot bugs before they cost you prospects.
Two logs: one for machines, one for people
The funnel log is a single CSV file (a plain spreadsheet file any tool can open) shared by every agent. Each run appends one row per step:
| run_date | run_ts | task | phase | step | count | detail |
|---|---|---|---|---|---|---|
| 2025-05-12 | 07:51 | 1 - Source & Research (Segment A) | in | search_candidates | 60 | |
| 2025-05-12 | 07:51 | 1 - Source & Research (Segment A) | filter | deduped_existing | 38 | |
| 2025-05-12 | 07:51 | 1 - Source & Research (Segment A) | filter | status_disqualified | 3 | 2 dissolved 1 in administration |
| 2025-05-12 | 07:51 | 1 - Source & Research (Segment A) | filter | unverifiable | 4 | |
| 2025-05-12 | 07:51 | 1 - Source & Research (Segment A) | out | researched | 15 | |
| 2025-05-12 | 07:51 | 1 - Source & Research (Segment A) | out | reached_review | 6 |
The human log is a monthly text file. Each run adds a heading and one line that reads like a funnel, plus one sentence on anything unusual:
1 - Source & Research (Segment A), 12 May 07:51. 60 in, minus 38 already in CRM, minus 3 not active, minus 4 unverifiable, 15 researched, 6 to Review. Two companies' accounts were scanned images and needed text recognition.
The CSV is for adding up; the text file is the one people actually read.
Rules that make logs trustworthy
Filter rows record how many were removed, not how many survived. Removals tell you where the bottleneck is. If "deduped_existing" climbs towards "search_candidates", your search keeps returning companies you already have, and it's time to widen it.
Use a shared list of step names. Keep the allowed step names in one document. If one agent writes "dedup" and another "deduped_existing", the numbers can't be compared. Adding a step means updating the list in the same edit.