Good outreach gives the recipient a specific reason to consider a conversation. Personalization should improve relevance, not merely prove that you found someone’s name and job title.
Start with the customer situation. If you cannot explain why the offer matters to this audience, more message variants will not solve the targeting problem.
Use this structure
- State the relevant situation or problem.
- Explain what your company helps change.
- Add one credible piece of evidence if it directly supports the claim.
- Ask for a clear, proportionate next step.
Keep the message short enough that the recipient can decide whether the subject is relevant. Do not force every detail of the company into the first contact.
A hypothetical example
“Teams managing appointments across several locations often end up reassigning staff manually when schedules change. We built a tool that keeps those changes in one shared workflow. If that is a problem your team owns, would a short example be useful?”
This example deliberately avoids invented customer logos, fabricated results, and a false claim that the sender knows the recipient’s internal situation. The product and target audience are fictional.
Make the evidence fit
A relevant customer example, accurate product demonstration, or specific observed capability can support the message. A large company logo without an explanation may add less than expected. Never imply a relationship or result you cannot substantiate.
If the message relies on a public trigger, verify it and explain the connection. Do not turn an unrelated announcement into an excuse for a pitch.
Choose the next step carefully
A request should match the recipient’s likely understanding and the complexity of the offer. Sometimes a short example is more appropriate than immediately asking for a long meeting. In other situations, a direct meeting request is clearer. Test the commercial outcome, not just which phrasing gets replies.
Evaluate the right responses
Separate interest, objections, referrals to another person, poor-fit replies, and no response. That classification helps distinguish a messaging issue from an audience issue.
When software researches, drafts, sends, or classifies replies, add an evaluation gate before increasing volume. Review account eligibility, contact fit, source support for each factual claim, opt-out handling, and the quality of the human handoff. The AI SDR evaluation checklist follows that work from the starting account list to sales-accepted opportunities.
Do not count an automatically booked meeting as pipeline merely because the workflow can create a calendar event or CRM record. A sales owner should accept the opportunity using consistent evidence and record why proposed opportunities are rejected. That feedback is how the automation gets commercially better instead of merely busier.
Use public professional routes and respect recipient preferences and applicable requirements. The goal is relevant business communication, not maximum message volume.
The ICP template should supply the situation behind the message. If it does not, improve the research before adding another sequence.
Co-founder and CEO of Stackmatix, startup advisor, and former Head of Sales at MightyHive. Connect with Matt on LinkedIn ↗ · More about Matt →