![]() ![]() While the focus with these reports is squarely on which vendors are positioned where in the charts, the analyst synopsis of the technology sector and vendor analyses receive relatively little attention, yet provide as much if not more insight. Being relegated to the dustbin, the Contenders band by Forrester ( Niche Players quadrant by Gartner), can bring even the burliest technology marketer or sales professional to tears. Well aware of the consequences, us vendors anxiously await the results, sweating over whether our dot is positioned in the coveted Leaders band or quadrant. Practitioners regularly refer to them to determine which vendors to invite to RFx’s and, to some extent, which vendor to select. The publication of a new Forrester Wave report (or Gartner Magic Quadrant for that matter) generates a lot of excitement to those of us in the industry. Forrester more recently updated their focused report on SRPM, with The Forrester Wave™: SRPM Platforms, Q3 2020, which provides more in depth analysis of that specific area. ![]() It covers spend analysis, sourcing, contract management and supplier risk and performance management (SRPM), similar in scope to Gartner’s Strategic Sourcing Application Suites Magic Quadrant. The second, authored by Andrew Bartels and published on December 18, is The Forrester Wave™: Source-To-Contract Suites, Q4 2019. The first, authored by Duncan Jones and published on December 10, is The Forrester Wave™: eProcurement Platforms, Q4 2019, which covers purchasing and invoicing (similar scope to Gartner’s P2P Suites Magic Quadrant ). Last year Forrester published 2 major Wave reports, which together span the full Source-to-Pay process. It makes the case for complete suites over best-of-breed and goes into details as to why ERP vendors are simply struggling to be competitive outside their core areas. ![]() This article pulls together several experts on the Source-to-Pay process including Alex Saric of Ivalua and Duncan Jones and Andrew Bartels of Forrester.
0 Comments
Leave a Reply. |