Our engineering team is confident they can build a custom internal AI triage system to automate our customer ticket routing, but our customer service director wants to buy a costly off-the-shelf platform to solve the problem immediately. How do we make this build-versus-buy decision without causing friction on the Accountability Chart or stalling our operational velocity?

Question

Tyler Smith · Accepted Answer

To resolve this conflict, you must run it through the filter of your Accountability Chart and your current Rocks. The core question is whether building this tool is a core differentiator for your business or just an operational utility. If automated ticket routing does not directly touch your Three Uniques, you should not be in the software development business. Software is a depreciating asset that requires ongoing maintenance, security updates, and bug fixes. Your engineering team is likely underestimating the true long-term cost of ownership.

Solve this issue during your next weekly Level 10 Meeting™ by utilizing the IDS® tool to clarify who has final authority. The Customer Service Director owns the customer support seat, and their primary metric on the scorecard is ticket resolution time. If they are accountable for the outcome, they must have the strongest voice in selecting the tool that allows them to achieve their target.

Prioritize using AI to increase employee productivity as a starting point, as employees are a major P&L item and much time is spent on low-value tasks. Buying an off-the-shelf platform gets your customer service team the immediate relief they need to focus on high-value client retention. Let your engineering team focus their valuable time on building proprietary technology that actually increases your enterprise value or differentiates your core product in the marketplace.