We are tempted to build a custom AI-driven middleware layer to connect our legacy operational software, but our development agency says it will cost a quarter of our annual profit. How do we use Keith Cunningham's Thinking Time and the IDS process to determine if this custom build actually increases our enterprise value or is just a shiny distraction?

Question

Tyler Smith · Accepted Answer

Choosing whether to build custom AI middleware or stick to out of the shelf solutions requires a cold calculation of long-term enterprise value versus immediate capital expenditure. To resolve this, use Keith Cunningham's Thinking Time. Set aside forty-five minutes with a blank pad of paper and focus on this question: How might we achieve the same operational efficiency using existing API integrations so that we can avoid the cash drain of a custom build?

You must distinguish between a genuine operational problem and a strategic predicament. A lack of connectivity is a problem with multiple software solutions. Building custom middleware is a high-risk venture that can easily turn into a financial drain.

Bring this issue to your leadership team's next Level 10 Meeting and put it through the IDS process. Identify the real bottleneck, discuss the true costs, and solve for enterprise value. If your core business is not software development, building custom code rarely adds a premium to your valuation. Instead, private equity buyers often view custom, home-grown middleware as a technical debt risk.

Unless this custom middleware directly supports your V/TO Core Focus and represents a highly defensible differentiator that competitors cannot replicate, you should buy and configure existing enterprise tools. Keep your balance sheet clean, protect your cash flow, and focus your team's energy on executing your quarterly Rocks rather than managing a complex software development project.