What you'll be able to do after this guide: add a standard set of guardrails to a sourcing agent's spec, and explain to a colleague why each one is there.
How to use this page
Each rule below is written so you can copy it into a spec, followed by the reason. Keep the reason in the spec too: an agent that knows why a rule exists applies it more sensibly.
Data quality
| Rule | Because |
|---|---|
| De-duplicate every candidate before any research, in one pass: domain, then name, then status, then exclusion list, then research date | Search tools return the same top results every month; research is the expensive step |
| Count only genuinely new candidates towards the daily minimum, and keep paging or widening until it's met | Otherwise the agent "meets" its target with duplicates, or stops early |
| Confirm the legal entity from the site's own legal pages before searching the company register | A name guessed from a domain once matched a real but unrelated company |
| Treat any status other than active on the register as a hard stop: score 1, Skipped, stop | Live websites hide companies in liquidation |
| Never guess an email address, domain, platform or identity | Wrong details undo the whole "I researched you" premise, and email law expects real addresses |
| Use enrichment data as Tier 2 at best; never as evidenced revenue | Tags go stale and get attached to the wrong companies |
| Reuse existing wording in free-text category fields | Otherwise counts and filters by category break |
CRM safety
| Rule | Because |
|---|---|
| Never create attributes, options or lists; never delete or merge records | The schema belongs to people. A missing option is flagged, not invented |
| Write company, then fields, then person, then notes, then status last | Status is the hand-off signal; setting it early hands over a half-built record |
| Set the research date only when research genuinely finished; leave it blank after a tool outage | The blank date is how the backfill agent knows to retry |
| Search for an existing note before creating one | Reruns otherwise duplicate notes |
| Don't write fields owned by other stages | Two writers with different meanings break clocks and queues |