Test one buyer, one problem and one route to a conversation

Choose one buyer for one pass. A broad audience produces broad messages and muddled feedback.

Write the customer record before the message

1. Name one buyer

Write the role that owns the workflow and the situation that makes the problem relevant. “Small businesses” is too broad. “The person who reconciles supplier invoices before month-end” is specific enough to investigate, but it still needs evidence from your market.

2. Record one sourced problem observation

Use an interview note, support ticket, public complaint, sales email or observable workaround only when its collection and reuse are permitted for this purpose. Public visibility alone does not authorize reuse or contact. Keep only the detail needed for the decision, remove personal or confidential details from shared notes, and record the source location, date and permitted use. Separate what the person said or did from your interpretation.

• Observed: the exact quote, action, artifact or failed handoff.
• Source: where it came from and when you captured it.
• Interpretation: the job or risk you think sits behind it.

Before drafting, check the sender, source, purpose, applicable contact rules, channel rules and any stop request. An accessible channel is only a possible route. If eligibility is unresolved, wait; do not treat research participation as permission for a sales approach.

Synthetic example: A supplier-invoice coordinator is a plausible buyer. Source: a fictional public community post, with its date recorded. Observation: the post mentions manual invoice reconciliation. Interpretation: month-end checking may be difficult. The community is accessible, but its contact and reuse rules are unknown. Decision: wait, verify those rules, and draft no message.

3. Turn it into one message hypothesis

Once you have established that contact is permitted, write a message that a recipient can confirm, correct or ignore without sitting through a product pitch.

When [situation] happens, are you currently [observed workaround]? I am looking into a narrower way to [job], and I would like to understand how you handle it now.

Keep only the parts supported by the source. Do not add estimated time saved, customer counts or claims about what similar companies do.

4. Choose one channel test

Use the channel where this buyer already has context for the problem: a direct introduction, a relevant community, a reply to an existing conversation, search-led content or carefully researched outreach. Define the test by learning value and permission, not by a borrowed daily quota.

• Channel: where the buyer can reasonably encounter the message.
• Signal to watch: correction, problem detail, referral, meeting, decline or silence.
• Stop or change rule: what would make the buyer, observation, message or channel unfit.

Keep a learning log

Do not combine several buyer types, messages and channels in the same pass. Record silence as no response, with the reason unknown; it does not establish interest, rejection or permission to follow up.