Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / How Marketing Automation Workflows Lose Leads at Midnight
Transcript
- Lucas: So, you’ve set up a beautiful marketing automation workflow. A lead fills out a form, gets a score boost, enters a nurture sequence, and eventually a sales rep gets notified. But here’s the thing — the whole chain might be breaking at midnight. Luna: Midnight? Like literally when the clock strikes twelve? Lucas: Exactly that. A lot of platforms — HubSpot, Marketo, Pardot — have what I call a 'midnight reset' problem. They schedule trigger evaluations or batch processes at the start of the day, usually midnight or 2 AM server time. If a lead does something at 11 PM, the workflow may not fire until the next run. Luna: So the lead waits. Maybe hours. In a B2B context, that could be the difference between hot and cold. Lucas: Right. And the delay is invisible to marketers. The workflow eventually fires, so reporting shows 'automation worked.' But the conversion that could have happened overnight? Gone. Luna: Do you have a number on how much this actually costs? Lucas: I looked at a case from a B2B SaaS company — let's call them CloudOps. They run HubSpot. They had a lead-scoring workflow that re-evaluated scores every 24 hours at midnight. Leads that hit a threshold at 8 PM wouldn't get assigned to sales until the next morning. They audited it, switched to near real time triggers, and saw a 12% lift in lead to opportunity conversion within a month. Luna: Twelve percent just from changing when the workflow runs? That's massive. Lucas: It is. And it's not uncommon. I've seen similar patterns in Marketo where smart campaigns are set to 'run once daily' instead of 'run on every trigger.' The logic is there, but the default scheduling masks the delay. Luna: So what's the fix? Do you need to go fully real-time? Lucas: Not necessarily. The fix is to audit your trigger cadence. For high-intent actions — demo requests, pricing page visits, cart abandonment — you want near real time. For lower-intent stuff like a blog download, daily is probably fine. The key is knowing which is which. Luna: And how do you audit that? Most marketers I know don't even think about the schedule tab. Lucas: Start with your highest-converting workflows. Look at the 'schedule' or 'trigger settings' section. If it says 'run daily at midnight' or 'evaluate every 24 hours,' that's a red flag. Then check the time stamps in your CRM. See if there's a gap between when a lead took an action and when the workflow fired. Luna: So the data tells the story. But doesn't HubSpot have a 're-evaluate each time' option? Lucas: It does. But many people don't use it because they're told 'it uses more API calls' or 'it could overload the system.' In practice, for most companies, the trade-off is worth it. CloudOps saw a 12% lift with no noticeable performance hit. Luna: That's a compelling argument. And it's a free optimization — just changing a setting. Lucas: Exactly. No new software, no extra headcount. Just operational awareness. And that's what I love about this space — often the biggest gains come from fixing the plumbing, not adding new tools. Luna: Speaking of fixing the plumbing — if you're finding these conversations useful and you've actually applied something like this at work, listener support is what keeps this show ad-free and independent. We're over at buy me a coffee dot com slash fexingo. No pressure, just if you've gotten real value. Lucas: Yeah, we hear from listeners who've tweaked one workflow and seen results. That's the stuff that keeps us going. And it means we can keep diving into these operational details without selling anything. Luna: Anyway, back to workflows. So after you fix the trigger timing, what's the next thing to check? Lucas: The next thing is what I call 'the midnight leak' — but this time it's about time-based gates within the workflow itself. Some workflows have a 'wait for X hours' step, and if that step spans midnight, the timer might reset or the condition might re-evaluate in unexpected ways. Luna: Oh, that's sneaky. So a lead enters a workflow at 10 PM, gets a 'wait 4 hours' step, but at midnight the system resets and the timer starts over? Luna: Exactly. Or worse, the workflow assumes the lead is still in the same state, but the reset triggers a re-evaluation that drops them out. I've seen cases where leads were removed from a nurture sequence simply because they entered after 8 PM. Lucas: That's a bug, not a feature. How do you catch that? Luna: You test it. Create a test lead, trigger the workflow at 11 PM, and watch what happens. Check the activity log the next morning. If you see 'removed from workflow' with a reason like 'timeout' or 'condition not met' when it should have met it, you've found a leak. Lucas: So the fix is either to change the wait step to use 'business hours' logic — if the platform supports it — or to shift the workflow to a trigger-based model that doesn't rely on daily resets. Luna: Right. And some platforms let you set a 'time zone' for the workflow. That helps, but only if your leads are in one time zone. Lucas: Good point. If you're a global company, midnight in New York is noon in Sydney. So you need to get smarter about using relative time delays rather than absolute timing. Luna: I think a lot of marketers set up workflows once and never revisit them. They assume the software handles the edge cases. Lucas: That's the danger. Marketing automation is powerful, but it's also full of hidden assumptions. The midnight reset is just one example. There's also the 'first day of the month' reset, where monthly evaluation workflows misfire because the calendar flips. Luna: Oh, I've seen that! A monthly lead scoring model that recalculates on the first of the month, but the data cutoff is midnight — so leads from the last day of the previous month get scored with incomplete data. Lucas: Exactly. And that can cause leads to get the wrong score for an entire month. By the time it's corrected, they've either been over-nurtured or ignored. Luna: So the takeaway: don't trust the default schedule. Audit your trigger logic, look for time-based gaps, and test with real timing. Lucas: And if you find a leak, fix it. The ROI is immediate. No new budget needed, just a few hours of attention. Luna: Alright, so for next episode, I want to dig into another hidden leak: how your automation handles returning visitors versus new ones. Lucas: That's a good one. The 'welcome workflow' that fires for someone who's already been a customer for six months. Luna: Exactly. See you next time. Lucas: Take care.