Are You Paying Twice? Find Redundant Software Spend Before 2027
Join Michael Shields, VP of Procurement, Tommy Noonan, VP of Product, and Kory Lanzel, Director of Procurement Services, to learn how to uncover overlapping software spend and turn the findings into a plan before the new year.
The team will share findings from Tropic’s analysis and show how to identify overlapping SKUs in your contracts, understand their cost, and prioritize opportunities. Through real-world examples, they’ll explore how to assess what your business needs and use upcoming renewals to eliminate redundant purchases, consolidate capabilities, or negotiate a better fit.
Get a live walkthrough on:
→ Spotting overlapping functionality within the software you already own
→ Deciding what to keep, consolidate, or cut
→ Applying real-world approaches to reducing redundancy through renewals and negotiations
→ Getting started with Tropic’s Redundancy Analysis to assess your own tech stack
Everyone, thank you for joining today. Excited topic today, honestly. Like, this feels very timely.
What's interesting is we'll get into this a little bit, but this idea of consolidation and and and pain multiple times, like, it's been around, but clearly is accelerated and and become more prominent in its importance over the past, you know, few months, and we'll dig into that.
And and maybe I'll start off by saying I fully acknowledge that, you know, some supplier redundancy can be intentional. It can be strategic.
You know? So said another way, dual sourcing can protect against risk and can keep, you know, us in a in a competitive environment, but that's not what we're talking today. We're talking about the unintentional kind. We're talking about what the outcome of what is happening despite our best efforts because of the situation we find ourselves in.
So it's it's not uncommon at all. In fact, it's quite common, and it's growing. And it represents, definitely a a large opportunity for for savings, for, better strategic deployment, for consolidation. So as...
Whereas before, you know, you know, it took some concerted efforts to identify. Now Tropic has released functionality that that really highlights these opportunities. So today, we're gonna show you some examples. We're gonna show you what it looks like in the product, and we're gonna talk about some best practices as well.
And with that, I'll introduce the true stars of the show. First up, our VP of product, Tommy Noonan. Tommy, I have to say, I thought you lived in Georgia, but then I went to fact check myself and checked your LinkedIn profile, and it says you live in Charlottesville, which I assume was in North Carolina. I'm thinking, oh, that's great.
I'm gonna be in North Carolina next month, but then it says Charlottesville, Virginia. So I don't know where you live. Maybe clarify that just, you know, from the get go.
Yeah. Well, sounds like the fact checkers have been working overtime today, but I am in Charlottesville, Virginia, not North Carolina. I am originally from Georgia, though. So there there are some partial truths to this.
Okay. And then another thing I I didn't know about you is that you did your MBA at MIT. I mean, it's not quite the same as MBA from Arizona State like I have, but, like, you know, I guess that's pretty cool.
Anything you wanna say to the group here, Tommy? What you're looking forward to most?
Yeah. Only that I'm most excited to share some of the data we've been looking at around this. We've looked at redundant spend across all of our customers. The most expensive overlap on a customer by customer basis typically wasn't the one they expected, and it's usually unique to each individual customer. So excited to show you a little bit more about this later in the presentation.
Okay. Cool. And then next up, we we have Corey Lanzel. Corey, you know, know, you know, you and I did a webinar, like, two years ago, and Yep. It was one of our highest rated webinar... Webinars ever. So it's... I'm sorry it took us two years to get back on the same schedule. I know you're a busy guy.
He is the director of procurement services, and there's no confusion on where he lives because he's the only other Tropic employee besides myself That's right.
To to reside in Utah. So which, by the way, we just got our first snowfall yesterday.
Yeah. Was gonna try and make a joke about having the first snow of the year yesterday, at least down here in Salt Lake Valley. Excited for ski season. As far as, like, this presentation's concerned, I have a couple of real life examples that our team... Our, our really wonderful procurement services team, has been able to generate on behalf of our customers to walk through a little bit later, but excited for the overall conversation. And and, yeah, I was gonna wear my Utah hat today, but I decided against it.
Hey. Number two, congrats. Congrats.
Well, look. You know you know, Corey, for years, you and I have actually partnered. Even though this is only the second webinar that we've done, we've partnered together and met with customers talking about consolidation and redundancy specifically in their tech stack. So it's not a new concept.
I...
Kinda looking back, I feel like it started in twenty twenty two ish. And if you recall, in in industries, you know, money was really cheap. And so prior to that, it was a little bit of a free for all, and it led to a bunch of bloated text acts. But then but then there was, like, this concerted effort.
And so over the past few years, we've working on it. And yet over the past twelve months, even though there was this concerted effort, I'm not gonna say a lot of that work was undone, but it feels like this has kinda resurfaced again in in an even bigger way than it was before. So in your in your opinion, what's driving that?
You know, I think it really depends on your your business need, if you will. Like, I I have a background, all sorts of different, industries, right, where, you know, redundancy was important to have for business continuity. Right? If you were at a winery and you needed labels for your wine bottles, you you needed to have a couple providers in case one of them went down or, you know, had, delays for whatever reason.
And so, like, I think there's this big difference between intentional or, you know, trying to be vendor agnostic, like redundancy versus the unintentional, right, which is where maybe you have two different teams or sometimes the same team. Maybe it's a really big team with the same goal using multiple tools that do pretty much the same thing. And, you're not benefiting from the economies of scale from the discounting that you could potentially be achieving. You're just...
You know, you're you're buying from two suppliers for maybe little to no real reason, like, real business reason. Right? And so I think that's kind of the difference. And, you know, one of the things, you know, I I think we're seeing lately is, right, being a little bit vendor agnostic when it comes to, like, the major AI tools like OpenAI and Anthropic.
Right? And so, being being able to test on on both, you know, systems, if you will, and and having that available to you is really important as that space is just moving so quickly. Right? And I think there...
It's just the speed aspect now, of some of the important vendor agnostic and or, you know, redundancy...
Like, good redundancies, if you will.
Yeah. The...
Oh, sorry. I was gonna say that the OpenAI and Anthropic, example is a really pertinent one for us. Like, we're always going to be involved with both of those suppliers, testing different workflows in our app on their different models, different workflows, etcetera.
Some of the maybe non obvious ones I'm starting to discover as a product leader is just the encouragement of our team to explore different tool sets based on some of the new capabilities these models are providing into the SaaS ecosystem in general. So I think of it as an investment. We want people to be thinking about, you know, what are some new tools that might be redundant with our existing ones but might eventually offer us a better solution in the long run.
Yeah. That's interesting. Kinda echoing on on what both of you has said. Number one, it sounds like, Tommy and and Corey, you're saying, like, there's this redundancy from a risk mitigation perspective when we talk about, you know, the LLMs.
But in this world of AI, things are changing so quickly that, you know, the the supplier supplier landscape is changing, which means there's probably, you know, new opportunities. New suppliers are popping up all the time that people are are trying, which, you know, inevitably, if you have...
You kind of...
And oftentimes, they're working in a little bit of silos, and maybe they just start with a little pilot and it didn't go quite through the procurement system. And so what you end up with is you end up with multiple tools that are...
They're doing a lot of the same things. So once again, it's this difference between intentionality, which, you know, if you're, you know, a product leader and and you're leveraging AI in your tool, that may be a good thing.
But then as a result of AI changing the landscape so much that it's it's creating a lot of this blow, redundancy, that sort of a thing.
Yeah. I mean, you know, I I think as long as, there's a real business reason or business case for what you're doing and and things are explainable, right, I think that goes a long way. I know when a CFO or, like, a customer, for example, asks, questions around, like, are we using multiple tools in this space? I think the last thing you wanna to be is, like, be unable to answer that question, for the reasons why.
Right? And so I think that's really important. Right? Different teams have different use cases. Different teams have different needs.
There's different speeds that, you know, different companies work at.
There's different reasons that in your industry, you might need backup for different services. Right? Maybe your your product is a business critical product for other products, and, like, you can't go down, for that reason. Right? And so I think a lot of it comes down to being able to explain the reasons why you're spending money the way you are across different tools.
So so you almost wanna be, like, separating the... And maybe it's not the the justified, the strategic versus the, you know, unintentional and maybe unjustified, and that's a part of probably the value that procurement can bring. And it's really interesting you say that because, you know, there's there's a big focus on data right now. In fact, like, I've been to a couple, like, conferences and events where the whole focus on... Is on data.
And last week, I was at a conference and decided to make this the focus of my presentation. And I shared how when it comes to data, you know, they're kind of like the...
I think about in four different...
Don't if it's, a checklist or or four steps. But but number one, we need to make sure that, like, our data is clean. And the and the the...
I think some people think of that as, like, you know, a one time thing, but the really...
The reality is we need to have processes that are constantly cleaning up because day...
Data is one of those things where it's like, you know, a garden left unkempt. It can just quickly become over...
You know, overcome with, like, weeds and, like, you know, not be great. Right? So once we once we have the process that's constantly cleaning up, we need to connect it all together. I feel like, historically, it's lived in kind of silos.
You have your information, your ERP. You have your information, your CLM. You have your, you know, Slacks. You have your emails, your recorded calls.
Like, how do we...
In the world of MCPs, how do we, like, connect all that together so as talking?
Number three, we wanna make sure we have access to the right data, meaning, like, we wanna make sure we're pulling in public data. And, of course, elements are great at, like, helping process both the internal and the external data and making sense of that, but they are and will always be limited by what data they can access. So how do we make sure we're licensing the right data? Benchmarking being a a great example.
And then step number four, and, Tommy, this is where I would love for you to weigh in, is, you know, is not enough to just have access to, you know, the right type of data and clean data and connected data. Like, we we need to have the data pushed to us. And so maybe I would love for you to kinda elaborate on why your team has been focused on this idea of proactive signals and and maybe what you're hearing from procurement leaders telling you that it's it's not enough to have this data. It needs to be pushed to us in a timely manner.
Sure. There's two big reasons to me why pull doesn't necessarily work over push. One is timing is everything, and two is the landscape isn't static. Now timing is everything is a little bit more straightforward.
If you discover a consolidation opportunity thirty days before renewal, you know, good luck. You can't get off that tool, migrate the internal controls, build consensus, etcetera. Now it's not static. I think it's a little bit more interesting.
We we just talked about kind of the proliferation of AI tools in the market, and this happens with both your existing stack is adding new capabilities at a lightning fast rate. Suppliers that were not competitive years ago, months ago even, are competitive today.
And then the second piece is people are using more and more and discovering more and more tools. So pulling a report last quarter does not reflect the tech stack of your redundant capabilities today. And and that's why it's extremely important for us to, you know, continually update and continually monitor the capabilities of all of these different products out there.
Yeah. It's interesting you say that because I... I'm definitely feeling that from my perspective. Like, I think, historically, what I would probably do is... And and, obviously, if it was a key or course... Or or a a key supplier, I might be, you paying know, a little more attention and doing QBRs. But for a lot of them, I was trying to engage thirty to ninety days out from a renewal time. And let's be honest, like, if that's when you're looking at the day and you're like, oh my gosh. There's a consolidation opportunity for, you know, me here.
You're almost kinda too late to the game. Right? You need to be giving yourself that time. Whereas if it comes to you and said, hey. This new product was released by a certain customer and and, oh, by the way, that makes, you know, an opportunity for rationalization or consolidation available, then you can start planning for that. You can you can do a a a strong evaluation, and and kinda give yourself a lot of that time.
Yeah. I think to to kinda echo a couple of points made there, you know, Intropic is helping with this, obviously, with redundancy analysis, you know, kind of in the in the platform is is the ability to research what different tools have started to dip their toes into feature and functionality wise, like you're saying, and and where they're kinda playing in. And the examples I have later, you know, it's it's companies that were maybe historically doing a couple things really well that have decided that to stay relevant in their space, they need to start doing a new thing that someone else has obviously historically been very good at.
And so, like, they kinda creep into each other's different, like, specialties, if you will. But then it off...
Also then offers you these new opportunities to explore, hey. Maybe we don't need both of these tools anymore. We can consolidate it to one. I think that's what, you know, I would have killed for something like this five, ten years, two years ago, right, where it could point me in the right direction of here's the opportunities they...
You know, at at face value, like, you're gonna have to figure out what is overlapping with with, you know, the other, if you will, and and you're probably gonna have to have some conversations internally. But it's a great starting point, in my opinion, and the ability to kinda dig in and and figure out, where those overlaps are, without having to, you know, have a 100 conversations internally on, like, you know, what tools people are using or or why, that kind of thing. And so I think that's really helpful.
Yeah. Very interesting. So before we get into, you know, to you you, Tommy, and kind of, like, talking about, like, what the contract show, I wanted to do a quick poll because I think for some people and for myself included, like, this is one of those things where up until recently, I wasn't even really aware or maybe I had looked at a couple years ago. And as what's been hopefully be... Been made very clear, it's not static. It's changing faster than we can keep up with. But, like... You know, so how many... How much overlap do you think you have? Right?
And this is one of those things where I I hope you're transparent and kind of honest with yourself. And, of course, there's a not sure button. Right? And I think for me, I I probably would have either picked one of the options and then been wrong or or been like, yeah.
I'm actually not quite sure. But...
You know? So this is what we wanna kinda...
One of the big takeaways today is it may be bigger than you think it is. You know? And and even though I would argue we want these data points pushed to us in a timely manner so that way we can be addressing them and exploring them as we pop up, which is going to ensure the most thorough review, ensure, you know, we can prioritize accordingly and give ourselves the the right time, It's also timely in the sense that we're coming up on budget season and...
Or actually, we're already in the throes of budget season, which, you know, I think budgets right now are are kind of getting attacked from a lot of different ways from, like, the move from, you know, from, like, seat base as we're talking about software to consumption based. Of course, you know, there's...
We're trying to make room for more AI spend, and some of the other stuff is kind of consolidating. So what we don't wanna do is kinda throw out the good with the bad. What we don't wanna do is, like, not push back from a position of, you know, strength and and from a position of knowledge. And, like, to your point, you know, Corey, you know, when when we're asked these questions that we can provide the data and intelligent data about it.
So really interesting to kinda see these see these results, you know, pop in. So I think this is a great segue, Tommy, for you.
You... You're, you know, our VP of product. You have access to, obviously, tons of data across, you know, hundreds of customers, etcetera. You know, how how much of this is actually showing up in contracts?
Yeah. Thanks, Yields. I am going to share screen a little bit and walk through some of the kinda interesting things that we found, kind of running our redundancy analysis across all of our customer base.
So the the first piece here to answer the poll question in general is that when we looked across our customer base, eight suppliers was the median number of suppliers that had that full or partial overlap with another SKU from another supplier.
Now a common thing that, we're gonna see through a couple other data points in this presentation is this this does seem to affect enterprise more than SMB. More on that in a second. But even when we looked at the SMB overlaps, there's still always a significant portion of suppliers with overlapping capabilities that that people are paying for. The other interesting thing is that there's over half of our customers. We're paying over three suppliers for the same capability. So the topic analysis doesn't just look, you know, at two companies together. They'll look at the capability itself and scan across all of your suppliers till it finds a match.
Now we looked at how many suppliers overlap, but let's talk about the actual dollar figure here.
If we looked at 20 companies, about five of them have an overlap of over $250,000 in annual spend that that they need to look at. And if we extend it to two more... If we go to a 100,000, we add two more companies to that list. So there's a a meaningful portion of our customer base is paying, you know, very high numbers for the same capability across suppliers.
This was another thing that we found very interesting. So even though the spend under management for mid market and enterprise is fairly close, the amount of overlap in the enterprise skyrockets. So enterprises spend 1,600,000 more on SaaS than our mid market customers, but they have five x the number of overlap. And this can be driven by a number of things. The types of suppliers that enterprises tend to choose over a mid market can potentially have more functionality and capability.
The internal, you know, controls and just larger teams of an enterprise make it more difficult for people to understand the tools that other departments, etcetera, are using.
But either way, a a huge jump in redundant spend when we go into the enterprise segment. The other thing that kind of harkens back to what Corey, Shields, and I were speaking at the beginning is that suppliers are really growing into each other's space. This idea of cross category overlap, so a supplier in one category like sales, for instance, and a supplier in another category like marketing, are now having overlapping capabilities in ways that we didn't see, you know, even just several years ago. So 84% of our companies have this type of cross category overlap. And you can see to the right on where some of the most common over split category overlaps are happening.
Can can can you go back to that slide really quick? I was just trying to absorb it, because it's interesting you have collaboration operations, you know, two two to three x. I'm actually surprised seeing, like, some of these other ones, like marketing and sales a little bit lower. And I wonder if if that... If they catch up because as... To your point, like, you know, as companies are leveraging AI more and it's easier for them to kinda roll out new products, I... I'm expecting this to increase for some of these, you know, categories with smaller percentages.
I I I... I'm guessing on the on the spot, you don't have the data, but it would be really interesting to compare this, you know, in six months or even a year and and see how how this changes. But very interesting to kinda see the breakdown here.
Yeah. For sure. I I too was actually surprised at the marketing and sales number. What's interesting is that the marketing and sales number for enterprise is up closer to that 50% mark that we see with collaboration and operations, but it's much lower for the mid market and SMB. You know, whether that's the products and suppliers that mid market and SMB are picking versus enterprise, I don't know. But I I I too would like to see how that changes. I I have a feeling that that number is going up and that SMB and mid market are gonna catch up to enterprise pretty quickly.
Yeah. And the IT and the security one's kind of interesting. I'm actually not surprised by this because it feels like sometimes, you know, in in this world that we live in, there's actually a lot of risk, taken by, you know, leveraging newer suppliers that maybe haven't, you know, been around. And and, of course, we've seen, you know, some issues with the the tech industry over the past week with, you know, downtime and stuff like that.
Whereas...
So if you're an IT or infrastructure security, I'm guessing maybe the the the pace is a little bit slower intentionally so. But I also know, you know, having, you know, seen some of, like, the macroeconomic trends, there's a massive amount of investment being funneled into this last category. So that might be a lagger, but I expect that to change just not as not as quickly. So that that actually does make sense to me.
Yeah.
When I look at some of the underlying data in these categories too, I I think it points to a lot of the strategic redundancies that Corey spoke about as well. I think a lot of people are intentionally buying some redundancy across DevOps and IT infrastructure in order to, you know, effectively deliver their products. Yeah.
Awesome.
And moving on, I I think, you know, we hear from a lot of procurement leaders that, like, you know, everybody assumes they turn on redundant spend, and we start to show, okay, Google and Microsoft overlap, Zoom and Google Meet overlap, project management, Asana, monday.com, etcetera overlap. And I think that that's largely true. Everyone typically has a lot of these usual suspects of office suites and platforms, but that's not actually where a lot of the spend that's driving up these numbers is located.
What I thought was very interesting about this is that looking across a lot of the customers, everybody's highest numb...
Redundant spend pairing was typically unique to them. There were 64 different categories represented in this. And, you know, a a lot of times it was, you know, I...
There wasn't a a lot I could say around, oh, everybody has this one product SKU that is, you know, causing redundant spend. It was very unique to the individual tech stacks that, you know, was driving this.
Yeah. And and what I'll say is definitely agree with everything you said. Corey, I don't know if you recall this when when we were, you know, running through some of these exercises with customers, you know, over the past couple years. But what was interesting is earlier on when...
You know, going back to, like, 2022 and 2023 when there was this initial push, they were, like, looking for that low hanging fruit where, you know, it was, you know, not the usual suspects, but it was more kinda the obvious ones. Sure. And they're like, yeah. We're we're never gonna move off of, you know, Zoom or Slack or something like that because...
But then what was interesting is as it progressed...
So then you then you move into, like...
You know, before AI really took off, but, like, 2004, for example, there was more of a willingness and appetite from the customers to even look at some of those usual suspects and start to, like, make some of those trade offs as well. And I'm hypothesizing hypothesizing here is that in this now second wave of AI where initially there was all these, you know, pilots and and, you know, redundant spend because of that, there will be that low hanging fruit again.
But then as, you know, more spend goes towards, you know, things like consumption models and as the budgets get squeezed and also as those other usual suspects increase their functionality that, once again, the appetite from the business increases compared to when, you know, maybe when it was initially identified once that low hanging fruit has kinda been, you know, addressed. So it it it was interesting to kinda see that phenomenon too where at first, there were, like, these untouchables. Like, no. We're never gonna do that. And those untouchables became very much not that way as things progressed for certain companies.
So Awesome.
Cool. Well, to leave you, with one last idea here, the... One of the exciting things that I saw when I looked at this is that one supplier typically made up about 74% of that redundant spend for a lot of organizations.
This... You can achieve a lot of savings by just targeting one or two of the suppliers that Tropic flagging as redundant. It's not necessarily a long checklist of suppliers that need to be weighted through.
It's, you know, simply helping point out, you know, two or three of the biggest opportunities and giving you the time to actually, you know, make the case to to drop one of those suppliers.
So I think I think prioritization is also really important here too. Right? Because if you if you go to the business with the full list and there's some things in there that are, you know, maybe not as important or maybe not as attractive, I I... You know, it's not something you wanna lead with. But as you start to kinda show some wins, prioritization's gotta be key.
Yeah. I'd add to that a little bit too that, obviously, you know, we always talk about prioritization timing as well. Right? It's it's... I think it's always a little bit of a surprise for end users, how maybe... I don't wanna say difficult, but I'm I'm not thinking of a better word right now. It it can be to go through a change management of removing a tool or consolidating all the moving pieces that happen internally and things like that. And so I think, like, obviously, getting a list, knowing what the possibilities are, seeing where the overlaps exist through a tool like this, and then being able to have those conversations early and often. And by often, I mean, obviously, like, now I would say every quarter, you know, there's some new...
Whether it's an AI feature from one of the big players or a release from some of your bigger suppliers that's coming out that's now challenging other providers in your... You know, in that space. So, like, constantly kind of checking back and making sure that the list is, you know, being reviewed and that the opportunities that are out there are being looked at internally, I think is a huge advantage for businesses trying to make sure that they're streamlined for for spending purposes.
Cool. Tommy, we've seen the data. You wanna show us the tool? Yeah. Let's do it.
So now that we've walked through the opportunity and, you know, what... What's out there, I'd love to walk through how Tropic actually shows you where those opportunities are and how it arms you with the information to fix it.
So I'm gonna be going through this demo under the the guise of two different personas. One is the procurement leader and two of the contract owner that actually owns the different tools that might overlap.
Stepping into the issues of the procurement leader, I know Shields at the beginning mentioned budget season, you know, planning for next quarter's renewals and potential cost savings opportunities. So I wanted to walk through how someone might do that in Tropic. And to do that, I'm gonna go over to our signals tab where we reveal different opportunities that exist for you, and some different ways that you might wanna be looking for, for those opportunities. In this case, consolidation or redundant spend.
And what I'm looking at here is all of the different suppliers that, Tropic is flagging as having some sort of overlap based on the end date of the supplier that's coming up first. So you'll notice here some of those usual suspects we talked about, like the the office suites, the communication tools, etcetera. But for this specific example, I'm gonna step into this Gong and Clari, redundancy.
Now Gong and Clari, I think, fit very well into the suppliers have grown capabilities over the years and are now colliding with each other. A lot of Clari's forecasting tools are now present in a lot of the Gong SKUs that you might already be purchasing or have added over the years after consecutive renewals.
And so what this report does is, a, it'll show you a high level of what are the suppliers that Tropic sees that has an overlap, show you the contract owners for both and the end date so you know when the potential decision time frame might be if you wanted to drop one or the other.
Some of the other things that it shows right here up at the top is you'll notice that Gong has a significant portion of its a $140,000 contract value with no overlap. So there's a lot of Gong SKUs and capabilities that you're paying for now that actually are not replicated or overlapped with any of your existing suppliers.
Query, on the other hand, is in a slightly different position. It has zero amount of SKUs or dollars and a no overlap position. Every single one of the SKUs or capabilities that you're paying for is fully replicated or at least partially replicated in the the the contract you have with Gong.
So in this scenario, you could you could migrate completely to Gong, but you couldn't migrate completely to Clari without replacing some aspects of the of the Gong tool.
Is that how I understand it?
Yep. That's correct. So... And even if you didn't completely migrate from Gong, maybe you have the opportunity to drop some of the SKUs.
But when I I look at this, I see an opportunity to potentially drop an entire supplier Yeah.
Which is, you know, all... Always a great opportunity.
The way that Tropic does this is by analyzing the actual products that are listed in the contracts that you're purchasing with these different suppliers. So you'll see here in this skew matrix here, we'll compare every single product that you're purchasing with Gong with the products from Clari where we're tracking the overlap. The other important thing to note is that, you know, again, this isn't just looking at, the Gong and Clari relationship. If there were other suppliers in your sales and marketing stack that, had overlaps with Gong, you would see them continually added to this matrix. So they give you a lot more fine grained ability to understand, you know, where the actual SKU overlaps and what is a more optimal way that you could potentially, you know, structure these contracts.
Awesome. So now that you've looked a little bit more into, like, the actual report and analysis itself, I wanna take myself into the shoes of the contract owner. So I'm going to look into the Gong and Clari contracts themselves.
What's interesting here about Clari is that, you know, Tropic is automatically notifying contract owners ahead of the renewal with their recommendations on what should...
You know, they they do about their upcoming renewal. And you can see the recommendation right here for Clari, really big upfront, is cancel. And this is where where some of the power of Tropic really comes into play. You know, we're not only analyzing that redundant spend report that we just looked at that showed, hey. There's a high amount of overlap between Clari and Gong, and it looks like every capability of Clari is potentially duplicated in Gong. But we're also looking at all of other topics intelligence. We see that there's plenty of contract terms here that are out of compliant with your procurement policies.
We see that the pulse survey has been run where we actually check with the users of this tool about do they still think the the product is completing the business need we we asked it to do? And is it doing it in a great way where we see low sentiment across both of those scores?
And so that gives the added recommendation to say, okay. I think that Clari is something that you should consider cancel. And it'll even say, you know, evaluate your options, begin transition planning to Gong or other alternatives because it knows that you already have the Gong contract and the overlap that exists there.
And I just wanna be very clear. There... There's no... It... It's it's completely data driven. It's not that there's some sort of, like, preferential relationship between Tropic or any provider. It's literally looking at the data, your data, and then making an unbiased recommendation and not because of any, you know, alter... Alter your motives, but simply based on the data. So...
Yep. No. That... That's a great call out. Thank you.
I I wanna contrast that with what we see over here on the Gong contract. Same...
Tommy, can you... It's... Can you zoom in a little bit?
It says it's a little hard to see some of this stuff.
Yep. Yeah. Good call.
So I'm gonna zoom in a little bit and show you the Gong contract. Now, again, this is looking at the same redundant spin report that we just looked at, but we have a recommendation here to negotiate. Why negotiate over cancel?
Tropic, has analyzed both contracts, recognized that the Clari contract would be easier to drop than Gong. We also see things like the pulse survey for Gong had very high scores from users on business criticality and supplier sentiment. So there's clearly some signal here that people prefer using Gong over the query supplier.
And we also combine it with the power of traffic price benchmarks. So, you know, while we recommend that you should renew this capability, there does look like there's a savings opportunity by just just paying out of market rates for the the tools and, you know, the quantities that you're purchasing.
Awesome.
So we've gone through here and looked at how Tropic identifies the different opportunities and how we can potentially get it in front of contract owners in a manner where they can start to make those decisions. But the next step to all this is then, you know, how do we take some of this into a negotiation, and how do we start to navigate the, kind of internal process of, of blocking a tool. And and that's something where Shields and Corey have a lot more, experience on and are gonna walk us through a few examples. Yeah.
Let me see if I can successfully navigate the slide situation here and, get this going. So, yeah, I'm gonna share a couple of... And if I could get somebody to tell me if this looks okay, like, Zoom wise.
It looks it looks it looks fine for me. Very, very nice. Okay.
Perfect. I can also see my own face in the corner of it. So if I'm blocking any information, just let me know. But, what Tommy was showing was obviously, a look at, you know, how our system is able to generate overlap opportunities, and I would say at least start the conversation for you internally as either, you know, procurement leader or if you're in finance or or where...
Whatever whatever your situation is and and ways for you to go and have discussions about potential overlaps. Right? And and in this case, we were able to, help a customer who had, identified, obviously, some some overlapping capabilities between Zendesk and Intercom, now Fin, now Salesforce. Right?
But, they're essentially...
We're using two tools to, help with, the same, you know, features and functionalities, slightly, you know, different use cases, if you will, for their help desk, right, and and resolutions. But, I think about April of this year, there was some concern, and I think it actually did happen where there's some changes to the integration, between Zendesk and Fin, and and there were some decisions, maybe some hard decisions that needed to be made, in in in certain cases. But, on the left hand side, you can see kind of there's this two platform situation over multiple years, where Zendesk was the help desk and Fin was being used for AI outcomes.
And you had, obviously, you know, separate vendors and contracts for what essentially is one, you know, maybe large teams workflow. Right? You're paying two vendors. You're, you know, you're relying on maybe different integrations.
There's there's a lot of potential, I wanna say, points, but, like, situations where maybe if one goes down or the other that you might have, you know, a situation internally that you have to work your way through. In this case, I think there was a bit of a, I wanna say forced move, but a forced decision to be made. And so, when this came across, essentially, there was already a conversation started up internally where our team member was able to jump in and help navigate, a a switch or a consolidation from Zendesk and Fin to to just, you know, Intercom Fin. Right?
And and like anything, I would say, it's not always as clean-cut as, like, turning a service off and starting up another one. Right? It's not like, you know, I think there's an example of, like, oh, I don't need Zoom anymore if I have, you know, Google, and I can use Meet or whatever. Can just shut Zoom off and and move on.
You know, a lot of times you need a little bit of or sometimes a lot of overlap to do various testing to make sure that, like, you know, business continuity, is there and and you're able to kind of make a successful transition. Right? And so in this case, we had a, a timeline here that we were looking into, where, you know, process kinda started back in in April, late March, April, and, the decision was made kinda to explore this consolidation route. Conversations had to be had with both suppliers.
And what ended up happening is, you know, at a high level, I won't want all the details, but, you know, this nonrenewal notice was sent to Zendesk, and that kind of, you know, shot over the bow that, like, hey. We're we're seriously, you know, considering some changes here. There was a negotiation that took place to reduce...
You know, to essentially get an extension of Zendesk for a few months to cover kind of this overlap period that the customer was looking to have.
That was initially, you know, not priced incredibly well, but that was negotiated to a place that the customer was comfortable with.
And as you can see, right, you know, looking at a multiyear commitment, the cost was a little bit higher in year one because of that bridge, because of the couple months of overlap where, you know, the customer needed that to feel comfortable with this change, make sure everything was working the way they wanted. But then you look at it, you know, in years two and three, and and you could potentially extrapolate this out further, but, you know, they're able to save a little over a 145 k on making this switch and consolidation, to to to Finn in this case. So, yeah, a really good outcome, I would say, and an opportunity that that shows that, you know, it's not just simple to, like, cut one off and and move to another, but a good outcome nonetheless.
So it was definitely work. And and what was interesting is you look how much time it took. It took what? What is that?
Like, six months or something like that? Yeah. Yeah. And this this highlights once again the need.
Like, if you're if you're...
It sounds like they were able to, like, negotiate some, you know, decent terms despite maybe the circumstances, but I I would say, like, that's that's playing with risk a little bit. Right? Because if you are waiting to renewal time, not every vendor will do a short term bridge renewal. Some are more going to push, you know, higher terms or maybe there's less willingness from the business.
I also know that, you know, if you're moving to a company, there there could be opportunities, especially if that contract expiring too to say, hey. If we choose you, can you help us bridge that gap so we're not having to, you know, double pay or something like that? So it really points to how to do this proactively. And if you're engaging, once again, you know, sixty, ninety days out, but but between the evaluation and and the transition, you know, that's probably not gonna be enough time.
Whereas if, you know, this is flagged proactively and this is something you start to have those discussions earlier on with the team, it's probably much more likely to occur and to get done.
So Yep.
Yeah. And and that's a great point. You know, obviously, I don't know how things would have been different or better, likely could have been better from a testing and pricing and negotiation leverage perspective if you start something like this, like, four to six months out or... And sometimes, you know, bigger tools, more business critical tools need need a year, you know, like, whatever it may be to... Especially to, you you know, negotiate the best outcomes from one or both companies for sure.
I would say a lot of the times, you know, we end up getting involved in situations that, you know, a customer needs help with for one reason or another, whether, you know, they didn't have the ability to review that in time or, you know, get get around to it and get all the right people out ahead of things. But, yeah, I think to your point, very true. Sometimes, you know, you can run into supplier rigidity on, you know, shorter terms. You'll actually see that in the next example. Right? Or the ability for a company, like your own company, to move quickly and, like, get off of one tool and move on to another. So so, yeah, that's a great call out for sure.
Cool.
Yeah. Let me hop to this next one, and then I wanna leave a little time in in case there's any wrap up or questions here. But...
So this situation was, as I mentioned, you know, a little bit of a longer overlap, if you will.
A customer was using RockerBox and house for some complimentary, you know, features, measurement and attribution on one side and incrementality testing on on the other. And, essentially, we... We've mentioned this a few times. Right? Suppliers that are dipping their toes into features and functionality that they maybe weren't, really, I guess, trying to be in prior. But now for whatever reason, you know, like, trying to get a bigger market share, trying to, you know, obviously beat their competitors, win more customers, etcetera, they're now doing those things. Right? That's, I think, a case of what was happening here.
It just so happened that, you know, this customer was less than thrilled with kind of some of the, I guess, functionality of of RockerBox, Hadhouse already for a different purpose. They rolled out this, you know, new feature that directly competed with RockerBox. But as you mentioned, Shields, right, came, I think, thirty, forty five days out. Very limited window and and was gonna need more time than that anyways. But, ultimately, what we ended up doing was, you know, negotiating essentially with both parties. First, with RockerBox to obviously opt out of that renewal, looking to multiple options landing on essentially a nine month with early termination rights, right, instead of a twelve month opportunity and then had this kind of flexibility secured as far as, like, payment terms were concerned as well. So it went from, like, annual payments to quarterly.
And and and in the positioning of the negotiation, right, it's very much, I would say, open ended for both of these suppliers to potentially win, you know, either their pieces or if they... If they're capable of the full business from this customer. But they needed this time to evaluate Houzz's new features. And, you know, ultimately, I would say, like, right now, we've given this customer flexibility and save them a little bit of money of having to pay for a full year.
And having that optionality, I think, is what most business leaders are looking for. Right? Like, under...
You know, knowing and understanding, alright. Well, we're we're doing this evaluation. We're maybe...
In the case of the previous example, we're having some overlapping spend, but we expect our business to be in a much better place moving forward because of it. Right? And so in this case, right, I think it was a, you know, a smaller win, if you will, but, like, customers having this opportunity to validate and, really test things out and make sure it's a good fit for their business. And then at at the moment, we've aligned on pricing that's slightly better if they were to fully consolidate the house moving forward.
But this could open up a lot of opportunities as they test things out too. Right? You know, RockerBox could come back better pricing, better features, similarly with house. Right?
And so, I think all around, it was a good outcome for for the customer, and one they're happy with, you know, overall.
Yeah. So on the one hand, like, I can see this being interpreted as, oh my gosh. This seems like a lot of work. And I guess to some degree, it is very much a strategic initiative.
It's also a necessary initiative. I think it's a high value initiative. You know, this is a smaller one, but when you start to, like, stack them on top of each other, it actually does a lot of things. It's not just the savings.
It's fewer suppliers to manage. It's it's less, you know, shelf where it's it's having more people on one tool is probably gonna increase the value proposition. Like, the the benefits of the business are certainly obvious when it comes to savings, but I think there...
There's so much more just beyond that. And and the other thing I'll I'll say is, you know, I've been thinking about is the three of us have been talking is, number one, I expect this to increase in frequency as AI continues to, you know, push companies to go laterally instead of, you know, just, you know, deeper. Like, companies can move faster. They can accelerate their road maps.
Plus, you know, once again, you have new suppliers popping on the scene. And by the way, AI is making it possible where switching costs are dropping with the help of AI too. So not only are there gonna be more opportunities, and even though it...
Yeah. I don't wanna underestimate. It's not like you just, you know, snap your fingers and and things happen, but it does make it easier to transition. I mean, I've I've had conversations with people of all organizations, including, like, finance, and and for the first time, they're evaluating, like, changing an ERP or something like that, which for a long time is like, no way we would never do that.
And that's kind of an extreme example, but it's just showing that the stickiness of really any product is is less sticky than historically it was even if there is still stickiness variability. It's a term I know...
I don't think I ever thought I would say. So, anyway, kind of really interesting. And so once again, I think that this is going to be an ongoing strategic pursuit, something that, you know, you need to kinda keep track on. And, and so, you know, prioritization and awareness are absolutely gonna be key.
Yeah. I think Tommy mentioned it in his portion, but, you know... And I know you've kinda touched on a little bit on, you know, hey. Maybe this seems like a bit of work here, and and I don't wanna devalue that because in times, it can be. But I think the mention of there being, you know, a a big, savings opportunity by addressing one or two of these a year is a good call out, right, and, like, a project worth undertaking, for any team. So, just wanted to kinda mention that. Right? It's... I I think, if you hadn't known where to start in the past or, you know, you didn't have an idea of, like, what overlaps were out there, this is, a great starting point in an area where you can kinda use this feature to, you know, make make real change and make real difference in your company.
Corey, maybe I'll... I I know you have a lot of experience here.
And and once again, it sounds like even if you're behind the eight ball, you know, you can sometimes work a little bit of magic, get creative, that sort of thing. But but how far ahead of the renewal do you feel like this does need to start? I see this question.
That's a great, great question that I'll answer with, obviously, very situational.
You know, you've mentioned, like, oh, you know, customers or or people considering replacing an ERP. Right? Well, replacing an ERP is an... A tremendous undertaking and and something you would need to start probably north of a year out. Right?
Easier opportunities, right, the the Zooms for Google's, the the, you know, the Asanas for monday.coms maybe potentially, you know, can be a shorter time frame for sure.
I generally like to say for a threat of churn to be credible that it needs to be, you know, several months out at the very least, just because I think every supplier out there in SaaS knows that even if they are highly replaceable, that if someone's coming to you ten days out or something, that the chances that they're actually gonna make a switch are probably a bit of a bluff. And so, you know, whatever whatever you think, I'd say, in this case, gives you the most leverage.
And, like, I think the earlier, the better is always the answer to that.
But, yeah, definitely situational depending on what you're looking at for sure.
Yeah. And if you do have any questions, you know, keep them coming. Put them in put them in the chat or the q and a section.
But I I would just add that, like, that's the one of the beautiful things about this product is, like, it it brings it to you at a time... It kind of not ignores the contract, you know, end date, but, like, I I think that you can be well aware of it. You know? And it doesn't have to be, oh, let's look at it six months. It could be, hey. Let's look at it now even if we have a year to go so we can start planning, maybe even from a budget perspective, get that consensus and and build a a proper road map instead of kinda always plan... You know, trying to be creative. Here's one that, you know, maybe I'll I'll send, you know, Tommy your way.
Know, we run OpenAI and Anthropic side by side on purpose. Is this going to flag that every time?
Yes. No. That that... That's a good question. Obviously, we have the same problem in our own redundant spend as I've mentioned with Corey earlier. We have the ability for customers to log that the spend is planned or, you know, not seen as redundant based on how we're using the tools, we'll ignore the report and take it away from our recommendations unless we see something material materially change in your contract the next time, you know, you you go through a renewal and add new products or SKUs?
K. Maybe I'll take this one. It says our our biggest overlap is what the tool would never cut. Is there a point in flagging it?
I mean, I I think this is where prioritization, I think, it's important to have on the list. But if you're kinda leading with, you know, one of these ones that is is a little more sticky or just culturally, like, that's probably not. But, like, I still think it's worth including in there and just recognizing that, once again, from my experience, what I've seen is is the appetite changes over time depending on, you know, the situation that you're in, depending on, you know, how much budget pressure there is, depending on as the companies continue to evolve. You know, you might say no to, you know, an overlap or consolidation once, and then twelve months later, be like, you know what? Actually, this situation has changed, and and then and then go back go back to that.
Gosh. We're almost out of time. I I guess maybe just kinda wrapping things up. Corey, Tommy, what's, one takeaway from each of you? One, like, very tactical, actionable, you know, thing. And then while while they're kinda thinking about that, you know, if you do wanna see this, if you wanna see the demo, if you wanna kinda see it in action, you can respond to the poll here or reach out to to either one of us.
Chavey, why don't we start with you?
Sure. You know, it's really just the encouragement from that. So much of your spend that's redundant is probably tied up into one supplier. Know, traditionally, suppliers has been a a difficult thing. But knowing that you only have to do this once or twice a year, I think, is extremely helpful. And even just thinking about, you know, people's preferences have changed so much on the tools that they would have fought and fought, you know, fought and fought for several years ago. They maybe have less, you know, loyalty to with some of the new tools and ways that they're working today.
Corey? Yeah. I think mine is is...
Obviously, it's along the same vein. There's just...
In addition to, obviously, this redundancy analysis feature that you have access to for your your particular tech stack, there's there's just this opportunity to use tools like Clot or or ChatGPT to also do research on, you know, other providers that are out there as well, outside of your tech stack for, you know, companies that are con...
You know, constantly adding features and functionality to their, you know, offerings and things like that. I think there's just this ability, to drive a ton of value as whether you're in procurement or IT or wherever else to other, you know, parts of your organization by being able to confidently speak to, you know, some of the tools that, are out there and and where there might be opportunity in your tech stack in particular. So, and, yeah, I mean, I think there's always, you know, staying curious and and and being engaged in that, you know, that space and bringing those things to light. You
know, I think being that proactive, and bringing those things to the table early and often is just a huge, you know, differentiator for people in this type of role to to be bringing to the table for sure.
Cool. Well, the the last thing I'll just add is, you know, in this world where it feels like, you know, me being in procurement, you know, sometimes it feels like we're always kind of, you know, behind the eight ball a little bit. Not always, but, you know, with things changing fast, it is certainly hard to do that. Like, having the data pushed to you, having the opportunities identified proactively is going to be a game changer because that puts you in that position of better timing.
That puts you in a position of, you know, be on a...
Have true optionality and and and evaluate it in the way that you should. And I've seen plenty of op...
Good opportunities kinda squandered because they just weren't in a position to kinda move or didn't have the time, etcetera. So, you know, time is your friend, but, of course, you know, with us, you know, focusing on on a thousand different areas at once, that's where, you know, we're pulling on it. Like, that's not gonna be near as effective as if it's, you know, pushing on you. So thanks, everyone.
Thanks, Corey. Thanks, Tommy, for for joining. Super relevant topic right now. Awesome job, Tommy, build...
Building this product and and great. You know, I can speak from my own personal experience. Like, it's it's definitely, you know, exactly something that I...
I've been needing for a long time. So thanks, everyone.
Thanks, guys. Take care.

Our Speakers

Michael Shields

Tommy Noonan


