When a supplier builds AI into its product, that usually doesn't appear as an announcement on your desk. It's in release notes, in a new button in a dashboard, in a feature that "from now on automatically" does something an employee used to do. That is exactly why this signal is easily missed: it comes in as product news, not as strategic news. But the CRM, the accounting package, the planning system or the customer service tool your organization works with is shifting, with that, a small part of the boundary between what is a task AI can take over, what requires oversight, and what remains human work. That boundary was somewhere when you wrote your strategy. It may now be somewhere else, without a single meeting having been held about it.
A supplier adding AI does not automatically change your staffing, your cost structure or your competitive position. What does change: the technical possibility of performing a task faster, with fewer steps or with less human work, now exists, where it did not exist last year. Whether that possibility is actually used depends on whether your organization turns on the feature, whether the quality is sufficient for your situation, and whether oversight is needed that approves or rejects with reason. In some companies, such a feature is incorporated into daily work within a quarter. In other companies it sits idle for a year, because no one has taken the time to assess whether it can be used, or because internal processes are not set up for the new step. That difference does not lie in the technology. It lies in who within the organization asks and answers the question.
A strategy rests on assumptions about costs, lead time, and what a competitor can or cannot deliver. If the software used in your sector structurally becomes faster or cheaper for part of the work, that changes the calculation underlying those assumptions, even if you yourself change nothing. A competitor using the same supplier may be able to perform a task more cheaply or faster tomorrow than today, without you seeing it happen. That is no reason for panic and no reason to wait for more clarity. It is a reason to know which assumptions in your own plan depend on the speed at which certain work is done, and to notice when that dependency shifts.
This signal does not require daily monitoring. Supplier updates that strategically matter don't come every week. A rhythm of once per quarter, tied to the main software suppliers in your sector, is sufficient for most organizations to avoid being caught by surprise. More important than the frequency is the question you ask with every update: does this affect a task that in my organization is still set up as human work? If the answer is no, the update is noise. If the answer is yes, it is time to check whether the assumption underlying your plan still holds.
A supplier adding an AI feature is not staffing advice and no reason for a decision about who continues to do which work. That consideration has its own legal requirements and should not be decided here based on a product update. What does belong here is the question of whether the task the feature affects is set up in your organization in a way that still fits what is technically possible. That is a question about capacity and the organization of work, not about who does the work.
The decision is not: turn on this feature or not. The decision is: which assumption in my strategy is based on the premise that a certain task remains slow, expensive or human work, and is that premise still current. That is a different question from what the price development of AI capacity means for your cost assumptions, and also different from what it means when competitors without a comparable workforce enter the market, but the three signals often point to the same spot in the plan: an assumption that was correct at the time of writing and that may no longer be so by now. Anyone who wants to know whether a strategy is aging for that reason will find a number of concrete indicators on the page about recognizing an aging strategy.
The underlying question is not whether AI is being built in somewhere in your sector. That question has already been answered: it is happening. The question that remains is which work within your own company can actually be taken over by AI, which work requires oversight, and which work remains human work. That is a question per task, not per sector, and it is answered with the work scan of FTE TO AI.
You can start today with the free assumption check: a short round in which you name the assumptions your strategy rests on, and see per assumption when it was last confirmed. That does not give a complete picture, but it does give a first answer to the question of which assumption is most subject to wear. The full strategic pressure test, with sector data, a self-plot of the management team and an ongoing assumption list, is under construction.
Stel uw vraag. Vaak zit de echte vraag een laag dieper — daar mag ik naar vragen.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.