ERP Software Solutions

#Dynamics 365 vs #Oracle vs #SAP: Choosing the Right Enterprise Platform Selecting an ERP or enterprise cloud platform is not just a technology decision. It affects finance, operations, HR, supply chain, reporting, user adoption, and long-term scalability. Microsoft Dynamics 365 is often a strong choice for organizations that want flexibility, faster adoption, and deep integration with the Microsoft ecosystem. It works well for companies already using Microsoft 365, Teams, Azure, Power BI, and Power Platform. Its modular structure makes it attractive for businesses that want to start with specific functions and expand gradually. Oracle Fusion Cloud is powerful for large enterprises looking for a unified cloud suite across ERP, HCM, SCM, and enterprise reporting. It is especially strong where finance, procurement, HR, and supply chain need to operate on a connected platform with strong governance and embedded AI capabilities. SAP S/4HANA Cloud is usually best suited for complex global enterprises with deep operational, manufacturing, logistics, and financial process requirements. SAP is highly scalable and strong in industries where process control, compliance, and multinational operations are critical. The simple way to think about it: * Choose Dynamics 365 for flexibility, CRM strength, and Microsoft integration. * Choose Oracle for a unified enterprise cloud suite across finance, HR, and supply chain. * Choose SAP for deep ERP process control, manufacturing strength, and global scale. There is no single “best” platform for every business. The right choice depends on company size, industry, budget, process complexity, implementation partner, and how ready the organization is for change. #ERP #Dynamics365 #OracleFusionCloud #SAP #S4HANA #DigitalTransformation #EnterpriseSoftware #FinanceTransformation #CFO #BusinessTechnology

𝗘𝗥𝗣 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻𝘀 𝗱𝗼𝗻'𝘁 𝗳𝗮𝗶𝗹 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗼𝗳 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆. 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.

"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?

I’ve audited ERPs across 6 countries. From SAP and Oracle to homegrown systems. And the single biggest root cause of reporting failure? Inconsistent spelling in master data. Let me give you a real story: In 2022, I worked with a large metals manufacturer in the UAE. $450M in annual revenue. Oracle backend. Everything “looked fine” on the surface. But month-end inventory valuation kept going off by 7–9%. The issue? Same raw material, different names:  - Aluminum Alloy - Aluminium Alloy - Alu Alloy - Al Alloy - ALUM.ALY Each spelling lived in a different item code or cost center. And WIP was overstated by $4.6M. ERPs fail silently when humans speak 5 dialects of the same data. Different teams create masters. Different countries have different spellings. Nobody flags it. Until a statutory audit or stock variance explodes. My fix? 𝐀 4-𝐬𝐭𝐞𝐩 𝐒𝐩𝐞𝐥𝐥𝐢𝐧𝐠 𝐀𝐮𝐝𝐢𝐭. Before I touch a single module or suggest a migration, I do this: ✓ Run a fuzzy match on item master names (threshold: 85% similarity). ✓ Check project WBS and cost center naming patterns. ✓ Map ledger account titles across entities. ✓ Ask the CFO to approve the “core vocabulary” that all teams must use. This takes 3–5 hours. But has saved companies anywhere between $600K to $6M. Your ERP doesn’t need another feature. It needs one language. Start with spelling. ♻️ 𝐑𝐄𝐏𝐎𝐒𝐓 so others can learn.

𝗪𝗵𝘆 𝗱𝗼 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗘𝗥𝗣 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹? 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝘁𝗿𝗲𝗮𝘁 𝗶𝘁 𝗹𝗶𝗸𝗲 𝗮 𝘀𝗶𝗺𝗽𝗹𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗽𝗮𝘁𝗰𝗵, 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.

🔗 SAP Datasphere & Apache Kafka: The Future of ERP Integration SAP ERP is the backbone of enterprises worldwide, but integrating it with other platforms, databases, and APIs is a major challenge. 🚀 This is where SAP Datasphere and Apache Kafka come in—together, they create a scalable, real-time, and open data fabric for seamless ERP connectivity. Key Takeaways: ✅ SAP Datasphere – A next-gen cloud-based data platform for SAP ERP integration ✅ Apache Kafka – A real-time data streaming powerhouse for scalable, event-driven architectures ✅ Hybrid & Multi-Cloud Ready – Connect on-prem SAP ECC & S/4HANA with cloud-native applications ✅ Seamless Data Flow – Synchronize real-time, batch, and request-response interfaces Why Apache Kafka for SAP Integration? • Real-time event streaming for operational & analytical workloads • Decoupling systems for better flexibility and scalability • Transaction support & exactly-once semantics for ERP-critical processes • Built-in integration with SAP Datasphere, Snowflake, Databricks, and other modern platforms Confluent & SAP: A Strategic Partnership Confluent is now available in the SAP Store, offering fully managed Kafka-powered data streaming. Enterprises can now build event-driven architectures for ERP modernization, just-in-time operations, predictive analytics, and more. 📌 How does your organization handle SAP integration today? Are you exploring real-time event-driven architectures? Let’s discuss in the comments! 🔗 Read the full blog post here: https://lnkd.in/eSd-ZKAY #DataStreaming #SAP #Kafka #S4HANA #ERPIntegration #EventDriven #Cloud #RealTimeData #ApacheKafka #Confluent

The biggest businesses can get major programmes horribly wrong. Here are 4 famous examples, the fundamental reasons for failure and how that might have been avoided. Hershey: Sought to replace its legacy IT systems with a more powerful ERP system. However, due to a rushed timeline and inadequate testing, the implementation encountered severe issues. Orders worth over $100 million were not fulfilled. Quarterly revenues fell by 19% and the share price by 8% Key Failures: ❌ Rushed implementation without sufficient testing ❌ Lack of clear goals for the transition ❌ Inadequate attention and resource allocation Hewlett Packard: Wanted to consolidate its IT systems into one ERP. They planned to migrate to SAP, expecting any issues to be resolved within 3 weeks. However, due to the lack of configuration between the new ERP and the old systems, 20% of customer orders were not fulfilled. Insufficient investment in change management and the absence of manual workarounds added to the problems. This entire project cost HP an estimated $160 million in lost revenue and delayed orders. Key Failures: ❌ Failure to address potential migration complications. ❌ Lack of interim solutions and supply chain management strategies. ❌ Inadequate change management planning. Miller Coors: Spent almost $100 million on an ERP implementation to streamline procurement, accounting, and supply chain operations. There were significant delays, leading to the termination of the implementation partner and subsequent legal action. Mistakes included insufficient research on ERP options, choosing an inexperienced implementation partner, and the absence of capable in-house advisers overseeing the project. Key Failures: ❌ Inadequate research and evaluation of ERP options. ❌ Selection of an inexperienced implementation partner. ❌ Lack of in-house expertise and oversight. Revlon: Another ERP implementation disaster. Inadequate planning and testing disrupted production and caused delays in fulfilling customer orders across 22 countries. The consequences included a loss of over $64 million in unshipped orders, a 6.9% drop in share price, and investor lawsuits for financial damages. Key Failures: ❌ Insufficient planning and testing of the ERP system. ❌ Lack of robust backup solutions. ❌ Absence of a comprehensive change management strategy. Lessons to be learned: ✅ Thoroughly test and evaluate new software before deployment. ✅ Establish robust backup solutions to address unforeseen challenges. ✅ Design and implement a comprehensive change management strategy during the transition to new tools and solutions. ✅ Ensure sufficient in-house expertise is available; consider capacity of those people as well as their expertise ✅ Plan as much as is practical and sensible ✅ Don’t try to do too much too quickly with too few people ✅ Don’t expect ERP implementation to be straightforward; it rarely is

Toast bet on hardware during peak SaaS. VCs called them insane. In 2013, Silicon Valley had one gospel: be asset-light. Zero marginal costs. Scale infinitely. Salesforce owned CRM at 70% gross margins. Workday just IPO'd. Zendesk scaled without servers. Toast did the opposite. Manufacturing POS terminals. Hiring installation armies. Running cables through restaurant walls. "You're insane," VCs said. "Hardware doesn't scale." They learned the hard way. Their first attempt - a sleek consumer app - crashed and burned. That failure taught them what competitors missed: Toast wasn't building a product. They were becoming the restaurant's operating system. Today: $25B market cap. 106,000 locations. 15% of US restaurant transactions. While everyone fought for the surface, Toast owned the plumbing. LegacyCo sells features. NewCo stacks outcomes. After their app failed, Toast realized restaurants didn't need features. They needed operational hell eliminated. Outcome 1: Orders Synchronized (2013) Kitchen synced with servers. No lost tickets. Critical workflow owned. Outcome 2: Payments Reconciled (2015) No more 2am reconciliation. Toast gets 2.6% of every transaction. Outcome 3: Unified Accounts (2016) Eliminated "Tablet Hell." One system while competitors added complexity. Outcome 4: Automated P&L (2017+) Self-running restaurant. Sales triggers payroll, inventory, everything. This is Outcome Stacking. LegacyCo sells licenses. NewCo creates partnerships. Core principle: We only win when you win. Payment Processing: Busy Saturday? Toast earns more. Slow Tuesday? Less. Success shared. Toast Capital: Repayment from daily sales. No sales, no payment. True partnership. Square tried pretty iPads. Clover pushed modularity. They missed the insight: Restaurants want one system that never fails when the kitchen's on fire. The NewCo Playbook Choose Constraints Wisely: Toast picked restaurants only. Focus became fortress. Stack Outcomes: Each layer solved complete problems. Do Hard Things First: Hardware was slow but unassailable. Become Essential: Not through contracts, through infrastructure. Toast embraced what others avoided: Hardware. Cables. Payments. Payroll. The unsexy became the moat. NewCo's future isn't everything for everyone. It's everything for someone. Choose your fortress wisely. (Condensed version for Linkedin - Subscribe to my newsletter to read the full case study)