Email is the only channel a software company genuinely owns, which makes it both the highest leverage thing in the stack and the easiest to damage. A poorly run campaign does not simply underperform: it burns list health, trains people to ignore your sending domain, and can affect whether your product notifications arrive at all. That last consequence is what makes software email different from ecommerce email, because for a subscription product the marketing sends and the transactional sends often share infrastructure and reputation. This page separates the kinds of email a software business sends, explains which rules apply to which, and sets out what to own and measure before an agency or contractor touches the list.
Lifecycle, broadcast and product email are three different jobs
Lifecycle email is triggered by behaviour: onboarding sequences, activation nudges, trial expiry, feature adoption, dunning and win back. It is mostly engineering and analytics work with copy attached, it runs continuously once built, and it produces the majority of email attributable revenue in most subscription businesses. Broadcast email is the newsletter and the announcement, judged on engagement and pipeline influence rather than direct conversion. Product email is transactional: receipts, alerts, invitations, password resets. Agencies are usually strongest at broadcast, because it is the part that looks like marketing, and weakest at lifecycle, because it requires access to your product events. When you brief a provider, say which of the three you are buying. A retainer that produces a fortnightly newsletter while the onboarding sequence remains a single welcome message is a common and expensive misallocation.
The rules that apply, including to messages you think are product email
In the United States, commercial email sits under the CAN-SPAM Act, and the FTC's compliance guide sets out the obligations plainly: do not use false or misleading header information, do not use deceptive subject lines, identify the message as an advertisement, include a valid physical postal address, tell recipients how to opt out, honour opt out requests promptly, and monitor what others do on your behalf, because a business remains responsible for email sent by a contractor or agency. The last point is the one software companies most often miss when they outsource. The other trap is classification: a message whose primary purpose is commercial does not become transactional because it was triggered by product behaviour, so an upgrade prompt inside an onboarding sequence carries the commercial obligations. Where you cannot decide, treat it as commercial, and keep transactional sending on separate infrastructure so a marketing complaint rate cannot affect password resets.
Deliverability is an asset you own, not a setting
Deliverability decides whether any of the rest matters, and it is built slowly and lost quickly. The fundamentals are dull: authenticate your sending domain properly, warm new sending domains and addresses gradually rather than importing a list and sending to all of it, use a subdomain for marketing sends so a bad campaign cannot damage transactional delivery, remove inactive contacts on a schedule instead of hoarding them, and make unsubscribing a single click rather than a maze, since people who cannot leave mark you as spam instead. Ask any provider how they handle each of those, because a contractor optimising for open rate has an incentive to keep sending to a decaying list. Ask also who holds the sending account. If you buy this as part of a wider SaaS marketing company engagement, the domain, the sending platform and the list must be in entities you control, with the agency granted access.
Measuring what email actually did
Open rate has been unreliable since privacy features began pre loading images, and it should not be a headline metric for a software business. Measure four things instead. Delivery health: bounce rate, complaint rate and the share of sends reaching the inbox rather than a promotions or spam folder. Click through on the specific action a message was written to cause, rather than any click. Downstream product events: activation steps completed, trials converted, features adopted, seats expanded, all read from your product analytics rather than from the email tool. And revenue retention effects for dunning and win back, which are the highest return sequences in most subscription businesses and the least glamorous to build. Agree these definitions before an engagement starts, because the email platform will happily report a set of numbers that look excellent and mean very little.
Questions people ask about saas email marketing
Do product notification emails need an unsubscribe link?
Purely transactional messages such as receipts and password resets are treated differently from commercial ones, but the distinction turns on the primary purpose of the message. A notification that mainly promotes an upgrade carries commercial obligations, so when in doubt include the opt out and a valid postal address.
How quickly must an opt out be honoured?
Promptly, and the FTC's CAN-SPAM compliance guide sets an outer limit in business days rather than leaving it open. Practically, honour it immediately and automatically, and make sure any agency or platform sending on your behalf is wired into the same suppression list.
Should an agency own our email platform account?
No. The sending domain, the platform account, the list and the templates should sit in entities you control with the agency granted access. Email is the asset a subscription business genuinely owns, and an engagement that ends with the vendor holding it has sold you a dependency.
What should a software company build first?
Onboarding and activation, then dunning and win back. Those sequences run continuously, act on people who have already chosen you, and usually outperform any broadcast programme. The newsletter is worth doing once the automated sequences are live and measured.