Ask HN: Writing automations – serverless or cron jobs?

Hey Hackers, I've got a classic conundrum on my hands: While most of my architecture is about handling events, we've got the first few requests for stuff that's happening at regular intervals, or happens a certain amount of time after an event. One example is follow-up pings after signup. We want to tell the user about additional features in the few days after they first sign up, so we want to emit messages 48 and 72 hours after sign up. My question is whether lightweight serverless tools feel 'ready' to do these scheduled tasks, or if you're still using cron jobs to do stuff like this. I should say that I'm aware of a third path that turns out to be pretty common: instead of follow up messages coming from our own stack, a signup would add someone to a 'campaign' in a CRM tool like Salesforce. That feels clunky, I'm not even an admin on our CRM, so I want to do it from inside my own tools.