From Five Years of Patience to Five Weeks to Go-Live: The ERP Story Nobody Told You

[Jens15]

There’s an old saying in Silicon Valley: it takes five years to become an overnight success. In the world of ERP, it sometimes takes a little longer; mostly because ERP projects have a way of absorbing time, money, and optimism in quantities that would make a black hole blush.

But something has quietly changed. And if you’re running a business on SAP, or sitting in a boardroom wondering why your last ERP transformation cost nine figures and delivered nine percent of what was promised, this is worth five minutes of your time.

The System That Runs the Flow of Value

Let’s give ERP its due. ERP systems are the backbone of how value moves through your business. Raw materials become products. Products become orders. Orders become invoices. Invoices become revenue. Every step in that chain is recorded, validated, and governed by your ERP system with a level of precision that your auditors love and your employees occasionally find soul-crushing.

ERP runs the flow of value. It is, in the most literal sense, the system that keeps score.

But here’s the thing about keeping score: it tells you what happened. It does not tell you what to do next. And in a world where a production line can grind to a halt, a shipment can miss a critical delivery window, or a customer can change an order after it’s already in motion, what happens next turns out to matter quite a lot.

This is the job ServiceNow was built for. Not to replace the scorekeeper; to make sure the right people act on the score, fast, every time.

The Problem Nobody Wants to Admit

ERP systems were built to be the system of record. The ledger. The source of truth. And for decades, that’s what they were: magnificent, expensive, and almost entirely locked away from the people who needed to act on the data inside them.

The workflow lived somewhere else. The decisions happened somewhere else. The experience of actually doing something with your ERP data involved a cocktail of manual steps, custom code, and the institutional knowledge of someone who had been at the company since before the internet.

This is the gap that nobody draws on the whiteboard during an ERP pitch: the distance between having the data and acting on it.

If Business Processes Ran Like Clockwork, You’d Only Need One System

Here’s a thought experiment. Imagine your business ran perfectly. Every machine ran without failure. Every shipment arrived on time. Every customer order stayed exactly as submitted. Every production schedule unfolded exactly as planned, with no surprises, no disruptions, and no 2am phone calls from a plant manager in a different time zone.

In that world, you wouldn’t need much beyond a good ERP system. It would record the flow of value, everything would go according to plan, and life would be a beautifully automated sequence of correct transactions.

But that’s not your business. That’s not anyone’s business. That’s why the average enterprise runs close to 200 different IT systems alongside their ERP; spreadsheets are still front and center, and that alone tells you everything you need to know about the gap between what ERP was supposed to solve and what it actually did.

Consider what really happens; A CNC machine on your factory floor starts showing irregular vibration patterns. The data is there, sitting in your ERP system, quietly accumulating. Four days later the machine fails completely. Production stops. Your line is down for three days. The cost runs into the millions; not because the warning signs weren’t there, but because nobody connected them to an action fast enough. Predictive maintenance isn’t a technology problem. It’s a workflow problem. The insight existed. The response didn’t.

Or consider a customer who calls your sales team two hours after submitting a large order, needing to change the delivery address and split the shipment across three locations. Simple request. Except the order has already touched four tables in SAP, a logistics system, and a warehouse management platform. Someone now has to manually chase each of those threads, hope nothing has already been picked and packed, and update everything in the right sequence before the wrong boxes end up on the wrong trucks. The customer experience lives entirely in the gap between what ERP recorded and what ServiceNow could have orchestrated.

Business processes don’t run like clockwork. Exceptions happen constantly; and the cost of those exceptions is directly proportional to how fast you can respond to them. The competitive advantage doesn’t live in the ERP system. It lives in the speed and quality of the decisions made around it. That’s the space ServiceNow occupies: not running the flow of value, but making the flow of value run faster by ensuring that when something goes wrong, or when something needs a human decision, it gets to the right person with the right context, immediately.

Insight Without Action Is Just Expensive Wallpaper

Here’s the honest version of what most ERP modernization projects deliver: better visibility into problems you already knew you had.

You can now see, in a beautiful dashboard, that a delivery is three days late and a downstream production schedule is about to be affected. You can observe, in real time, that a customer’s order modification request has been sitting unacknowledged for six hours while the warehouse prepares the wrong configuration. You can track, with impressive precision, that a critical spare part for a production asset hasn’t been reordered despite the inventory dropping below threshold two weeks ago.

What you often still can’t do is fix any of it; not quickly, not without touching the ERP system, and not without a specialist who knows which SAP transaction code to use and in which sequence.

This is the insight-to-action gap. And it turns out it’s not a data problem. It’s a workflow problem.

ERP records what happened. ServiceNow helps determine what happens next. The two systems were always meant to work together; the problem has been that connecting them intelligently has historically required months of integration work, data replication, and enough custom code to make a systems integrator very comfortable and a CFO very nervous.

Two Systems, One Job

ServiceNow and SAP aren’t competitors. They’re colleagues with very different personalities.

SAP is the CFO of your technology stack: precise, compliance-minded, built for accuracy over speed, and deeply uncomfortable with improvisation. It runs the ledger. It keeps the books. It does not appreciate being asked to move quickly.

ServiceNow is the COO: focused on getting work done, orchestrating people and processes, and making sure decisions don’t die in somebody’s inbox while a production line waits. It runs the work.

The flow of value runs through SAP. The speed of that flow is determined by ServiceNow. Together, they cover the full picture; what happened and what happens next.

Enter Zero Copy Connectors for ERP

ZCC for ERP is the bridge between those two worlds; and it’s been a longer journey than you might expect.

The story starts with a small Danish company called Gekkobrain, which ServiceNow acquired in 2021. It continues through a platform rebuild, a product rename, a GTM team formed and reformed, and five years of customers telling us they needed exactly this.

Today, customers are going live in weeks, not months. A kiwifruit marketer in New Zealand ran three ERP workflows in under three weeks. A US federal agency has over 100 custom ERP models in production.

The technology works. Zero data movement. Bidirectional access. Your ERP data stays exactly where it is; SAP, Workday, Oracle, whatever you’re running. ServiceNow can read it, act on it, and trigger workflows against it without you replicating a single record or writing a line of custom integration code.

What This Actually Means for Your Business

Let’s get specific, because “seamless connectivity” is the kind of phrase that makes CFOs reach for their coffee and check their phones.

A shipping carrier notifies you of a two-day delay on a component critical to next week’s production run. ServiceNow picks up the signal, reads the affected production orders directly from SAP, identifies which finished goods are at risk, calculates downstream customer delivery impact, and routes an exception workflow to the right supply chain manager with full context and suggested alternatives; all before anyone has had to open a single SAP transaction. The manager approves a sourcing switch in one click. SAP is updated. The production schedule holds.

A key customer calls to modify a large order already in progress. ServiceNow checks the order status in SAP in real time, determines what has and hasn’t been committed to the warehouse, surfaces the modification options that are still feasible, and routes the change request for approval with full impact visibility. No frantic calls between sales, logistics, and the warehouse. No wrong boxes on wrong trucks. The customer gets a confirmed answer in minutes rather than hours.

A sensor on a critical production asset starts logging anomalies. ServiceNow reads the asset data alongside the maintenance history in SAP, identifies the pattern as consistent with a bearing failure mode that has caused downtime three times in the past two years, and automatically generates a maintenance work order, orders the required spare part, and schedules a technician for the next planned maintenance window. The machine never stops. The millions in unplanned downtime never happen. ERP recorded the history. ServiceNow acted on it before history repeated itself.

That last one is worth sitting with for a moment. The insight was always there. It just had nowhere to go.

The Overnight Success Nobody Noticed

Five years ago, the idea of a lightweight, zero-copy, workflow-native ERP layer felt like an interesting concept. Today it’s a growing library of content packs covering Master Data Management, Quote-to-Cash, and Source-to-Settle, and a roadmap that extends into agentic AI operations on live ERP data.

The five years weren’t wasted. They were the foundation.

If you’re one of the 17,000 SAP customers staring down a 2027 modernization deadline and wondering how to show ROI from a transformation that has so far delivered more complexity than clarity, the answer might not be more ERP. It might be better workflows around the ERP you already have.

The flow of value is already running through your systems. The insight is already there. You paid a lot for it.

It’s time to do something with it.