HomeCase studiesKudobuzz
SaaS
Kudobuzz
An event schema and a lifecycle stack, built together so they spoke the same language.
kudobuzz.com, as it looks today.
What I did
Audit before anything else
I audited what was already installed before proposing anything new. Most of it was not wrong so much as undefined.
An event schema for activation and acquisition
Written first, implemented through Tag Manager, with the views, goals and weekly and monthly report templates built on top.
Map every comm before writing a journey
Email, SMS and push, catalogued as they stood. Only then did I define the user stages and build nurture campaigns against each one — which is how the automation and the analytics ended up using the same definitions.
What came of it
Results.
Figures belong to this engagement and this client. Nothing here is an average or a benchmark, and no number appears without the work behind it described above.
“They connected and worked with our team as if they had been with us since the beginning. They are skilled analytics and traction testing experts, and provided great growth marketing training as well.”
What I took from it
Lifecycle automation built before the event schema will always drift from it. Build them in the same fortnight or you will reconcile them forever.
Something similar, at your company?
If I am not the right fit I will say so on the call, and tell you who is.