DPW Remote Dispatch: To Build Or Not To Build In-House

EDITOR’S NOTE: Here is a quick synopsis from a session that speaks directly to my recent post: Is it time for practitioners to build their “own” ProcureTech solutions?

Below are the highlights from Kearney’s presentation this morning. Have a read, and I will follow up with another post later today, sharing my thoughts.

• The survey was with 200 procurement executives (CPO, digital leads) in large companies (min 1bn majority was 5-20bn in revenue)
• In a nutshell, they almost considered themselves early adopters (a majority) or fast followers (and not wait-and-see-ers). They all planned to build solutions (not buy) with a share of their budget increasing between this year and next year, from a third to two-thirds of the budget they allocate to tech.
  and when asked for the challenges they are facing, number 1 was the last of skills/competencies (north of 2/3) followed closely by a “lack of understanding of the possibilities”. 1% named “Other” Reasons
• A few people were surprised by the results. I was personally shocked by the cognitive dissonance! Basically, people are going to spend more money on something they have no clue about the purpose or how to do.
  Bring the popcorn (or tissues…)
• And I asked if anyone mentioned “quality of the underlying data” as a challenge, but apparently not. Just a CPO in the audience replied “but that’s exactly the point of GenAI, to fix the data”.
  Bring more tissues.

More to come.

30