Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Ignores Customer Job Searches
Transcript
- Lucas: So I got an email last week that made me genuinely angry. Not in a 'this is spam' way — in a 'how did your marketing automation not see this coming' way. Luna: Ooh, I need to hear this. What was it? Lucas: A friend of mine was laid off about a month ago. Big tech company, total surprise. He updates his LinkedIn, updates his resume, starts applying. And then — three days after the layoff — he gets an email from a B2B SaaS platform he uses for project management. Subject line: 'Resume Building Tips for Your Next Career Move.' Luna: No. They didn't. Lucas: They did. And look — the content itself was fine. It was a generic career-advice email they probably send quarterly to their whole user base. But the timing was catastrophic. He already felt raw about the layoff, and here's this tool he uses to manage his work, suddenly reminding him he doesn't have work anymore. Luna: It's the automation equivalent of walking into a funeral and handing out business cards. Lucas: Exactly. And it made me wonder — how many marketing automation systems are blissfully unaware of a customer's biggest life events? Not the happy ones like birthdays or anniversaries. The hard ones. Job loss, divorce, a death in the family. Luna: Most platforms let you trigger on a birthday. But I've never seen a 'recently laid off' segment in any Marketo or HubSpot template library. Lucas: That's the gap. And it's a real business problem, not just a sensitivity issue. Let's talk about what this SaaS company could have done differently — and what signals they missed. Luna: Alright, let's start with the signals. What data points might indicate a customer has lost their job? Lucas: First and most obvious: a change in their LinkedIn profile. If someone updates their headline to 'Open to Work' or removes their current position, that's a massive signal. And yes, it's public data. Companies can ethically pull that into a CRM enrichment tool — as long as they're transparent about it. Luna: But you'd need real-time integration. Most LinkedIn enrichment runs on a weekly batch cycle. You'd miss the window. Lucas: True. But there are other signals that are easier to catch in near-real time. A sudden drop in login frequency. If a user who logged in daily suddenly stops for five business days, that's a red flag. Especially for a B2B tool tied to their employment. Luna: Also changes in bill payment. If they switch from a premium annual plan to a free tier, or if a credit card declines, you can infer financial stress. Lucas: Right. But the key is putting those signals into a trigger that pauses outbound marketing — not just sending a different email. The SaaS company I mentioned should have had a 'life disruption' flag that suppresses all non-essential campaigns for 30 days. Luna: And then what? After the suppression, do you send anything? Lucas: You can, but it has to be empathetic. Maybe a note saying 'We noticed you haven't logged in recently — want us to put your account on hold? No questions asked.' Or a link to a deferred payment option. That's the kind of message that builds loyalty for years. Luna: There's a risk, though. If you explicitly acknowledge 'we know you lost your job,' it could feel creepy. There's a fine line between helpful and invasive. Lucas: That's why you never name the event directly. You say 'we noticed changes in your account activity' — vague and caring. And you always give the user control. Let them opt into support offers, rather than assuming. Luna: So what about the platforms themselves? Could HubSpot or Marketo build this in natively? Lucas: They could, and I think they should. Imagine a 'life event suppression list' that you can activate with one click. It would look for patterns: reduced login, billing changes, profile updates. Then it would automatically pause all marketing emails and add the contact to a special nurture track with softer messaging. Luna: That would solve the 'resume building tips after layoff' disaster entirely. Lucas: It would. And the ROI is clear. Let me give you a number. That same SaaS company — my friend told me he unsubscribed within two weeks of that email. He wasn't alone. They saw a 28 percent open rate on that career-advice email, but a 14 percent unsubscribe rate. Fourteen percent! For a single send. Luna: That's brutal. Especially when the average monthly churn for B2B SaaS is around four to six percent. One email doubled their normal churn rate for that month. Lucas: Exactly. And the lifetime value of a churned customer is zero. So the cost of not having this trigger is enormous — not just in lost revenue, but in brand damage. My friend now actively avoids that tool. He's migrating to a competitor. Luna: And the competitor probably won't be any better unless they've thought about this too. Lucas: Which most haven't. I dug around before this episode. I looked at the major marketing automation platforms' standard templates. Out of the box, HubSpot has a 'life event' category, but it only includes births, marriages, and home purchases. Nothing for negative life events. Luna: Marketo's 'behavioral triggers' are better — you can build a custom smart list based on login frequency decline. But it requires manual setup. No pre-built 'life crisis' playbook. Lucas: So we're essentially saying that the industry has baked in an assumption that life only gets better. More birthdays, more promotions, more anniversaries. But real customer journeys include setbacks. Luna: If this conversation has sparked something you've actually used in your own marketing — maybe a tip about triggers, or the idea of a suppression list — I'd love to hear about it. And if you find these episodes useful, the way we keep them ad-free is through listener support. It's truly that simple. Buy me a coffee dot com slash fexingo. Lucas: Yeah, and it's a small gesture that goes a long way toward keeping this conversation independent. No sponsors, no pressure — just marketers talking to marketers. Luna: Exactly. Alright, back to the signals. Lucas, you mentioned LinkedIn enrichment as one source. But what about privacy regulations like GDPR? If you're tracking someone's public LinkedIn changes and then acting on it, does that require consent? Lucas: It depends on jurisdiction. Public data is generally fair game, but if you're in the EU, you need a legitimate interest basis. Most marketers can argue that pausing emails during a stressful period is in the customer's interest. But you should document that rationale. Luna: And what about using AI to predict job loss before the user even updates anything? I've seen startups that analyze email sentiment or calendar patterns. Lucas: That's a step too far for me. Predictive models based on internal communication data feel invasive. We're talking about observable behavior changes that the user themselves controls — like not logging in or changing their billing info. That's respectful. Analyzing the tone of their support tickets? No. Luna: Fair. So where should a marketer start if they want to build this today? Without platform support? Lucas: Start with a simple list. Go into your CRM and create a 'life disruption' suppression segment. Rule one: any contact whose lead source was a layoff-related event — like a career change trigger — gets flagged. Rule two: if login frequency drops below once per week for two weeks, flag them. Rule three: if billing tier changes from paid to free, flag them. Then suppress all marketing emails to that segment for 30 days. Luna: Manual but effective. And you can automate it over time with workflows. Lucas: Exactly. And the beautiful thing is, you can test it. Run a split test on a subset: one group gets suppressed, the other gets the standard nurture. Measure unsubscribes, support tickets, and reactivation rates after 60 days. I'd bet the suppressed group has higher retention. Luna: I'd love to see that data. Maybe we can find a case study for a future episode. Lucas: Definitely. But for now, the takeaway is: your marketing automation is probably ignoring the moments that matter most to your customers. And fixing that doesn't require a platform overhaul — just a little empathy and a trigger.