You've built an integration that solves a real problem. It works. But nobody knows about it yet, and your sales team is stuck sending emails that sound exactly like every other integration pitch out there.
The problem with most B2B SaaS integration cold email is that it treats the integration like the main event. It's not. The integration is the delivery mechanism for the actual value - which is solving a specific workflow problem for a specific type of person.
This is different from standard B2B SaaS cold email because you're not selling a standalone tool. You're selling a connector that lives in existing software people already use. That changes the entire approach.
Understanding Your Real Buyer for Integrations
Most integration pitches target the wrong person. They email the platform owner when they should email the person who actually suffers from the gap the integration fills.
A Salesforce-to-Slack integration, for example, shouldn't be pitched to "Salesforce admins." It should be pitched to sales operations leaders who are tired of their team missing Slack notifications about urgent deals, or to sales leaders who want real-time visibility into pipeline changes without logging into three different apps.
The specificity matters: your integration solves a workflow problem, not a software problem. Target the person whose job gets measurably easier when the integration is running.
The Core Email Structure That Works
The most reliable integration email follows this exact structure:
- Line 1: Name a specific operational friction point (not the integration itself)
- Line 2-3: Show the before/after workflow change in concrete terms
- Line 4: Mention the integration exists and add one technical detail showing you understand their stack
- Line 5: Ask a narrow qualification question
Here's an actual example that's been sent 200+ times with an 18% reply rate:
Hi Sarah, Most ops teams we talk to are manually logging Stripe payments into Quickbooks - which means 2-3 hour blocks disappear every Friday doing data entry that should be automated. With a Stripe-QB integration running, that sync happens automatically. Payments hit Quickbooks 10 minutes after they clear Stripe. No manual touches. We've built this for teams doing $50k-500k MRR. Does your team currently have this automated, or is someone still doing it manually?
Why this works: It doesn't lead with the integration. It leads with the pain. It shows the exact outcome (10 minutes after they clear). It assumes nothing about whether they have it set up. The qualification question at the end creates a forced binary answer.
Targeting the Right List for Integrations
Where most integration campaigns fail is the list building. Generic "ops managers" or "SaaS founders" lists don't work because you need people using both platforms in your integration.
The best list approach is to build backwards from actual usage data:
- If you have access to integration marketplaces (Zapier, Make, etc.), pull companies with active installations of both connected tools
- Use LinkedIn filters to find people at companies using both platforms (most company pages list tech stacks)
- Look for companies mentioning both tools in public channels - Slack communities, Twitter, Reddit, or your own product's user database
- Query ZoomInfo or Apollo to find prospects with both tools in their tech stack
A focused list of 200 people actually using both platforms will outperform a generic list of 5,000. Aim for lists of 500-2,000 prospects maximum for integration campaigns.
The Follow-Up Sequence That Keeps It Real
Integration decisions often move slower because they involve technical stakeholders plus the person experiencing the pain. You need a follow-up sequence that respects this.
A working 4-touch sequence looks like this:
- Email 1 (Day 0): The core pain-focused pitch above
- Email 2 (Day 3): Social proof from similar companies ("3 teams at Series A logistics companies are using this")
- Email 3 (Day 7): Case study or specific metrics ("Reduced manual data entry by 8 hours/week")
- Email 4 (Day 14): Pivot to a different angle - maybe technical setup time if workflow angle didn't land
Keep each follow-up short. Two sentences plus a link to a 60-second walkthrough video works better than longer copy. People are deciding whether to spend 5 minutes evaluating this - match that pace.
What Actually Gets Replies (And What Doesn't)
Subject lines that work for integrations tend to avoid generic framework language and focus on the outcome state:
Stripe→QB data entry taking 6 hours every Friday?
This is specific, metric-based, and asks a question that creates cognitive dissonance if the answer is yes. Generic subject lines like "Integration for Stripe users" or "Automation tool" won't cut it.
Replies start coming when you acknowledge the real constraint: if they need to talk to a developer or their security team, say that upfront. "Takes 15 minutes to set up and works with your current auth" removes friction and builds credibility.
The biggest mistake: treating integrations like feature announcements. Cold email for integrations should feel like you're helping them solve an operational headache they're already experiencing. The fact that it's an integration should almost feel secondary.