Implementing ERP Systems

ERP won't streamline operations effortlessly. Without planning, it creates chaos instead. Most founders assume an ERP implementation will automatically fix revenue leakage and improve decision-making. The reality? Without proper planning, you get tangled data and frustrated teams. I've watched a founder plug in their ERP expecting magic. Instead: → Data became a mess → Employees grew frustrated → Decision-making got worse, not better The gap between expectation and execution comes down to three things: • No clear strategy before implementation • Lack of team buy-in from day one • Underestimating the complexity of system integration ERP systems are powerful tools for reducing revenue leakage and enabling better decisions - but only when you treat implementation as a strategic project, not a plug-and-play solution. The best founders don't assume technology will solve their problems. They build the strategy, align the team, and execute with precision. That's how you turn an ERP from a headache into a competitive advantage.

A big 4 consulting firm implemented ERP which caused a major business disruption for a client.   Top level partners in top notch suits made best promises in a beautifully crafted presentation.   The client got excited. Deal signed.   I joined the party at the SIT phase. Which could not complete.   The integration between ERP, WMS and boundary systems was failing.   SIT lasted for 3 more months. Go live data had to be pushed. But the integration still did not work.   The burn rate was insane.   Eventually the leadership decided to make it live and forced half-baked solution.   Yay! Everyone was happy until they realized what a sh*t show they were in.   Right after go live the planners and supply chain operations realized that the stock on hand in ERP, WMS, their custom system and on the shelf were all different.   They had to call the warehouse to make sure they had the right quantity of equipment.   The result: ·      All the departments started overordering to cover up for their projects. ·      2 million dollar sales were lost. No stock. Couldn’t deliver. ·      Inventory across the supply chain grew by $20M. ·      It took 18 months to stabilize the system.   Why did that happen? 1.      The vendor recently bought the WMS solution and did not yet build native integration. 2.      Poor integration between the systems. Transactions were stuck due to errors. 3.      Terrible user experience. Warehouse workers could not perform their role in a system and circumvented the restrictions. 4.      Lack of training and end user support   Want to avoid this costly mistake? Here’s what you should consider. ·      ERP can look great on a slide deck but may not necessarily fit your business ·      ERP can fit your business but not your boundary systems ·      An implementation partner can have a big brand name, but one integration architect can screw the whole thing ·      Hire an independent ERP adviser to make sure you have the right solution and partner   In summary:   Don’t trust ERP fairy tales.   Do your due diligence.   #ERP    #TheERPGuy     #ERPImplementation

𝗧𝗵𝗲 𝗖𝗜𝗢 𝘄𝗵𝗼 𝗸𝗶𝗹𝗹𝗲𝗱 𝗮 $𝟭𝟮𝗠 𝗘𝗥𝗣 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘄𝗮𝘀𝗻'𝘁 𝗶𝗻𝗰𝗼𝗺𝗽𝗲𝘁𝗲𝗻𝘁. 𝗛𝗲 𝘄𝗮𝘀 𝗷𝘂𝘀𝘁... 𝗯𝘂𝘀𝘆. A few months ago, I watched a manufacturing CIO explain to his board why their Oracle implementation was 4+ months behind schedule... "I've been integrating systems from our recent acquisitions, and dealing with critical bugs in our technology product. The ERP team has been handling things." The "ERP team" was an inexperienced team of business stakeholders making million-dollar decisions. Here's how the timeline usually plays out: Week 1-12: Executive engagement starts strong... CIO attends steering meetings, asks good questions, makes decisive calls on scope disputes. Week 13-28: Business crises emerge. Acquisition opportunity. Major customer complaint. Supply chain fire drill. ERP meetings get rescheduled or delegated. Week 29-52: Project team is now making architectural decisions that will define the next decade of business operations... 𝗪𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗽𝗲𝗿𝘀𝗼𝗻 𝘄𝗵𝗼 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝘀 𝘁𝗵𝗲 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆. The result? Technical success, business failure. I've seen this exact pattern destroy millions in projected ROI that companies expected from their ERP upgrade... Not because the technology failed... Because 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗮𝘁𝘁𝗲𝗻𝘁𝗶𝗼𝗻 𝗴𝗼𝘁 𝘀𝗽𝗹𝗶𝘁 𝗮𝘁 𝘁𝗵𝗲 𝘄𝗼𝗿𝘀𝘁 𝗽𝗼𝘀𝘀𝗶𝗯𝗹𝗲 𝗺𝗼𝗺𝗲𝗻𝘁. Here are the three decisions that can't be delegated: → Integration vs. customization trade-offs (affects scalability for 10+ years) → Data migration scope and quality standards (determines operational reliability) → Change management investment levels (drives user adoption and ROI) When these decisions get pushed down to project managers or business teams, you get systems that work perfectly fine... But for problems you don't actually have. 𝗛𝗲𝗿𝗲'𝘀 𝘄𝗵𝗮𝘁 𝘀𝘂𝗰𝗰𝗲𝘀𝘀𝗳𝘂𝗹 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻𝘀 𝗹𝗼𝗼𝗸 𝗹𝗶𝗸𝗲: The CIO treats ERP leadership like merger integration...  • Non-negotiable calendar priority  • Weekly deep-dives  • Personal accountability for outcomes Because that's exactly what it is: 𝘆𝗼𝘂'𝗿𝗲 𝗰𝗵𝗮𝗻𝗴𝗶𝗻𝗴 𝗵𝗼𝘄 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘄𝗼𝗿𝗸𝘀 𝗮𝘁 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹 𝗹𝗲𝘃𝗲𝗹. 𝘌𝘹𝘦𝘤𝘶𝘵𝘪𝘷𝘦 𝘢𝘵𝘵𝘦𝘯𝘵𝘪𝘰𝘯 𝘥𝘶𝘳𝘪𝘯𝘨 𝘌𝘙𝘗 𝘪𝘮𝘱𝘭𝘦𝘮𝘦𝘯𝘵𝘢𝘵𝘪𝘰𝘯𝘴 𝘪𝘴 𝘵𝘩𝘦 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘤𝘦 𝘣𝘦𝘵𝘸𝘦𝘦𝘯 𝘥𝘪𝘨𝘪𝘵𝘢𝘭 𝘵𝘳𝘢𝘯𝘴𝘧𝘰𝘳𝘮𝘢𝘵𝘪𝘰𝘯 𝘢𝘯𝘥 𝘦𝘹𝘱𝘦𝘯𝘴𝘪𝘷𝘦 𝘥𝘪𝘨𝘪𝘵𝘢𝘭 𝘥𝘦𝘤𝘰𝘳𝘢𝘵𝘪𝘰𝘯. 𝘐𝘧 𝘺𝘰𝘶𝘳 𝘭𝘦𝘢𝘥𝘦𝘳𝘴 𝘢𝘳𝘦 𝘴𝘵𝘳𝘦𝘵𝘤𝘩𝘦𝘥 𝘵𝘰𝘰 𝘵𝘩𝘪𝘯 𝘵𝘰 𝘭𝘦𝘢𝘥 𝘵𝘩𝘦 𝘪𝘮𝘱𝘭𝘦𝘮𝘦𝘯𝘵𝘢𝘵𝘪𝘰𝘯, 𝘺𝘰𝘶'𝘳𝘦 𝘯𝘰𝘵 𝘳𝘦𝘢𝘥𝘺 𝘵𝘰 𝘪𝘮𝘱𝘭𝘦𝘮𝘦𝘯𝘵. How are you structuring executive accountability for your current implementation?

We got a call from a large manufacturing group in the UAE. They had gone live with ERP 6 months ago. Finance was still doing reconciliations in Excel. Inventory reports took 3 hours to compile. No one trusted the data. Everyone blamed the system. The irony? The ERP was technically “implemented.” We were brought in to fix it. Here’s the exact 3-𝐬𝐭𝐞𝐩 𝐭𝐮𝐫𝐧𝐚𝐫𝐨𝐮𝐧𝐝 𝐟𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤 we used (that most consultants skip): 1. 𝐑𝐞𝐛𝐮𝐢𝐥𝐝 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐀𝐥𝐢𝐠𝐧𝐦𝐞𝐧𝐭 (𝐍𝐨𝐭 𝐉𝐮𝐬𝐭 𝐖𝐨𝐫𝐤𝐟𝐥𝐨𝐰𝐬)  → First meeting was not with IT. We sat with Finance, Supply Chain, and Ops leaders to map pain vs. process. 𝐖𝐡𝐚𝐭 𝐰𝐞 𝐟𝐨𝐮𝐧𝐝? Core processes were shoehorned into the system. Nobody mapped them against real-world cycles. 𝐅𝐢𝐱: We restructured key flows based on actual business needs—not system defaults. 2. 𝐂𝐥𝐞𝐚𝐧 𝐭𝐡𝐞 𝐌𝐚𝐬𝐭𝐞𝐫 𝐃𝐚𝐭𝐚 (𝐍𝐨𝐭 𝐉𝐮𝐬𝐭 𝐏𝐚𝐭𝐜𝐡 𝐑𝐞𝐩𝐨𝐫𝐭𝐬)  → Sales was struggling with mismatched SKUs.  → Finance had duplicate vendors and unlinked POs. 𝐈𝐧𝐬𝐭𝐞𝐚𝐝 𝐨𝐟 𝐛𝐥𝐚𝐦𝐢𝐧𝐠 𝐮𝐬𝐞𝐫𝐬, 𝐰𝐞 𝐫𝐚𝐧 𝐚 𝐟𝐮𝐥𝐥 𝐦𝐚𝐬𝐭𝐞𝐫 𝐝𝐚𝐭𝐚 𝐚𝐮𝐝𝐢𝐭: ✓ Duplication heatmaps ✓ Inconsistencies by module ✓ Cross-functional reconciliation tasks 𝐅𝐢𝐱: Built validation rules + cleansing pipelines. Tied ownership to teams. 3. 𝐑𝐞𝐝𝐞𝐬𝐢𝐠𝐧 𝐭𝐡𝐞 𝐆𝐨𝐯𝐞𝐫𝐧𝐚𝐧𝐜𝐞 𝐋𝐚𝐲𝐞𝐫  → There was zero change control.  → Anyone could raise config requests.  → No one tracked impact or training. 𝐖𝐞 𝐢𝐧𝐬𝐭𝐚𝐥𝐥𝐞𝐝 𝐚 𝐥𝐢𝐠𝐡𝐭 𝐛𝐮𝐭 𝐟𝐢𝐫𝐦 𝐠𝐨𝐯𝐞𝐫𝐧𝐚𝐧𝐜𝐞 𝐦𝐨𝐝𝐞𝐥: ✓ Change advisory board with business+IT ✓ Measured impact before rollout ✓ Micro-trainings for every major change 𝐅𝐢𝐱: Business users re-engaged. System stability returned. 6 weeks later, the CFO said something I’ll never forget: “This is the first time the ERP feels like ours, not something pushed on us.” And that’s what real ERP rescue looks like. Not flashy. Not fast. But real. ♻️ 𝐑𝐄𝐏𝐎𝐒𝐓 𝐒𝐨 𝐎𝐭𝐡𝐞𝐫𝐬 𝐂𝐚𝐧 𝐋𝐞𝐚𝐫𝐧.

The ERP implementation: $600K. The integrations to make it actually work: $780K. Yeah. You read that right. The "duct tape" cost more than the engine. Here is the anatomy of a $1.4M mistake. The client wanted a clean, modern cloud ERP. But they refused to let go of their legacy baggage The custom CRM (Sunk cost fallacy). The WMS (Change aversion). The Billing System ("Accounting likes it"). I asked the CFO: "Why not consolidate these into the ERP?" His answer: "We don't want to disrupt those areas right now." Famous last words. To avoid "disruption," we built a Frankenstein monster: CRM Sync ($180K): Because sales wouldn't switch. Warehouse Middleware ($220K): Because the WMS had no API. E-commerce Bridge ($150K): Custom mods on Shopify broke standard connectors. HR & Billing Feeds ($230K): Bridging ancient systems to modern tech. Total Integration Cost: $780K. The Aftermath (6 Months Later): Three integrations failed. Not because the code was bad, but because the ecosystem changed. Shopify updated → Integration broke. WMS vendor patched → Middleware crashed. CRM team added a field → Data sync failed. I told the CFO: "You paid more to keep your old systems than you would have to replace them." If we had consolidated everything into SAP: Total Cost: ~$900K. Single point of truth. Unified support. Instead, they paid $1.475M to maintain six points of failure. Every integration you build is technical debt. It will break. It will slow you down. It will cost 3x more than you budget. If you are implementing an ERP to simplify your business, don't complicate it with eight integrations. Consolidate first. Integrate only when you absolutely must. Before you sign that SOW, run the math Cost to Integrate + Maintenance vs. Cost to Replace. If integration costs more, kill the legacy system. Don't trap yourself in integration hell just to avoid an awkward conversation with the Sales VP.

ERP migrations are BRUTAL. They cost a fortune, take forever, disrupt the organization, etc. Companies usually bring in consultants, but A LOT of work falls on the internal team, and many people gloss over this critical piece. Let's focus on the client's responsibilities and why the client is at a major disadvantage during these projects. Your ERP implementer signs up for a lot of work, but they expect the client to provide clean data, explain business processes, test the new system, sign off on the new system, and run parallel processes with the old/new systems to ensure the business runs correctly. A common data process during an implementation: 1) Your team pulls data for a specific process from the old systems. 2) Your team fights to get it into the format for the new system. 3) The implementer loads it into the new system. 4) The implementer and the client test the new system. 5) Errors are found. 6) The implementer asks you to track down the errors, fix them, and provide a new data set. (back to step 1) This portion of the ERP implementation puts a MASSIVE load on your internal team. They will be doing constant data integration tasks, and most internal teams aren't data engineers. Most are also working full-time jobs with the ERP migration being added to their 40+ hour workload. IT can help you, but they likely don't have a ton of bandwidth, and they rarely have the background in the business processes to know if the data is correct. They give you what you ask for...but you probably don't know the table structures or nuances of the database. Any delays or data issues that stem from you (the client) are fair game to delay the project, and the implementer (contractors) will keep billing. You've caused the delay, so there's nothing they can do. To recap: 1) You are resource-constrained. (Your team has full-time jobs already.) 2) Your teams aren't SQL/Database wizards or data engineers. 3) IT can help but is busy and doesn't know all of the business logic. 4) You are responsible for the data quality and testing. 5) Any delays cost 10s or 100s of thousands of dollars. 6) If the delays are because of tasks assigned to the internal team, the implementer will ensure that they are clearly documented and understood. Our recommendation is to have a consulting team like Capitalize Analytics on YOUR TEAM. We'll bring in the data engineering skills, work with your IT team efficiently, keep the ERP implementer in check, advocate for you, and shoot straight with you on issues and where they are coming from. We'll bring in data technology like Alteryx and testing automation technology like UiPath to speed things up and keep you on time. We'll also train your team so they are better, stronger, and faster when the project is over. ERP implementers are indispensable, but they won't do it all. They may make it seem "easy" to close the sale and start the project, but we've been down this path before. It's HARD work. Thumbs up if it's not BS! :-)

ERP is keeping many of us busy in the Gulf right now, particularly large-scale SAP programmes across KSA and the UAE. What I see repeatedly is not a technology issue. It’s an operating model issue. A regional group decides to standardise on SAP to harmonise finance, procurement, and supply chain across multiple countries. The blueprint is clean. The system goes live on time. The dashboards look impressive. Six months later, decision-making is slower than before. Why? Because the ERP has imposed process discipline, but leadership behaviours haven’t adapted. Approval hierarchies remain relationship-driven. Local entities still escalate exceptions informally. Data exists, but it isn’t trusted. So executives revert to parallel spreadsheets. An ERP transformation in the Middle East should be a governance reset. In Europe, process compliance is often culturally embedded. In the Gulf, speed, hierarchy, and negotiation dynamics play a stronger role in how work actually gets done. If you don’t design for that reality, the system will technically succeed and operationally underperform. The firms getting this right are the ones aligning three layers simultaneously: system architecture, decision rights, and executive incentives. Not one after the other but together. Technology implementation is easy to announce. Behavioural change is harder to invoice. But that’s where I believe the real ROI sits.

CFOs will drop $500K on ERP software without blinking. But watch what happens when you mention the 9-month implementation timeline. Their face changes. They know what's coming. Here's what nobody talks about during the sales pitch: For the next 9 months, you're running two companies. The old books don't disappear. The board still wants their monthly reports. Quarter-end doesn't take a vacation because you're "in transition." Meanwhile, you're manually migrating years of data. Learning a new system. Training your team. Checking that everything moved correctly. Then (and this is the part that breaks people) once you finally go live, you have to run back and manually catch up everything that happened during the transition. It's not one implementation. It's TWO. Most implementation partners know this. They just don't mention it. They'll pitch you "seamless migration" and "90-day go-live" because that's what you want to hear. What they won't tell you: Your controller will be pulling all-nighters for months. Your best people will burn out. That analyst you just hired? They're updating their LinkedIn. The money was never the problem. The 9 months of operational hell was. At DualEntry, we built our entire implementation around one principle: No double work. We've been in those war rooms at 2 a.m., trying to reconcile two systems while the board meeting is in 6 hours. We know the real cost isn't in the software line item. It's in the people you lose along the way.

Do you know Hershey's lost around $100 million dollars… In 1996, Hershey's wanted to introduce new technology to manage their business. But it turned into one of the biggest disasters in their history. They wanted to replace their legacy IT system with an integrated ERP system. This meant implementing - → SAP's R/3 ERP software for overall business management → Manugistics' supply chain management software (SCM) for inventory and logistics → Siebel's customer relationship management software (CRM) for customer data The recommended timeline for the project was 48 months, but Hershey’s leadership demanded it to be completed in 30 months. The new system went live in July 1999, which was Hershey’s peak season for Halloween and Christmas. However due to integration issues and a lack of proper testing, the new system was unable to process $100 million worth of orders even after having the stock. All because they rushed the business transformation. The key takeaways from this study could be - → Don’t rush system testing. Even if it means delaying to go-live → Allow enough time for implementation. Cutting corners in the timeline increases the chances of failures → Instead of going all in, go slow. → Avoid launching a new system during peak seasons as you don't get time to test. Remember: not everything goes as planned, but a thoughtful approach can save you millions in transformation. #transformation

Going live with Dynamics 365 F&O doesn't mean your ERP implementation was successful. Here's a list of painful stuff you could find out after go-live: 1. Dirty data Turns out the system is missing critical data (parameters, etc.) and the master data is full of dirty records. As a result, operations suffer and many reports are wrong. Decision making is impacted. 2. Insufficient integration Surprisingly, your ERP doesn't exist in a vacuum and it actually depends on data contained in other applications. Are these applications talking to each other, and are they doing it correctly? If not, expect operational delays and a lot of manual intervention from employees. 3. Lack of training It's almost like it's impossible for people to master Dynamics in an afternoon. Exposing key users to a single round of UAT only wasn't enough, and it wasn't very smart to skip creating documentation. Result? Inefficiency that persists months after go-live, and money wasted to build features that are not used. 4. Technical debt Oh noes, the system is slow. Surely it's not related to those 72 major customisations you had your system integrator develop because "we have it in the old system and it's essential for go-live". Now you've spent millions to replicate the same inefficient, slow, clunky monster of an application that was your previous ERP, just on a new platform. Prepare to face the same problems you had before, just on a bigger scale. 5. Bad fit for purpose Ah yes, my favourite. You implemented (or worse, custom built) a feature that was perfect for your company. Except it doesn't match how your people do things. So you see workarounds, out-of-system processes, and parallel databases on Excel spreadsheets. The ROI of your ERP implementation is basically negative. So how do you save yourself from these issues? Get an independent advisor on board. Somebody who understands how ERP implementations work. And make sure they're on your side. And if it's too late? Well, start fixing those issues now, because the more you wait, the worse they'll become.