Our tech-savvy Visionary wants to build custom AI middleware to connect our various internal databases, while our Integrator wants to stick with the native, bolted-on AI tools coming out from our existing CRM and ERP providers. How do we run this strategic dilemma through our EOS processes?

Question

Tyler Smith · Accepted Answer

This is a classic tension between the Visionary's drive for customized innovation and the Integrator's focus on stability and cost control. To resolve this dilemma, you must take it to your weekly Level 10 Meeting and put it on the Issues List. Use the IDS process to unpack the issue completely. Start by asking if building custom middleware aligns with your Core Focus on the V/TO. If your Core Focus is not software development, building custom middleware is a massive distraction that will drain your cash and focus. Building proprietary connections means you own the maintenance, security, and ongoing updates. Every time an external API changes, your custom code will break, pulling your team away from core operations. On the other hand, relying solely on bolted-on tools from CRM providers might limit your flexibility and keep you dependent on their ecosystem. Evaluate this using Verne Harnish's four decisions framework, specifically focusing on execution and cash. If the off-the-shelf tool gets you eighty percent of the way there for a fraction of the cost, the business case for building custom middleware disappears. Unless that remaining twenty percent is a core differentiator that directly impacts your three uniques, choose the off-the-shelf path. Keep your execution clean and focus your capital on activities that build tangible enterprise value for an exit.