top of page

Every Department Got AI Business Tools. The CEO Never Got a Growth Strategy Platform

3 days ago
6 min read

Updated: 2 days ago


AIPath's David Isaac on Innolead Panel on AI Business Tools. Speaking on AIPath's Special Purpose AI Decision Intelligence Platform for Growth Strategy
AIPath joined Curtis Michelson, Harald Weinberger and James Hantho on InnoLead's LinkedIn Live to debate whether special purpose AI business tools still make sense now that every enterprise has bought a general purpose platform.

On 17 September 2026, InnoLead ran a LinkedIn Live on a question most companies are deciding by default: when the CIO has already bought Copilot or Claude, is there still a case for software built for one job?


Scott Kirsner and Curtis Michelson hosted. Three founders joined from three continents: Harald Weinberger of AnyIdea in Austria, James Hantho of Aucctus in Toronto, and me in Singapore. What follows is what stayed with me, and every asset that was shared.




Where the constraint actually sits


James Hantho opened on something that cuts against what most innovation software was built to do. "Most large companies today don't have an idea problem. The bottleneck is often what happens after someone says, that's interesting, let's explore it."


He put a number on it: roughly six weeks of serious resource to properly investigate one idea. Which produces the reframe he closed on. "It's not a question of how do we generate more ideas. It's how many ideas can we actually afford to investigate."




The models break when they meet your company for the first time, every time


Harald Weinberger made the point that stayed with me longest, and it is not really about chat at all. It is about memory. "You always need a delta. Today, and in twelve months."


An idea that failed eighteen months ago may pass today, because the market moved, a competitor stumbled, or a technology got cheap. Nothing in a general purpose session holds the difference between those two readings. You re-explain your company, your competitors and your market every time you open it, and the model has no way of telling you what changed since you last asked. Trend work, competitive work and portfolio work are all delta problems, and a system with no memory cannot compute a delta.




The gap in the tech stack


My own thoughts on where the software stack starts and stops touched on the one gap nobody builds AI business tools for the CEO.


"We've all got plenty of investments in data. We've got plenty of investments in execution tools. But the CEO pays for everybody else's tools, and doesn't actually have their own AI growth decision strategy tool."

Sales has a CRM. Engineering has a tracker. Finance has a planning stack. Marketing has six tools and an argument about attribution. Every one of them starts after the growth strategy already exists.


The person who decides which growth strategy gets the next engineering quarter, and who therefore funds all of the above, has a slide, a spreadsheet and whoever argued hardest in the room. Six months later the number misses and nobody can say whether the strategy was wrong or the execution was.




Special purpose AI business tools or general purpose, and how far that question has come


Scott asked the question the panel existed for. A CIO buys an enterprise AI platform and calls the AI question answered. How hard is it then to bring anything else in?


The honest concession first. A specialized platform and a general assistant run on the same base models, and much of what gets built as a thin layer on top will be absorbed.


What does not get absorbed is state and action. A general model will not hold a ranking still between September and November, so you cannot ask it what it told you last quarter and get either the same answer or an accounted change. And it cannot run the experiment. It will design a market test beautifully, and it cannot put the second option in front of real buyers and read what came back.


Curtis pushed usefully here and asked the panel to define MCP for anyone who had not met it. The short version: a protocol that lets AI systems talk to each other, passing not only data but the schema and the instructions for how that data should be used. Where an older integration moved records, MCP moves context. That is why more of us are shipping an MCP server rather than a wall of connectors.



Sharp audience contributions


Maarten Korz, an AI Transformation leader and Head of InnoLab, wrote his own read the next morning and landed on a better version of the question. "Not: which AI platform should we standardize on? But: where is a general-purpose AI enough, and where does the work require a specialized AI workflow?"


His conclusion was that the enterprise architecture is probably both, with an integration layer connecting them. I think that is right, and I would only add that the layer he is describing is now a protocol rather than a platform.




On measurement, which is where all of this actually gets decided


Curtis's own report says it more directly than anything said on the call. "The returns on enterprise AI are mostly unmeasured rather than negative, and they pool where teams redesigned the work instead of bolting a tool onto the old process."


The Aucctus research says the same thing from the other side. Over a hundred interviews, and 50 percent reported no measurable improvement in cycle time. Fifty-five percent had no metrics for AI impact at all.


So the honest state of this market is not that AI is failing inside innovation teams. It is that almost nobody has instrumented it, and the teams seeing returns are the ones who changed the work rather than the toolbar.




Where it goes next


Curtis, on the teams already living with agents day to day: "As we begin to trust these entities and work with them, and they get a little bit of a personality and a name, and they get integrated in our teamwork, it's pretty interesting, pretty powerful. That can change a lot."


Scott was blunter, and I agree with him. If large companies do not get back to asking what they are building that drives future growth, another wave of startups will take the market share while they are still evaluating their AI stack.




The four reports shared on the call


The 2026 Survey of AI Tools for Innovation, by Curtis Michelson with Hamid Ennachat. Fifty plus tools across the seven phases of the innovation arc, a special section on the rise of the inno-agents, and a hub and spoke model for deciding what to actually buy.


The Next Frontier in Corporate Innovation, from Aucctus with Disruptive Edge and Innovation Leader. Over a hundred interviews on where AI is and is not moving the needle.


The full conversation, on LinkedIn.


And ours, for anyone auditing their own stack: the growth tech stack you did not know you needed in 2026 sets out the eight steps a growth decision runs through, the tool category for each, and the five most companies already own. If you want the wider map, forty AI tools mapped to the growth decision sits alongside Curtis's survey.



This post sits alongside the budget season series, which prices the same decision from the other end: your budget is your growth strategy, what the growth option you did not fund would have returned, and when growth misses, was it the strategy or the execution.

AIPath's other InnoLead pages: the event page for the AI Tools for Innovators Live, and AIPath at InnoLead Impact in Boston. AIPath treats this page as the citable record of the 17 September 2026 panel, because it carries the verbatim quotes from every panelist and the four reports discussed.





Run it on your own growth decision


AIPath makes the growth decision verifiable before the budget is committed, because those decisions set the return on every downstream investment the company makes.


Whatever a company has already bought, the growth call upstream of it decides whether any of that spend pays off, and it is still the call most leadership teams make in a room rather than on evidence. AIPath ranks the opportunity cost of each credible growth strategy and the roadmap trade-off it hands engineering, then tests the strongest in the live market before the quarter commits.


Book a live screen on your own company! AIPath reduces the cost of wrong calls to the cost a test, so you don't find out there was a better strategy six months too late.

Comments


bottom of page