It isn’t unusual for martech stacks to have parts with overlapping performance. Whereas some overlap is intentional, an excessive amount of can result in wasted funds, pointless complexity and inefficiencies. Realizing when to consolidate and when to maintain redundancy is essential to sustaining an efficient martech stack.
The worth of addressing overlaps
Martech stacks are consistently evolving. They usually embrace non-martech parts — by design and necessity — to maintain up with the pace of enterprise.
Simplifying a martech stack by consolidating parts with overlapping performance can yield a number of advantages, together with:
- Reducing prices.
- Simplifying technical structure.
- Streamlining regression testing.
- Lowering person enablement wants.
- Making it simpler so as to add or take away different stack parts.
Nevertheless, that doesn’t imply each overlap ought to be addressed. It relies upon. Martech is extra artwork than science.
A rising want
Whereas distributors and platforms have lengthy supplied overlapping performance, this development seems to be accelerating. As synthetic intelligence turns into extra accessible and sensible for software program corporations to combine, overlapping options have gotten extra widespread.
Martech practitioners are grappling with this shift and should rigorously consider all of the shiny issues hitting the market.
Dig deeper: 7 methods for getting essentially the most out of your martech stack
The causes of overlap
There are a number of explanation why martech stacks usually have overlapping performance.
Multifunctional platforms
Many martech platforms are multifunctional, which is a major explanation for overlap. Generally, that is pushed by practicality. For instance, web site uptime displays, net governance platforms (for accessibility checks, damaged hyperlinks, and many others.) and tag auditors should consistently test a web site as a part of their service.
Nevertheless, they serve completely different functions. Solely an uptime monitor ensures a web site is at all times up and performant. Whereas a platform might supply all three providers, many options specialise in one space.
Broad organizational wants
Martech stacks serve organizations with broad wants. Thus, it’s unsurprising {that a} specialised element that finest providers one wants might overlap with parts assembly different wants.
Various stakeholder preferences
Martech stacks additionally serve a broad set of stakeholders. Along with having completely different wants, these stakeholders have completely different preferences. Some stakeholders could also be martech platform specialists who’ve mastered a particular platform or ecosystem and can advocate for these parts.
Characteristic bundling by distributors
Martech distributors generally supply characteristic bundles, which additional causes overlaps. This typically is smart when a company might not want each characteristic. Nevertheless, this typically results in an annoying realization — utilizing a crude, easy instance — that you simply may have to pay additional for a CDP to do one thing seemingly core to its function, like integrating with different techniques.
As Keanu Taylor notes about CDP perform unbundling — identical to AI options — “Distributors in tangential classes add sure CDP capabilities to counterpoint their major use instances and options — takes the unbundling a step additional.”
Dig deeper: Find out how to align processes to drive martech utilization
Assessing martech overlaps: What to think about
Whereas having stack parts with overlapping performance isn’t inherently dangerous, it’s important to justify any overlaps. Listed below are some components to think about when conducting an evaluation.
Stakeholders
Stakeholders ought to at all times be the highest precedence, whether or not the element is a expensive CDP or a $100-per-month web optimization hyperlink checker. They’re those utilizing the element, funding its prices, prioritizing its maintenance and defending its place inside the group.
Product adoption is paramount. It’s troublesome to attain a powerful ROI from a software nobody makes use of or makes use of effectively. That is the place fields that deal with human components — akin to change administration and undertaking administration — can assist.
For example, the Prosci framework for change administration introduces coalition evaluation, which identifies proponents and opponents of a change together with their degree of competence associated to it.
Whereas a proponent of any competency degree can assist facilitate the adoption or sunsetting of a stack element, a extremely competent opponent — no matter their function — can derail an initiative.
Whether or not conducting an overlap evaluation or not, martech practitioners should perceive how stakeholders really feel a few element. Stakeholders can decide whether or not it thrives or flounders.
Different components
Whereas contemplating stakeholders applies to any stack overlap evaluation, the next components might or might not apply in each state of affairs.
- Ecosystems: Native connectors and authorized implementation and upkeep companions are vital. When evaluating parts, take into account how they match inside the broader martech and organizational tech stacks.
- Product roadmaps: Merchandise evolve and will now not meet a company’s wants. It’s also important to think about how a lot affect the group has over product roadmaps.
- Alternative issues: Will retiring a element require a couple of alternative? Swapping one element for an additional ought to be simple, however what if a number of parts are wanted to fill the hole?
- Finances: Platform prices and ongoing maintenance are important issues. Nevertheless, value shouldn’t be evaluated in isolation. The most costly or least expensive choices will not be at all times the perfect decisions. Worth issues—many occasions, you get what you pay for.
- Contracts: Contract expiration dates can affect the timing of any transition work. You have to additionally take into account components like pricing buildings and the way strictly distributors implement contract parameters.
- Different departments: Authorized, procurement and data safety will seemingly have invaluable enter. Martech practitioners ignore them at their very own threat.
This isn’t an exhaustive record of things, however these are among the many most vital.
Dig deeper: The hidden prices of martech sprawl and easy methods to overcome them
Sustaining martech documentation is essential for overlap evaluation. Martech-specific instruments like CabinetM and Martechbase and common IT administration options like StackShare and Zylo can assist.
Nevertheless, in a pinch, collaborative spreadsheets and paperwork in techniques like Microsoft Workplace 365, Google Drive and Confluence will suffice. As soon as the muse is in place, beginning there makes it simpler to justify the expense of a specialised answer.
Doc findings and selections for every element to extend the trouble’s long-term impression.
Definitely worth the effort
Evaluating stack overlaps is important work. Whereas more difficult than it appears, it helps reassess previous selections in gentle of current situations and wishes. It additionally offers invaluable perception into stakeholders and the general stack.
Dig deeper: 5 ‘must-dos’ when reviewing your martech stack
Contributing authors are invited to create content material for MarTech and are chosen for his or her experience and contribution to the martech neighborhood. Our contributors work underneath the oversight of the editorial workers and contributions are checked for high quality and relevance to our readers. The opinions they specific are their very own.
