Thinking right with AI: Where a CEO should start with technology in the next 24 months

The business problem should choose the technology. In the next 24 months, the CEOs who still let the technology decide the problem will find the resulting gap expensive to close.
Published on
August 7, 2026
Written by
Leadership Desk

Board decks this year keep carrying the same slide: a line item for an "AI initiative," approved months before anyone in the room can name the process it is meant to fix. The spending happens. A year later, most of it will not show up on the P&L at all.

This happens because technology decisions don't start with a naed business problem. Rather they start with named technology. Mid-market companies that get the sequence right, starting now, will spend the next 24 months compounding an advantage in data and operating knowledge that a slower competitor, sometimes even an enterprise company, will struggle to close later. Companies that keep buying tools before naming problems will spend the same 2 years running up cost with nothing durable to show for it.

The cost of skipping the first question

Gartner expects more than 40% of agentic AI projects to be canceled by the end of 2027, and it names the causes as runaway costs, undefined business value, and risk controls added as an afterthought. None of those causes is a complaint about the model. They describe a project that was funded before anyone decided what it was for.

Much of the technology-first instinct in mid-market boardrooms comes from mimicking enterprise moves rather than from an original read of the business. A CEO hears that a large competitor is rolling out agents across hundreds of use cases and assumes the lesson is speed. Large organizations struggle hardest to get a single pilot into full production. Importing their playbook into a 500-person company imports the failures too, along with the ambition.

MIT's Project NANDA measured the underlying pattern at a larger scale, in the report that became the reference point for AI's return problem in 2025. Despite $30 to 40 billion in enterprise generative AI investment, 95% of pilots showed no measurable profit-and-loss impact; about 5% created real value. The gap tracked the approach organizations took more than the sophistication of the model they bought.

A mid-market company that buys the wrong tool for the wrong reason fails on a smaller balance sheet than an enterprise does, which makes the mistake visible sooner. The advantage shows up once the sequence starts with a clearly identified problem attached to a number, and technology chosen to solve the problem in the way the business needs.  

This argument does have a limit. Identifying the problem first improves the odds without guaranteeing the outcome. A failed pilot aimed at the identified problem still teaches the company something concrete; a failed pilot aimed at nothing in particular teaches it nothing.

The mid-market advantage measured

The same researchers measured what happens when the sequence starts in the right order, and the mid-market comes out ahead. Top-performing mid-market companies in the study reached full implementation in about 90 days. Large enterprises working through the same category of pilot took about 9 months or longer. The focus explains the gap clearly. A 20,000-person company chasing the same problem is negotiating with 40 department heads before it ships anything.  Whereas, a 500-person company chasing one problem can put its whole organization behind that problem.  

Smaller company start with speed. Mid-market distributors know which 3 customers complain about the same invoicing error every month; a workforce of that size hears about it first-hand, not through a support ticket routed twice. That is a genuine head start over a business intelligence team three layers removed from the customer, and it disappears the moment a company stops treating its own operational detail as an advantage. It starts shopping for whatever a vendor calls "AI-powered" this quarter.

It is also seen that companies pairing with an outside specialist reached production about twice as often as those building the equivalent system alone, about 67% against 33%. This answers a specific worry about moving first without an in-house AI engineering function: what it takes is a problem specific enough to hold an outside partner to a result, and a partnership that pays for that result instead of hours worked.

None of this is free. If you want the 90-day version of this outcome, give the chosen problem the kind of attention a board presentation gets, for a full quarter, not a kickoff call and a check-in. Skip that quarter of attention, and a mid-market company inherits the enterprise timeline anyway, with less budget to absorb the delay.

New research

Understand Your AI Potential - Get Clarity In Minutes

Ai maturity curve-img

Meaningful Tech Podcast

Entrepreneur and thinkbridge co-founder Anand Krishnan discusses how the meaningful use of technology leads to business growth through software, strategies, data science, and culture.
Integration icon

Transformation starts with a diagnosis  

In a survey of 100 US private-company leaders, 52% named expanding AI use a top-3 priority for the year ahead, more than double the 22% who said so 12 months earlier. The same survey found 63% already investing past the pilot stage. The shift most CEOs sense in board meetings is now a number, and it moved fast within a year.

A 24-month sequence built around a diagnosis has a concrete foundation. The first quarter belongs to naming 2 or 3 places where money, time, or customers are leaking, in terms a profit-and-loss statement would recognize rather than a vendor's product category. By month 9, the sharpest of those problems, the one with a number already attached to it, should be in production, built alongside a specialist rather than assembled from scratch alone. The following 9 months are where the sequence starts paying twice: a second problem gets fixed, and the company keeps a working understanding of how these systems perform against its actual operations, something the first deployment could not purchase outright. By month 24, that company is running its third or fourth AI project, on a team that has already made most of the mistakes a first-timer has not yet reached.

The sequence breaks in a specific way when a board decides it wants "an AI strategy" instead of a sequence. That framing invites one org-wide initiative sized to look serious in a board deck, covering multiple departments at once, owned by no one in particular, and measured by adoption instead of a number on the P&L. It fails for the same underlying reason a technology-first bet fails anywhere else, arriving later and at a higher cost.

That gap compounds in ways BCG's research quantifies. In a global study of 1,250 companies, BCG found AI "leaders," the group that had moved past pilots into core operations, posting 1.7 times the revenue growth, 3.6 times the 3-year shareholder return, and 1.6 times the profit margin of the "laggards" that had not (BCG, 30 September 2025). A company that spends its 24 months waiting for a cleaner AI strategy is watching a gap widen against a competitor that spent the same 24 months running the sequence twice.

Approaching the future with strategy

Sequence, not size, will separate companies over the next 24 months. The ones pulling ahead are already identifying problems to solve before they settle for a solution with existing technology, and chose a partner over a generic vendor to build it. Their second win arrived faster than their first, because the team already had tribal knowledge over a company which is starting from month zero still has to learn. That head start compounds, quarter over quarter, whether or not the budget behind it was the biggest one in the room.

Related Articles

4 min read

How to Embed AI into Your MSP Service Stack Without Adding Headcount

Jonathan Mitchell
Jonathan Mitchell
| Author
Read More
4 min read

Why MSPs Need to Start Thinking About AI-First Service Models

Jonathan Mitchell
Jonathan Mitchell
| Author
Read More
4 min read

Building AI-Powered Efficiency: A Roadmap for MSPs with thinkbridge

Jonathan Mitchell
Jonathan Mitchell
| Author
Read More
5 Min Read

Thinking right with AI: Where a CEO should start with technology in the next 24 months

The business problem should choose the technology. In the next 24 months, the CEOs who still let the technology decide the problem will find the resulting gap expensive to close.
CEO, AI Strategy
Written by
Leadership Desk
Published on
August 7, 2026

Board decks this year keep carrying the same slide: a line item for an "AI initiative," approved months before anyone in the room can name the process it is meant to fix. The spending happens. A year later, most of it will not show up on the P&L at all.

This happens because technology decisions don't start with a naed business problem. Rather they start with named technology. Mid-market companies that get the sequence right, starting now, will spend the next 24 months compounding an advantage in data and operating knowledge that a slower competitor, sometimes even an enterprise company, will struggle to close later. Companies that keep buying tools before naming problems will spend the same 2 years running up cost with nothing durable to show for it.

The cost of skipping the first question

Gartner expects more than 40% of agentic AI projects to be canceled by the end of 2027, and it names the causes as runaway costs, undefined business value, and risk controls added as an afterthought. None of those causes is a complaint about the model. They describe a project that was funded before anyone decided what it was for.

Much of the technology-first instinct in mid-market boardrooms comes from mimicking enterprise moves rather than from an original read of the business. A CEO hears that a large competitor is rolling out agents across hundreds of use cases and assumes the lesson is speed. Large organizations struggle hardest to get a single pilot into full production. Importing their playbook into a 500-person company imports the failures too, along with the ambition.

MIT's Project NANDA measured the underlying pattern at a larger scale, in the report that became the reference point for AI's return problem in 2025. Despite $30 to 40 billion in enterprise generative AI investment, 95% of pilots showed no measurable profit-and-loss impact; about 5% created real value. The gap tracked the approach organizations took more than the sophistication of the model they bought.

A mid-market company that buys the wrong tool for the wrong reason fails on a smaller balance sheet than an enterprise does, which makes the mistake visible sooner. The advantage shows up once the sequence starts with a clearly identified problem attached to a number, and technology chosen to solve the problem in the way the business needs.  

This argument does have a limit. Identifying the problem first improves the odds without guaranteeing the outcome. A failed pilot aimed at the identified problem still teaches the company something concrete; a failed pilot aimed at nothing in particular teaches it nothing.

The mid-market advantage measured

The same researchers measured what happens when the sequence starts in the right order, and the mid-market comes out ahead. Top-performing mid-market companies in the study reached full implementation in about 90 days. Large enterprises working through the same category of pilot took about 9 months or longer. The focus explains the gap clearly. A 20,000-person company chasing the same problem is negotiating with 40 department heads before it ships anything.  Whereas, a 500-person company chasing one problem can put its whole organization behind that problem.  

Smaller company start with speed. Mid-market distributors know which 3 customers complain about the same invoicing error every month; a workforce of that size hears about it first-hand, not through a support ticket routed twice. That is a genuine head start over a business intelligence team three layers removed from the customer, and it disappears the moment a company stops treating its own operational detail as an advantage. It starts shopping for whatever a vendor calls "AI-powered" this quarter.

It is also seen that companies pairing with an outside specialist reached production about twice as often as those building the equivalent system alone, about 67% against 33%. This answers a specific worry about moving first without an in-house AI engineering function: what it takes is a problem specific enough to hold an outside partner to a result, and a partnership that pays for that result instead of hours worked.

None of this is free. If you want the 90-day version of this outcome, give the chosen problem the kind of attention a board presentation gets, for a full quarter, not a kickoff call and a check-in. Skip that quarter of attention, and a mid-market company inherits the enterprise timeline anyway, with less budget to absorb the delay.

Weekly newsletter
No spam. Just the latest releases and tips, interesting articles, and exclusive interviews in your inbox every week.
Read about our privacy policy.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Explore how custom tech strategies can help your business.