Spreadsheets breed little kingdoms, and SAP is often left outside the gate. That is the operational mess Martin Rowan, managing partner at Reveal USA, Inc. in Naperville, is taking aim at in a Nov. 19, 2026 HelloNation feature. His central point is not terribly glamorous, but it is dead right: a company gets less stable when it uses SAP to explain yesterday's results while running today's decisions through scattered files, side conversations, and competing assumptions.
Reporting Is Not the Same as Running the Business
Plenty of organizations have made a hefty investment in SAP, then behave as if the real operating system is a spreadsheet somebody emailed at 6:42 p.m. That arrangement feels flexible until it does not. Planning gets detached from execution, departments carry their own versions of inventory, demand, procurement needs, or performance targets, and management spends precious time arguing over whose numbers are current. Rowan's argument is that SAP should sit at the center of planning and execution, not merely serve as the place where the final score is posted.
There is a hard-nosed business implication here. Decision latency is not some consultant's decorative phrase. It means a buyer, planner, plant manager, or finance team waits too long for reliable information and reacts after a problem has already become expensive. The notes do not attach a dollar figure to those delays, and investors should not invent one. Still, anybody who has watched excess inventory accumulate or procurement scramble after a missed signal knows the broad direction of travel. Slow, fragmented decisions usually cost money.
One Data Source Changes the Accountability Game
Rowan highlights version control, automated checks, and system-wide integration as benefits teams lose when they pull SAP data into disconnected spreadsheets. None of that sounds dramatic on a slide deck. On an operating floor, it can be the difference between a manageable exception and a week of cleanup. If everyone is working from the same live information, it becomes tougher to hide behind an outdated tab or claim a handoff was somebody else's problem.
- Planning and execution can draw from current SAP data rather than dueling spreadsheet estimates.
- Automated checks can reduce avoidable errors and duplicate work.
- Shared visibility can make responsibilities clearer across functions.
- More consistent processes can help stabilize service levels for customers and employees.
The catch, naturally, is that software does not fix a company that refuses to make decisions. A centralized system can expose stale master data, weak ownership, and messy workflows with brutal clarity. That is uncomfortable, and it is precisely why some teams keep a private spreadsheet lifeboat nearby. They trust the file because they control it. Rowan is arguing for a cultural shift: trust the integrated process enough to operate in real time, then make people accountable for maintaining it.
“When SAP Stops Explaining Results and Starts Delivering Them”
Working Capital Is Where the Argument Gets Serious
The most investor-relevant part of this discussion is not the tidy promise of better dashboards. It is the prospect of tighter procurement and inventory decisions. The HelloNation article says that aligning planning and execution in SAP can free up working capital and reduce unnecessary spending. That makes sense. When purchasing and inventory actions rely on current operating data instead of disconnected estimates, a business has a better shot at avoiding surplus stock, rushed orders, and cash tied up in the wrong places.
But this is not a magic lever. The notes offer no before-and-after figures, no implementation timeline, and no claim that every SAP user will suddenly become lean and flawless. Good. Those details matter, and their absence should temper any grand conclusion. The value lies in the discipline: better information can support better action, provided leadership actually redesigns the work around the system rather than digitizing old confusion.
The Practical Signal to Watch
For executives and investors watching businesses that rely heavily on SAP, the useful question is painfully simple: does the company execute inside the platform, or does it export the data and manage the business elsewhere? A firm that keeps reconciling conflicting files may have more operational fragility than its polished reporting suggests. A firm that integrates planning, procurement, inventory, and execution around current data may gain faster decisions, clearer ownership, and steadier operations.
Rowan's message is ultimately a warning against treating an enterprise system like an expensive rearview mirror. SAP can report what went wrong. Used properly, it may also help a business spot trouble earlier and act while there is still room to maneuver. That is less flashy than a transformation slogan, but it is the kind of boring competence that tends to hold up when conditions get rough.