Hi Paul! Second email for SimpliScada, and this one is a bigger send than the Utah conference email. Context: in late July more than 30 municipal water systems in Minnesota were hit by coordinated cyberattacks. SimpliScada published a security brief about it, and this email drives traffic there. It's their main content push on security, and Brad approved the copy and graphics on September 8. Graphics (attached, in order of placement): Graphic 1, header banner, sits at the very top Graphic 2, "Called air gapped, not actually air gapped," goes midway through after the first CTA button Graphic 3, traditional vs. cloud SCADA comparison, goes below the supporting text section, full width not a narrow column Graphic 3 needs the full width of the email. The labels get unreadable on a phone if it's squeezed into a column. Campaign request: Client / account: SimpliScada Campaign name: 2026-09 Security Brief - Minnesota Cyberattacks Send date + time (with time zone): Tuesday, Sept 15. 9:00am MST Recipient list / segment: the full list of contacts Subject line: Your PLC isn't on the internet. But is anything that touches it? Preview / preheader text: A VPN. A remote laptop. A cellular modem. Any one of them can be a bridge. From name: Carson Freeman Reply-to email: carson@simpliscada.com Links / CTAs (label + URL):
- Read the Security Brief → https://simpliscada.com/minnesota-water-cyberattacks-scada-architecture/
- Book a Free Demo → https://simpliscada.com/free-demo/
Email copy: - final, approved by Brad Matheson Sept 8 Notes: Three graphics included. Alt subject lines available for A/B if wanted. Greeting uses $[UD:FIRST_NAME||there]$ - fallback intentional.
Two steps before this goes live: Send a test to me, Ryan, and Suzan (ryanesco01@gmail.com + abby@firerockmarketing.com) and confirm the recipient count. Then comment in the "Activity" section here so I know the test is out. I'll review and reply with approval. Once you have that, send the real email. The recipient count is the one I'd double check. This is going to a much larger list than Utah and their contact data is messy, so I'd rather catch a wrong segment before it sends than after.
Thanks Paul!
Due 2026-09-16