Use evidence to earn a correction or conversation
Choose a fact that connects to the problem your product solves. A product or pricing change is often more useful than a generic congratulation. State it accurately, then ask about the current workflow. Keep the message short enough for the buyer to see the point.
Test the inference before sending. Could another explanation make the account unsuitable? Does the chosen role own the question? Can your standard product support the scenario? A responsible message permits the buyer to say the premise is wrong without being pushed into a demo.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Observation | Reliable source describing a business condition | State the fact without private conclusions |
| Hypothesis | Possible consequence linked to your product problem | Keep it conditional and open to correction |
| Question | Relevant role can explain the workflow | Ask for a small useful answer rather than demand a meeting |
Work through the decision
Illustrative message: 'I saw your enterprise plan separates access by customer. How are plan changes handled across the product today? We work on the research-to-selling motion around technical B2B problems; if this is already solved, that is useful to know.' Adapt the product statement to your actual service rather than copying it blindly.
The message does not say the company is struggling. If the buyer confirms the issue, ask for the current process and consequence before discussing scope. If they reject it, update the research record and stop that pain narrative.
Personalization is accurate but irrelevant
An unrelated hobby, school or old social post may show research effort while adding no commercial relevance. Use information tied to the business problem and respect the buyer's attention. More facts do not necessarily make a better opening.
A concrete next step
Rewrite three existing messages using observation, hypothesis and question. Have a colleague identify the unsupported inference and remove it before testing.
Sources and research notes
- Schematic product documentationCompany product description
- FTC: CAN-SPAM business guideRegulator guidance; US scope
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic