Blog / Sales operations

Write a first-touch research note a seller can use

A first-touch note that records the source, the trigger, the account context, and the one question the seller should ask.

Sales Development Rep Editorial Team · Published · 8 min read

Write a first-touch research note a seller can use article cover

How to approach: Write a first-touch research note a seller can use

A first-touch note should give the seller a reason to reach out and a question worth asking. Start with the source, the trigger, and the account context. A note that only lists the company name and the title is not research. Keep the boundary visible in the place where the work is assigned.

Keep the note to one screen. The seller should be able to read it before the call and use it during the call. A long dossier will be skipped. Record the date and the source so the next reviewer can repeat the check.

Record the source and the trigger

Name the source of the information and the date it was checked. A public announcement, a job posting, or a product change is a trigger. A note without a source cannot be defended if the buyer asks where the information came from. Keep the original note beside the corrected version.

Record the specific change, not a general impression. A note that says the company is growing is weak. A note that names the new location and the hiring plan is useful. Name the owner in the same line as the action.

Add the account context

Record the segment, the size, and the relevant product or service. A seller should know whether the account fits the ideal profile. The context should be short and factual. A control that depends on memory is not yet a control.

Name the likely owner of the problem, not just the executive. A first touch to the wrong person wastes the research. The note should say why this person is relevant. A control that depends on memory is not yet a control.

Use the related specialist service as a starting point for scope and evidence.

Write the question

Write one open question that follows from the trigger. A question about how the new location will handle onboarding is better than a generic request for a meeting. The question should invite a real answer. Keep the evidence with the record rather than in a separate log.

Avoid a question that can be answered with a brochure. The seller wants a conversation, not a data request. The question should be specific to the account. Record the exception and the person who approved it.

Set the next step

Record the next step and the date. A first touch without a follow-up plan is a one-off message. The next step might be a call, an email, or a LinkedIn message. Update the template when the same question appears twice.

Record the channel and the approved message. A seller should not have to invent the first touch from scratch. The note should make the next action obvious. Keep the original note beside the corrected version.

U.S. Small Business Administration provides public guidance that can help test workflow assumptions.

Review the note after the touch

After the first touch, record what the buyer said and whether the research was useful. Update the note for the next touch. A note that improves after each conversation is more useful than a perfect template. Keep the original note beside the corrected version.

Share the best notes with the team. A short example teaches more than a policy. The goal is a better conversation, not more research. Record the date and the source so the next reviewer can repeat the check.

Common questions

What should a first-touch research note include?

The source, the trigger, the account context, the relevant person, and one specific question.

How long should the note be?

One screen, readable before the call and usable during the call.

Turn the guidance into a controlled role

Bring the workflow, systems, current owner, and known exceptions. We will help shape a focused first handoff.

Plan a consultation

Related field notes

Continue building the system.

Set a lead response standard the team can measure for the following cycle

A response standard that names the start event, the window, the channel, and the exception Revisit the rule with one current example before the following cycle.

Write a discovery note that names the next step for the following cycle

A discovery note that records the buyer's words, the need, the next step, and the owner Revisit the rule with one current example before the following cycle.

Build a handoff from SDR to account executive for the following cycle

A handoff that records the qualification, the buyer's words, the next step, and the AE's acceptance Revisit the rule with one current example before the following cycle.