Transcript
A (0:00)
The thing about automation is it is prone to the butterfly effect. There's tiny little change that shouldn't be affecting anything. This can have catastrophic effects. You can't predict for it.
B (0:08)
How often do you suggest checking systems.
C (0:11)
That are working, being realistic? Twice a year. You do once you're already almost good enough.
B (0:17)
Every six months is fine. But if there's a dollar amount attached to that automation, how many hundreds of thousands of dollars do you think that that cost their clients? And how many millions of dollars in the future did it cost them? Thank you for joining us for another episode of Special Ops podcast. I'm Emma Rainville, your host here. We give actionable insights to direct response marketers and e commerce sellers. Today we have with us Thiago and Richard from Shockwaves team. And we're going to be talking about how and when to check on working systems. Guys. Far too often we find that our clients will have something automated, that it works. So they left it alone, they never touched it, they never looked at it, and it turns out there's some disaster laying behind it. Richard, I'll let you open up and start that.
A (1:01)
Yeah. So the thing about legacy systems is that you don't look for the problems. If you're not actively doing that, you will not see what is going wrong. 5% of the people who purchased your product, maybe they are previous members, so they're being tagged wrongly and the delivery is not going as it should for them. That's something that can happen very easily with any kind of automated system. Just something that wasn't considered at the time because it didn't exist at the time. Since then has become a issue and if you don't actually investigate, you will not find this. So when we come in for new clients, the first thing we do is this kind of deep dive for their systems. And we see this with pretty much every area we come in with. I mean, it's not always a disaster, it's not always costing them money, but it may be costing them some level of.
B (1:44)
We found enough that costs a disaster of money that we need to talk about it on a podcast. Absolutely. Tiago, how often do you suggest checking systems that are working, being realistic?
C (1:57)
I think if you do it twice, and we may disagree, twice a year, you're going to be better than 95% of small businesses. You do once, you're already almost good enough. Once a year is already pretty decent unless you're going through too many changes.
