Most organizations I work with spend significant energy tracking competitors. They monitor product launches, pricing changes, talent moves. Standard competitive intelligence.
They're watching the wrong threat.
The $600K signal
Here's a case that should keep enterprise software vendors awake at night. An operations manager — not a developer, not an engineer, not a technical hire — 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.
This isn't a prototype gathering dust on someone's laptop. It's running in production. 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, strategists — professionals with deep domain expertise who had never previously been able to translate that expertise into working software.
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 wasn't the idea. 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 it's the most significant competitive dynamic most organizations are ignoring.
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. You can analyze their strategies. You can 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 understand the problem better than any vendor ever will, but who previously lacked the technical capability to build solutions.
AI coding tools have eliminated that constraint. And the implications are cascading through every industry.
The strategic question most organizations are asking — "How do we defend against this?" — is the wrong question entirely. The right 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.
Every organization I work with has 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. Route everything through official channels.
That's exactly wrong. These people are showing you what your customers actually need. Smart leaders don't fight this energy — they become the platform these builders use. Provide sanctioned AI development environments. Offer templates and guardrails that channel building toward organizational standards rather than away from them.
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 at scale. Professionals who refused to use clunky enterprise software are now building exactly what they need — lightweight, domain-specific tools that solve their precise problem without the overhead of systems designed for everyone.
The opportunity here isn't to improve your existing product to win them back. It's 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 no vendor had identified as opportunities.
The SheBuilds buildathon participants are a perfect example. Many had never written a line of code. They weren't refusing existing tools — they simply never imagined that they could build. Now they can. And the products they're creating are informed by domain expertise that no external development team could 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. Every tool a customer builds using your API is an extension of your ecosystem, not a competitive threat. The companies that win will be the ones whose products become the foundation non-actors build upon.
Create builder communities and hackathons. As I discussed in my post on hackathons as innovation engines, hackathons aren't just innovation events — they're talent discovery mechanisms. 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 the most authentic product requirements you'll ever get.
Treat user-built solutions as market intelligence. When an operations manager builds a $600K replacement using AI tools, the correct response isn't alarm. It's curiosity. What did they build? What problem were they solving? Why didn't your existing offerings solve it? Every shadow-built solution is a product requirements document written in the most honest language possible: working code.
Redirect shadow AI usage toward supported tools. This connects directly to the Shadow AI challenge facing every organization today. Rather than banning unsanctioned building, provide enterprise-grade alternatives that give builders the capability they want with the governance the organization needs. Don't say no — say how.
The deeper strategic shift
The non-actor disruption pattern reveals something fundamental about where AI is taking us. For decades, the software industry has been built on the assumption that building requires builders — specialized, trained, expensive technical talent. That assumption created entire market categories: enterprise software, systems integrators, outsourcing firms, development agencies.
AI tools are dissolving that assumption. Not eliminating technical expertise — complex systems still require deep engineering. But for the vast middle of business software — the dashboards, workflows, automations, and tools that constitute 80% of what organizations buy — the people who understand the problem can now build the solution.
Organizations that recognize this shift early and position themselves as platforms for non-actor builders will thrive. Those that try to maintain the old gatekeeping model — insisting that building must go through official technical channels — will 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 own walls.