When ERP Funding Approval Gets Delayed | ERP Without the Chaos
ERP Implementation

When ERP Funding Approval Gets Delayed

Your October greenlight became November, then January. Here's how to find value in the waiting and stay sane.

There's something that can catch people by surprise, often right when things seem like they're going to start moving. Maybe you're the CFO, a controller, or a project manager brought in specifically for this role. You met with stakeholders, defined requirements, survived vendor selection. But suddenly, everything pauses. The approval process for project funds takes far longer than expected. October became November. November became January.

There are many reasons this happens. ERP projects and digital transformations rank among the largest expenses a business may experience, outside facilities or R&D. Even though a successful ERP project will have positive ROI, it's mentally harder for leaders to commit dollars to something not directly tied to sales revenue. Add the sticker shock of the quoted price, and they'll start questioning value. Add the complexity risk, and they get nervous about what they're being asked to trust you with.

But that won't stop you from feeling frustrated. You're responding to asks, reworks, and constant meetings related to your project with no approval in sight. If this is your first time, it's easy to question what you're doing there, especially if you were brought in for this role specifically.

I'm here to tell you now: This is normal. And there is absolutely value that can come out of it.

Get Grounded

Appreciate the gravity of what you're asking

It will help to appreciate just how significant this request is. ERP projects are among the most expensive investments a business can make. This is especially difficult mentally for executives because financial gains aren't always easy to conceptualize, even when the numbers show clear value. And it's not just about initial cost. You're asking them to trust your plan and ability to execute, knowing that a shockingly high number of ERP projects fail. When you look at it this way, a lengthy approval process should almost feel inevitable.

Ground Yourself in the Journey

You're not just waiting. You're learning.

During this approval period, you're not exactly doing nothing. You're handling requests from executives, dealing with mobilization activities, and more. You're learning valuable lessons that will help you run better projects and navigate smoother approval processes in the future. This period isn't wasted time, even though it can feel that way. These lessons matter, and they'll shape how you lead projects for years to come.

Reframe to Appreciate Opportunity

Changes often come for a reason

Many of the changes requested by your leaders are made intentionally. Your leaders have seen things. Their requests often lead to actions and modifications that genuinely improve or reduce risk in your program. This is a good thing that's easy to miss when you just want to get started. Even better, you can capitalize on the slower-than-expected approval runway and use that additional time to prepare. When approval finally comes, you'll be ready to hit the ground running.

The Hard Question: When to Leave

You may be asking: "Yeah, that all sounds great, but at some point, it may be time to leave. How do I know when that is?"

I'm not going to directly answer that question. The outcome of that decision is highly impactful to your career and can only be made through your judgment. What matters most is keeping a level head and avoiding decisions without careful thought and consideration.

Anchor yourself to the positives I mentioned, but read the room and watch for concerning signals. You'll recognize them when you see them:

  • Delays with no feedback
  • High levels of executive dysfunction
  • Extreme losses of scope

Only you can discern what's a normal friction point and what's a red flag. But in many cases, there's a light at the end of the tunnel. You will get your greenlight. And once you do, it will be full steam ahead.

Focus on preparing for your program, take advantage of the slower runway, and get ready to execute.

Next
Next