Replay | Focal Point Request Intake & Orchestration for Coupa Webinar

0:00
welcome everyone thank you so much for
0:02
joining us today um we’re really excited
0:04
today we’re bringing you focal point
0:06
request intake and orchestration for
0:08
Koopa the webinar um this is a Q&A
0:11
session so if you do have any questions
0:13
while we’re going through this please
0:14
feel free to go ahead and send them in
0:15
the chat and we can touch on them at the
0:18
very end but without further Ado I’m
0:20
going to go ahead and introduce you to
0:22
your wonderful hosts today we’re joined
0:24
by Matthew Buckingham who is our SC
0:26
Business Development um and Partnerships
0:28
here at focal point and Zach bolt who is
0:30
our SVP of strategy and operations thank
0:33
you both so much for joining and
0:34
chatting with us today thanks by thank
0:37
you I appreciate it we’re super excited
What are Request Intake and Orchestration
0:40
so this is a Q&A format um we have three
0:43
main questions we’re going to cover
0:44
today the first is what are request
0:46
intake and orchestration the second is
0:48
why Koopa customers need an intake and
0:50
orchestration solution and then of
0:52
course third what does focal point
0:53
intake and orchestration actually
0:55
includes so we’ll get into the
0:56
nitty-gritty of that solution um and
0:58
give you some opportunity to ask
0:59
questions so without further Ado let’s
1:01
jump into question one what are request
1:03
intake in
1:06
orchestration
1:09
sure first yeah okay I got it um yeah I
1:15
think what we need to think about with
1:16
intake and orchestration is often they
1:18
get muddled up into the same thing so
1:20
people talk about orchestration and they
1:22
think about intake or they talk about
1:23
intake and they think about
1:25
orchestration um I’d just like to
1:27
separate it out and say okay it is kind
1:30
of two things one is a task so intake is
1:33
is getting a request it’s it’s getting
1:35
something into the system whereas
1:36
orchestration is actually going through
1:39
the whole flow of that that request and
1:42
making sure that it happens and um
1:44
that’s that’s how I kind of look of it
1:46
what about you Z yeah you know I really
1:49
love this breakdown here on on this line
1:51
that’s been
1:52
drawn such a brilliant take on this
1:55
where intake is is like a point in time
1:57
it’s a task it’s an activity that’s done
1:59
and honestly it’s it’s it’s the really
2:02
most tactical element of all this it’s
2:04
basically just taking the room and
2:05
sweeping something in the door and where
2:07
it goes after that the user may or may
2:09
not know or even care but then what what
2:12
really makes the impact in terms of
2:14
organizational efficiency and what you
2:16
get out of that is the orchestration
2:18
which is a much broader process based
2:20
sort of function and so going to get
2:23
that I mean it requires both of them in
2:24
order to really automate your your
2:26
processes and to to extract the maximum
2:28
amount of value you know if you’re
2:30
coming off a Google form or something
2:31
like that obviously intake going to
2:33
going to help you and make your life
2:34
better getting in the door let you
2:36
triage and sort of manage cues of work
2:39
but then when you really talk about
2:41
stitching all of your technology
2:42
together as a process as a function
2:44
orchestrations required to do that and
2:47
that’s how we at focal point really draw
2:49
that line and the distinction between
2:50
the two that to your point people use
2:52
the term sort of interchangeably U but
2:55
they’re not exact they’re not fungible
2:56
you know they have they they stand alone
2:58
but they also work together very
3:01
well yeah I agree I think you know you
3:05
and you can have those different types
3:06
of intake as well so there’s there’s
3:08
different elements that you could bring
3:10
into the system um with the intake but
3:12
without an intake there’s no point for
3:14
orchestration got nothing to orchestrate
3:17
basically um so you know if you’re just
3:19
if you’re just bringing in something to
3:21
do a a contract or you’re bringing in a
3:23
procure to pay something you somebody
3:25
needs to buy um you need an intake for
3:28
that and that can come from various
3:30
places yeah that’s a good point too
3:32
about intake as as it like so what
3:35
you’re collecting it is a task but what
3:37
are we collecting what are we taking
3:39
into the to the to the organization a
3:41
lot of the folks that we talk to are are
3:43
procurement individuals and they’re like
3:45
okay I have a a point sort of a point
3:47
need I need to intake a request for a
3:49
contractor A supplier largely it starts
3:51
as a as a business need you’re your user
3:54
may or may not know what they need in
3:55
terms of like Vehicles like a contract
3:58
or you know a tender or anything like
3:59
that but they know they have a business
4:00
need I I need a piece of technology I
4:03
need a consultant you whatever right and
4:05
so but beyond the the procurement
4:08
Centric lens of that as well is the
4:10
broader organization you need intake
4:13
because you have it tickets you need
4:15
intake for people to make inquiries into
4:18
the operations department or to uh go
4:20
find their HR representative and
4:22
information like that so intake is
4:24
broader than just the front door for
4:25
procurement it can really be a a front
4:27
end or a front door for your organ for
4:30
users inside your organization who need
4:32
anything this is your one place to go to
4:35
jump off to get to any channel inside
4:37
this company that you need and so that’s
4:39
that’s another key distinction in terms
4:41
of intake it’s not just a procurement
4:43
function it is a
4:44
broad-based uh organizational function
4:47
that provides a good user experience for
4:49
your entire requestor community and that
4:51
can be any employee in your
4:53
organization yeah and then the
4:55
orchestration element’s going to take it
4:57
to the right place from there as well so
4:59
whether it’s
5:00
as you said it could potentially be an
5:01
IT ticket it’ll then whiz it off to
5:04
somebody in it to say solve this and and
5:06
that’ll be the that part of the triage
5:09
but um I think here here we’re trying to
5:11
focus very much on the on the intake for
5:13
procurement to some extent and and
5:16
specifically for Cooper honestly but um
5:20
yeah awesome thanks yeah I think that’s
Why do Coupa customers need Focal Point
5:23
a really good differentiation between
5:24
both of these things obviously like you
5:26
brought up Matthew orchestration um it
5:29
isn’t only Rel intake but definitely
5:31
focusing on on that solution that side
5:33
of the solution today so let’s go ahead
5:35
and move on to the next question now
5:37
that we’ve made that differentiation
5:39
we’re going to talk a little bit about
5:40
why Koopa customers might need an intake
5:43
and orchestration solution um to uh go
5:46
along with their their existing Koopa
5:50
investment yeah absolutely so I’ll start
5:53
off on this one Matthew and then and
5:55
then let you add some commentary to it
5:57
there’s several reasons why uh Koopa
6:00
Koopa customers and you know different
6:02
different clients have or different
6:04
companies have made different
6:05
investments in Koopa you know there’s
6:06
the core PTP then there’s the Upstream
6:08
solutions that you can purchase
6:10
separately and then you can go full
6:11
source to pay and they’ve got all their
6:12
power apps and things like that so you
6:15
know different people have different
6:16
different starting points and that sort
6:17
of informs the the Upstream need one of
6:20
the major uh major challenges that that
6:23
we helped to solve when when we worked
6:25
with Koopa to build a certified app here
6:27
was the different ations like some of
6:30
the supplier sourcing uh the contract
6:32
solution and the P2P you needed to go
6:35
through all these motions maybe you have
6:36
a supplier that needs to be on boarded a
6:38
contract that has to be done and
6:40
companies even if they’ve got investment
6:41
in the entire Koopa source to pay stack
6:44
those don’t all necessarily talk to each
6:46
other and there’s no way to tie all the
6:48
breadcrumbs together for the user
6:50
Community like okay I’ve submitted my
6:52
need now where is it in the process and
6:54
so focal point has helped to solve that
6:56
transparency and visibility and that’s
6:58
one reason why that you might would need
7:00
that a second reason would be you’ve got
7:03
Investments Beyond Koopa you’ve got
7:04
Koopa PTP but you’ve got another system
7:06
for CLM you’ve got another system for
7:08
supplier another yet another for
7:10
sourcing and again you need to tie all
7:12
of these together in a single Enterprise
7:14
workflow not only for the requester
7:16
community but also so that folks who
7:18
have to take the appropriate actions to
7:20
get those needs met they all know when
7:22
they need to to when the gun goes off
7:24
and when they need to to start their
7:25
work and thirdly I mentioned this point
7:28
earlier to kind of segue into this topic
7:30
a little bit was that broader based you
7:31
know Koopa is one point of of of
7:34
interaction for your your request or
7:35
your business Community but you may have
7:38
tickets that need to go to it and other
7:39
things is so focal point can become a
7:41
digital front door if you need that sort
7:43
of DFD uh approach for your your
7:46
business Community then uh that’s why
7:49
you might would consider even though
7:50
you’ve already got investment in a
7:52
procure to pay or a source to pay
7:53
solution Suite Matthew what are your
7:55
thoughts on
7:57
this yeah I I agree with you know what
7:59
you’re saying I mean we we both love
8:01
Cooper we both used to work for Cooper
8:03
at some point not at the same time but
8:05
both both Zach and I are ex or Cooper
8:08
alumni so we love Cooper um but you’re
8:12
right I mean it could be that this is
8:14
something that that’s outside the bounds
8:16
of Cooper that that we’re processing
8:17
here it could be something that’s that’s
8:19
coming in from somewhere else within the
8:21
business um that doesn’t even need to to
8:24
to touch Cooper but when it does go into
8:27
Cooper what we enable then with the or
8:29
rtion layer especially we’ve we’ve got
8:31
this into into Koopa now we we enable
8:34
that communication between the the teams
8:36
and the Departments so I see it as two
8:39
different levels of orchestration you’ve
8:41
got the the data or system orchestration
8:44
where you’re bringing in different
8:46
information from different systems which
8:48
could be Cooper but it often is not all
8:51
kooper um but then you’ve also got the
8:54
human integration or orchestration um so
8:57
so allowing people to communicate with
8:59
each other um be it through slack or
9:02
through teams or through email hav
9:05
forbid um and other places um you can
9:08
you can orchestrate all of the the
9:11
communication through our solution then
9:14
and and use Cooper for what it’s really
9:16
really good at which is which is buying
9:18
stuff and making sure the right catalogs
9:20
are being accessed and that that the
9:23
customer and and the end user are buying
9:25
from the right place um you can you can
9:28
do all of that within Koopa and take it
9:31
right through to purchase order and
9:32
purchase receipt and um and everything
9:35
else but within within the Koopa
9:37
platform but you’re at the same time
9:39
giving your users that access to
9:43
information of where’s my stuff if you
9:46
like so taking away that that level of
9:49
effort that the procurement team the
9:51
human part of the the procurement team
9:53
needs to do um to interact with the end
9:57
users and and let them know what the
10:00
latest status is and everything so we
10:02
can we can do the intake from that end
10:04
user and that end user can follow that
10:06
all the way through within the focal
10:08
point platform even though the work is
10:10
going on within Cooper a lot of the time
10:12
it could also be going on somewhere else
10:14
and I always get told off by how I say
10:16
Cooper by the way just because of my
10:17
silly
10:19
accent but what an elegant way to unpack
10:22
uh the the topic of orchestration there
10:25
you talked about data orchestration
10:27
process orchestration system
10:28
orchestration and then people so it’s a
10:31
really I think that’s an elegant way to
10:33
unpack that that to that topic a little
10:35
bit more and and because you need to be
10:39
able to do all of those those things in
10:41
order to truly orchestrate processes and
10:44
and if you if you step back away from it
10:46
the the idea is to give people the the
10:49
stakeholders regardless of who that
10:51
constituent group is whether it’s the
10:52
request or Community or the folks who
10:54
are actually doing the work either in an
10:56
orchestration solution or in an external
10:58
system to get them all the best outcome
11:00
and to help them know paint by numbers
11:02
what do I need to do and when do I need
11:04
to do it by and so that they can all
11:06
work the most efficiently and be the
11:07
best version of themselves which creates
11:09
good outcomes for the
11:10
organization yeah and it gives you that
11:12
order to portrayal as well at the same
11:15
time so that you know it’s it’s drisking
11:17
you now as well so you’re you’re you
11:20
know you’re buying from the right place
11:22
at the right time um and that that
11:25
you’re using the right supplier and that
11:26
you’re using the right contract as well
11:29
and
11:29
that’s an amalgamation of the two
11:31
different systems at that time but we
11:32
can track all of that and have that
11:35
auditable trail within our system and
11:37
then after that you can you can also
11:40
start to follow those kpis and
11:43
understand you know how are we doing
11:45
it’s not just about where’s my stuff
11:47
anymore it’s how are we doing on those
11:49
sustainability Targets on those
11:51
financial targets or or whatever um and
11:54
we can track all of that within our
11:56
orchestration tool as well at the same
11:58
time pulling that data from from Cooper
12:00
and and working with Cooper to to make
12:03
that um accessible to
12:07
everybody absolutely awesome thank you
What does Focal Point Intake Orchestration include
12:10
both for those answers I think of course
12:12
words my stuff is always a relatable
12:14
question um for for procurement but kind
12:17
of hearing how orchestration can help
12:19
solve that and also go beyond and uh and
12:21
help procurement move in into those
12:23
strategic initiatives like ESG is is
12:25
awesome so thanks for that thorough
12:26
answer we’ll move on to topic three now
12:30
um which is why or what does focal point
12:32
intake and orchestration include so I’ll
12:34
scoot this up here so we can all see um
12:37
and let’s just kind of get into what
12:39
that solution is going to cover for us
12:41
and maybe some of the benefits for
12:42
procurement as
12:46
well yeah I mean I I can jump in but
12:49
Zach’s the absolute expert on this but
12:51
um you know what’s included we’ve talked
12:53
about a lot of these things already so
12:55
that single front door experience so you
12:57
only have to have that one place to
12:59
start um the flexible no code intake
13:03
form so so your business team can set up
13:06
those those intake forms and and also
13:09
use you know our our AI engine to to
13:13
complete those forms for the for the
13:15
users as well um configuring those
13:18
orchestration workflows I mean it’s it’s
13:21
easy to do Zach do you want to jump in
13:25
oh well you’re doing a Yan’s job there
13:27
so uh not not going to interrupt a man
13:29
when he’s uh doing a fantastic job yeah
13:32
this was you know this out was a lot of
13:34
fun for us to to work with CP but a
13:37
partner with and and to develop we
13:39
delivered so many certified out ofthe
13:41
box Integrations that bolster and
13:43
support the underlying data layer inside
13:46
a focal point and the and the
13:47
orchestration so to Matthew’s point you
13:49
know that having that single front door
13:51
experience to jump off and I need to go
13:53
I need to create a request it’s you know
13:55
maybe some sort of service grouping or
13:57
something like that and we need to have
13:58
all these different motions done before
14:00
ready to cut a PR um very flexible
14:04
simple no coding take forms I mean
14:05
that’s just core focal point stuff
14:07
orchestration workflows that are fully
14:09
integrated to Copa core products meaning
14:11
that you can have a workflow that after
14:14
a requestor submits a request can run
14:16
completely autonomously you do your work
14:18
in Koopa set up the supplier set up the
14:20
contract all that and the workflow is
14:22
just informed back and then advances
14:23
automatically inside our solution
14:25
keeping people a breast of what’s going
14:27
on so fully integrated
14:29
configurable workflows obviously that
14:31
enables the the business Community to do
14:33
self-service checks and then we support
14:36
even if you have activities that you’re
14:37
doing let’s say inside of Koopa but then
14:39
other activities that need to go on in
14:41
parallel uh that maybe are not even
14:43
technology related there stuff people
14:45
need to do you can do serial or parallel
14:47
workflow processing with as many
14:50
connected systems as you need and then
14:52
of course all of our Integrations in the
14:53
entire application are fully certified
14:56
by Koopa which means that you know you
14:58
have the confidence that that’s going to
14:59
going to work uh just perfectly in fact
15:02
we we had just got a notification
15:03
yesterday koopa’s uh put out their new
15:06
release and so we have to recertify
15:08
every time that Koopa puts out a new
15:09
release and and and confirm that
15:11
everything that we have built still
15:13
functions properly as it’s specified
15:16
that it should and we do that every time
15:18
Koopa does a new release so you can
15:19
always know that that you’re going to
15:21
have certified Integrations that have
15:22
Koopa stamp of approval on them so
15:24
that’s what you get with focal point in
15:26
terms of our intake and and uh and
15:28
orchestration Solution that’s powering
15:30
that’s powered by CP and helping you to
15:32
get the most out of that
15:35
investment awesome thank you okay sorry
15:39
is there anything yeah I was just gonna
15:41
say one of one of the other things that
15:43
that’s kind of included it’s it’s an
15:45
almost a negative but in some ways but
15:48
we include you you can get away from
15:50
using spreadsheets you can get away from
15:52
um that complicated process and that
15:54
process ambiguity as well so so suddenly
15:57
you you can do all of these things but
16:01
what that what’s the benefit for it um
16:03
the the benefit is really you know that
16:06
that ambiguity goes away people know
16:08
where they stand at any one time you’re
16:10
not using spreadsheets um I saw
16:13
something the other day vlookup is not a
16:16
uh is not a procurement strategy um and
16:21
you can you can start to manage your
16:23
tail spend and everything much better so
16:26
it’s not what’s included but it’s kind
16:28
of included but you’ve got all those
16:30
things that you don’t have to do anymore
16:33
which is awesome I
16:35
think awesome thank you yeah I think
Prerequisites to Deploy AI Orchestration
16:38
that that’s getting a little bit into
16:39
the benefits too as well um but I I
16:42
think that’s awesome thank you both so
16:44
much um so real quick we’ll jump on to
16:47
the next slide I don’t think that I see
16:49
any questions in the chat if you jents
16:51
see any questions at all I do Maya I see
16:54
one okay yeah you want to go ahead and
16:56
start taking that yeah I can so I’m
16:58
going to look up here my other screen
16:59
where I’m monitoring that and I’m going
17:00
to read this off so someone’s asking
17:03
what are the prerequisites to deploy AI
17:06
orchestration successfully in a source
17:09
toay platform so um if you want to
17:12
provide any more clarification as I talk
17:14
on that please feel free to do so I’ll
17:16
I’ll take that and I’m going to answer
17:17
that question you know a couple of
17:19
different ways so first of all When
17:21
anybody comes to us and they want to
17:22
start engaging in in this this broader
17:25
topic of of orchestration the first
17:27
thing that we always ask is all right
17:28
what you your process flows look like we
17:30
tie everything in terms of configuration
17:32
and
17:33
deployment uh to uh business processes
17:37
that we need to support and then we let
17:38
technology be informed by the support of
17:41
a business process so what does that
17:43
workflow look like what what is the
17:44
process flow who what are the approvals
17:47
what systems are going to be involved
17:48
all of that stuff to meet those needs so
17:51
that’s kind of the first basis getting
17:52
the the process flows that we’re going
17:54
to be automating and then secondly is
17:57
being able to get access to all all of
17:59
the data that is required to to
18:00
orchestrate you know all the systems so
18:03
confirming that the systems that you
18:04
have investments in I mean koopa’s got a
18:06
great API but others you know you have
18:08
to check can we actually do what we want
18:10
to do sometimes you can get there
18:12
sometimes you can’t and so then you got
18:14
to figure out if you can get there great
18:16
if you can’t you got to figure out okay
18:17
well what’s the work around here and how
18:19
do we automate to the extent possible
18:21
with the existing technology stack so
18:23
those are a couple of potential pitfalls
18:25
and things that you sort of have to
18:26
think about as you’re starting out on
18:28
this journey to uh embed orchestration
18:30
like this and I think of it like this
18:32
broad uh broad-based workflow layer on
18:35
top of your processes what are we going
18:37
to automate and do the systems connect
18:39
and then and then lastly I would add in
18:41
the other teams you know procurement is
18:43
is often the custodian of policies that
18:45
they don’t own and so in that in that
18:48
being the case you have to collaborate
18:50
with a lot of different groups you know
18:51
third party risk and with legal and as
18:53
others what is the organizational
18:54
willingness of each of those teams to
18:56
collaborate and be a part of a broader
18:58
hold
18:59
in terms of that orchestration layer do
19:01
they want to adopt technology do they
19:03
want to keep using their their tools do
19:05
they want to line up with a different
19:07
process or whatever so those are all
19:08
things that you need to think about as
19:10
you start trying to to to move toward
19:12
implementation of a solution like this
19:14
the technology honestly is the easiest
19:15
part of it it’s the process it’s the
19:17
people you got to work with and it’s the
19:18
external systems that you’re going to be
19:20
working um together with all taken as a
19:23
whole that ultimately inform what you’re
19:25
going to be able to do and then you got
19:26
to figure out how to make the best
19:27
outcome with that we have a very
19:29
experienced just a focal point we have a
19:31
practitioner Le Services organization so
19:35
consultant people that have been a big
19:36
for Consulting have worked as
19:38
practitioners and they’re like you know
19:39
that’s going to work and that’s not
19:40
going to work big differentiator for us
19:43
having these practitioners on staff that
19:45
can help guide and direct Matthew I’m
19:47
going to look at the chat panel a second
19:48
I’m G ask if you have you’d like to add
19:51
on to that as I check for additional
19:53
questions yeah and I’ll just add on to
Focal Point Partners
19:56
that you know we we have our own
19:57
Professional Services team absolutely in
19:59
practitioner Le we we like to ensure the
20:02
quality of what’s going on what we are
20:04
doing though is is starting to work with
20:05
Partners as well to implement our
20:07
solution so if you’ve already got your
20:09
Cooper partner um absolutely we’ll work
20:12
with them to to do that whether it’s you
20:15
know one of the big ones that Accenture
20:17
or deoe or KPMG or PWC or the the
20:20
smaller ones like the cross countries
20:22
and Aquis and and everything else
20:24
they’re going to hate me for saying
20:25
smaller um or or the you know the very
20:29
specialized ones as well we can we can
20:31
definitely work with them and we would
20:33
love to work with them to to implement
20:35
at the same time as well I see there’s a
20:37
couple more questions so I’ll um you
20:40
know both people I know as well that’s
20:42
cool I’m gonna I’m gonna tee this one up
20:44
for you I’m gonna give you a softball
20:45
map so the question for you here we’ll
20:48
both take a whack at this but I’m GNA
20:49
give you a softball so what does it mean
20:52
and why does it matter that focal point
20:54
is a certified Koopa partner why should
20:56
people care about that I I think think
Why does it matter
20:58
for yeah that’s a really good one and uh
21:01
thanks for asking that um why does it
21:04
matter it matters because it it means
21:07
that we’re engaged with Cooper first of
21:09
all so on the on the relationship side
21:12
of this it means that we’re going to
21:14
work together with Cooper to implement
21:16
um kooper’s gonna going to support us in
21:19
this and we’re going to support Cooper
21:20
in this all the way through so so we’re
21:23
going to work as a as a team um I think
21:26
the other element of it is that uh which
21:28
is probably more on your side Zach than
21:30
it is on mine but it’s it’s around what
21:33
we have access to as well so so Cooper
21:35
is is very very um accommodating to to
21:39
Partners um to certified Partners on uh
21:43
enabling them to to do more than
21:47
somebody just off the street um but Z do
21:49
you want to jump into that around the
21:50
apis and stuff yeah I do so so Koopa has
21:54
been a fantastic partner for us you know
21:56
they have a a really open API
21:59
uh public API strategy but as a
22:01
certified partner in this intake and
22:03
orchestration we have jointly worked
22:05
together to develop and bring to Market
22:07
additional capabilities that are
22:09
available only for certified partners
22:12
and so what that means for for you folks
22:14
out here is you get access through focal
22:16
point you get access to do things with
22:19
your Koopa investment that you cannot do
22:21
otherwise and so we’re able to to to
22:24
build and to model and to work closely
22:27
hand inand everything that you’re going
22:28
to get with focal point is fully tested
22:31
it has gone through the Koopa solution
22:32
Consulting team to review it we have
22:35
voluminous documentation on this so you
22:38
know that the package that you’re
22:39
getting out of the box is not only going
22:41
to work but it enables you to do things
22:43
and extract value that you cannot get
22:46
either on your own or with other intake
22:48
and orchestration solutions that are not
22:51
certified yeah I totally agree I’ll I’ll
ARA Integration
22:55
jump on on Jerome’s um question hi
22:57
Jerome
22:58
um so yeah do you provide the same level
23:01
of integration with ar Reba um really
23:03
good question and you know other tools
23:05
are available okay um so we understand
23:09
that Cooper doesn’t have the Monopoly on
23:11
on uh on you know procurement or
23:14
business spend management or or whatever
23:16
we want to call it out there um done a
23:19
terrific job since since they started
23:21
but ARA was one of the one of the first
23:24
procure to pay solutions back in 1996 I
23:27
believe I did work for sap as well um
23:30
but um back in 1996 they launched it
23:34
we’re we’re talking um to some extent
23:37
with sap and and with ARA for sure um
23:40
can we integrate with it absolutely
23:42
there are open apis uh available we’re
23:45
not certified with with sap it’s not
23:48
been
23:49
until until now at least um a priority
23:53
for us um you know we we see Cooper as a
23:56
much better partner for us at at this
23:58
point point in time for sure um and
24:00
we’ll continue to move down that that
24:02
route but um we can integrate with the
24:04
Rea for sure um we can also inter
24:07
integrate with with bruy with Esa with
24:10
Jagger with um a number of the other
24:13
ones that are out there as well we just
24:15
see that you know a lot of the Cooper um
24:19
customers out there have been relatively
24:21
Innovative over the years so that’s been
24:23
kind of where we decided to focus um
24:26
first of all um but um yeah we can we
24:29
can work with the reaper for
24:31
sure awesome good answer so I’ve got one
Cost
24:34
here Matthew I’m going to tee this one
24:35
up you this is definitely right in your
24:37
wheelhouse so someone’s asking how much
24:40
does it cost and do I need a license for
24:42
each user I’ll let you take that
24:44
one okay okay uh it depends uh you know
24:49
the typical salesman’s salesman’s answer
24:51
to that it’s going to depend on the size
24:53
of your company and and um and how many
24:56
people you’re using will will be an
24:58
impact on it for sure um it also depends
25:02
how you have your your Cooper set up
25:04
already um to some extent also um you
25:07
know we we talked about the different
25:10
types of intake you can do we talked
25:12
about so it can be as complex or as
25:13
simple as you want and the cost will be
25:16
reflected in that so um it says here
25:19
Anonymous endee if Mr Anonymous if you
25:22
could uh if you could contact me
25:24
directly I can talk to you about it for
25:26
sure and I would love to have that
25:27
discussion with you
25:29
yes absolutely I was going to say
Contact us
25:31
definitely feel free to reach out to us
25:33
we’re more than happy to chat with you
25:34
there’s a ton of ways you can um chat
25:36
with us oh there one more oh yeah go
25:38
ahead one
25:40
more going back to the benefits Point
25:43
what is the most significant value
25:44
proposition that AI orchestration can
25:46
add to the organization and how
25:48
procurement can build a compelling
25:49
business case around it we didn’t talk
25:51
about AI how could
25:54
we Zach do you want to take that jump
Business Case
25:57
into the business case
25:59
let me read this one again there’s
26:01
several lines here so give me just a
26:02
moment going back okay let me read this
26:05
out loud so for the benefit of everyone
26:07
so going back to the benefits point this
26:09
is from the original question up above
26:11
what’s the most significant value
26:13
proposition that AI orchestration can
26:16
add to the organization and how does
26:18
procurement build a compelling business
26:20
case around it so uh on the business
26:23
case we have an Roi model that’s
26:26
associated with our our technology and
26:28
implementation and so we can work with
26:30
you on that and and walk you through the
26:32
levers and everything for anyone on this
26:34
call who’s who’s interested in having a
26:36
conversation on in terms of of just the
26:38
overall benefits that it adds there are
26:41
several I’m going to start with the one
26:43
that to me I think is is the greatest
26:45
one
26:46
so a lot of the business case for for
26:49
for a solution like focal point is
26:51
predicated on the idea that when you
26:54
start orchestrating processes together
26:56
and you start leveraging intake look
26:59
ideally you’re capturing additional
27:00
spend that you’re not already capturing
27:02
or at least you’re influencing it
27:03
earlier so that procurement has a a
27:06
bigger or more outsized effect on the
27:09
money that the organization is spending
27:11
inside the the orchestration itself
27:13
proper though you get this collaboration
27:16
and the efficiency that is drawn our
27:18
customers tell us that with focal point
27:20
their staff that they have in
27:21
procurement whether that’s five people
27:23
50 or you know 150 200 whatever that
27:26
number is become up to 30% more
27:29
efficient by leveraging focal point now
27:31
if you think about it let’s take a
27:32
number let’s say 20% that gives you back
27:34
a day a week per FTE to do something
27:37
else more strategic with you can manage
27:40
more spend you can take more categories
27:41
to markets you can drisk yourself you
27:43
can help bolster compliance there are
27:45
all kinds of things that you could do if
27:47
the staff that you already have becomes
27:48
substantially more efficient generally
27:51
speaking people tie that to a creative
27:53
spend under management and when you do
27:54
that and you manage more spend you touch
27:57
more spend per year there’s a dollar
27:59
value associated with that that goes on
28:01
top of what you’ve already made in terms
28:03
of Roi with your P2P stack Etc so that
28:06
being the case the business case sort of
28:08
builds itself to say all right if we can
28:10
tackle x amount more spend then we get
28:12
five seven 8% whatever more on that
28:15
dollar that we get and thereby get
28:17
deliver more savings which then feeds
28:19
right back into our PTP system we’re now
28:21
capturing it it’s on catalog it’s on
28:23
punchouts it’s have you know we have
28:24
forms or whatever and so it just kind of
28:26
it’s an engine that feeds it self so
28:28
those are a couple of the leevers
28:30
there’s more but a couple that we can
28:31
really pull on to help you build a
28:33
business case awesome thank you so so
28:37
much for answering all those questions
28:38
and thank you as well to everybody who
28:39
asked um I do want to go ahead and jump
28:41
to this last slide um only because we
28:43
have a QR code here if you have your
28:45
phone go ahead take it out and scan
28:46
it’ll send you right to our um our
28:48
listing on the Koopa app Marketplace so
28:50
you can explore a little bit more and of
28:52
course as Matthew said always happy to
28:55
talk so feel free to reach out to us as
28:56
well um and yeah we’re super excited to
28:59
be partnered with Koopa so thank you
29:00
guys all for joining um and learning a
29:03
little bit more about this partnership
29:04
and uh we will see you at the next
29:06
webinar thank you so much