# SaaS Email Marketing Mistakes > The lifecycle email failures we see most often: date based sends, missing suppression rules, discount reflexes and nurture sequences that never exit. Source: https://saas-marketing.net/guides/saas-email-marketing-mistakes/ Topic: SaaS Email Marketing Type: listicle Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/saas-email-marketing-mistakes/ ## Short answer The most expensive SaaS email mistakes are structural rather than creative: sending on calendar dates instead of product events, sequences with no exit condition, no suppression across overlapping campaigns, mailing unengaged users and degrading domain reputation, discounting reflexively at trial expiry, and measuring opens after Apple Mail Privacy Protection made them unreliable. Deleting three sequences usually improves results more than adding one. ## Key takeaways - Date based sends ignore what the user did, so a fully activated customer still receives the day five setup nudge. - Sequences without an exit condition keep emailing people who already converted, which is the most visible failure a prospect sees. - Mailing unengaged addresses to hit volume targets pushes complaint rates toward the 0.3 percent ceiling Gmail enforces. - Reflexive discounting at trial expiry buys conversions you would have won anyway and permanently resets price expectations. - Open rate stopped being a reliable metric after Apple Mail Privacy Protection, yet most SaaS dashboards still lead with it. - Running no holdout group means you cannot tell whether any sequence caused anything, which makes every optimisation a guess. --- Every ranking guide on SaaS email tells you what to add. None of them tell you what to stop. That asymmetry is why most lifecycle programmes are a pile of sequences that nobody has audited since the person who built them left. Twelve failures, with the symptom, the cost and the fix. Our view up front: deleting three sequences usually beats adding one. ## 1. Sending on dates instead of events **Symptom.** A user who connected their data source on day one receives the day five email asking whether they are ready to connect a data source. **Cost.** This is the fastest way to signal that nobody is paying attention. It suppresses engagement on every later send in the sequence because the user has already categorised your email as automated noise. **Fix.** Trigger on product events. The instrumentation work is real, usually a sprint of engineering time to emit and pipe the five or six events that matter, and it is the highest return investment in most lifecycle programmes. Start with signup, first key action, invite sent, limit approached and payment failed. ## 2. No exit condition **Symptom.** Someone upgrades on Tuesday and receives "still thinking about upgrading?" on Thursday. **Cost.** Direct and embarrassing. It also inflates your sequence conversion numbers, because people who converted independently are still counted as sequence members. **Fix.** Every sequence gets an exit condition written at the same time as the first email, not retrofitted. The exit is the goal event. Test it by completing the goal action yourself mid sequence and confirming silence. Sequences without exits plus sequences without suppression means a newly converted customer can receive three different upgrade prompts in a week from three campaigns that do not know about each other. This is common enough that we check for it first in every audit. ## 3. No suppression across overlapping sequences **Symptom.** A trial user is simultaneously enrolled in onboarding, a webinar promotion and a product announcement. **Cost.** Four emails in three days from one company. Complaint rates rise, and the message you cared about gets buried by the two you did not. **Fix.** One global frequency cap enforced in whichever tool sends the most, plus priority ordering so lifecycle beats marketing when they collide. Three commercial emails per person per week is a defensible ceiling for most B2B products. ## 4. Mailing unengaged users to protect volume **Symptom.** A quarterly send to everyone who ever signed up, because the list is big and the number looks good in a deck. **Cost.** Reputation. Gmail and Yahoo expect bulk senders to stay below 0.3 percent complaints, and you should already be intervening at 0.1. Once placement degrades, your good sends suffer too, including the ones that make money. **Fix.** Sunset policy. No engagement in 180 days means no marketing email, with one re permission attempt before removal. The list gets smaller and the revenue does not. **0.3%** Complaint rate ceiling for bulk senders at Gmail and Yahoo, with degradation starting well below it ## 5. The discount reflex at trial expiry **Symptom.** Day 13 of a 14 day trial, every user gets 20 percent off. **Cost.** You pay for conversions you already had. Worse, the offer leaks, gets documented in forums and on coupon sites, and becomes the price. Once a category learns that your list price is negotiable at trial end, it stays learned. **Fix.** Run it against a holdout. If the incremental lift over an untreated group is under roughly 15 percent, the discount is costing you money. Try extending the trial or offering a setup call first, both of which convert without resetting price. ## 6. Onboarding email that duplicates in app messaging **Symptom.** A day two email saying "invite your team" while an in app checklist says the same thing. **Cost.** Users learn that both channels repeat each other and stop reading either. You also cannot tell which channel drove the action, so both teams claim it. **Fix.** One job, one primary channel, with exposure based suppression between them. The full mapping is in [In App Messages vs Email](/comparisons/in-app-messages-vs-email/). ## 7. Heavy HTML templates on activation sends **Symptom.** A four column responsive template with a hero image for an email whose entire job is to get someone to click one link. **Cost.** Slower rendering, worse deliverability on image heavy sends, and a message that reads as marketing rather than as help. Plain text styled sends consistently outperform designed templates on activation in our experience, though they lose on brand launches and newsletters. **Fix.** Keep templates for newsletters and announcements. Use near plain text for anything triggered by product behaviour. ## 8. One shared sending domain **Symptom.** Newsletters, dunning notices and password resets all leaving from the root domain. **Cost.** A single bad campaign degrades account access for everyone. Support volume spikes and nobody connects it to the webinar invite sent on Monday. **Fix.** Separate subdomains, ideally separate providers. The architecture is in [Transactional vs Marketing Email](/comparisons/transactional-vs-marketing-email/). ## 9. Still optimising for opens **Symptom.** A dashboard where open rate is the headline number and subject line tests are judged on it. **Cost.** Apple Mail Privacy Protection pre fetches images, inflating opens for a large and unevenly distributed share of B2B recipients. You cannot compare segments, and subject line tests produce winners that mean nothing. **Fix.** Judge on the downstream action. For activation sends that is the activation event. For dunning it is recovered revenue. Keep opens as a directional trend line and stop putting them in front of executives. Our benchmark ranges and their caveats are in [SaaS Email Benchmarks](/research/saas-email-benchmarks/). ## 10. No holdout group anywhere in the programme **Symptom.** Every sequence reports a conversion rate. None reports an incremental lift. **Cost.** You cannot tell whether any of it works. Teams spend quarters optimising sequences that would perform identically if switched off, which is not a hypothetical: we have seen a six email nurture removed with no measurable change in conversion. **Fix.** Hold out 5 to 10 percent from every major sequence, permanently. The reporting is slightly harder and the answers are real. Size the stakes first with the [SaaS Email Revenue Calculator](/calculators/email-revenue/). ## 11. Personalisation tokens exposing bad data **Symptom.** `Hi {{first_name}},` or "Hi there," to a named contact, or a company field showing a domain instead of a company name. **Cost.** Small per instance, large in aggregate, and it undermines every claim you make about understanding the customer's workflow. **Fix.** Fallbacks on every token, and a rule that no token appears in a subject line unless the field is populated for over 95 percent of the segment. Audit by sending to a seed list that deliberately includes records with missing fields. ## 12. Newsletters to churn risk accounts **Symptom.** An account whose usage dropped 70 percent and whose renewal is in six weeks receives a cheerful product announcement. **Cost.** It reads as tone deaf to a customer already drafting an internal case for cancelling, and it wastes the only attention you have left with them. **Fix.** Suppress marketing sends to accounts flagged as churn risk, and route them to a customer success owned sequence instead. That handoff is covered in [Expansion Revenue Email Campaigns](/playbooks/expansion-revenue-email-campaigns/). ## What to do with this list Do not try to fix twelve things. Pull your active sequence list, mark which of these twelve apply, and count how many sequences are involved. Then delete. In almost every audit we run, three to five sequences are producing nothing measurable while consuming list attention and complaint budget. Removing them improves the performance of what remains, costs nothing, and takes an afternoon. Rebuild what survives on events rather than dates, and put a holdout on each one so the next version of this conversation has evidence in it. The programme level structure that prevents most of these sits in [SaaS Email Marketing Strategy](/guides/saas-email-marketing-strategy/), worked examples are in [SaaS Email Marketing Examples](/guides/saas-email-marketing-examples/), and the tooling constraints that cause several of them are covered in [HubSpot vs Customer.io](/comparisons/hubspot-vs-customer-io/) and, for the self hosted route, [Mautic for SaaS](/guides/mautic-for-saas/). If you want the full sequence by sequence walkthrough, the [Lifecycle Email Course](/courses/saas-lifecycle-email/) covers it, and the cluster hub is at [SaaS Email Marketing](/saas-email-marketing/). ## Frequently asked questions ### What is the most common SaaS email marketing mistake? Triggering on calendar dates rather than product events. A day five onboarding email that says 'ready to connect your data?' sent to someone who connected their data on day one destroys credibility instantly. Event triggering costs a sprint of instrumentation work and fixes the single most visible quality problem in most lifecycle programmes. ### Why are my SaaS emails landing in spam? Usually reputation rather than content. The common causes are mailing unengaged addresses to maintain volume, sharing one sending domain between marketing and transactional email, and complaint rates drifting above 0.1 percent. Gmail and Yahoo expect bulk senders below 0.3 percent complaints, and degradation starts well before you hit the ceiling. ### Should I stop measuring email open rates? Stop making decisions on them. Apple Mail Privacy Protection pre fetches images, which inflates opens for a large share of B2B audiences and makes cross segment comparison unreliable. Keep opens as a rough directional signal, judge sequences on the downstream action, and use click to conversion rate as your working quality metric. ### Is discounting at trial expiry a mistake? Usually. The people who convert on a discount email include a large group who would have converted anyway, so you pay for conversions you already had and teach the rest of the market to wait for the offer. Test it against a holdout before making it permanent. If the incremental lift is under about 15 percent, it is losing you money. ### How many emails should be in a SaaS nurture sequence? Fewer than you have, and every one needs an exit condition. Most sequences we audit have between eight and fourteen emails and produce nearly all of their conversions in the first four. Cutting to five with a clear exit usually improves total conversions because unsubscribes fall and the remaining sends reach a healthier list. ### What is a holdout group and why does email need one? A randomly selected slice of your audience, usually 5 to 10 percent, that receives nothing from a given sequence. Comparing their conversion rate to the treated group tells you the sequence's incremental effect. Without it you are measuring correlation between being in a sequence and converting, which is not the same thing at all.