A vendor announcing its own placement
SAP published a post on September 18 saying SuccessFactors was named a Strategic Leader in the 2026 Fosway 9-Grid for Cloud HR. The post is SAP's own, written by Lara Albert, and it exists because the result went SAP's way. That is how this works. Every vendor in this market publishes the placements that flatter it and says nothing about the ones that do not.
Fosway cites an Excelling Trajectory for SuccessFactors, which the post describes as reflecting increased market performance and customer advocacy. Fosway also says SAP has accelerated its rollout of AI features across HCM and expanded its integration with AI agents. SAP frames where it is heading under the label Autonomous HCM, and you can follow the product line through our SuccessFactors coverage.
This desk has not read Fosway's underlying report. What follows is a read of SAP's post and of what to do when a chart like this one lands in a selection deck you are already carrying.
The Wilson line does more work than the ranking
David Wilson, CEO and founder of Fosway Group, is quoted in the post saying "AI is rapidly expanding what HCM platforms can do, but buyers need providers that combine innovation with real operational depth and consistent execution." That sentence is more useful to a buyer than the zone SuccessFactors landed in.
Wilson is drawing a line between what a platform can do and whether the company behind it can run the thing every month without drama. Those are two different purchases. Capability shows up in a demo. Operational depth shows up in the fourth quarter of year two, when a statutory change lands six weeks before it takes effect and somebody has to get it into your payroll calendar on time.
Convert the sentence into questions you can score. How many of the AI features in the pitch are generally available today rather than in a controlled release. Who staffs the support queue for your region, in what language, and at what hours. What is the vendor's record on shipping legal change patches before the effective date, measured across the last eight quarters. Answers to those separate providers more reliably than a position on a grid does.
Five days to four hours needs a starting point
The number that will travel furthest from this post is PostNL. SAP says PostNL cut payroll processing from five days to four hours, a 90% reduction, and expects an 80% cut in payroll support costs. Both figures are SAP's account of a customer result. The support cost saving is also still an expectation rather than a measured outcome, which is a meaningful difference in a business case.
Before anyone quotes the payroll figure, work out what was being measured. The 90% arithmetic lines up only if a working day means eight hours, which suggests the clock covers elapsed processing time rather than total effort. Elapsed time drops when waiting is removed, and waiting usually sits in handoffs between HR, payroll and finance rather than inside the payroll engine.
Then ask what the five days looked like. A payroll run of that length normally carries manual pre-checks, spreadsheet reconciliation and a batch window scheduled around a nightly interface. Replacing that whole stack moves several things at once, and giving one platform credit for all of it is generous. Our guide on what a payroll parallel run actually proves covers the measurements that survive an audit.
One reference customer tells you about that customer. PostNL's result is not a forecast for your payroll, your country mix or your current process, and a vendor who offers the number should also be willing to put you on a call with the people who produced it.
Who Fosway asked
The 9-Grid draws on Fosway's Corporate Research Network, which the post describes as more than 250 organizations including BP, HSBC, PwC, Sanofi, Shell and Vodafone. That tells you something real and something limited at the same time.
Real, because those are large multinational employers with HR and payroll operations complex enough to put weight on a suite. Limited, because a 1,200 person employer operating in one country holds a different definition of a good HCM provider, and a research network of that shape was not built around it. Our read is that the further your own profile sits from those names, the less the placement should move your ranking.
None of that makes the grid wrong. It makes the grid a measurement of a market rather than a measurement of your requirements. A vendor sitting one zone over may still be the only one who handles your works council agreements or your collective pay rules without a custom build behind it.
Using a grid in a selection
Use the 9-Grid to decide who gets a demo slot. That is the whole job. The criteria behind any analyst grid are written for an entire market, your requirements are narrower than that, and the distance between two vendors on the chart says very little about which one will handle your twelve country payroll footprint.
Once the shortlist exists, evidence has to come from somewhere else. Run the scenarios your own team wrote rather than the ones in the vendor deck, which is the argument in our guide to running a demo on your own terms. We applied the same caution this week to a first edition workforce management grid, where the criteria themselves had no track record yet.
So take one line from this announcement into your evaluation document and drop the rest. Wilson's split between innovation and consistent execution converts into two scoring columns, one for what the platform does in a demo and one for what the provider has delivered on time for customers your size. Fill in the second column before anyone circulates a chart to the steering group.
