IN THIS ISSUE 🌱
Good Morning {{first_name}}!
It’s Fri(yay) - and that means it’s time for your Revenue Play - an issue where I share some stories from my own career as a data nerd.
This week, it's the messy lifecycle data living underneath it. (I know. Not the sexy answer. But it's the right one, and your wallet will thank you later.)
Let’s dive in.

THE AUTOMATION THAT WASN'T ✨
THE SITUATION
An automation isn’t just an automation
A client once came to me, completely frustrated that a workflow wasn’t working. Nothing was triggering, sequences and numbers were at a nice big 0%.
The idea that they’ve invested in a solid tool, built out the workflows and wanted things to “just work” was becoming a complete nightmare.
And once she flagged it to me, she had built a workflow that eliminated thousands of people. On paper, everything looked like it should be working.

FILTERS WILL MAKE THINGS WORSE AT TIMES 🌊
THE GAP
It’s almost always the filters
The thing was - everything was fine. The sequences were fine, the tool was fine, and the messaging was spot on.
But the filters? That was the problem. Filtering on top of broken data fields? Even worse.
Lifecycle stages were inconsistently defined. CRM sync was patchy, so customers were not syncing over from their ERP.
Event taxonomy was all over the place. So when the automation fired, it was firing based on signals that didn't actually reflect where the contact was in their buying journey.
We see this constantly in 2026. Teams feel like their automation is "not working" and immediately start blaming the sequence or the platform. Rarely do they look at the foundation.

QUESTION THE FOUNDATION - ALWAYS ⚡
THE FIX
It was never about the obvious fields…
We went back to basics. Together, we rebuilt their event taxonomy so behavioural signals actually meant something. That included double-checking syncs from ERP and Salesforce (turns out, there were 243 issues - just waiting to be addressed).
Then, we tightened their lifecycle stage definitions so contacts were moving through stages based on real actions, not accidental ones. Turns out, sales were skipping SQL altogether and moving MQLs into opportunities.
And we cleaned up the CRM sync so the data flowing into the automation was actually trustworthy.

KEEPING UP WITH AI AND DATA 🧪
SPONSORED POST
Join 2M+ Professionals Getting Ahead on AI
Keeping up with AI shouldn't feel like a second job.
But between the new tools, viral posts, and endless hot takes, most people spend hours every week trying to figure out what actually matters.
The Rundown AI fixes that.
It's a free newsletter that gives you the AI news, tools, and tutorials you actually need to know. All in just 5 minutes a day.
Over 2M professionals at companies like Apple, Google, and NASA already read it every morning to stay ahead.
Plus, if you complete the quiz after signing up, they'll recommend the best tools, guides, and courses for your specific job and needs.

AUTOMATION THAT FINALLY MADE SENSE ⚡
THE RESULTS AND TAKEAWAYS
Always audit and track success
Once the foundation was solid, the existing automation started performing the way it was supposed to. Directionally, the team went from questioning every trigger to actually trusting the data they were seeing. That trust shift matters more than people think.
When you implement something like this, always have a period of 30-60 days where you track and audit - and verify - that things are indeed accurate.

CLOSING THE LOOP
💡 Final Thoughts
TL;DR
Before you rebuild your sequence or blame your platform, pull your lifecycle stage data and ask: are contacts moving through stages based on real purchase behaviour, or based on whatever someone clicked on a Tuesday? If you can't answer that with confidence, that's your gap.
And always question whether marketing and sales are speaking the same language. In 95% of cases, they aren’t.
How was this issue!?
P.S.
Has your team ever blamed the tool when the real issue was the data underneath it?
Hit reply. Yes or no. I'd love to know how common this actually is.


Until next time!
Ships three times a week.


