Enrichment is a starting point.

A new field can make a record look more complete without making it more useful. The value might be old, belong to the wrong company, or answer a question nobody needs to ask.

Before adding a data point, decide what it is for. Will it help someone research an account, route a record, or make a specific decision? That purpose should shape what gets collected.

Match first, then update

Clay can help gather company and contact information. Enrichment adds attributes; it does not establish that every result is accurate, current, or attached to the intended record.

A common ambiguityTwo companies share a similar name. A research result describes one of them, while the CRM record belongs to the other. Adding more fields would make the mismatch harder to spot. Checking the company domain and source comes first.

Before writing an update, check the match, map the intended properties, and decide which existing values should be preserved. Clay’s HubSpot update action uses the HubSpot object ID to target the record; a company name alone is not the update target.

A value needs a definition

A field also needs a meaning people share. Is “company size” a current figure or an estimate? When was it checked? Does an empty value mean unknown, not relevant, or not yet researched?

These distinctions matter when a property feeds HubSpot enrollment criteria, routing, or reporting. The same value can affect several decisions downstream.

Keep the source and research date where they will be useful. Revisit stale values, and check which workflows depend on a property before changing its definition or removing it.

The point is to collect information that earns its place in the next decision and leave enough context to question it later.