{"id":639458,"date":"2026-08-16T01:11:30","date_gmt":"2026-08-16T01:11:30","guid":{"rendered":"https:\/\/www.europesays.com\/ie\/639458\/"},"modified":"2026-08-16T01:11:30","modified_gmt":"2026-08-16T01:11:30","slug":"ai-isnt-changing-how-companies-work-its-changing-what-a-company-is","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ie\/639458\/","title":{"rendered":"AI isn\u2019t changing how companies work. It\u2019s changing what a company is"},"content":{"rendered":"\n

Stephen Messer is co-founder of Collective[i] and Intelligence.com, and has been writing about the AI economy on Artificial CommonSense<\/a> at reloadnyc<\/a>. This column synthesizes much of Messer’s recent writing, and is related to several others, including “What It Means to Be AI-First<\/a>,” “The Oldest Trick in Management Just Stopped Working<\/a>,” “The Weakest Link<\/a>,” “The Next Computer Is Alive<\/a>,” and “The Death of Privacy. The Rise of Unbreakable Communications<\/a>.” <\/p>\n

Most companies think they have an AI strategy. <\/p>\n

They have licenses. They have pilots. They have a chief AI officer, an oversight committee, a vendor roadmap, and a slide deck that says “responsible innovation” in a reassuring font. <\/p>\n

What they do not have is a different company. <\/p>\n

Their salespeople still type into CRM systems. Their managers still spend half their weeks gathering information from one team and relaying it to another. Their customers still wait while work moves through the same chains of approval. The old workflows remain. The old hierarchy remains. The old software architecture remains. AI has simply been added to it. <\/p>\n

That is not transformation. It is decoration. <\/p>\n

I have called this the “AI Shuffle<\/a>“: the corporate habit of exchanging one technology logo for another while preserving every underlying assumption about how work gets done. It feels like progress because it generates activity. It does not produce an advantage. <\/p>\n

The companies that pull away in this transition will start from a much more difficult question:\u00a0What work should no longer exist?<\/strong> <\/p>\n

Not: How can AI make this process 10% faster?
Not: Which chatbot should we license?
Not: How many employees are using the tool? <\/p>\n

What can we delete? What decisions can move closer to the customer? What information no longer needs to be collected, reconciled, summarized, and passed up a chain of people before anyone acts? <\/p>\n

That is the difference between adding AI to a company and becoming an AI-first company. <\/p>\n

Start with subtraction<\/strong> <\/p>\n

The conventional corporate response to a new technology is addition. Add a tool. Add a dashboard. Add a project team. Add a layer of governance. Add another system to the stack. <\/p>\n

But the first instinct of an AI-first company should be subtraction. <\/p>\n

In “The Art of Subtraction<\/a>,” I argued that companies should question every requirement, remove unnecessary steps, simplify what is left, and only then automate. That sequence matters. Automating a bad process does not make it a good process. It makes the bad process faster, harder to see, and more expensive to unwind. <\/p>\n

Take sales forecasting. For decades, companies have asked individual sellers to enter projections into CRM, then asked managers to interpret them, then scheduled calls where leadership negotiates a number that everyone knows is partly theater. The data is late, incomplete, and distorted by incentives. The meeting exists because the system cannot observe the buying process directly. <\/p>\n

The AI-era alternative is not a more elegant forecasting meeting. It is a system that analyzes the buyer’s actual behavior, market conditions, timing, relationships, and signals across the commercial process. The goal is not to make the old ritual more efficient. It is to make the ritual unnecessary. <\/p>\n

That is why the companies winning with AI are playing a different game<\/a>. They begin with a specific business constraint and a measurable outcome. They do not measure usage. They measure whether the constraint has moved. <\/p>\n

Software is not the only thing at risk<\/strong> <\/p>\n

This is why the AI conversation is not really about software. <\/p>\n

Yes, traditional software is vulnerable. Much of the enterprise stack was built to organize human data entry: applications that store records, route tasks, generate reports, and help managers reconstruct what happened after the fact. AI agents will increasingly observe activity, maintain context, initiate work, and recommend or execute the next best action. <\/p>\n

But software is not going down alone. <\/p>\n

The management structures built around it are also being challenged. In “Software Is Not Going Down Alone<\/a>,” I made the case that AI will pressure the layers created to gather information, translate it across functions, prepare it for meetings, and relay decisions downward. <\/p>\n

That does not mean leadership disappears. It means that the leaders who create value will be different. <\/p>\n

The people who will matter most are builders: people who understand a real business problem, can use technology to solve it, and are close enough to customers and operations to know whether the solution works. The people who lose relevance will be those whose role depends on preserving friction, controlling access to information, or managing processes no one would design from scratch today. <\/p>\n

In “Find Your Builders. Or They’ll Leave and Start Without You<\/a>,” I argued that too many companies have placed their AI future in the hands of people selected to prevent mistakes rather than create new capabilities. Governance matters. Security matters. But a company that treats every low-risk experiment as if it were a high-stakes autonomous decision will discover that its competitors have learned more while it was still approving a pilot. <\/p>\n

The safest move in AI may be the one that makes you irrelevant<\/a>. Responsible deployment does not require paralyzing every use case. It requires separating the applications that demand rigorous control from the ones where learning must begin now. <\/p>\n

The real moat is above the model<\/strong> <\/p>\n

The debate over AI is still trapped at the model layer: whose benchmark is best, who has the largest training run, whether a particular frontier company is overvalued. <\/p>\n

Those questions matter. They are not the most important ones. <\/p>\n

The models will improve. They will also proliferate. Open and closed systems will compete, prices will decline, and capabilities that once seemed exclusive will become available to more companies. The durable advantage will not come from having access to a model everyone else can rent. <\/p>\n

It will come from what sits above it. <\/p>\n

In “The Only Fight That Matters in AI<\/a>,” I described that battleground as the orchestration layer: the systems that determine which model handles a task, retain context across work, connect intelligence to proprietary data, and learn from the outcomes of real decisions. <\/p>\n

That is where lock-in lives. Not in a prompt. Not in an interface. Not in an employee’s temporary familiarity with a tool. <\/p>\n

The moat is the learning system: a company’s ability to connect proprietary context, trusted relationships, operating data, and feedback from the market. This is why, in “Your Buyer Has a Process<\/a>,” I argued that commercial intelligence must move beyond what a seller enters into a CRM. A buyer’s process unfolds across relationships, timing, incentives, and signals that no single sales rep can fully see. <\/p>\n

The same is true of human networks. The old warm introduction was valuable because it compressed trust. But it was also opaque and dependent on gatekeepers. In “The Warm Intro Is Dead<\/a>,” I explored how verified relationship intelligence can make that trust more visible and usable\u2014if it is built with the right controls and consent. <\/p>\n

This is bigger than the firm<\/strong> <\/p>\n

AI is often discussed as a workforce issue or a technology-budget issue. It is neither. It is an institutional issue. <\/p>\n

The systems that govern housing, infrastructure, energy, capital formation, communications, and privacy were designed in the same pre-AI world as corporate hierarchies: a world where collecting and interpreting information was slow, expensive, and centralized. <\/p>\n

That is why permitting matters. In “Time Kills All Deals<\/a>,” I argued that America’s permitting machinery has become an economic bottleneck. The point is not to automate judgment away. It is to eliminate the administrative drag that turns building a home, opening a business, or investing in infrastructure into an endurance test. <\/p>\n

It is also why the AI infrastructure buildout deserves more serious attention than the usual bubble-versus-no-bubble debate. In “The Trillion-Dollar Trade Wall Street Isn’t Seeing<\/a>,” I argued that data centers, power, and compute capacity are not simply costs attached to a speculative technology cycle. They are strategic options on the next industrial architecture. <\/p>\n

And it is why we should resist simplistic narratives. Circular capital flows can create excess, as I wrote in “The Most Expensive Money in the Room<\/a>.” But it is possible for financing structures to be frothy and for the underlying transition to be real. The important question is what survives if the financial enthusiasm recedes: infrastructure, skills, proprietary intelligence, and operating capabilities\u2014or merely expensive stories. <\/p>\n

The choice in front of leaders<\/strong> <\/p>\n

Every company now faces the same choice. <\/p>\n

It can use AI to preserve yesterday’s institution: the same departments, workflows, data silos, approval chains, and management rituals\u2014just with a more impressive interface. <\/p>\n

Or it can use AI to build the company that should have existed all along: one that sees more, learns faster, acts closer to the customer, and spends less time administering work than creating value. <\/p>\n

The first path will produce plenty of announcements. <\/p>\n

The second will produce a widening gap between companies that appear to be adopting AI and companies that are actually being remade by it. <\/p>\n

The window to choose is open now. It will not remain open indefinitely. <\/p>\n

The opinions expressed in Fortune.com commentary pieces are solely the views of their authors and do not necessarily reflect the opinions and beliefs of Fortune. <\/p>\n

Suggested author disclosure:<\/strong>\u00a0Stephen\u00a0Messer\u00a0is co-founder of Collective[i] and Intelligence.com. The views expressed are his own. <\/p>\n

For publication, I would also consider adding a linked endnote module\u2014“Read the related Artificial CommonSense columns”<\/strong>\u2014with the remaining pieces, including “What It Means to Be AI-First<\/a>,” “The Oldest Trick in Management Just Stopped Working<\/a>,” “The Weakest Link<\/a>,” “The Next Computer Is Alive<\/a>,” and “The Death of Privacy. The Rise of Unbreakable Communications<\/a>.” <\/p>\n

This story was originally featured on Fortune.com<\/a> <\/p>\n","protected":false},"excerpt":{"rendered":"Stephen Messer is co-founder of Collective[i] and Intelligence.com, and has been writing about the AI economy on Artificial…\n","protected":false},"author":2,"featured_media":639459,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[261],"tags":[291,289,290,270505,6930,270506,18,19,17,201968,82],"class_list":["post-639458","post","type-post","status-publish","format-standard","has-post-thumbnail","category-artificial-intelligence","tag-ai","tag-artificial-intelligence","tag-artificialintelligence","tag-chief-ai-officer","tag-companies","tag-crm-systems","tag-eire","tag-ie","tag-ireland","tag-software-architecture","tag-technology"],"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@ie\/117102528657636000","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/639458","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/comments?post=639458"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/639458\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media\/639459"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media?parent=639458"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/categories?post=639458"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/tags?post=639458"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}