--
The Most Common Objection We Hear Before ERP Implementation — And Why 500 Engagements Prove It Wrong
Across 500 ERP implementations delivered exclusively for PE-backed portfolio companies there is one objection that appears more consistently than any other. It comes in different forms and from different roles — CFOs, Operating Partners, Managing Directors — but it expresses the same fundamental concern every time.
“We are not ready for this right now.”
The specific version of the objection varies. The portfolio is mid-integration on a recently closed acquisition and the finance team does not have the capacity to manage an implementation project alongside the integration work. The operational priorities of the current phase of the hold period are demanding enough without adding an infrastructure change to the workload. The current system is not ideal but it is working well enough that the disruption of replacing it feels disproportionate to the benefit. There will be a better moment — after the next deal closes, after the team stabilizes, after the current operational intensity subsides.
The objection is sincere. It reflects a genuine concern about adding implementation risk and organizational disruption to an environment that is already demanding. And it deserves a direct response rather than a dismissal.
The direct response, grounded in what we have observed across 500 engagements, is this. The better moment almost never arrives. And the objection, examined carefully, is almost always describing conditions that the implementation is designed to eliminate rather than conditions that exist independently of the infrastructure problem.
What The Objection Is Actually Describing
When a PE-backed portfolio company says the timing is not right because the finance team is stretched, it is worth examining why the finance team is stretched.
In most cases the finance team is stretched because the manual processes the current infrastructure requires are consuming a disproportionate share of their capacity. The close cycle is consuming fourteen days of every month. The manual consolidation across disconnected systems is requiring reconciliation work that should not exist. The LP reporting preparation is consuming three to four days after each close. And the post-acquisition integration work that the objection cites as the reason the timing is wrong is itself more complex and more time-consuming than it should be because the infrastructure was never designed to absorb a new entity efficiently.
The finance team is not stretched despite the infrastructure. It is stretched because of it. And the implementation that the objection is deferring is the change that would release the capacity the stretched team needs.
The same logic applies to the active operational priorities that the objection cites. The operational decisions the Managing Director and Operating Partner are trying to make during the current demanding phase of the hold period are more difficult than they should be because the financial visibility that would support better decisions is arriving two weeks late through a manual consolidation process that the infrastructure requires. The operational intensity is higher than it would be with the right infrastructure — not lower.
And the integration work that feels incompatible with implementing ERP simultaneously is, in most cases, more complex and more time-consuming than it would be with a standardized ERP infrastructure already in place — because integrating a new entity onto a common platform is a defined process, while integrating a new entity into a manual consolidation process that is already complex is an open-ended one.
The conditions that make the current moment feel wrong are, in almost every case, conditions that the implementation is designed to eliminate. They do not resolve while the infrastructure remains unchanged. They compound — with every additional month the manual process runs, with every additional acquisition that adds another layer of complexity to an infrastructure that was already insufficient, and with every decision that is made on delayed financial visibility during a hold period where every decision matters.
Why The Better Moment Never Arrives
The implicit assumption behind the timing objection is that there will be a future moment when the conditions are more favorable — when the current integration is complete, the team has stabilized, and the operational priorities are less demanding. A moment when the implementation can be executed without the competing demands that make it feel untimely now.
That moment rarely arrives for two reasons.
The first is that the conditions cited as the reason for the current timing being wrong tend to recur. A PE portfolio in active management mode has recurring periods of integration complexity, recurring finance team capacity pressure, and recurring operational intensity. The acquisition that is currently closing will be followed by another. The integration that is currently consuming finance team capacity will be followed by another. The operational priorities that are currently demanding will be followed by a different set of equally demanding priorities. The window of relative calm that the objection implicitly anticipates consistently turns out to be shorter and less available than the plan assumed.
The second reason the better moment does not arrive is more fundamental. The infrastructure problem that the objection is deferring the solution to does not become smaller while it is being deferred. It becomes larger. Every month the manual consolidation continues it consumes the finance team capacity that could have been redirected. Every new acquisition that integrates onto the manual process adds complexity rather than being absorbed into a standardized infrastructure. Every period close that runs fourteen days instead of four is fourteen days of delayed visibility for the Managing Director and Operating Partner. And every month that passes without the implementation is a month in which the audit trail and financial history that the exit process will eventually require is being maintained at a lower standard than the right infrastructure would have maintained it at from the beginning.
Deferral does not reduce the cost of the infrastructure problem. It accumulates it.
What 500 Implementations Tell Us
Across 500 implementations delivered exclusively for PE-backed portfolio companies there are two observations that are relevant to the timing objection.
The first is that we have never had a client tell us at go-live that they wished they had waited longer. In five hundred engagements — across PE portfolios of different sizes, different industry mixes, different stages of the hold period, different levels of operational complexity — not one client has reached the end of the 90-day implementation and expressed regret that they had proceeded rather than deferred.
The second observation is the one that appears with the most consistency and the most genuine feeling behind it. Many clients tell us they wished they had started earlier. Not that the timing turned out to be perfect — but that the improvements delivered by the implementation were significant enough that every month they operated without the right infrastructure before it was a month whose cost, in retrospect, they would rather not have incurred.
These two observations together constitute the most honest answer we can give to the timing objection. The cost of proceeding is a defined 90-day process with a proven methodology and a 100 percent success rate. The cost of deferring is the ongoing and compounding accumulation of the infrastructure problem — distributed across close cycles, integration complexity, delayed visibility, and the financial history that is being built toward exit at a lower standard than it should be.
The 90-Day Response To The Timing Objection
The 90-day implementation timeline exists, in part, as a direct response to the timing objection.
If the objection is that the portfolio cannot afford a long and disruptive implementation project during a demanding operational period, the 90-day timeline addresses it directly. The implementation is short enough to complete between acquisitions. Defined enough to execute without disrupting the operational priorities that are already in motion. And structured as a phased process that delivers a working consolidated reporting infrastructure at go-live rather than an ongoing project that produces value only at its eventual conclusion.
The methodology that delivers the 90-day timeline was built specifically for the PE environment — not adapted from a general framework — and has been validated across 500 engagements with a 100 percent successful launch record. The implementation risk that the timing objection is concerned about is not theoretical. It is addressed by a methodology that has not produced a failed launch across five hundred opportunities to do so.
The question the timing objection is really asking is whether the defined cost and disruption of proceeding now is preferable to the ongoing and compounding cost of deferring. Across 500 implementations the answer has been the same every time. Proceed. And wish you had started earlier.
The Next Step
Every engagement begins with a free 30-minute assessment — an honest conversation about the current state of the portfolio’s financial infrastructure, what the 90-day implementation would look like in the specific context of the portfolio’s current operational demands, and whether the timing concern that has kept the conversation from happening sooner is protecting the portfolio or costing it.
No commitment. No sales pressure. Just the honest conversation that 500 implementations tell us is worth having sooner rather than later.
Visit erpforprivateequity.com or call (210) 756–4227 to book your assessment.
Tags: Private Equity, ERP, Portfolio Companies, Acumatica, CFO, ERP Implementation, PE Operations, Operating Partner, Post Acquisition, FinTech
