15/08/2024
Author:
Anthony Botibol CMO Relay42 |
No organization is perfect. Within every company, there are inefficiencies and opportunities to do things better. Solving some of those issues requires a certain individual within the business to think strategically outside of their own department and be brave enough to bring together the relevant teams, understand how technologies are being used, and find out any hidden processes to solve a cross-department business problem.
The need to invest in a Customer Data Platform (CDP) is no different and requires a leader that has buy-in right from the top, as well as the trust and backing from the business to go and make a transformational change. After all, by investing in a CDP, you will need to leverage financial and operational data; as well as marketing data leading to a CDP champion inside the business who needs to identify and understand the technologies, the data that resides within them, and the processes that are involved in making those technologies work for the business.
Here's a simple scenario that we’d all like, as marketers, to be able to implement at scale:
None of this should be difficult in 2024 – today’s marketing technologies can accommodate all of that!
For approximately $20,000, you can get your web personalisation up and running, (integrated to your ESP) and you are potentially covered for the first and second stages. Depending on additional ancillary features in your ESP, or personalization/CRM tools, you may also get to stage 5, and 6 too.
However, it isn't that uncommon for email marketing and ecommerce/website teams to sit in siloed worlds with competing priorities who don't talk to each other. They are wedded to their own tools; perhaps built a custom CMS that struggles to integrate with an ESP.
The result is a human ETL solution to have an actual individual employed to be extracting, cleaning, manipulating, standardizing and joining databases to derive answers that lead to more questions and an eternal loop of manipulating data that is messy and unreliable at source.
This person, or team, could be Data Scientists and Data Analysts who groan at the menial list creations that the marketing team wants daily, weekly, monthly (hourly even), or prepare data for dashboards.
Equally, the burdens could sit with the IT department to provide data access and exports, write custom scripts to automate some slick efficiencies; but, at the end of the day, it is all highly inefficient – simply due to the fragmented way of working in the business. This means that your customer data is unusable, or highly inefficient when attempting to activate the data.
With many departments impacted, the project to solve those inefficiencies with a CDP requires input from many business stakeholders and departments. This is where kick-starting and managing a CDP project starts to appear daunting.
Depending where you look, there are 5 critical elements to a marketing transformation.
Each of these 5 elements have the potential to make or break a successful project, and all need to move together at the same pace.
In my opinion, People and Culture are the first two elements that usually impede the success of a CDP or Marketing Transformation project due to competing workloads & priorities (i.e. People), and attitudes & expectations (i.e. Culture).
Equally, if there is no champion for customer experience at board level (CMO, CCO, CXO,...), then a project like this will either fail, or has to move very slowly at the same pace as the culture change will allow. A sales-led company cannot become customer-led overnight – as much as a product-focused business often struggles to change to a sales-led business.
All the elements must therefore move in harmony, at the pace of the slowest element for a truly transformational, business-changing project (which a CDP is!) to be effective. But, there is a solution to those inhibitors!
Read on…
A full transformation in one big project is not always the best idea. When investing in a CDP, the more data you throw into it, the more it will cost.
CDPs pay huge sums of cash to Amazon, Microsoft, Google and other hosting providers to store that data. They can lower costs through economies of scale, but there is a baseline. If you start small, you should also pay small and use that small unified dataset to solve a business problem, and measure the result.
Back to the example before, let’s imagine a scenario where unifying ecommerce, email, CRM and web behavioral data replaces an employee’s current role (or department) by removing manual ETL work, or perhaps reduces one business day of work for the IT department on data extracts. Here, a simple equation to compare the cost of the small implementation with the reduction of people hours is an easy one to do, which is one cost justification.
On top of that is the less tangible benefit of those people and teams being able to focus on other jobs that are actually way more valuable and strategic – remember, they too will have a CDP to work from and devote more time to analyzing patterns rather than menial data enrichments. That is, unquestionably, time better spent.
Of course, for enabling cross-channel orchestration of the customer experience, a CDP should connect to your marketing channels as well. This is where team siloes need to be replaced with cooperation on some shared, non-competing KPIs.
That cooperative approach can map out a cross-channel customer journey that fully considers the others’ objectives to achieve the common goal. So, if the business is not ready for that at a large scale across many teams and departments, that is okay.
But, to justify a CDP or transformation cost to your board, there needs to be a lot of upside in whatever business plan you propose. Thinking in terms of small use cases that a CDP can optimize for, is therefore the way to build out that plan, and map to cost/revenue calculations.
Just presenting that you’ll be ‘improving results by creating a real-time, personalized experience on every channel’ is just aspirational and unquantifiable, and so you need to start with practical use cases in your industry. For example:
It is important to maintain your focus on practical use cases which come down to cost, revenue, time, resource and processes.
By understanding, across each department, where those inefficiencies are, where cost is being accrued, where revenue can clearly be improved, you can almost create a line-item report of the use cases alongside the results, and a time frame to achieve them. This makes it easier to pitch for a smaller budget to solve for the most critical use cases and which impacts smaller (but still vital) parts of the business.
Layering in aspirational hypotheses and use cases with assumed revenue or cost calculations can also be included to show the full potential of ROI, but must be secondary to the practical cases.
If you start small with a POC or phased approach to a CDP deployment, perhaps one brand, one territory, one branch or even one team, then you can more easily present all the components for a compelling case why a CDP investment is justified.
However, don't ignore the bigger picture entirely. This small implementation you have secured sign off for is approximately a 12-month time frame to be able to collect the results and improvements from your CDP use cases. (Though, I have witnessed big-scale enterprises achieve a kick-off in three months as well!)
If that is not going to wash with the immediacy of your board, then a paid-for POC is a fallback option, although that can often require a vendor to devote time to build an approximate of 80% of the full solution for a fraction of the cost – and with risk.
In this case, there needs to be a good collaboration between the CDP vendor and the enterprise with expectations, milestones and expected results shared upfront. This usually requires commitment to move forward if agreements are met – which means that there would be no going back unless it does not work out, and then that is the great de-risk for your business, and the vendor must honor that.
This can lead to an unhappy business that is tied into investing in a CDP solution that they have already lost confidence with.
So, this is why the partnership dynamic is important. The vendor needs to know that you have their back, and you need to know they have yours too. And, you are both willing to do what it takes to achieve the common goal - success and a long-standing, profitable and beneficial relationship on both sides.
A CDP is not a product you buy and forget, it is indeed an ongoing practice and transformation, so work with vendors that you trust (and vendors that have the market trust!), and do not make the purchase solely a transactional one.
It is not practical for a business to invest in a solution that will deliver the whole scope of use cases you need in one huge implementation – I call this ‘The Moon on a Stick’.
Before CDPs came into existence, if you wanted to unify all the data from customer data-holding systems, then you would undertake a 12-18 month bespoke SQL database build, some custom built connectors and ETL tools to run quite a fragile solution – all of which would be delivered to solve every use case and business requirement you need.
However, the danger was that businesses had already evolved by the time the solution was delivered.
This exists today as well with many CDPs looking to deliver on every use case in one monolithic solution. I would not say that they are all negative stories, but we have a much more immediate, agile and accountable tech world today; and a CDP should be implemented in that way too to ensure quicker ‘Time to Value’.
P.S. I can tell you through experience, seeing both ways (firsthand!) that the agile, phased approach is 9 times out of 10 the better option than getting delivered the proverbial 'Moon on a Stick'!
Use cases are extremely important in kick-starting your CDP journey, and so my advice is to be militant in sticking to the phased approach and not trying to run too fast. You can have use cases live and running in a couple of months, if you are ambitious, even weeks! Start deriving value quickly by getting four or five of your top use cases up and running in the initial phases, and build on those use cases over time to create compounding value. Don’t let other departments and teams, or the board, veer you off course.
Prioritizing the most impactful use cases and phases from the start is a prudent choice.
Finally, be brave, you're on a quest!
The marketer with the bravery to take on the transformation project needs to always think about it like a quest. Knowing that, they will be putting themselves in unfamiliar territories and departments and learning many new things along the way, collecting stories and searching for a prize.
At the end of the project, they may move onto bigger and better things, new roles (and probably a promotion!), or can go back to their home in the shire (marketing team), ready to benefit from clean, trustworthy and actionable customer data, with highly efficient automation and insights.
Every quest starts somewhere, but navigating a quest gets much easier with the right guide. Our team of consultants at Relay42 aim to be that guide to our many great customers and CDP users.
So why not start with a demo or a chat?