ERP Software Solutions

𝗘𝗥𝗣 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻𝘀 𝗱𝗼𝗻'𝘁 𝗳𝗮𝗶𝗹 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗼𝗳 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆. They fail because of people. After 25+ years helping organizations navigate digital transformations and serving as an expert witness in some of the largest ERP lawsuits in the world, I can tell you the pattern is always the same. It's not the software that breaks. It's the system around it: → 𝗕𝗶𝗮𝘀 in vendor selection — where decisions are driven by relationships and sales influence rather than business fit → 𝗖𝗼𝗻𝗳𝗹𝗶𝗰𝘁𝘀 𝗼𝗳 𝗶𝗻𝘁𝗲𝗿𝗲𝘀𝘁 — where the people advising you also profit from the outcome → 𝗖𝘂𝗹𝘁𝘂𝗿𝗮𝗹 𝗿𝗲𝘀𝗶𝘀𝘁𝗮𝗻𝗰𝗲 — where organizations believe they're "too big to change" → 𝗪𝗲𝗮𝗸 𝗴𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 — where no one owns the outcome and risks go unmanaged → 𝗣𝗼𝗼𝗿 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 — where leadership delegates instead of leads The US Air Force spent $5 BILLION on an Oracle ERP implementation before canceling it. A Senate investigation called it an "organizational disaster." The technology wasn't the problem. Haribo nearly killed the gummy bear market when their SAP go-live — timed at peak Christmas season — caused supply chain chaos and millions in losses. These aren't just cautionary tales. They're proof that your transformation strategy matters more than your software choice. If you're about to embark on an ERP journey, ask yourself: Are the people advising you truly independent? Is your organization ready to change? Do you have governance strong enough to catch problems before they become disasters? The answers to those questions will determine your success — not the logo on your software. ♻️ Repost if you agree. Follow me for more transformation insights. #ERP #DigitalTransformation #ERPFailure #ChangeManagement #EnterpriseStrategy #SAPFailure #OracleERP #TransformationStrategy #Leadership #ThirdStageConsulting #CIO #CFO #BusinessTransformation

The mid-market ERP buying journey in Australia is rarely as straightforward as it looks from the outside. That's not a criticism of the ecosystem. It's just worth understanding before moving your business into the middle of it. 𝗛𝗼𝘄 𝘁𝗵𝗲 𝗺𝗮𝗿𝗸𝗲𝘁 𝗶𝘀 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝗱 Global ERP Software Vendors typically work through local Australian Implementation Partners who have invested in software certification and delivery capability. These partners bring genuine expertise, often deep industry knowledge, and they're the ones who will actually implement the solution for you. The complication arises because some of those same ERP Global Vendors also sell directly. Both channels are usually working in good faith to serve their clients. But when a Software Vendor competes against its own partner network, it can be confusing for buyers. 𝗪𝗵𝗮𝘁'𝘀 𝘄𝗼𝗿𝘁𝗵 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗲𝗮𝗿𝗹𝘆 Implementation Partners and Software Vendors bring different things to the table. Partners tend to focus on scoping, design and implementation delivery. Vendors are more focused on software licensing. Those goals usually align, but not always, and not automatically. Some useful questions to consider before you progress too far include: ➡️ Who will be responsible for delivering the end-to-end ERP Solution? ➡️ When do you really need to start paying for ERP licenses? ➡️ Who will support you and resolve issues associated with the ERP Solution? These are not challenging questions. They're simply the kinds of things a potential buyer would want to clearly understand. 𝗪𝗵𝗲𝗿𝗲 𝗶𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝘁 𝗮𝗱𝘃��𝗰𝗲 𝗳𝗶𝘁𝘀 𝗶𝗻 ERP is not just a licence purchase. The decisions made before contracts are signed shape everything that follows for many years to come. An independent ERP advisor sits outside the commercial ecosystem. We do not have any allegiances to Vendors or Partners, only our clients. The issue is not that the ecosystem can't be trusted; but because we offer a different vantage point that helps buyers make informed decisions with a clearer view of what they're actually choosing as well as having a clearer understanding of how to best approach the transformation process.

Before I let a CFO in Dubai sign an ERP contract, I ask 7 questions about multi-currency and FX rules. (Most vendors can’t answer even 3.) And that’s exactly why 90% of ERP finance teams end up with workarounds, Excel patches, or fire drills every month-end. Here’s what I ask every single time: (1) How does the system handle revaluation gains/losses across ledgers in real-time? (Or are you manually booking journals at month-end?) (2) Can FX rates be pulled live from central banks or is it still a static upload via CSV? (3) What happens to historical FX rates when you reopen a prior-period transaction? (4) Can you tag currency exposure by project, vendor, or contract in reporting? (5) Does multi-entity consolidation auto-adjust for intercompany FX differences? (Or do you have to “explain” the ₹6.2M gap to auditors every year?) (6) How does the ERP treat rounding off in multi-currency AP/AR aging reports? (7) Does the ERP allow dual base currencies? (say, for reporting in USD and AED natively?) If your vendor can’t answer these, walk away. Because the moment your business hits scale or enters new geographies… Your ERP won’t just fail. It’ll cost you millions in lost visibility and manual firefighting. Want the full 23-question FX audit checklist I use before every ERP project? Just comment “FX Checklist” below and I’ll send it across. ♻️ 𝐑𝐄𝐏𝐎𝐒𝐓 so others can learn.

"We're moving forward with another vendor." Every rep's nightmare sentence. I pressed for details. "Their approach felt more open. We actually knew what we were buying into." That stung. I'd shared: ••• Exhaustive feature documentation ••• Dozens of success stories   ••• Complete pricing breakdowns Where'd I go wrong? Days later, I got access to our competitor's sales process. The difference hit instantly: They didn't preach transparency. They lived it. Their follow-up wasn't an email avalanche. It was one collaborative hub where buyers could: ••• Monitor which stakeholders engaged with what ••• See their exact position in the evaluation journey ••• Find materials curated for their unique pain points ••• Manage internal distribution seamlessly My revelation: I was buried in PDFs. They were cultivating partnership. Next prospect, new approach: I built a shared workspace exposing EVERYTHING: → Which team members on our side viewed their data → Critical docs they'd missed → Realistic implementation expectations → Where we excel AND where we don't The buyer's response: "Finally, someone not playing games." Ink on paper in 10 days. Here's what's real: Today's buyers aren't starved for data. They're starved for authenticity. Yesterday's strategy: Bombard with polished assets that sidestep weaknesses. Tomorrow's strategy: Build transparent environments that tackle doubts directly. Your buyers know when something's off. Even when nothing is. Quit running sales like a shell game. Start running it like a glass house. You with me?

For 30 years, enterprise software was built around a single constraint: the human on the other end. Every feature had to be discoverable. Every workflow had to be learnable. The ceiling on what software could do was set by what a person could navigate.     When agents are doing the work, that ceiling disappears. The most consequential changes are happening under the hood. Three things are shifting:  · The user experience. There are now two classes of user — human and agent — and software has to serve both.  · The business logic. As agents take on more of the execution, logic moves into the system as skills an agent can invoke directly. That's where the biggest efficiency gains come from.  · The data. Every application stores data, but agents need it prepared in advance. That lets them get straight to the question instead of figuring out what they're looking at.     As human work shifts upstream, the organizations that pull ahead will be the ones that deliberately build their people's capacity to set direction, evaluate outcomes, and stay accountable for how the system performs. 

𝗪𝗵𝘆 𝗱𝗼 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗘𝗥𝗣 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹? 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝘁𝗿𝗲𝗮𝘁 𝗶𝘁 𝗹𝗶𝗸𝗲 𝗮 𝘀𝗶𝗺𝗽𝗹𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗽𝗮𝘁𝗰𝗵, not the business transformation it truly is. Listening to my network, there seems to be a rush to complete ERP migrations, as fast as possible, with SAP S/4HANA plans driving most of it. But an ERP system is more than just an IT upgrade. It’s a chance to redesign how your business operates and build a solution architecture that supports agility and innovation. While necessary, these migrations often become redundant without proper alignment to business goals. Something, I've seen happen! Here some get rights to consider: ◉ 𝗔𝗹𝗶𝗴𝗻 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗮𝗻𝗱 𝘁𝗲𝗰𝗵 𝗴𝗼𝗮𝗹𝘀 Ensure that IT and business leaders are on the same page. ERP systems serve broader business objectives, such as innovation, improving procurement strategies, and enhancing supplier relationships. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘁𝗼𝗼𝗹𝘀. Instead of getting caught up in the technology itself, be clear about the business benefits you'd like to achieve. New ERP functionality can be of support to achieve goals like efficiency, cost reduction, and agility. ◉ 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝘆 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 𝗮𝗻𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 Don't just migrate complex, outdated processes but streamline them end-to-end. Reevaluate processes for efficiency and desired outcomes. ◉ 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 - 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗶𝗻 𝘁𝗿𝗮𝗶𝗻𝗶𝗻𝗴 ERP migrations often fail due to poor user adoption. Beyond training, invest in communication & ongoing support showing the value and relevance of the system to users. ◉ 𝗜𝗻𝘃𝗼𝗹𝘃𝗲 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘁𝗲𝗮𝗺𝘀 ERP impacts every area of the business, so cross-team collaboration is essential. Involve stakeholders from finance, procurement, IT, and operations ensures the system meets everyone’s needs. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗱𝗮𝘁𝗮 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 - 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗰𝗼𝗺𝗽𝗿𝗼𝗺𝗶𝘀𝗲 An ERP system is only as good as the data it processes. Ensure that data is clean, consistent, and reliable before migration. Dirty or incomplete data is one of the biggest challenges post-go-live. ◉ 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘀𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗖𝗼𝗺𝗽𝗼𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 Choose an architecture which allows for future-proofing and integration of new features, scalability and integration. Business models evolve, and your ERP must evolve with them." ◉ 𝗦𝗲𝘁 𝗿𝗲𝗮𝗹𝗶𝘀𝘁𝗶𝗰 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲𝘀 - 𝗶𝘁'𝘀 𝗻𝗼𝘁 𝗴𝗼𝗶𝗻𝗴 𝘁𝗼 𝗯𝗲 𝗾𝘂𝗶𝗰𝗸 𝗶𝗳 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝘃𝗲 Don’t rush an implementation. ERP migrations are complex and require time to integrate properly. A phased approach allows for troubleshooting and mitigates a risk for failure. ❓Any other "get rights" i missed and you would add from your experience. #erp #businesstransformation #migration #sap4hana

Most sellers only uncover ONE level of impact in discovery. That’s why their deals stall, why their ROI slides don’t land, and why their champions can’t sell internally. The truth? There are 4 levels of impact—and if you miss even one, you’re selling half-blind. Selling is helping. But helping means going deeper than “company KPIs.” Here’s the framework I coach every AE on when they’re trying to win enterprise SaaS deals: 1. Company Impact This is where 90% of reps stop. “What’s the cost savings? What’s the revenue upside?” That’s table stakes. If you don’t tie your software to actual numbers—lost revenue, margin impact, labor cost—your ROI story collapses in front of a CFO. Example: A Service Cloud rep I coached quantified millions lost in unbooked hospital referrals because of missed scheduling calls. That turned a “$500K tool is too expensive” into “8X ROI, no-brainer.” 2. Buyer Impact Your champion has skin in the game. They left a stable job. Their reputation, career trajectory, even their family’s well-being are tied to this project. If you can show them how your solution makes them the hero internally, you create unstoppable personal buy-in. 3. User Impact These are the people who log in every day. If they hate the tool, adoption dies. If they love it, productivity soars, morale improves, turnover drops. Shadow them. Ask what frustrates them. Show them a better day in the life. 4. Customer Impact The most overlooked layer. How does your product improve the end customer experience? Faster service, better outcomes, less stress? For a hospital, it’s not about “efficiency.” It’s about a patient getting a life-saving scan booked in hours instead of days. Stop selling features. Stop selling “savings.” Start selling IMPACT. - Company. - Buyer. - User. - Customer. Miss one—and you’ll miss the deal. Hit all four—and you’ll never sell the same way again. Selling is helping. Always.

Enterprise software is entering its Post-UI Era Most enterprises haven’t recognized it yet. Over the last few months: - Salesforce made Model Context Protocol (MCP) production-ready. - SAP introduced its vision for the Autonomous Enterprise. - Microsoft shifted its AI narrative from copilots to orchestration. Most people saw three product announcements. Few have noticed this architectural shift. For the last 30 years, enterprise software has been built around a single assumption. - Humans are the primary users of enterprise applications. - That’s why we’ve invested billions in dashboards, forms, workflows, navigation, training and user adoption. But AI doesn’t need dashboards. - It doesn’t need menus. - It doesn’t need training. It needs something entirely different. - Context - Business rules - Permissions - Policies - Memory - The ability to execute actions Once AI can securely understand business context and orchestrate work across enterprise systems, something fundamental changes. Applications stop being the destination. - They become infrastructure. - Think about your own enterprise. Today, an employee logs into SAP, Salesforce, Workday, ServiceNow and several internal applications just to complete a single business process. Tomorrow, they may never open those applications. They’ll simply ask: “Approve this supplier.” “Prepare next quarter’s forecast.” “Identify every customer at risk of churn.” “Generate tomorrow’s executive briefing.” The AI won’t replace those applications. - It will orchestrate them. - That’s not a user experience shift. - It’s an enterprise architecture shift. For four decades, enterprises have been designed around systems. ERP CRM HRMS SCM The next decade will be different. We’ll increasingly design enterprises around an Enterprise Intelligence Layer that orchestrates those systems instead of asking employees to navigate them. Which raises a question I don’t hear enough boards asking: If AI becomes the primary interface to enterprise systems… …why are we still investing in application roadmaps instead of intelligence roadmaps? The enterprises that lead the AI era won’t necessarily have the best applications. They’ll have the best intelligence architecture. My prediction is that within the next five years, Enterprise Intelligence Architecture will become as important to the board as Enterprise Architecture once was. This isn’t a theory I’ve arrived at overnight. It’s a pattern that’s emerging across conversations with enterprise leaders, technology vendors, and clients who are actively exploring what it truly means to become AI-native. I’m going to keep documenting these shifts as I see them. Not because I have all the answers—but because I believe we’re witnessing the biggest change in enterprise computing since the rise of cloud. If you’re seeing similar patterns, I’d love to compare notes. The most interesting insights often emerge through discussion.

McKinsey's ERP warning for CFOs: 1. 70% of ERP transformations fail     Most ERP projects run over budget and underdeliver. Why? Because companies underestimate complexity. Finance expects a big bang switch. Instead, they get endless data cleanups, mismatched chart of accounts, and broken workflows. In finance, a 90% rollout isn’t a win. If one close process breaks, the whole system stalls.     2. It's your design, not your tech     CFOs blame vendors. But the real issue is design. Too many teams lift-and-shift old processes into new systems. That hardcodes inefficiency. The 30% who succeed don’t copy the past. They redesign approvals, reconciliations, and controls before go-live. ERP isn’t a tool migration. It’s an operating model redesign.     3. Finance feels the pain first     In sales, if CRM misses a field, people workaround. In finance, if ERP misses a journal entry, you misstate results. Month-end closes, audits, and compliance magnify every flaw. That’s why ERP failures show up in finance before anywhere else. Unless you engineer accuracy and reliability from day one, the CFO’s credibility is at risk.     4. The gap turns critical     McKinsey calls it out: 70% stuck, 30% pulling ahead. The stuck companies run digital systems that replicate legacy pain. The winners embed automation, shared data models, and continuous improvement. Over time, that gap compounds into faster closes, lower costs, and better decision-making.     TAKEAWAY ERP failures don’t just cost money at go-live. They lock in inefficiencies for years. Every close takes longer. Every audit is harder. Every board deck gets delayed. The reverse is also true. When ERP is designed right, benefits compound: - Faster closes free capacity - Automation creates leverage - Cleaner data sharpens insight The real gap isn’t visible at launch. It shows up quarter after quarter, year after year.

Are you considering implementing a new ERP system? Lately, I've engaged in a number of discussions regarding the selection of ERPs, their capabilities, and the intricacies of their implementation process. For any business embarking on this journey, it's a significant decision, but one that holds the potential to transform operations. Drawing from my experience as a CFO, I've witnessed the impact that new ERP implementations can have on businesses. It can present remarkable possibilities to streamline operations, enhance decision-making, and stimulate growth. However, it can also come with its own set of challenges and complexities. So, what exactly does it take to ensure a successful ERP implementation? 1️⃣ Process-Oriented Strategy   - Prioritise Processes: Instead of getting lost in features, focus on your business workflows. Identify areas for enhancement, pinpoint bottlenecks, and imagine how the ERP can boost agility.   - Thorough Mapping: Take stock of current processes and spot any gaps. Consider factors like mobile accessibility, real-time alerts, and data analytics as you modernise. 2️⃣ Harnessing Team Potential   - Team Dynamics: The team driving any ERP implementation is of great importance. You will need to gather a diverse group of executives, project managers, end users, and IT specialists. Their collective insights and dedication will be key to a successful implementation.   - Skills and Expertise: Look beyond job titles. Recruit team members with relevant expertise, industry knowledge, and a knowledge of your chosen ERP platform. 3️⃣ Selecting the Right Implementation Partner   - Industry Understanding: Your chosen partner should be able to grasp the fundamentals of your industry. Seek referrals and validate their track record.   - Methodology: What is their implementation approach? It should reflect their own learning and not just be a generic template. 4️⃣ Avoiding Common Pitfalls   - Robust Governance: Establish strong project governance from the outset.   - Clear Scope Definition: Set precise objectives and requirements - avoid scope creep!   - Data Integrity: Ensure your data is clean and reliable.   - Training: Invest in comprehensive user training, during implementation and after.   - Executive Support: Secure backing from leadership. 5️⃣ People-Centric Strategies   - Inclusive Teams: Engage stakeholders at all levels. Everyone should feel accountable for success.   - Promote Collaboration: Foster open dialogue and teamwork.   - Risk Awareness: Acknowledge potential risks and address them early. Oh, and finally, as the CFO ensure the budget is appropriate and costs controlled! Remember, a successful ERP implementation hinges not only on technology but also on people, processes, and collaboration. I would love to hear about your implementation stories and the key to success. 👇 #ERPImplementation #DigitalTransformation #BusinessGrowth #CFOInsights