It's budget season, and if you're in year 2 or 3 of an ERP implementation, you're probably having the same conversation I just had with our CFO: "Why are we still spending money on this project that was supposed to be done by now?"
This is the conversation that derails ERP projects. Not technical failures, not vendor problems, not user adoption issues - but loss of executive support when the investment extends beyond original projections. I've seen promising transformations abandoned at 70% completion because the business lost patience.
Here's how I approached this year's budget conversation, and some frameworks that might help you approach yours.
Reframe "Still Spending" as "Continuing to Invest"
Language matters. If you let the conversation be framed as "why is this project over budget and behind schedule," you're already losing. Instead, reframe it as "here's the value we've created, and here's the additional value available if we continue investing."
Our D365 implementation has delivered measurable results:
| Metric | Before (S2K) | After (D365) | Impact |
|---|---|---|---|
| Invoice processing time | 4.2 days | 1.8 days | $180K annual savings in billing errors |
| Inventory accuracy | 94.2% | 99.1% | $220K reduction in shrinkage |
| Order-to-ship time | 26 hours | 18 hours | Customer satisfaction, competitive advantage |
| Month-end close | 12 days | 5 days | Faster decision-making |
I didn't present these as "project outcomes" - I presented them as "return on investment already achieved." Then I showed what additional returns are available if we complete the remaining 10%.
Show the Cost of Stopping
Executives often underestimate the cost of pausing or abandoning an ERP project mid-stream. Make it explicit:
Sunk cost crystallization. If we stop now, the $2.1M we've invested becomes a pure expense with no additional return. Continuing to invest turns that into a platform that generates returns for 10+ years.
Dual-system maintenance. We're currently running both S2K and D365 in parallel. Stopping means we maintain two systems indefinitely - double the licensing, double the support, double the training, forever.
Staff morale and retention. We've invested heavily in training our team on D365. If we stop now, what does that say to people who've dedicated years to this transformation? We risk losing our best people to organizations that actually complete what they start.
Competitive disadvantage. Our competitors aren't standing still. The real-time visibility, automation, and analytics that D365 enables aren't nice-to-haves - they're table stakes in modern food distribution. Stopping means falling behind.
Be Honest About What Went Wrong
If your project is over budget or behind schedule, don't hide it. Executives respect honesty more than spin. Here's how I addressed our timeline slippage:
"We originally projected 24 months. We're now at 32 months with 3-4 months remaining. Here's why:
- Data quality: We underestimated how much cleanup was needed. S2K had 22 years of accumulated data debt. Cleaning it took 8 months longer than projected.
- Scope additions: The business identified integration opportunities (BFC Dakota, Adobe Commerce) that weren't in the original scope but added significant value. We chose to do them right rather than bolt them on later.
- COVID hangover: Supply chain disruptions in 2023-2024 meant we couldn't disrupt operations as aggressively as planned. We extended parallel running to manage risk.
Each of these decisions was the right call given the information we had at the time. I'd make the same decisions again."
This isn't an excuse - it's an explanation. It shows I understand what happened and why, and that the extensions were deliberate choices, not failures of execution.
Show the Path to Completion
Executives hate open-ended commitments. Give them a clear path:
"The remaining work breaks into three phases:
Phase 1 (Q1 2026): Capital Heights location cutover. Budget: $180K. This completes our multi-site deployment.
Phase 2 (Q1 2026): S2K decommissioning. Budget: $60K. This eliminates $85K/year in ongoing maintenance costs.
Phase 3 (Q2 2026): Advanced warehouse management features and remaining Power BI dashboards. Budget: $140K. This captures the remaining efficiency gains we identified.
Total remaining investment: $380K. Expected annual benefit once complete: $480K. Payback period: 9.5 months."
Specific numbers, specific timelines, specific outcomes. No ambiguity.
Address the "Can't We Just Stop Here?" Question
This question will come up. The temptation to declare victory at 90% is real. Here's how I addressed it:
"Technically, yes, we could stop here. D365 is functional for our Philadelphia operation. But here's what we'd be leaving on the table:
- Capital Heights efficiency gains: That location is still running S2K. They're not getting any of the benefits Philadelphia is seeing.
- Ongoing dual-system costs: $85K/year in S2K maintenance, plus IT time managing two systems, plus user confusion about which system to use for what.
- Advanced analytics: The Power BI dashboards we haven't built yet would give sales real-time visibility into customer patterns. Our competitors have this. We don't yet.
- Warehouse optimization: The advanced WMS features would reduce picking time by an estimated 15%. At our volume, that's 2 FTE equivalent.
Stopping at 90% means getting 60% of the value for 90% of the cost. That math doesn't work."
ERP implementations often deliver diminishing visible value as they progress. The first 50% is dramatic - new screens, new workflows, new capabilities. The last 10% is boring - data cleanup, edge case handling, documentation. But that last 10% often determines whether the project actually achieves its ROI targets. Don't let budget fatigue kill you at the finish line.
Align with Business Priorities
Your ERP investment needs to connect to whatever the business cares about this year. For us in 2026, that's:
EBITDA improvement. The efficiency gains from D365 directly contribute to margin improvement. I quantified this: completion is expected to add 0.8% to EBITDA through reduced labor costs and elimination of legacy systems.
Acquisition readiness. We've been approached about potential M&A activity. A modern, integrated ERP makes us more attractive to buyers and easier to integrate. I didn't dwell on this, but I made sure the CFO knew the connection.
Customer experience. Our B2B customers increasingly expect real-time order status, accurate delivery windows, and self-service capabilities. D365 + our e-commerce integration enables this. S2K never will.
The Outcome
I got my budget approved. Not without negotiation - we trimmed some nice-to-have features and pushed a few things to 2027 - but the core completion path is funded.
More importantly, I rebuilt executive confidence in the project. The CFO understands why we're still investing, believes in the returns, and is bought into the completion timeline. That alignment is worth more than the budget itself.
Final Advice
If you're heading into a similar conversation, remember:
- Lead with value delivered, not money spent. Show ROI, not expense.
- Be specific about what's left. Vague timelines kill confidence. Concrete plans build it.
- Quantify the cost of stopping. Make inaction feel like a choice with consequences.
- Connect to business priorities. Your project needs to matter to what the business cares about.
- Own the delays honestly. Spin erodes trust. Transparency builds it.
ERP projects are marathons. Budget season is just another mile marker. Keep moving.
Planning an ERP modernization?
6 SAP-to-Dynamics conversions with zero business disruption. Let's discuss your project.
ERP Services Book a Call