Don't Build Your 'Secret Sauce' in an ERP
A recent podcast featured consultant Darian Chwialkowski arguing that competitive advantages should be built outside of vanilla ERP systems. He stressed that business value and pain points must directly correlate with project requirements to ensure technology serves actual business results, not the other way around.
The debate over customizing Enterprise Resource Planning (ERP) systems versus developing proprietary solutions is central to enterprise strategy. While ERPs offer a standardized "single source of truth," they can enforce generic processes, potentially neutralizing a company's unique operational advantages. Consultants argue that a company's most critical and unique processes—its "secret sauce"—should be developed in-house to maintain a competitive edge. Boutique consulting firms are increasingly hired to guide these strategic decisions, focusing on aligning technology with business outcomes. Unlike larger firms that might have preferred ERP vendor relationships, smaller consultancies often provide more objective advice on whether to build or buy. These firms specialize in areas like process optimization and operational improvement, ensuring that technology investments directly address specific business pain points. For professionals in enterprise strategy roles at these boutique firms, the day-to-day involves deep analysis of a client's operations to identify areas of competitive differentiation. This includes mapping critical workflows, benchmarking against competitors, and determining which processes are core to the business model versus which are standard operational functions. This analysis forms the basis for recommending custom software development or selecting and integrating best-of-breed applications alongside a standard ERP. The skill set prioritized by these niche firms includes strong business systems thinking, process redesign, and the ability to translate operational needs into technology requirements. Consultants in this space must be adept at communicating complex technical trade-offs to executive stakeholders, making a clear business case for where to invest in custom solutions. This often involves demonstrating how a tailored application can lead to greater market responsiveness or higher margins. The primary difference in this work at a boutique firm versus a large consultancy lies in the scope and level of hands-on involvement. At a smaller firm, a consultant is more likely to see a project from strategic recommendation through to implementation, working closely with a client's internal teams. This provides a granular understanding of how strategic technology decisions impact the operational realities of a business. Career transitioners looking to enter this field should highlight experience in operational analysis, project management, and any instances of leading technology-enabled business process improvement. Boutique firms often value deep industry or functional expertise over a generalist consulting background. Demonstrating a clear understanding of how specific business processes create value is key to positioning oneself for a role in enterprise strategy and operations at a specialized firm.
