Separate problem evidence from account evidence

A thread may show a precise operational problem while leaving the organization unidentified. A professional profile may show an organization without proving active demand. Keep these fields separate.

Do not guess a pseudonymous user’s identity by combining unrelated clues. Work within the context the person chose to provide.

Qualify the next business decision

Ask what system or workflow is affected, what outcome is needed and which constraints apply. Then identify who needs to evaluate the approach. The first question should resolve the most important uncertainty.

Hypothetical example: a team asks about reporting automation. Clarify data sources and approval requirements before proposing an integration. A technical answer may be useful even when the team is not buying.

Use a context-preserving handoff

Handoff fieldReason
Original discussionPreserve what was actually stated
Problem and impactConnect the opportunity to an outcome
Known roleAvoid inventing authority
ConstraintsCheck delivery fit
UnknownsGuide the next conversation
Permitted next stepRespect the original context

A sales owner should not receive only a username and an intent score.

Measure viable conversations

Count substantive exchanges, qualified accounts and documented opportunities. Deduplicate people from the same organization when supported by evidence.

Review why promising discussions failed qualification. That feedback can improve both the account hypothesis and the listening brief.