Our operations manager wants to hire a costly outside developer to build our first automated AI pipelines. How do we use our weekly Level 10 Meeting to stress-test this proposal and ensure we are not wasting money on over-engineered technology?

Question

Tyler Smith · Accepted Answer

Before you authorize your operations manager to hire an outside developer for a custom AI project, you must run the proposal through a rigorous IDS process during your weekly Level 10 Meeting. Custom development is often a trap that leads to high costs, delayed timelines, and fragile systems.

Start by identifying the real issue. Is your team trying to solve a unique operational problem, or are they just attracted to a shiny new technology? Ask your operations manager to present a clear business case that defines the exact bottleneck we are trying to clear.

Next, discuss the build versus buy trade-off. In almost every case, a combination of off-the-shelf software and basic API connections is faster, cheaper, and safer than custom code. Ask tough, reality-based questions. Who will maintain this custom code when the developer leaves? How will it integrate with our existing core software?

Finally, solve the issue by setting a specific, measurable Rock for the next ninety days. Do not fund the entire project upfront. Instead, create a pilot phase with a strict budget to test a basic prototype. This disciplined approach ensures you remain healthy and SMART with your finances while driving real operational execution.