A B2B outreach checklist should confirm the contact’s current role, verify the email address, and check sender authentication before a campaign starts. Use separate checks for contact data and domain configuration. Then review a small batch to identify address failures, incorrect targeting, and sender problems before scheduling more messages.
The checklist below connects contact research with email security. It is meant for small B2B teams preparing targeted outreach, not for sending a large list without checking whether each person has a reason to hear from you.
That distinction matters when diagnosing a failed campaign. A hard bounce may point to a bad address. A DMARC failure points to how your mail was authenticated. A relevant message that reaches an active mailbox but earns no reply may call for a different buyer or offer. Keep those outcomes apart so you do not rewrite copy when the list is broken or replace a contact source when the sending setup is at fault.
1. Confirm the person before finding an address
Start with the account and the business problem. A new office may make an operations lead relevant, while an upcoming software migration may point to an IT owner. Check the company site and a recent professional profile for the person’s current role. When that role is clear, you can get email from a linkedin url with a profile-based finder and compare the returned details with the company domain. Do not assume a name match proves that the person still works there.
Record the profile URL, company, title, and date checked. That short trail helps you catch duplicate records and prevents a stale contact from quietly moving through the campaign. It also makes the first message more specific: you can state the business reason for reaching out without pretending you know the recipient personally.
Build a contact record that another teammate can check
A useful B2B contact record explains why the person belongs in the campaign. Add a short buying reason beside the company and role. For example, an advertised warehouse opening may justify research into inventory operations. It does not establish that every employee at that business handles purchasing.
Resolve conflicting details before exporting the record. A company website may list a new position while an older directory still shows the previous employer. Keep the evidence and the date checked beside the selected role. If the disagreement remains unresolved, hold the record for review.
Give one teammate responsibility for each account. That owner checks whether a colleague already contacted the company and records the next permitted action. Two representatives sending similar introductions to the same person can make a carefully researched campaign look careless.

2. Verify the address, then consider the context
An address can pass a format check and still be a poor choice. Verify the domain and mailbox where your tool can do so, and treat catch-all results with care. Remove hard bounces, duplicates, and old domains before the next send. PowerDMARC’s email verification guide describes when to check a list and why that check differs from sender authentication.
The harder issue is often relevance. Clean b2b contact data should connect the right person to the right company and role, with a contact channel that still works. Someone may have a valid mailbox but no authority over the problem in your pitch. Keep account fit, role fit, and address status in separate CRM fields so one green verification result does not hide the other gaps.
Use address status to decide the next action
Separate verified, invalid, and uncertain results in the working list. A catch-all domain may accept mail for addresses that do not represent individual mailboxes. An unknown result may reflect a temporary restriction on verification. Neither result establishes that the intended person will receive the message.
Keep uncertain records outside the first campaign until someone reviews them. Check the spelling, current employer, and evidence supporting the address. If a previous message produced a permanent delivery failure, suppress that address. Repeating the same attempt without new evidence adds little information.
Store the verification date separately from the date you imported the record. Importing an old list today does not make its contents current. Recheck records when the campaign has waited in a queue or when research indicates a job change. Choose review intervals around the list’s actual use.
Keep suppression decisions when records move between systems. A fresh CSV import should not restore an address that opted out through another platform. Match records carefully, check duplicates, and retain the reason for exclusion. A technically valid address can still belong on the suppression list.
3. Authenticate the system that sends the message
Once the recipient record is sound, check the sending domain. SPF lists authorized sending sources. DKIM adds a signature that receiving systems can validate. DMARC checks whether an authenticated identifier aligns with the visible From domain and tells receivers how to handle failures. These records address identity and spoofing; they do not make a stale list relevant or guarantee inbox placement.
Google's 2024 bulk sender rules show why this work matters. Senders of more than 5,000 messages a day to personal Gmail accounts must meet added authentication requirements. Google's email sender guidelines also say to keep user-reported spam rates below 0.10% and avoid 0.30% or higher. These thresholds apply to defined Gmail traffic; they do not promise inbox placement for one campaign. Even smaller teams should inspect authentication results and complaints, then fix a failing source before sending again.
List every service that sends mail for your domain, including the CRM, outreach platform, and any older integrations. Test each source, review DMARC reports, and fix failures before tightening policy. If the team uses a separate outreach subdomain, configure and monitor it deliberately. PowerDMARC’s sales outreach security guide covers the sender-side checks in more detail.
Check SPF, DKIM, and DMARC on a real message
Ask the person responsible for email administration to send a test through the same platform the campaign will use. Inspect the received message’s authentication results. A successful test from an employee mailbox does not prove that a separate outreach platform uses the correct settings.
SPF evaluates the sending infrastructure against the domain used for the envelope sender. DKIM verifies a signature associated with a signing domain. DMARC uses the visible From domain and requires alignment with a passing SPF or DKIM result. Authentication and alignment both matter.
If a message fails, record which platform sent it and which domain appears in each relevant identifier. Share that evidence with the administrator. Avoid editing DNS records by trial and error. An incorrect change can affect invoices, support messages, and other mail using the same domain.
Keep a record of approved sending services
Create a short inventory containing each service, its business owner, and the domain it uses. Include systems outside sales, such as support desks and billing software. A forgotten service can explain failures that appear unrelated to the outreach campaign.
Review reports before moving to a stricter DMARC policy. A monitoring policy provides visibility but does not request rejection of failing messages. Move cautiously after legitimate sources work correctly. Authentication reduces spoofing risk; it does not replace recipient relevance, complaint monitoring, or list maintenance.

4. Send a small batch and read the signals
Run a test with a narrow group rather than sending the entire list. Keep the subject and offer straightforward, avoid a fake “Re:” thread, and give the recipient an easy way to say no. Track delivery failures, role corrections, complaints, replies, and referrals separately. A reply that points you to a different department can improve the next list even if it does not become a sale.
Do not treat an open rate as a reliable verdict on the list. Mail clients can load or block tracking pixels, and an open says little about whether the message reached the right decision-maker. Look instead at hard bounces, genuine replies, and the share of contacts whose role you could confirm. When one category is weak, change that part of the process. For instance, repeated referrals to operations may mean your initial title filter selected finance staff too often.
Compare results by segment instead of combining them into one average. If finance contacts refer you to operations, your role selection needs work. If both segments bounce, look at verification age and data source. If authentication fails only for one platform, audit that platform's configuration. Record what changed between batches so the next test has a clear purpose.
Work through a sample campaign before increasing volume
Imagine a small software company preparing outreach about warehouse scheduling. The representative selects businesses with a recent warehouse opening and checks who handles local operations. This is a hypothetical workflow, not a claim about campaign results.
During review, one prospect turns out to have changed employers. Another address returns an uncertain verification result. The representative holds both records and checks whether the remaining contacts already appear in an active sequence. The campaign starts with the records that have a clear research trail.
A test message then shows an authentication failure from the outreach platform. The team pauses that source and asks its administrator to inspect the configuration. Replacing the recipient list would leave the sender problem unresolved. After correction, another test checks the same platform.
When replies arrive, record what they actually say. A referral to procurement may suggest that operations staff recognize the problem but do not own the purchase. Use that information to revise the role filter. A refusal should trigger the appropriate suppression action.
Use this order before you expand:
- Choose 20 to 30 accounts with one clear buying reason.
- Check each person’s role and verify the address or mark uncertainty.
- Confirm the sending service passes the planned authentication checks.
- Send, review outcomes, and correct the list before the next batch.
A short diagnosis table for the next campaign
The same poor result can have several causes. This table helps the team investigate the right layer before rewriting the email.
| Signal | First check | Possible action |
| Hard bounces | Address and domain status | Remove or re-verify records |
| Wrong-person replies | Current role and buying team | Change the target role |
| Authentication failures | SPF, DKIM, DMARC alignment | Fix the sending source |
| Few relevant replies | Account fit and message reason | Narrow the segment or offer |

For each batch, keep a record of:
- When the person and address were last checked
- Which service sent the message
- What the recipient or mailbox response actually said
Assign an owner to each failed check
The person preparing the list can confirm research evidence and remove duplicates. The email administrator handles sender configuration. A campaign owner reviews replies and decides whether to continue. Write those responsibilities beside the checklist so a failed check reaches someone who can fix it.
Keep a short change log for each test. Record the segment, sending platform, message version, and correction made since the previous batch. Change one suspected cause where practical. If everything changes together, the next result will be harder to explain.
Make the final send decision from the exceptions
Before launch, review every record still marked uncertain and every unresolved sender issue. The size of the ready list should follow those decisions. A campaign deadline does not turn missing evidence into a checked contact.
Set a review time before scheduling follow-ups. Someone needs to read replies, stop messages after an objection, and remove contacts whose circumstances changed. Automation can continue sending while the team is busy elsewhere. Assigning review time makes that responsibility visible.
Use the next campaign to test a stated correction, such as a narrower role filter or a repaired sending source. Keep the evidence with the batch. The checklist then becomes a working record of decisions that another teammate can understand and repeat.
Before the next campaign, give one representative a sample account and ask them to complete every check. Have the email administrator review the sending test, then assign someone to read the first replies. If a step has no owner or supporting evidence, hold the affected records until the team resolves it. Use the completed checklist as the approval record for that batch.