SAP IBP, o9, Kinaxis — what the demos don't show you

The demo will be flawless. The consultants will fly in with a pre-built tenant on your industry's template. They will show you a dashboard that reconciles financial and operational plans in real time, a demand sensing module that adjusts on point-of-sale data, and a scenario comparison screen where you can stress-test your supply plan against three disruption options simultaneously. The slides will feature your competitors' logos with the phrase "over 200 customers in your industry." The numbers will be impeccable.

None of this is dishonest. The platform does all of that. What the demo does not show you is the eighteen months of data harmonisation work that precedes any of it, the internal headcount required to keep it running, and the gap between what the platform can do and what your organisation will actually use three years after go-live.

This is what that gap looks like — and what to ask before you sign.

The three platforms, without the marketing

SAP IBP — Integrated Business Planning — is the S&OP and supply planning module within SAP's S/4HANA ecosystem. It runs on HANA's in-memory database, which gives it genuine speed advantages on large datasets. The architecture is modular: Supply, Response & Supply, Demand, Inventory, and Sales & Operations are separate licenses. You can start narrow. The trap is that the modules are priced separately and the real value emerges from integration across them — so your "starter" implementation has a built-in upsell path built into the product architecture.

Pricing for a mid-market manufacturer (5,000–15,000 active SKUs, 10–15 planners) lands in the $380,000–$520,000 annual range for software alone. Implementation from a Big Four partner typically runs 18–24 months and 1.5–2.5x the first-year software cost. IBP's natural home is a company already deep in SAP — if your ERP is S/4 and your master data lives in SAP, the integration argument is real. If your ERP is Oracle or a custom stack, you are adding an integration layer whose maintenance cost will compound annually.

Gartner's 2024 Magic Quadrant for Supply Chain Planning placed IBP as a Challenger, not a Leader. The reasoning: strong functional depth, strong SAP ecosystem fit, weaker on ease of use and speed of deployment relative to the pure-play competitors. The customer satisfaction scores in Gartner Peer Insights are telling — not bad, but consistently below Kinaxis on "time to value."

Kinaxis Maestro (formerly RapidResponse) operates on a different architectural principle: concurrent planning. Rather than running sequential optimisation runs — demand plan feeds supply plan feeds financial plan — Maestro maintains all plans simultaneously in memory and propagates changes across them in near-real time. When a supplier confirms a component shortage, Maestro does not queue a nightly batch job to repropagation across the plan. It cascades the impact immediately, across demand, supply, and finance, and surfaces the decision options.

This architecture is genuinely differentiated. It is also genuinely expensive: $100,000–$500,000+ annually depending on user count and module scope, with a similar 1.2–1.8x implementation multiplier. Kinaxis is a Leader in the 2024 Gartner MQ, and its peer review scores are consistently the highest of the three platforms on user satisfaction and planning cycle speed. Its weakness is the opposite of SAP's: strong in planning agility, weaker in deep S/4 integration for companies where the ERP is the system of record for everything downstream of the plan.

The concurrent planning proposition matters most for companies with high supply volatility, short customer lead times, and planning cycles that currently run weekly or longer because the batch window is the bottleneck. If your planning cycle is daily or faster, Kinaxis's architecture removes the clock from the constraint. If your planning cycle is monthly and driven by human alignment rather than compute time, you will not see the architectural advantage in practice.

o9 Solutions competes at the high end: Fortune 500, complex global networks, multi-enterprise planning. Its differentiator is the Enterprise Knowledge Graph — a unified data model that maps the relationships between customers, SKUs, suppliers, facilities, and contracts, and allows planners to query the plan the way you would query a graph database: "what are the second-tier supplier dependencies for this SKU in EMEA?" rather than "run this report."

o9 was a Visionary in the 2023 Gartner MQ. It was demoted to Niche Player in 2024 — the report cited execution concerns as o9 scaled its customer base rapidly. Customer reviews are more polarised than Kinaxis: high scores on capability breadth, lower scores on implementation experience and support responsiveness. The pricing is bespoke and non-public, but industry benchmarks put it above Kinaxis at the enterprise tier.

Figure

The question the demo cannot answer

Every platform produces a better plan than your current process in a controlled demo environment. The demo tenant has clean master data: consistent units of measure, no duplicate material numbers, supplier lead times that reflect reality rather than the system default from 2017. Your tenant will not.

The foundational constraint of supply chain planning software is not algorithmic. It is data. The plan is only as good as the master data that constrains it and the actuals that feed it. Every implementation I have seen that underdelivered on its business case ran into the same root cause: the planning tool was deployed before the data was ready, and the data was never fully cleaned because the project ran out of budget after the software was live.

Before evaluating any platform's planning logic, audit your master data against four questions:

1. Lead time accuracy. Do your system lead times reflect current supplier performance, or the contract lead time from three years ago? In most implementations, the answer is the contract lead time. The gap between system lead time and actual lead time is the single largest source of planning error, and no platform fixes it algorithmically.
2. Unit of measure consistency. Are all inputs — demand forecasts, supply plans, inventory positions — expressed in the same unit? Mixed UoMs are common in multi-ERP environments and produce planners that override the system because they do not trust the quantities.
3. BOM completeness. For discrete manufacturers, is every active finished good covered by a current, accurate bill of materials? The supply plan is built on BOM explosion. An incomplete or stale BOM produces a plan that is structurally wrong before any optimisation runs.
4. Supplier capacity data. Do you have confirmed supplier capacity by period, or do you plan against unconstrained supplier output? Most companies plan unconstrained and discover constraints during execution. The platform cannot model constraints that are not in the system.

What to ask before you sign

The questions worth asking in vendor negotiations are not about feature matrices. They are about failure modes.

Ask for a reference with your data profile. Not your industry — your data complexity. If you have 80,000 active SKUs across 14 manufacturing sites with 6 ERPs feeding the planning layer, ask to speak to a customer with a similar profile who is three or more years post-go-live. The early adopters are the ones in the case studies. The three-year customers tell you what the steady state looks like.

Ask who owns the model post-implementation. Most implementations are delivered by a system integrator. When the SI leaves, the model sits with an internal team. Ask specifically: how many internal FTEs does a comparable customer require to operate this platform in steady state? The answer should be verifiable. "Two power users and a part-time IT resource" and "four dedicated planners and a full-time IT architect" are both legitimate answers. The first is optimistic for a complex implementation; the second is expensive but honest. Whichever number you are given, double it for the first two years.

Ask about the change management scope. Supply chain planning tools change how planners work every day. The platform is not a background system — it is the planners' primary interface. If the implementation plan does not include a structured change management workstream with named internal owners, the implementation will produce a system that planners route around rather than work within. This is not hypothetical. Most of the "failed" planning implementations I have seen were technically delivered on time and budget. They failed because the planners continued to use Excel as the system of record and used the new platform to generate a report for the S&OP deck.

The right sequence

The platforms are real and the value is available. The sequence for capturing it:

1. Baseline your current process. Measure forecast accuracy at each tier, measure planning cycle time, identify the top five manual workarounds in your current process. These are your benchmarks. Any vendor should be able to show you specifically how their platform addresses each one.
2. Clean the data first. Or at minimum, define and fund the data cleanup workstream before go-live, not after. Scope it as a parallel track to implementation, not a post-go-live cleanup.
3. Pilot on a constrained scope. One product family, one region, one manufacturing site. Prove the concept against your data before scaling the license. Most vendors will agree to a paid pilot that converts to full license on success — if they will not, that tells you something.
4. Define what you will stop doing. Every planning tool is adopted faster when the old process is turned off. If planners can continue using the legacy process in parallel, they will, particularly when the new platform encounters the inevitable rough patches of early rollout. Define the cutover date and hold it.

The platform is not the bottleneck. You are. The question is whether your organisation has the discipline to fix its data, change its process, and build the internal capability to run the tool you just bought. The vendors will be helpful at sales and implementation. The capability that survives after they leave is entirely yours to build.

---

Sources

• Gartner. (2024). Magic Quadrant for Supply Chain Planning Solutions. gartner.com
• Gartner Peer Insights. (2024). Reviews for Supply Chain Planning, 2024. gartner.com
• Lee, H.L. (2004). The Triple-A Supply Chain. Harvard Business Review.
• Lapide, L. (2005). Sales and Operations Planning Part I: The Process. Journal of Business Forecasting.
• SAP. (2024). SAP IBP Product Overview. sap.com
• Kinaxis. (2024). Maestro Platform Overview. kinaxis.com
• o9 Solutions. (2024). Enterprise Knowledge Graph. o9solutions.com