A source beside the field
Know what the observation came from before deciding how to use it.
Enrichment
Add useful context. Keep the open questions visible.
A company name is a starting point. Enrichment should add relevant context and its source preserve conflicting information, and make the next review decision clearer before an account becomes a message brief.
Example
One account. The context behind each field.
Start with what the record actually says.
The original record names Harborline and a broad service category. It leaves buyer role and contact details open. A location is recorded, but its source and current relevance still need review.
Harborline LogisticsExample record / Original
| Field | Original record | Source observation | Review note |
|---|---|---|---|
| Company | Harborline Logistics | Not assessed | Check the source identity |
| Service | Logistics | Not assessed | Seek a more useful description |
| Operating base | North district | Not assessed | Check the source and relevance |
| Buyer role | Not recorded | Not assessed | Keep the gap visible |
| Contact details | Not recorded | Not assessed | No contact channel established |
Useful enrichment keeps three things in view
An honest unknown
A missing role or a conflicting location remains a question to resolve.
A reason for the next step
Use the context to shape a reviewable brief with claims and contact decisions kept separate.
How useful context is added
Start with the question behind the missing field.
Ask what the record needs to support the next decision. Compare a source observation with the existing field, keep the original visible, and distinguish what was stated from what you infer. Review adds understanding without pretending every gap has closed.
Explore source gatheringA broad category becomes a useful observation.
- Original field
- Service: logistics.
- Source statement
- company note: freight operations.
- Interpretation
- A logistics-handoff discussion may be relevant.
- Review
- Check the offer fit; the statement does not show intent.
Company context
Give the account more than a category.
Freight operations tells Northstar more than a generic logistics label. It suggests a question about handoffs not a reason to assume a purchase. Carry the source wording into the account brief so the reviewer can judge whether the connection makes sense.
Explore qualification contextContext informs the question. It does not answer it.
- Observation
- The example note describes freight operations.
- Possible relevance
- Logistics work may involve handoffs worth discussing.
- Open question
- Which handoff, if any, needs a closer look?
- Next review
- Northstar checks relevance before drafting an approach.
Conflicting information
Keep both statements until the difference is understood.
An existing record and a new source can disagree. Harborline's original record says North district; the example says South district. Keep both statements and their provenance together. A reviewer needs to resolve the difference before location informs a message or segment.
Explore relationship recordsDifferent statements. One unresolved field.
- Existing record
- Operating base: North district; source not recorded.
- New observation
- company note: South district.
- Unresolved
- No date or explanation establishes which statement applies.
- Review decision
- Retain both; confirm before using location in the brief.
From context to a useful brief
Know what is missing before choosing whom to contact.
Company context can improve a brief while the recipient remains unknown. The next task is to clarify the role before considering a relevant message.
Explore thoughtful OutreachA better brief can still need another question.
- Useful context
- Harborline's example service is freight operations.
- Buyer role
- Unknown; no decision-maker is identified.
- Contact details
- Unknown; no address, number, or channel is established.
- Next decision
- Clarify the role, then review relevance and any contact permission.
Different fields. The same care with context.
An account brief can hold company context, source notes, and open questions together. Each field needs its own meaning and review decision a fuller record should never make an unknown look certain.
Discuss the fields your team needsCompany identity
Harborline Logistics
Name retained from the original recordService context
Freight operations
Added from the example source noteOperating base
North district / South district
Conflict retained for reviewBuyer role
Research question
Open question; no person inferredContact details
Research question
No address, number, or channel providedReview decision
Clarify the role and location
A focused next task before contactExample
Make the record more useful for the next decision.
Tell us which gaps slow your team down. Start with the context, sources, and review questions your growth workflow needs.