Blog

Disruption by Non-Actors: When Your Customers Become Your Builders

The biggest AI disruption threat isn't from competitors — it's from customers gaining capabilities previously locked behind expertise and capital. An operations manager just replaced a $600K enterprise contract with an AI-built system.

Business ValueAI DisruptionBlue Ocean StrategyNon-ActorsEnterprise AIInnovation

Organizations I work with usually spend a lot of energy tracking competitors. They monitor product launches, pricing changes and talent moves.

I think they are missing a different kind of threat.

The $600K signal

An operations manager, not a developer or an engineer, built a production-ready system using AI coding tools. The system replaced what would have been a major enterprise software purchase. Cost avoided: approximately $600,000.

It is running in production, not sitting as a prototype. And the person who built it had no formal programming training.

I keep seeing variations of this pattern. At the Stockholm AI Labs Live event, where I presented on AI-driven innovation, the builders shipping actual products weren't the people you'd expect. They were educators, communicators and strategists, professionals with deep domain expertise who had not been able to turn that expertise into working software before.

One example stood out. Emelie Fågelstedt built Digital Fika, a virtual coffee connection platform, using Lovable during the SheBuilds buildathon. The idea had existed in her mind for years. What changed was that AI tools like Lovable removed the barrier between having an idea and shipping it.

This is disruption by non-actors, and I think it is one of the most significant competitive dynamics organizations are overlooking.

Why non-actor disruption is different

Traditional disruption theory focuses on competitors: existing or emerging players who enter your market with better, cheaper or more innovative offerings. You can track competitors, analyze their strategies and respond to their moves.

Non-actor disruption doesn't work this way. It comes from people who were never in the market as builders. They're your customers, your employees, your partners. They're domain experts who often understand the problem better than vendors do, but who previously lacked the technical capability to build solutions.

AI coding tools have removed that constraint, and the effects are spreading across industries.

Many organizations are asking "How do we defend against this?" I think that is the wrong question. A more useful question is: "How do we invite non-actors into our ecosystem?"

Three tiers of non-customers turned builders

Blue Ocean Strategy offers a useful framework here. W. Chan Kim and Renée Mauborgne described three tiers of non-customers. Applied to the non-actor disruption happening right now, each tier reveals a different strategic opportunity.

Tier 1: Soon-to-be non-customers

These are people already at the edge of your market, using your products minimally while looking for alternatives. In the AI context, they're the employees bypassing official IT channels to build their own tools.

Many organizations I work with have shadow builders. Marketing teams creating their own analytics dashboards with AI. Operations managers automating workflows that IT deprioritized. Sales teams building custom CRM extensions because the enterprise system doesn't fit their process.

The natural organizational response is to shut this down, enforce compliance and route everything through official channels.

I think that is a mistake, because these people are showing you what your customers actually need. Rather than fighting this energy, leaders can become the platform these builders use. Give them approved AI tools to build with, plus templates and rules that keep what they build in line with company standards.

Tier 2: Refusing non-customers

These are people who have actively rejected your products: they've evaluated what exists and decided it doesn't work for them. In enterprise software, they're the teams using spreadsheets and manual processes because every available tool is either too heavy, too generic, or too expensive.

AI tools are activating this tier. Professionals who refused to use clunky enterprise software are now building what they need: lightweight, domain-specific tools that solve their problem without the overhead of systems designed for everyone.

The opportunity here is not to improve your existing product to win them back, but to create platforms where they build alongside you. Think of it as moving from software-as-a-product to software-as-a-platform, where your customers' custom-built tools extend your ecosystem rather than compete with it.

Tier 3: Unexplored non-customers

These are people in entirely new market segments who never considered your category at all. They didn't refuse your product. They never knew they could be builders.

This is the tier that Lovable, Claude Code, and similar AI building tools are activating right now. People who never considered software development as an accessible activity are suddenly shipping production applications. They're creating markets that didn't previously exist, solving problems that vendors had not seen as opportunities.

The SheBuilds buildathon participants are a good example. Many had never written a line of code. They weren't refusing existing tools. They never imagined that they could build. And the products they're creating draw on domain expertise that an external development team would find hard to replicate.

Four organizational responses

If non-actor disruption is inevitable, and the evidence strongly suggests it is, organizations need structural responses, not just awareness.

Open APIs for user-built extensions. Make it easy for non-actors to build on your platform rather than around it. A tool a customer builds using your API extends your ecosystem rather than competing with it. I think the companies that do well will be the ones whose products non-actors build on.

Create builder communities and hackathons. As I discussed in my post on hackathons as innovation engines, hackathons are talent discovery mechanisms as well as innovation events. When you create spaces where non-technical domain experts build with AI tools, you learn what your market actually needs. The solutions they create are some of the most authentic product requirements you can get.

Treat user-built solutions as market intelligence. When an operations manager builds a $600K replacement using AI tools, the better response is curiosity rather than alarm. What did they build? What problem were they solving? Why didn't your existing offerings solve it? A shadow-built solution is a product requirements document written in working code.

Redirect shadow AI usage toward supported tools. This is related to the Shadow AI challenge many organizations face. Rather than banning unapproved building, give builders supported tools that do what they want, with the oversight the organization needs.

The deeper strategic shift

For decades, the software industry has been built on the assumption that building requires specialized, trained and expensive technical talent. That assumption created entire market categories: enterprise software, systems integrators, outsourcing firms, development agencies.

AI tools are weakening that assumption. This does not remove the need for technical expertise, since complex systems still require deep engineering. But for the vast middle of business software, the dashboards, workflows, automations and tools that make up 80% of what organizations buy, the people who understand the problem can now build the solution.

I expect organizations that recognize this shift early and position themselves as platforms for non-actor builders to do well. Those that keep the old gatekeeping model, insisting that building must go through official technical channels, may find their customers have already left.

Your action step

Conduct a one-page "non-actor audit" this week. Survey three departments to answer: (1) What tools have employees built using AI without going through IT? (2) What enterprise software are teams working around rather than through? (3) Who in the organization has domain expertise but no way to translate it into tools? Map the answers to the three non-customer tiers above. The pattern will show you where your next platform opportunity lies, and where disruption is already happening inside your organization.

Frequently Asked Questions

What is disruption by non-actors in AI?
Disruption by non-actors occurs when customers, employees, and domain experts gain AI-powered capabilities that let them build solutions previously requiring specialized teams, enterprise software, or external vendors. Unlike traditional disruption from competitors, this threat comes from people who were never in the market as builders before.
How are non-technical professionals disrupting enterprise software?
AI coding tools like Lovable and Claude Code enable non-developers to ship production software. A real example: an operations manager built a production-ready system using AI tools instead of purchasing $600K enterprise software. At Stockholm AI Labs Live, educators and strategists - not engineers - were shipping actual products for the first time.
How should organizations respond to non-actor disruption?
Rather than defending against it, organizations should invite non-actors into their ecosystem using Blue Ocean Strategy's three non-customer tiers: become the platform soon-to-be non-customers build on, create platforms where refusing non-customers build alongside you, and activate unexplored non-customers through lowered barriers. Open APIs, builder communities, and hackathons are key mechanisms.

Originally published in Think Big Newsletter #24 on Amir Elion's Think Big Newsletter.

Subscribe to Think Big Newsletter