UDSKRIFT 🔗
WEBVTT
1
00:00:00.320 --> 00:00:14.360
So you're researching procurement software. You've got a dozen tabs open on your browser, and every one says the same thing. AI-powered, agentic, end-to-end, one platform to run all your spend.
2
00:00:15.180 --> 00:00:24.400
You read four of these homepages back to back, and you still can't tell what any of them does differently. That's not a you problem. The tools are more different than they look.
3
00:00:25.300 --> 00:00:34.540
The companies selling them are just bad at saying how. So buyers end up choosing on a slick demo, a gut feel, or whoever got in the room first.
4
00:00:34.940 --> 00:00:41.940
This episode is about why the market reads like one long copy-paste and what you do about it when you're the one who has to choose.
5
00:00:42.520 --> 00:00:50.480
I'm bringing on someone who gets paid to fix this from the inside for the vendors and to help buyers see through it from the outside. Let's get into it.
6
00:00:50.600 --> 00:01:02.620
[gentle music] Technology presumes there's just one right way to do things, and there never is. AI will do what you tell it to do, but that may be very different from what you had in mind. Computers are useless.
7
00:01:02.720 --> 00:01:09.860
They can only give you answers. For a list of all the ways technology has failed to improve our quality of life, please press three.
8
00:01:11.000 --> 00:01:19.520
Welcome to ProcureTech Unpacked, the show for procurement professionals who want to understand the technology shaping our function. Today, my guest is James Meades.
9
00:01:19.880 --> 00:01:28.920
James spent more than 18 years in corporate procurement as a category manager before going independent, and today he runs EntProc, a remote solo consulting practice.
10
00:01:29.440 --> 00:01:44.100
If you've ever tried to make sense of the procurement tech market, you've probably run into his work, whether it's the tech maps that sort vendors by company size, the software finder, or the Procurement Software podcast, where he's been talking to founders and operators for years.
11
00:01:44.740 --> 00:01:48.880
He works on both sides of the market, and that's why I wanted to bring him on for this conversation.
12
00:01:49.340 --> 00:01:58.980
He advises procurement tech vendors on their product, their positioning, and their go-to-market strategies, and he also helps buyers, the CFOs and heads of procurements in the mid-market choose what fits them.
13
00:01:59.640 --> 00:02:12.040
So when we get into why the tools all look the same, he's seen it from both sides, inside the vendors and across the table helping clients pick. James, welcome to the show. Thanks, Joël. Quite the introduction.
14
00:02:12.120 --> 00:02:23.820
And, uh, and you're actually the most featured guest on my podcast, a joint featured guest, so, uh, yeah, that's, uh, quite an honor to have as well. Yeah, likewise. I was gonna address that, right?
15
00:02:23.840 --> 00:02:31.300
I'm like, "Oh, we should get you going on, on getting that record on this podcast," so very happy- [laughs]... to have you. [laughs] Always happy to come back.
16
00:02:31.380 --> 00:02:50.180
[laughs] Yeah, and maybe w- we could start somewhere where I think it, it illustrates the pain of, of what people have to deal with trying to navigate this market, which is that, you know, offline you told me recently about a conversation that you had, uh, when you ex- You were chatting with experienced buyers that even, you know, attend conferences, uh, webinars, right?
17
00:02:50.220 --> 00:02:59.040
Are quite active. And even they admitted that they couldn't tell the providers apart. Uh, can we start there maybe with, you know, regaling us with that tale?
18
00:02:59.540 --> 00:03:02.320
Uh, just 'cause I think it's actually pretty common, and it's a good place to start.
19
00:03:03.700 --> 00:03:19.020
Yeah, I mean, I could, I could tell you probably 10 different instances in one form or, or another where I've had a similar conversation over the, uh, o- over the past m- months or, or certainly year where the conversation starts around, yeah, you know, we know, we know we need to digitize.
20
00:03:19.060 --> 00:03:27.620
We know that we need to modernize our, uh, our organization, or even, you know, we're looking from a greenfield perspective, and we want to bring some tech in.
21
00:03:27.740 --> 00:03:37.720
But everyone's kind of saying that they do the same thing, and we don't really understand how to differentiate from them, so yeah, it, it is, it is a common problem.
22
00:03:37.820 --> 00:03:45.300
And I think it's probably got worse, not better, as a lot of solutions have sort of converged.
23
00:03:45.940 --> 00:03:56.200
You know, whereas before when you had very distinct point solutions that were offering contract management, supplier onboarding, procure to pay risk,
24
00:03:57.320 --> 00:04:11.340
it was pretty easy to sort of pigeonhole them into one sort of core category. They had other modules sometimes as well, but they typically would lead with one, you know, specific core offering.
25
00:04:12.380 --> 00:04:24.520
That, and I noticed that when I put my tech maps together now, it's becoming increasingly harder to be able to, to give them just one primary category, which you have to on a, on a diagram like that.
26
00:04:24.560 --> 00:04:32.360
Otherwise it just gets too busy and no one can understand it. So yeah, it's, it's a problem that I don't see going away anytime soon.
27
00:04:33.140 --> 00:04:42.460
Yeah, and, and, uh, on those tech maps and, and the software finder that you put together and refresh, uh, periodically, have you also seen the number of providers growing over time?
28
00:04:42.480 --> 00:04:53.640
Because I think the last time we had spoken, you were in the 650 range around there. We-- Yeah, so we got up to about 450 at the highest point that we've ever been.
29
00:04:53.680 --> 00:05:04.060
We started off when we first launched it in
Load full transcript
2022 with the website. Uh, we were-- we had 275 solutions on there. We got up to about 450, and then I got to the point...
30
00:05:04.080 --> 00:05:17.660
And this, I took a little bit of feedback from people in the space as well that sort of reached out. I ended up culling a few, and that was mainly down to, is it a category that is more sort of finance- Mm...
31
00:05:18.280 --> 00:05:31.860
or legal or, um, or perhaps risk related rather than pure procurement technology. So if your- Pun intended, right? Y- yeah. [laughs] So, so if your,
32
00:05:33.160 --> 00:05:44.080
if your platform is on, on your website and in your marketing primarily fo- uh, targeting lawyers or, or chief sustainability officers, then we're probably not gonna put you in the list.
33
00:05:44.820 --> 00:05:57.780
If you have a product that you're actively marketing and selling to procurement professionals and it attacks a problem that procurement typically is gonna get involved in, then, then it should be on there.
34
00:05:57.860 --> 00:06:03.840
You know, ensuring that a couple of other factors, uh, uh, are, are in line as well. You know, we don't list anyone that's pre-revenue.
35
00:06:03.920 --> 00:06:17.180
We don't, um, we, we don't list anyone that's, that's a consultancy that only offers that software as part of a wider consultancy package. Mm-hmm. So, you know, we do have some prerequisites, but yeah, it's-
36
00:06:18.348 --> 00:06:31.208
It's a number that I think will, will stay relatively stable because I think for every company that gets acquired or that goes out of business, there'll be a new AI upstart that will- Mm...
37
00:06:31.248 --> 00:06:36.208
that, that will come into the market that can, that can do something better than some of the legacy tech.
38
00:06:36.288 --> 00:06:54.188
And, you know, we've seen some of the older technology become somewhat less relevant over the pa- certainly over the past two or three years since AI has been sort of natively embedded into the new breed of procurement, uh, of procurement technology.
39
00:06:55.808 --> 00:07:08.808
I don't think we'll see a mushrooming of solutions. You know, I don't think there'll be the appetite from VCs to be able to invest in procurement SaaS as there was perhaps in 2021, 2022. Because
40
00:07:09.948 --> 00:07:28.948
as AI gets smarter, and I guess we'll probably dig into this as we, as we go through the interview, but as AI gets smarter, there's gonna be more that you can do within, within your Claude or, or ChatGPT or whichever AI you use terminal now that it can do, like, multi-step tasks if you use something like CoWork.
41
00:07:30.128 --> 00:07:40.688
Yeah, and, and it's funny you mentioned the, the number, because I've seen, I think there was other tools released that were trying to count the number of procure tech firms, and I think depending on your definition, I think the, the biggest- Yeah...
42
00:07:40.748 --> 00:07:49.208
I saw was in, like, the 900 range as well, but
that's probably- Yeah... you end up finance and fin- uh, FinOps tech and all this stuff as well. Um- That's it.
43
00:07:49.228 --> 00:07:56.328
You know, I s- I saw that yesterday as well when, when, when I, when I saw, when I, when I saw that new platform that was launched. You know, the guys behind it are ve- very, very credible.
44
00:07:56.388 --> 00:08:04.748
I don't-- So, I mean, I'm sure their, their, their research is substantiated, but then I think it just boils down to how do you define it. You know- Yeah...
45
00:08:04.808 --> 00:08:14.588
is a company that's doing accounts payable automation procurement tech? Well, if it's got some source to pay functionality on, you know, more upstream of that, then, then probably yes.
46
00:08:14.648 --> 00:08:26.268
But if it's, if it's just a, a, a payables-based software product, I would argue that it's not. It's the office of the CFO, but it's not really something that's core procurement. Cool.
47
00:08:26.328 --> 00:08:36.368
So, and so I think that just points to, you know, make sure you have a common definition or a, a definition that you understand going out to the market of what am I trying to look at, right? Is it procurement technology?
48
00:08:36.468 --> 00:08:46.608
Is it wider than that? And am I looking at, uh, you know, a database that aligns with what I'm trying to find, right? Or maybe I need, I need to look in adjacent spaces.
49
00:08:46.848 --> 00:08:58.928
Um, and I also wanna point to or get y- your take on, you know, when, when we say that this, this, uh, positioning is off or everything looks the same, what is the actual failure, in your opinion?
50
00:09:00.828 --> 00:09:14.688
So I think it originally started out that marketers were trying to be everything to everybody because historically, this is marketing 101 to anyone that's procurement on here that doesn't understand how, how search engines work.
51
00:09:14.768 --> 00:09:17.588
But historically, if you
52
00:09:18.528 --> 00:09:40.768
put the right keywords on your homepage or in your content on your website, that would typically tell Google, um, that especially if you're a big name and you've, and you've built some, some links and your re- your website's a credible website, that would tell Google that you're a product that's playing in that space.
53
00:09:41.348 --> 00:09:46.248
So if you're a startup and you want to build website authority,
54
00:09:47.288 --> 00:09:59.588
let's say in source to contract or in, uh, or, or in anything that's maybe taking on some of the more established players like, uh, you know, SAP or Coupa or Ivalua, you know, these big suites, what were they doing?
55
00:09:59.628 --> 00:10:05.268
Well, they were stuffing their websites full of keywords like spend analytics and contract management, and
56
00:10:07.128 --> 00:10:18.208
they were really just paying lip service to that, that yes, it can in some way help you with your spend analytics or contract management, but it didn't, didn't
necessarily have that as a standalone module within, wi- within the system.
57
00:10:18.728 --> 00:10:27.248
So I think that's initially how it started, that the marketers were just keyword stuffing their websites full of things that they thought would get clicks from Google- Trafficked...
58
00:10:27.248 --> 00:10:37.228
from, from, from procurement and supply chain and finance people that were perhaps looking for, for, for that type of solution. What it's become now is that
59
00:10:38.428 --> 00:10:51.228
I think there's so much convergence now in terms of what the different solutions offer, and it's become so much easier to build, at least to build a, a prototype that
60
00:10:52.128 --> 00:11:00.728
you can be a procurement software playing in, in this one space, let's say supplier relationship management, for example.
61
00:11:00.768 --> 00:11:09.688
And then it's pretty easy then to build modules on top of that, that do contract management because they're related, you know, vendor lifecycle management, vendor performance.
62
00:11:09.748 --> 00:11:21.808
If you're doing CLM and SRM, they're kind of intertwined. Mm-hmm. So if you're an SRM platform and you wanna build a basic contracts module because your customers are asking for it, it's pretty easy to do that now.
63
00:11:22.248 --> 00:11:25.308
Before that, it would've taken a, a big team of software engineers.
64
00:11:25.408 --> 00:11:40.308
Now you can get a couple of your guys in your team to vibe code it in, in, in a weekend and then, you know, build the security and the workflows and the, and the guardrails around it to, to, to make it, you know, enterprise grade if you're building it into an existing system.
65
00:11:40.988 --> 00:11:50.608
So I think because the, the barriers to building have been removed to a large extent, there's a proliferation of tools that are doing more and more.
66
00:11:51.208 --> 00:12:01.908
Um, and it's becoming then for anyone that doesn't study this space, like, like, like ourselves, increasingly harder to be able to differentiate themselves, them, them from each other.
67
00:12:02.508 --> 00:12:10.688
And would you think, uh, I'm kinda leading the witness here, but agentic AI and the fact that people are, you know, clicking on AI agent stuff, right?
68
00:12:10.728 --> 00:12:21.992
And, and there's still, uh, lots of attention going towards those types of key terms. Do you think that ac- exacerbates the problem? Yeah, it's a g- yeah, it's a good, it, it's a good challenge.
69
00:12:22.072 --> 00:12:27.432
I think, uh, th-there was at the beginning a lot of AI washing. Um,
70
00:12:29.692 --> 00:12:43.312
I think now the t- the tech providers that aren't really AI native are kind of getting called out for that, and there's enough people around, and, and also from other procurement tech companies now that are calling them out and saying...
71
00:12:43.632 --> 00:12:50.332
They're maybe not naming them, but they're saying, "Hey, you know, if a company's, if a, if a platform's 15 years old, are they really AI native?
72
00:12:50.372 --> 00:13:04.532
Unless they've started out and rebuilt every single line of code, are they really gonna be AI native?" Which, which then I think puts the question back to, well, do you really need something that's AI native?
73
00:13:04.672 --> 00:13:16.392
If you're, if you're a company with 500 employees and you just need a simple workflow automation tool to, to, to tackle the, the classic, you know, intake procurement front door challenge- Hmm...
74
00:13:16.612 --> 00:13:25.552
do you need something that's gonna orchestrate into your quality management, your finance system, your ERP? Maybe it'd be nice to have, but
75
00:13:26.572 --> 00:13:34.952
really you can get started spending a few grand on something that does that perfectly adequately or, or even, or even build something in an existing tool, you know.
76
00:13:35.012 --> 00:13:38.372
And I, and I know we always have the debate, should you build versus should you buy?
77
00:13:38.472 --> 00:13:55.372
But I would always say if you're a, if, if you're a team of one in a relatively small or growing company, just build a tool that tackles the basics first before you look at going out to buy something, because that will give you the experience of what you want, and it will give you something that's good enough for the next 12 months.
78
00:13:56.232 --> 00:14:08.792
Which gives you a chance then to research the market and really do your homework, homework and understand, you know, maybe go to these, some of these, uh, uh, events that, that, where, where there are some sponsors there and have deep conversations with them, understand what they can do.
79
00:14:08.892 --> 00:14:21.072
But, um, there was a lot of AI washing. I think it's becoming less so, but, but yeah, there is still a lot of marketing out there that makes it difficult to distinguish between the different providers. And I think I...
80
00:14:21.552 --> 00:14:23.872
It, it's, it's deliberate to some extent, right?
81
00:14:23.932 --> 00:14:32.952
Because no, no provider's gonna hold their hands up and say, you know, "Hey, we're not as good as the s- as the, [chuckles] as the company that launched a year ago and has got the latest tech." Hmm.
82
00:14:33.472 --> 00:14:36.012
No, and I, and I, I love the point that you make around, you know,
83
00:14:37.192 --> 00:14:46.512
y- you may not need agentic capabilities to solve a business problem depending on the scale, depending on the s- you know, the sub-process that you're looking at in terms of, of problems to solve.
84
00:14:46.912 --> 00:14:53.752
So that's the first thing I take away. And the second thing around, you know... And if you start with a more simple, uh,
85
00:14:55.332 --> 00:15:03.412
system or process, you're actually gonna go out to the market with a better, you know, with, with experience instead of theory behind your, the belt, right?
86
00:15:03.552 --> 00:15:20.172
And, and being able to have those deeper conversations based on what you've actually lived through and what you're seeing as limitations, uh, to the processes supported by systems that may rely on traditional algorithmic automation instead of, you know, inserting a, a large language model into the process.
87
00:15:20.752 --> 00:15:22.872
So I think those are two, two interesting points there.
88
00:15:23.492 --> 00:15:34.252
Um, and, and given that you're on, you know, you're also in, in doing vendor advisory, what do you see that, that buyers never get to see in terms of what's happening on the other side, right?
89
00:15:34.292 --> 00:15:48.552
That maybe m- making an individual marketing decision to lean on agentic makes sense in, in s- a silo because, you know, it's gonna get us more visibility online or in, uh, uh, more clicks, et cetera.
90
00:15:49.012 --> 00:15:58.632
Uh, but what are, what are you seeing? Like, what happens when buyers are, are thinking through their messaging, thinking through their marketing that, uh, you know, as a procurement professional, I may not see?
91
00:16:00.492 --> 00:16:14.812
That, that's a really good question. So I think that tech vendors really underestimate how granular a procurement buyer wants to go when they're looking at a tool. And,
92
00:16:16.472 --> 00:16:22.992
you know, if you ever, if you've ever listened to any sort of online or digital marketing podcast, which I'm sure you, I'm sure you have as a business owner.
93
00:16:23.012 --> 00:16:32.932
But anyone out there, if you've, if you've ever listened to any of these marketing or, or, or solopreneur small business podcasts or YouTube channels,
94
00:16:34.212 --> 00:16:44.992
o- one of the first pieces of advice that they give you is find your niche and niche down, or, or niche if you're American. And because that rhymes, right? The riches are in the niches. That's why that thing.
95
00:16:44.992 --> 00:16:53.792
[laughs] I swear that's why they use that. Yeah, it's better than the riches are in the niches. [laughs] I see you're French-Canadian, you say niche as well. So
96
00:16:54.792 --> 00:17:06.772
I think it's, it's counterintuitive because we all wanna try to be everything to everybody by, by human nature, especially if we're, if we're people pleasers by, by personality. But
97
00:17:07.672 --> 00:17:13.972
I think one of the things that they really underestimate is it's better to focus on a small niche and just really nail that.
98
00:17:14.012 --> 00:17:24.832
You know, get your case studies, get your positioning, get your marketing, go to the right events that aren't just in procurement, but are more sort of industry-wide for that specific sector or country, if you're just focusing on, on one market.
99
00:17:24.912 --> 00:17:31.712
Okay, the US is big, but if you're focusing on, I don't know, Germany or UK, there are, there are lots of specific events where,
100
00:17:32.652 --> 00:17:42.672
you know, the Zips and the Oros and everyone that's got a ton of funding are not necessarily going to, but, but you can, and you can really dominate that, that market. Yeah.
101
00:17:42.732 --> 00:17:52.572
And I f- I feel like that's, you know, the insight you're giving us is, like, that life cycle is of the, of the company as well, right? At the beginning, you don't have any paid customers, right?
102
00:17:52.652 --> 00:18:00.292
You're trying to feel your way through, where can we generate unique value? And so, you know, you have a tendency to wanna be everything to everyone.
103
00:18:00.372 --> 00:18:05.572
But then I think the mistake that happens is, is everybody keeps going in that, in that direction, right?
104
00:18:05.672 --> 00:18:14.972
Whereas, uh, again, you know, I align 100% with you on this, where I try to push people to say, "Like, who, who do you not serve?" Right? Can you answer that question?
105
00:18:15.612 --> 00:18:26.176
And, and how does it push you towards your ideal customer profile and then your ability to generate unique value versus your competitors? For that unique, for that ideal customer profile, right?
106
00:18:26.256 --> 00:18:34.536
Whether it be industry, right? You're the top, uh, you know, I think back to like SciQuest and, and how they dominated in the higher education market, right?
107
00:18:34.596 --> 00:18:40.156
Like every single university you went to was running SciQuest, and probably many of them still are, right?
108
00:18:40.236 --> 00:18:47.996
But that was-- I don't know that that was specifically in their marketing when they initially did that, but, uh, and before being, uh, bought by Jaggaer.
109
00:18:48.096 --> 00:18:58.576
But I feel like there's, that's missing today from the market, which is like, you know, industry-specific focus and, and expertise, and also playing on the things that aren't technology-based, right?
110
00:18:58.656 --> 00:19:14.176
So do you have a very deep, you know, procurement bench within your, uh, your organization that's gonna actually get you to the outcome as a client versus focusing solely on agentic and the functionality that, that people are gonna offer up?
111
00:19:14.876 --> 00:19:24.136
Uh, do you think that's actually a symptom of, um, how procurement asks the market to sell them, right? Specifically in RFP documents, for example?
112
00:19:25.396 --> 00:19:37.556
Uh, that's a really, really good question, and it's difficult to answer because I've never, I've never done an RFP as a practitioner buying technology personally. Hmm. Um,
113
00:19:38.496 --> 00:19:46.876
do I think that RFPs, the procurement issue are, are too rigid? I mean, yes, I've heard, I've heard stories from procurement tech companies.
114
00:19:46.976 --> 00:19:59.796
I've even seen some examples of, of what they've, of, of what they're asked to fill out, and some of it is complete nonsense. You know, just if you, if you wanna do an RFI, then just make it small and call it that.
115
00:19:59.896 --> 00:20:15.576
But don't, don't give people the indic- the, the, the assumption that they're being invited to, to, to bid, and then you're gonna ask them, you know, 200 questions that, that's gonna disqualify half of them because they're just not big enough to have, you know, the type of things that you're asking them to do.
116
00:20:16.156 --> 00:20:22.876
Um, so it's a great question. I can't, I can't answer it for su- for, for 100% is the, is the short answer.
117
00:20:23.396 --> 00:20:32.216
But you touched on something leading up to that that I think is important around, well, you mentioned having a strong enough procurement bench in the organization.
118
00:20:32.996 --> 00:20:40.076
And, and I think that can come in several different formats, and there's not necessarily a right or wrong answer there.
119
00:20:40.116 --> 00:20:50.436
But I think it's worth drilling down into that a bit because you've got some companies that, that will hire a, an in-house procurement expert.
120
00:20:50.616 --> 00:20:54.696
There are more and more of them now that are, that are coming in as former, as former procurement practitioners.
121
00:20:56.136 --> 00:21:09.396
I often think that they get underutilized a little bit, you know, especially in terms of product and customer success. You know, if they're just being, if they're just there for, for show and, and to help internally,
122
00:21:10.316 --> 00:21:17.136
I think that's kind of a bit of a waste. I think for, for customer success, for sales enablement, having procurement people
123
00:21:18.656 --> 00:21:23.896
n- n- not only just as a, as a sounding board, but actually sat on calls, I think is really important.
124
00:21:23.936 --> 00:21:35.476
Because first of all, you get to spot bad sales behavior, which is perhaps not obvious to a VP of sales or a CRO, but it's, you know, a procurement pro, a pre- procurement pro would see it instantly- Hmm...
125
00:21:35.816 --> 00:21:48.816
um, by the type of tactics they're using. Um, but I think also the, the another common thing that happens is that procurement tech companies will look to recruit a former CPO on their advisory board, which is great.
126
00:21:48.856 --> 00:21:52.096
I understand why they do it. You know, they've, they're very well-connected people.
127
00:21:52.136 --> 00:22:03.456
They've got their little, little red boo- book of contacts that, that every tech company wants to get ahold of because warm introductions, especially in an ultra-conservative industry like procurement, warm introductions count for a lot.
128
00:22:04.896 --> 00:22:11.496
Where, where I think they go wrong with that strategy is they often think that by bringing in a former CPO as an advisor,
129
00:22:12.496 --> 00:22:20.436
that they're gonna be well-versed in product marketing, competitor analysis, and all the other type of stuff that, that they need to do.
130
00:22:20.556 --> 00:22:29.536
But really, if you're bringing in a former CPO as an advisor, the only thing they're really good for is warm contacts. Hmm. They don't understand marketing.
131
00:22:29.836 --> 00:22:38.636
They, they understand a little bit of product maybe if they've, if they've tried and done it, if they've run RFPs, or if they've maybe implemented a, a, a tool when they were a practitioner.
132
00:22:38.676 --> 00:22:51.056
But the market moves fast, right? So if they did something like that 10 or even five years ago, it's pretty much obsolete. Um, they don't really understand positioning. They don't really understand sales enablement.
133
00:22:51.096 --> 00:23:00.356
They, they, they don't understand customer success. I mean, okay, they know how to not piss off a procurement professional, but, um, they're not the complete rounded
134
00:23:01.316 --> 00:23:13.096
person that I think that the, the, that a procurement tech company would, would need to have. So by all means, they should do that, especially if they're focusing on enterprise where contacts are really important. But
135
00:23:14.216 --> 00:23:27.316
having someone as a procurement advisor doesn't necessarily solve all of their end-to-end GTM issues is, uh, is, is what, is I guess what I'm getting at here. And I dig it. But well, it's also delivery, right?
136
00:23:27.416 --> 00:23:30.276
And that's why I said, I think I said depth of bench, right? Because,
137
00:23:31.336 --> 00:23:45.556
uh, I think the future is owned in, in each business function, procurement as well, by who can assemble the, the largest, most well-versed teams of people that sit at both the intersection of procurement or the business function and technology.
138
00:23:45.996 --> 00:23:48.456
And so everybody needs to become a business analyst, right?
139
00:23:48.516 --> 00:24:07.316
And so if I'm a, a software vendor and I have that-- I'm able to assemble that team, to me it gives me a huge advantage in delivery and potentially in, in solutions consulting and sales as well, because I'm gonna speak the language, and I'm also gonna be able to execute on, on the promises that we make through that sales process, right?
140
00:24:07.376 --> 00:24:16.556
And so I think it's, you know, in a, in an era where the tech is, is more commoditized, uh, I think there's still areas for differentiation in the tech for sure.
141
00:24:17.176 --> 00:24:27.612
Uh, but to me, the human aspect of, of who's behind the tech becomes much more important when you start trying to differentiate between vendors. Yeah, yeah, I, I 100% agree with you.
142
00:24:27.632 --> 00:24:39.412
And I think if we look back to when, when Oro acquired ProcureTech, when was it? March last year, I think. I think that, that was clearly one of the big reasons behind it.
143
00:24:39.612 --> 00:24:52.972
If Oro suddenly is able to solve that bottleneck of having former consultants who, who have worked and done software implementation and have done solutions consulting, if you've suddenly got, what were they?
144
00:24:53.012 --> 00:25:00.992
I
think they're a team of about 12 then when ProcureTech, when, when Procure, ProcureTech were acquired. They've suddenly got a bunch of them now sat in London that can do that, then
145
00:25:02.112 --> 00:25:08.932
that massively accelerates their, their go-to-market strategy because they're not scrambling around trying to, what?
146
00:25:09.232 --> 00:25:19.672
A, trying to hire, or B, trying to pull people in from other areas of the business to, to, to help on implementation when they should be, you know, doing sales or product or whatever it is that, that their real job is.
147
00:25:19.732 --> 00:25:29.932
So yeah, I mean, I think that's a solid example of, of an acquisition that clearly was, wa- was executed to fix that issue.
148
00:25:30.472 --> 00:25:43.372
It's also something that we're seeing much more with these, I'll call them new generation providers, that didn't used to be the case with older generation providers where, um, or, uh, there's never a good term, right?
149
00:25:43.432 --> 00:25:51.232
Like tr- traditional or legacy w- you know- Yeah... people that are more established providers- [laughs]... where it was really all about selling the software, right?
150
00:25:51.312 --> 00:26:06.032
Giving you the software deal, and we're just focused on product, and, like, you're gonna have to use a partner, an implementation partner or an SI, uh, right, the, the, the big firms of the world to implement the solution, and that adds complexity and, and layers of complexity.
151
00:26:06.452 --> 00:26:19.852
And I think we're prob- they're, you know, they're probably getting to that point as well with this, these new gen solutions where you're never gonna be able to do everything in-house and have as deep a bench where you're, you're actually in the services business versus the software business.
152
00:26:20.292 --> 00:26:35.312
But I do feel like that's, you know, the most successful deployments I see are, is when the software vendor has the delivery capabilities and, and is able to, um, to completely carry out, uh, the implementation and deliver the outcomes that, that are promised for, right?
153
00:26:35.352 --> 00:26:44.632
It just makes the relationship so much simpler because there's one less party involved. Um, and then, you know, go get staff augmentation if you need to to, to supplement that project team.
154
00:26:44.672 --> 00:26:57.372
But, um, that's where I've seen the best, the best results, right, is like what the simplest business relationships and, and the providers that have the capability to deliver on what they're, they're selling and not just giving you software.
155
00:26:58.372 --> 00:27:04.292
It's a classic textbook case, isn't it, of how Elon Musk managed to disrupt the automotive industry by vertical integration with- Mm....
156
00:27:04.352 --> 00:27:13.992
with, with Tesla when every other OEM was, uh, w- w- was subcontracting different aspects of the manufacturing process out to suppliers.
157
00:27:14.032 --> 00:27:23.212
And, and with that, all of the D&D, all of the design and development work, um, he, he, he flipped that on i- on i- on its head and, uh, and, and created...
158
00:27:23.252 --> 00:27:26.912
Well, you could argue, is Tesla a tech company or a, or an automotive, automotive company? Mm.
159
00:27:26.932 --> 00:27:36.472
We won't go there, but, but the, the point is the same that he, he, he completely flipped the script and, and, and that's given him the moat. Yep. No, absolutely.
160
00:27:36.832 --> 00:27:47.292
Uh, and so as we, you know, we've taken some time to define another problem, right? Uh, there's, there's a tendency for every piece of procure tech to, to look the same, at least on the surface.
161
00:27:47.832 --> 00:27:54.452
Yes, there's differentiation at the tech level and also big differentiation at the expertise level to be able to deliver the outcomes.
162
00:27:54.912 --> 00:28:08.072
And so if we shift gears towards helping procurement pros, like, find a solution to this, this issue of how to navigate the market, uh, I have, I have my little perspective, but I'd love to hear yours and maybe we can contrast and, and complement each other.
163
00:28:08.612 --> 00:28:17.832
Uh, how, how do you-- what do you advise procurement pros do that are trying to make sense of this market? I think the biggest one is understanding
164
00:28:18.952 --> 00:28:30.092
what, what implementations have already been done in your industry sector, in your country or geographical region, and in, and in com- and in companies that are of your similar size.
165
00:28:30.932 --> 00:28:39.792
Because that gives you a benchmark of, A, how mature they are and B, whether they've got experience of, of delivering in, in, in the space that you're playing in.
166
00:28:40.452 --> 00:28:44.932
So I think that would be, that would be the first of all the one that would be a qualifying question.
167
00:28:44.972 --> 00:28:55.912
I mean, not, not if we're talking early stage startups, but if we're talk- talking like intake and orchestration players that are quite established or source-to-pay suites, that, that would be, that would be one of the first things I would look at.
168
00:28:57.132 --> 00:29:00.972
Also- References. Yeah, re- yeah, references, but relevant references.
169
00:29:00.992 --> 00:29:13.692
You know, if, uh, if the, if the CPO of Google splashed all, all over Procurement Magazine on a case study, but you're a, a 1,000 employee manufacturer somewhere in, in, in, in the middle of Germany, then is that relevant?
170
00:29:13.772 --> 00:29:17.012
Well, probably not. Mm. Um, so relevant references.
171
00:29:17.652 --> 00:29:28.592
Um, the second one, and I think this is all on procurement leaders' minds as they do their due diligence, even if they've been able to differentiate between all of the different providers,
172
00:29:30.012 --> 00:29:36.032
which ones have the backing and the runway and enough, uh, and, and enough
customers and enough
173
00:29:37.112 --> 00:29:44.752
profit or, or, or a roadmap to being profitable, that means they're not just clinging on for dear life to get the next round of funding.
174
00:29:45.372 --> 00:29:52.312
And we, we have seen quite a bit of wash out of, uh, of some of the ones that haven't made it, certainly over the past year or two.
175
00:29:52.892 --> 00:29:59.052
But, but I still think that it's all a case of how close is the system gonna be to your data layer, right? So
176
00:30:00.272 --> 00:30:09.552
if y- if this system's not gonna be your system of record, then it's not as critical if you need to rip it out and replace it with something new.
177
00:30:10.252 --> 00:30:24.132
But if it's going to be, especially if it's your first piece of tech and it's gonna be your data layer and it's gonna be your single source of truth, I mean, this goes back to why is it so difficult to rip out something like SAP Ariba or Coupa if you decide that you don't really like it anymore?
178
00:30:24.532 --> 00:30:29.852
Because it was always the data layer, right? That feeds into your ERP system. It holds all of your supplier data.
179
00:30:30.412 --> 00:30:43.516
So, so how critical is it to your tech infrastructure, I think would be the other one to look at, you know, as you, a- a- because then it becomes a little bit less important Around the amount of due diligence that you do for that product.
180
00:30:44.776 --> 00:30:57.416
You're gonna need to get IT involved extremely early because otherwise you could do a lot of work and then just have that poo-pooed by your IT department because, you know, cybersecurity concerns around, uh, around the AI model that they're using,
181
00:30:58.656 --> 00:31:13.976
all of that. And then increasingly, how are you going to pay for, for the, for the consumption around the AI that, that this system uses if it is indeed, you know, an AI, an AI agentic or AI native tool? Um,
182
00:31:15.836 --> 00:31:28.176
yeah, they would be, they would be, I think, the biggest ones as I look at it now, uh, off the, just off the top of my head. Cool. And I like r- on the references piece, I would add, uh, relevant delivery experience.
183
00:31:28.256 --> 00:31:42.796
Like, and, uh, is the people that are gonna deliver the technology, even though the technology might have been implemented, you know, in a similar company, similar size, industry, or geography, you know, do the people delivering it for you also have relevant references?
184
00:31:42.856 --> 00:31:50.996
Because you could have the exact same setup as an indust- you know, somebody else in your industry, but delivered by another team that gives you completely different outcomes, right?
185
00:31:51.076 --> 00:31:55.056
And so I bring it back to, like, looking at the people behind the, the product. Yeah.
186
00:31:55.096 --> 00:32:08.896
I love your point on due diligence of, of, you know, if you're, if you're gonna use, um, it's gonna be pillar technology for you to run the business function, it is a strategic vendor, right? It is a strategic supplier.
187
00:32:09.136 --> 00:32:11.596
Yeah. And so you need to thre- treat them as such, you know.
188
00:32:11.696 --> 00:32:27.296
In the same way that a manufacturing company would look at, you know, their key raw material suppliers and, and do a deep dive and look at, you know, how the business is structured and who owns what and, and what's the runway and the, the mission and where are they going from a roadmap standpoint.
189
00:32:27.336 --> 00:32:31.056
I think those are all things that people don't think about when they're buying technology.
190
00:32:31.136 --> 00:32:40.416
But increasingly, if you're putting mission-critical business processes in those pieces of tech, then, then yeah, due diligence, deeper due diligence is, is worth it.
191
00:32:41.136 --> 00:32:52.396
Um, and then what I'd, I'd submit to you as a, as a, a way for people to think about it is to flip the script. Because typically we go to the market, we say, "Hey, what does the market have to offer me?" Right?
192
00:32:52.476 --> 00:32:58.136
"What is available?" And we're in listening mode, right? And then we try to make sense of what we're being told.
193
00:32:58.736 --> 00:33:04.696
And I think you do need to do some of that, especially if you're lower maturity in terms of understanding the structure of the market and who the players are.
194
00:33:05.256 --> 00:33:14.416
But very quickly, I, I encourage folks to flip that question around and say, "Hey, let's make our own framework internally for how we wanna develop tech," right?
195
00:33:14.516 --> 00:33:24.316
How we think of the pieces and how they fit together, and let's go to the market asking who can do this for us instead of being kind of passive the other way around, right?
196
00:33:24.396 --> 00:33:36.116
So it's, it's like having your own, you know, using maybe your, you know, your tech map or I have a couple roadmap template slides, uh, that I have on the, the Pure Procurement store as well that people can use as a starting framework.
197
00:33:36.136 --> 00:33:44.056
And then y- you know, it's all about having a conversation that's useful with the vendor, right? Like, "Hey, here's how we think about procure tech. Where do you play in that?" Right?
198
00:33:44.156 --> 00:33:53.036
And they will tell you, like, "Put an X in these three boxes," right? Oh, okay, you can help us with, like, 80% of what we're trying to get to, right? And so having a technology agnostic
199
00:33:54.056 --> 00:34:14.876
framework that you're trying to fill out, uh, as you go to the market, I think is super helpful, and it gets, uh, a vendor, a potential vendor and you talking the same language very quickly, which is your language, your definitions, what you're trying to get to, and the outcomes you wanna generate, which I think kind of fits in nicely with what, the points that, that you mentioned.
200
00:34:15.236 -->
00:34:26.256
Any thoughts on, on that? Yeah, no, 100% agree with you. I think I would, from what, from what you j- just said, actually, I would take, look at this from a procurement tech vendor side and almost say
201
00:34:27.236 --> 00:34:36.836
if you've got a prospect that comes across as super keen and never cancels a meeting and i- is always really responsive, then
202
00:34:38.296 --> 00:34:51.056
I can guarantee that, A, they're not the economic buyer, a- and B, they're probably just looking around to see who's out there in the marketplace as a, as an information gathering session because they, they don't really know what they want.
203
00:34:51.416 --> 00:34:55.356
Which doesn't necessarily mean that they'll never become a customer, but I think it's...
204
00:34:55.396 --> 00:35:00.956
And again, this goes back to, you know, are procurement technology companies as good as they could be with, with sales and marketing.
205
00:35:01.016 --> 00:35:07.416
I think this goes back to understanding how qualified is that prospect in terms of how much time should I be dedicating.
206
00:35:07.556 --> 00:35:13.696
You know, if, uh, if it's someone that's, uh, that's exploring the market, you probably don't wanna put your best salesperson onto that account.
207
00:35:14.856 --> 00:35:26.896
And so, and so, uh, actually that allows me to kind of shift gears to this last set of questions here around, like, so, so can you give us more insight about, like, what types of things are you doing with software vendors to help fix this problem?
208
00:35:26.956 --> 00:35:39.216
I know it's, it's a hard one for one man to solve, but, uh, at least, you know, on a case-by-case basis, uh, how, what are you, um, what are you d- offering as, as services to be able to do that? So ultimately
209
00:35:40.416 --> 00:35:48.836
it's that, it's, it's the end to end, end-to-end go to market typically is, is marketing, sales, and, and customer success. So
210
00:35:50.156 --> 00:35:58.696
what I would typically look at is nothing, it, I would, I wouldn't look at anything that's branding or digital marketing because that's something that a typical marketing agency could do.
211
00:35:58.756 --> 00:36:04.216
You don't need to have procurement expertise to do that. A marketing professional will be able to do that 10 times better than I can.
212
00:36:05.196 --> 00:36:27.476
Where, where I come in is I can help them with their positioning, I can help them with their website, with their copy, with their content, with their materials, with even the kind of events that they're planning to go to, to say, "Okay, where do you want to be seen, and who do you actually want to be signing up for, for, for your white papers or your webinars so as you've not got a load of deadwood sat inside your CRM or on your email list?"
213
00:36:27.816 --> 00:36:38.616
And then that goes through from a sales perspective. Salespeople are much better than I could be as a, a, a, if they're experienced salespeople at doing, at, at doing outreach and appointment setting.
214
00:36:38.896 --> 00:36:47.916
Sales is kind of two, two jobs, right? It's like- Outreach and appointment setting, and then it's nurturing that lead through the sales process and converting them into being a customer.
215
00:36:48.516 --> 00:37:04.976
That sort of more downstream part I can help with much, much more because I know who their competitors are, I know how a procurement professional would typically behave, I know who the other people are that need to be in the room, uh, and I know the sort of behavior that, that signals to me...
216
00:37:05.556 --> 00:37:15.216
And a lot of this is similar to dating as well. You know, it's reading, it's about reading signals, to anyone that's maybe a little bit lost by this conversation. It's all about reading the signals and being able to then
217
00:37:16.596 --> 00:37:28.516
use that psychology to be able to then apply the next step, to be able to... Ultimately, procurement technology companies don't need more lead- well, they don't necessarily need more leads in their funnel.
218
00:37:28.576 --> 00:37:36.176
They just need to, they, they just need to seal all of the holes in that conversion funnel that's stopping them converting all of those deals.
219
00:37:36.536 --> 00:37:51.396
So if you've got a former CPO as an advisor that's opening his little red book and bringing 10 warm leads, but then their sales team screw them up, what's the point of paying this guy, you know, five figures a year to sit on their advis- to, to sit on your advisory board and, and join the odd strategy call now and then?
220
00:37:51.556 --> 00:38:02.096
You know, this... It, it's- Yeah... it's, it's, it's, it's dead dollars if you're doing that. And then the, the final part of that is around increasingly people wanna do proof of concepts, right?
221
00:38:02.176 --> 00:38:08.956
To make sure the, to, to make sure that, that they're, they're familiar with the UX and the, and, and with the workflows and with how you set up users and everything.
222
00:38:09.736 --> 00:38:18.316
Uh, and often procurement professionals or pr- or buyers will push tech companies to do that for free. And, or, or, you know, it's, and, and it's kind of expected now.
223
00:38:18.396 --> 00:38:28.776
So how do you from a solutions consulting or customer success side take that POC, uh, and make sure that you convert that into a, into a paying customer?
224
00:38:29.216 --> 00:38:40.536
Assuming that you've pre-qualified them and you know that there's budget there and they're not wasting your time, and, and, and there's actually, you know, the, the purchase order for the software that's, that's ready to be written if, uh, if you do a good job.
225
00:38:41.156 --> 00:38:49.716
So I think all of these things are intertwined, and if you're at seed stage, then it's, you just need to pick one and fix it because you can't fix everything all at once, you know?
226
00:38:50.096 -->
00:38:58.516
Everyone in those sort of companies in a startup of maybe 15, 20 people is doing three jobs. So you just gotta pick one and, and do it well and, and then move to the next one.
227
00:38:59.096 --> 00:39:11.116
If you're at Series A, Series B, it's more around then having that conversation with the founder or someone at board level and saying, "Okay, we need to look at this holistically, and you need to give me
228
00:39:12.196 --> 00:39:20.136
the resources and the access to be able to go into sales, marketing, customer success," maybe even, you know, product or solutions consulting.
229
00:39:20.796 --> 00:39:31.256
A- and just get them to work together to understand where the gaps are and close them. Because I can tell you one thing, it's a damn sight cheaper than paid ads or [laughs]
230
00:39:31.356 --> 00:39:36.256
influencer marketing or sponsorships or, or conferences. If you can...
231
00:39:36.316 --> 00:39:47.096
If, if the average revenue that you get from a customer is 250K over a lifetime, and I think that's a pretty conservative number, then if you can just close one more deal,
232
00:39:48.176 --> 00:39:56.476
the ROI on doing this is, is really a no-brainer if you do it well. Hm. It is... And there's so much to unpack there, which we don't have time for.
233
00:39:56.536 --> 00:40:06.256
But the whole time you were talking I was thinking about, like, you running a, a matchmaking agency and, and helping with dating and, and just being like, "They're not that into you, man. Like, just let them go."
234
00:40:06.256 --> 00:40:16.716
[laughs] But, but thanks so much for- Well, suddenly cold, cold outreach is like being on a dating app- Yeah... if you're a guy and you're not really tall and good looking, so yeah. [laughs] That's right. That's right.
235
00:40:17.336 --> 00:40:26.196
So anyways, so I, I appreciate you kind of peeling the curtain back on that for people to, to understand as, as procurement professionals as well, like, what's happening on the other side, right?
236
00:40:26.296 --> 00:40:29.236
And what, what the challenges are and all, all this good stuff.
237
00:40:29.336 --> 00:40:40.156
So as we close out here, I'd love to, to shift to, you know, the man behind the role, and I know you're, you're, um, you know, you've got a, a pretty unique lifestyle I think is safe to say, right?
238
00:40:40.236 --> 00:40:47.176
In terms of, like, being a nomad, a digital nomad and, and traveling the world, uh, um, uh, throughout the year.
239
00:40:47.676 --> 00:40:57.336
So, so what made you, and I'm kind of hinting at, at your answer maybe, but what made you leave corporate procurement, uh, to, to bet on yourself and to bet on, on this business model that you described?
240
00:40:58.516 --> 00:41:07.416
Yeah, the, the, there were two things really. I mean, I, I kind of felt that I, I'd plateaued in terms of where I could get to career-wise in, in, in sort of large corporate.
241
00:41:08.096 --> 00:41:19.496
Uh, so that was sort of the push factor and, and kind of why I got into procurement tech was I, I often felt like a very well-paid admin assistant with some of the stuff that I was getting dragged into.
242
00:41:19.516 --> 00:41:27.436
And I thought there must be a better way. You know, you shouldn't be paying me my salary to spend half of my day doing stuff that, that, that, that a good admin assistant could do.
243
00:41:28.136 --> 00:41:39.456
But the real pull thing was, you know, I, I'd just turned 40. I didn't have, didn't have kids, didn't have a big mortgage, and I thought, "Well, what are my two, what are my two biggest expenses in life?"
244
00:41:39.756 --> 00:41:48.476
Well, number one is the government in terms of how much tax I'm paying them. Uh, and number two is, well, how much am I paying for housing and general, you know, cost of living?
245
00:41:48.876 --> 00:42:01.856
I thought if I can, if I can halve those or if I can arbitrage that but still be, but still be able to keep a, a, a Western income or salary, then, you know, that's, that's a mu- a much faster way to financial freedom.
246
00:42:02.456 --> 00:42:12.036
Hm. And e- every time you tell, you t- you tell that story and you start with like, "Oh, I was 40," I'm always like, "You don't even l- look 40 now." [laughs] Like, how are you... He's l- he looks so good.
247
00:42:12.056 --> 00:42:20.156
[laughs] Um, and so yeah. So I, I encourage people to... I know you have, like, you have a weekly newsletter, which I read.
248
00:42:20.256 --> 00:42:30.896
Uh, you know, I follow you on, on LinkedIn and all this good stuff as well, and, and you're always sharing, uh, interesting perspectives, which I don't always agree with, but I think that's part of the richness of, of conversation and debate.
249
00:42:31.216 --> 00:42:40.096
Um, how would you, how would you recommend, before we let people off here with, like, how they can find you, how would you recommend the practitioners think about having a fulfilling career, right?
250
00:42:40.156 --> 00:42:49.076
I, I think you, when you speak, passion seeps through you. Uh, and so, you know, maybe not solo consulting for everybody is, is fit for everybody.
251
00:42:49.136 --> 00:42:58.364
But how would you think about having a fulfilling career as a, as a procurement pro? I think there are so many more options now available to you.
252
00:42:58.424 --> 00:43:09.664
You, you don't have to follow the, the well-trodden path of, you know, try and get a team leadership or a people management role as early as you can in your career so as you've got some chance of, of progressing up the ladder.
253
00:43:09.784 --> 00:43:35.304
I think now more than ever with, with AI and with technology and, and all of the change that's happening in, in procurement, there are, there are way more opportunities now to be a functional or technical expert that will give you a fulfilling and rewarding career if you're maybe tired of the grind as a sourcing manager
or a category manager having to deliver a, an unrealistic savings target every year, and, and you don't really see a way out of that.
254
00:43:35.524 --> 00:43:46.164
You, uh, the historical way out of that was going into some sort of compliance role. Uh, but now there are so many more different procurement roles that you can go into that are not just frontline category management.
255
00:43:46.904 --> 00:43:53.644
That, and I feel like agentic AI kinda, or the AI era blows that wide open, right? Because- Yeah, yeah, 100%. Yeah...
256
00:43:53.664 --> 00:43:58.484
and I was, I was hinting at it earlier in the conversation around, like, everybody needs to become a business analyst, right?
257
00:43:58.524 --> 00:44:07.804
And I feel like there's, if your company does not have a procurement center of excellence or, you know, digital procurement lead type roles or whatever you wanna call it, right?
258
00:44:07.884 --> 00:44:19.644
But somebody who's focusing on, like, how do we use tech and organize work in our function to get the most out of what everybody's putting into it on a day-to-day basis, I'd f- I...
259
00:44:19.684 --> 00:44:27.024
and, and you've listened all the way to the end of this podcast, like, you're an ideal candidate to make the pitch to be like, "Hey, I wanna become that person- [laughs]...
260
00:44:27.104 --> 00:44:35.104
at our company, and I can justify the role with ROI and all this good stuff," right? So, uh, I couldn't agree more on, on that last question, James.
261
00:44:35.704 --> 00:44:48.064
Um, yeah, so thanks so much for, for your time, for being generous with us, uh, your knowledge and, and as I said, right, peeling the curtain back on, on what happens on the other side and why procurement pros see the same messaging everywhere and, and how to go about it.
262
00:44:48.404 --> 00:44:57.144
Where can people find more about, you know, what you're up to, your work, and, and, uh, get engaged with you? Uh, LinkedIn's the, the easiest way. Just look me up on LinkedIn.
263
00:44:57.244 --> 00:44:59.204
I'm pretty active on there, so you'll find me.
264
00:44:59.304 --> 00:45:24.124
Um, like I say, I have podcast, newsletter, other stuff, but LinkedIn's the easiest way, and I'm more, I'm most responsive on there if you do wanna reach out, if you're maybe in a, in a position where you're thinking of transitioning into a different area of procurement or, uh, or even if you're in a procurement tech f- uh, company and, uh, and are wondering how to, uh, how to sort of close the gap in terms of leads that are coming in versus customers that you're getting out the other end, then just reach out.
265
00:45:24.144 --> 00:45:27.784
We'd love to have a conversation. And, uh, and Joël, thank you for everything that you do as well.
266
00:45:27.784 --> 00:45:37.604
And it, you m- we, we play in a similar space, but it's, uh, it's always a pleasure working with you and chatting with you and, uh, it's nice when you can make genuine friends in this space, so I appreciate you.
267
00:45:38.144 --> 00:45:41.804
Yeah, likewise. Likewise. So thanks again for, for coming on.
268
00:45:41.864 --> 00:45:58.344
Thanks for listening to everybody on the, uh, on the podcast here, and if anything, uh, tickles your fancy in terms of Jam- wanting James to speak more about it, let me know and we'll, we'll get him that record, uh, sooner rather than later around being the most, uh, [laughs] the person that comes most on the podcast.
269
00:45:58.364 --> 00:46:05.924
[laughs] Thanks. Thanks, James. Cheers, Joël. Thank you. That's a wrap on this episode of ProcureTech Unpacked.
270
00:46:06.324 --> 00:46:16.144
If you enjoyed this one, give us a follow on your podcast app or YouTube and sign up for the Pure Procurement Newsletter to get procurement technology insights delivered straight to your inbox.
271
00:46:16.724 --> 00:46:26.604
Otherwise, what's the single best way to tell us you're enjoying the show? Leave us a five-star review on Apple Podcasts or Spotify, like the video on YouTube, or drop us a comment.
272
00:46:27.104 --> 00:46:37.764
Whatever platform you're listening on, your feedback means absolutely everything to a niche show like this. All the links, reports, and resources we mention in the episodes are in the show notes.
273
00:46:38.204 --> 00:46:53.784
And as always, a big thank you to our production team over at Resonate Recordings for making us look and sound good. I'm Joël Kanamitsas. We'll see you next week. [gentle music] Resonate.