IoT companies have a unique cold email problem - your buyers are distributed across departments, your sales cycle is long, and your value prop is hard to explain in one paragraph without sounding like you're selling vaporware.
On top of that, most IoT decision makers (operations directors, plant managers, facility heads) don't spend much time reading emails. They're busy running actual operations. So your email either hits them fast or it dies in their inbox.
Here's what actually works for IoT cold email based on what we see converting:
This is where most IoT companies get it wrong. You think you're selling to the CTO or VP of Engineering. You're not always.
Your actual buyers are usually:
The tech people often show up later in the conversation - but they're rarely the first person to say yes.
Your lead list should reflect this. If you're only targeting CTOs and engineering VPs, you're hunting in the wrong department.
IoT is absurdly broad. Smart buildings, connected vehicles, industrial sensors, medical devices, environmental monitoring - these are completely different buyers with completely different problems.
Pick one. Actually pick one.
Example: Instead of "manufacturing companies with IoT needs," target "food processing plants in the Midwest." Instead of "smart building solutions," target "commercial real estate companies with 50+ properties."
This specificity matters because:
For IoT, we typically see the best results targeting 200-500 specific prospects in a narrow vertical rather than 5,000 semi-relevant companies across industries.
Your email has one job: prove you understand their specific problem and hint that you have a solution. Not sell the solution. Hint at it.
Here's the structure:
Subject Line: Lead with their pain or recent event, not your product name.
Example: "Unplanned downtime at [Company Name]?" or "One question about asset tracking at [specific facility type]."
Why? Because operations people scan emails for relevance. If you lead with your product name, it looks like spam to them. If you lead with something that could affect their day, they open it.
First Line: Reference something specific about their company or a recent event in their industry - a new facility opening, a recent acquisition, a change in their supply chain. Don't make it up. Use public info.
Example for a logistics company: "Saw [Company] just opened a distribution center in Dallas - probably managing new asset tracking complexity there."
The Problem: State the problem in their language, not yours. Not "real-time sensor data integration" - "unplanned equipment downtime" or "manual asset audits that take three people a week."
The Hook: One sentence that implies your solution without describing it. This is where specificity wins.
Example: "We've helped [similar company type] cut maintenance response time from days to hours because they can see actual equipment status before it fails."
The Ask: Ask for 15 minutes, not a demo, not a call "when they're ready." 15 minutes. This feels doable to a busy operations manager.
Example email for a water treatment facility:
"Hi [Name], Saw [Facility Name] recently upgraded your main pump systems - that's a significant infrastructure investment. One thing we've noticed with facilities your size: pump failures usually cascade because nobody catches the pressure drop until it's too late. We help treatment plants get real-time alerts before that happens, which means your maintenance team catches issues in hours, not after a breakdown. Would 15 minutes make sense to see if it's relevant for [Facility Name]? [Your name]"
That's it. Short, specific, problem-focused.
IoT buying cycles are long and weird. A facilities manager might need your solution but not have budget approved until Q2. So your follow-up sequence needs to be longer than typical SaaS email.
Standard structure:
For IoT, don't add a sixth email. After day 26, they're either not interested or it's not the right time. Move to your next list.
Email 2 and 3 should include actual data relevant to their industry - "Plants with predictive maintenance systems reduce downtime by 40%" matters more to a plant manager than anything you say about your platform.
IoT companies love talking about their technology. Machine learning algorithms, edge computing, cloud integration, real-time dashboards. Your buyers don't care about any of this.
They care about outcomes: uptime, cost reduction, labor hours saved, compliance risk reduced, safety improved.
Keep your emails outcome-focused. Save the technical deep-dive for the conversation if they're interested. If you spend your cold email explaining your architecture, you've already lost them.
This applies whether you're selling to manufacturing companies or automotive companies - the operations people who decide are evaluating impact, not innovation.
You now have a framework. But actually running this at scale - managing lead lists, writing personalized openers for 300 prospects, handling the replies when they come in, knowing which objections mean "not now" versus "not ever" - that's a different beast.
Most IoT companies either run these campaigns inconsistently, or they start strong and burn out after a month when replies come in and nobody is assigned to follow up properly. If you want to build a consistent pipeline without managing the day-to-day operations of email campaigns, BEC Growth handles the full execution - infrastructure, personalization, sequencing, and reply management - so you can focus on closing deals.
Ready to Sign Clients On-Demand?
BEC Growth builds and manages your entire cold email system from infrastructure to reply handling.
Book a Call →