The Platform Got The Budget. The Integration Got The Leftovers.
The conversation I have most often with finance leaders is a version of the same one. A CFO calls about an ERP project that is not delivering what was promised. The platform was selected carefully, the implementation partner was vetted, and the go-live happened on schedule. And yet, somewhere in month nine, the project quietly becomes a disappointment. The reporting is still partial, and the finance team is still exporting to Excel before every board meeting.
When we audit these environments, the pattern is consistent. The ERP platform is fine. The implementation was technically clean. The failure is somewhere else: in the seam between the ERP and the rest of the business systems that surround it. The connection between Coupa and the ERP that should automate AP. The link between Salesforce and the ERP that should turn closed-won into recognized revenue. The data feed from the HRIS should populate headcount-driven planning models in Adaptive. These integrations were not built, were built poorly, or were built years ago and quietly stopped working.
Every CFO conversation about a struggling ERP eventually arrives at this layer. Most ERP project conversations do not start there.
The Platform Got The Budget. The Integration Got The Leftovers.
Most ERP selection conversations focus, reasonably, on the platform. Which ERP is the right fit? What it costs. How long does the implementation take? Who is the right partner to deliver it? The procurement process is structured around these questions. The board approval is structured around these questions. The line items in the implementation budget are structured around these questions.
The integration layer between the ERP and the surrounding systems gets a smaller budget, a later start, and a more junior team. By the time the implementation partner is scoping the actual integration build, the project already has a go-live date that the integration work has to fit into. The CRM-to-ERP connection becomes a Phase 2 item. The procurement-to-ERP feed gets the standard connector instead of a properly scoped integration. The reporting-to-data-warehouse pipeline is left for the internal team to figure out post-go-live.
The result is predictable. The ERP goes live on schedule. The integrations either do not exist, run on best-effort connectors that miss edge cases, or work for a few months and then break silently when one of the source systems releases a version update.
In our practice, roughly 60 percent of the inbound conversations about underperforming ERPs trace back to integration problems, not platform problems. The buyers do not always know that when they call. They call about the symptoms: forecast cycles that take twice as long as they should, AP teams manually rekeying invoices for days at a time, and sales pipeline data that does not match what finance is forecasting. The diagnosis usually finds the same root cause: the ERP is fine, but the integrations around it are not.
What Actually Breaks At The Seams
Three patterns show up repeatedly. They are not platform-specific. They appear across NetSuite, SAP, Oracle Fusion, Workday, and the AI-native finance platforms that have entered the category in the last two years.
The first is the connector that nobody owns. The ERP vendor supports the ERP. The procurement or CRM vendor supports their product. The connection between them was either built by a third-party tool, a consultant who has since moved on, or a now-defunct vendor whose product still runs in production. When the connection breaks, two help desks point at each other. No team owns the resolution. The AP or sales ops team manually rekeys data for the duration of the outage, which is often weeks rather than days.
The second is the integration that quietly stopped matching the business. The integration was correct on the day it was built. Then a department was renamed. A subsidiary was acquired. A new product line was launched. A reorganization changed approval thresholds. The integration kept running, but the data flowing through it no longer represented the business accurately. The reports built on top of the integration started showing numbers that were technically true and operationally meaningless. By the time anyone caught it, the discrepancy was already in a board package.
The third is the integration that was scoped out of the original project. The CFO who approved the implementation budget was told that the CRM integration could be deferred. The procurement integration could come in Phase 2. The data warehouse pipeline was the internal team’s problem. Each of these decisions made sense individually. Collectively, they shipped an ERP into production that was not actually connected to the systems it needed to talk to. Eighteen months later, the deferred work is still deferred, and the operational gap has become permanent.
The Vendor Model Has Not Caught Up
Part of the problem is structural. The way the ERP services market is organized, integration work is rarely owned by anyone with the institutional incentive to make it succeed.
Most ERP implementation partners are paid to implement the ERP. Their incentive ends at go-live. The partner is gone before the connector breaks. Most managed services contracts cover the ERP, but they do not cover the integration layer. When a connection fails, the customer is left caught between two vendors, neither of whom owns the primary responsibility.
“I’ve spent my career realizing that the platform is nearly never the hero. You can have the best AI-native ERP in the world, but if it’s sitting on a foundation of manual exports, it’s just a digital filing cabinet. My focus is always on reading between the lines, the automated connections that actually turn software into a growth engine.”
This reality is why we’ve had to change the way we approach these engagements. The technical solution is not the hard part; the fix is structural, not technical.
The Fix is Structural, not Technical
I’ve spent enough time in this industry to know that the technical solution isn’t the hard part. The tools, MuleSoft, Boomi, and Workato, are mature and powerful. We already have the technology to connect Coupa to NetSuite or Salesforce to Adaptive. What is missing is the backbone: a contracting structure that makes a partner actually accountable for those connections over the long haul.
The fix is to scope integration as a primary deliverable, not a secondary one. To name a single party accountable for the integration layer, with a contract that covers integration uptime alongside the ERP itself. To treat the integration as a maintained system with its own version update, testing, monitoring, and quarterly review, not a one-time build that runs until it breaks.
In our practice, we structure managed services contracts to cover the integration layer alongside the ERP, not as a separate engagement. The customer has one team accountable for both the ERP environment and the connections into and out of it. When something breaks, there is no help-desk routing exercise. When a source system updates and a connection needs reconfiguration, the same team handles it. When the business changes and an integration needs to be reshaped, the work happens inside the existing engagement rather than as a renegotiation.
This structural change is unusual in the market. Most managed services partners specialize in one platform. The integration layer is genuinely complex and requires a different skill set than configuring the ERP. The contractual depth required to cover both is operationally expensive for the partner. Most do not do it.
Thinking Ahead
If you are a finance leader, your finance stack is only as strong as its weakest link. Continuing to follow the standard vendor model ensures that you will remain the mediator between disconnected help desks.
Thus, the next time you sit down to scope a digital transformation, stop asking about the platform’s features. Start asking who owns the seams. Because eighteen months from now, you won’t care about the ERP’s dashboard; you’ll care about whether the data got there without a spreadsheet.
Jermaine Jackson is Managing Partner at Zanovoy and a seasoned professional services consultant specializing in NetSuite, Coupa, Adaptive Insights, and Salesforce implementations across software, services, and life sciences. Jermaine’s expertise lies in guiding organizations through complex integrations and financial transformations to drive operational efficiency. He is a results-oriented expert dedicated to helping businesses achieve scalable, transformative growth.
Read More From Techbullion
