Prospecting
Part of Measuring sales development performance
Comparing activity volume with useful conversations
Separate contact attempts, connections and useful conversations, then compare activity with outcomes using consistent cohorts and denominators.
Compare contact actions with exchanges that help the team decide. Attempts show work done; a connection or human reply shows a response; a useful conversation shows what was learned or decided. Keep the counts separate so a higher activity total does not hide fewer worthwhile exchanges.
Define the counts
Count an attempt when a representative makes a call or sends a permitted message, not when they merely schedule a task. Record the channel and the account or contact. A second call is another attempt, not another contacted account.
Record a connection or human reply separately. A call may reach someone but end before the topic is discussed. An automatic email response or a stop request is not a useful conversation merely because it produced a reply. Record stop requests and act on them.
Define a useful conversation as a two-way exchange that resolves at least one material question: whether the issue is relevant, who owns the work, whether a necessary fit condition holds, or what action the prospect wants next. A respectful exchange confirming a mismatch can be useful for a sound stop. Record that decision separately from an exchange that supports further sales work.
A short note should show the question, what the prospect said, what remains unknown and the resulting action. Call duration or a Connected outcome alone cannot supply that meaning. If a thread has several replies on one issue, decide whether the reporting unit is the thread or each distinct conversation, then apply that rule consistently.
How to Define and Track Useful Conversations
- Count an attempt when a rep makes a call or sends a permitted messageDo not count scheduled tasks; record channel and contact.
- Record connections or human replies separatelyExclude automated responses or stop requests; act on them.
- Define a useful conversation as a two-way exchange resolving a material questionInclude decisions on relevance, ownership, fit, or next steps.
- Document the outcome in a short noteNote the question, prospect’s response, unknowns, and action taken.
Put volume beside reach and outcome
For a defined cohort and cut-off, review attempts, distinct accounts contacted, connections or human replies, useful conversations and their next decisions. Two calculations answer different questions:
- Attempts per useful conversation = attempts ÷ useful conversations.Show the counts and leave the ratio undefined when there are no useful conversations. It describes a cohort, not the effort required for each individual exchange.
- Share of contacted accounts with a useful conversation = distinct contacted accounts with at least one useful conversation ÷ distinct contacted accounts.This is an account-level reach measure. It depends on which accounts were worked and how long they were observed.
Keep channels visible, but do not assign a conversation to a channel merely because it was the last recorded touch. A prospect may have received calls and emails before replying. State any attribution rule and its limit.
Audit a change before explaining it
Suppose a fictional team records 100 attempts and six useful conversations in one cohort, then 130 attempts and five in a later cohort. The counts warrant investigation; they do not establish that extra activity caused fewer useful exchanges.
Check the account mix, number of distinct people, contact routes, observation periods and recording habits. Read a sample of replies and call notes, including declines and no-fit decisions.
If calls are logged without outcomes, the useful-conversation count may be incomplete. Correct the coding rule before treating a movement as a performance trend.
If connections rarely address the intended work, review the account premise or opening question. If useful conversations rarely lead to a sound next action, investigate that different gap. Compare later cohorts under the same definitions.
Audit Checklist Before Explaining Performance Changes
- Review account mix and number of distinct people contacted
- Check contact routes and observation periods
- Read a sample of replies and call notes (including declines)
- Verify that calls are logged with outcomes
- Assess whether account premise or opening question needs review



