SAP vai morrer por causa da IA? Por que o mercado entrou em pânico, e o que voce deveria considerar

In January 2026, the launch of an AI agent wiped out nearly $1 trillion in market value from software companies in less than a week. The Financial Times published an analysis this week discussing what happened. I've included their argument, added what I'm seeing in practice, and disagreed where I felt it lacked depth. In this video: FT Source: Why the market panicked and why the logic makes sense FT Source + personal opinion: The three components of enterprise software moat that agents don't easily replicate Personal opinion: A fourth component the article doesn't mention, bug and vulnerability detection scale Personal opinion: What really changes, including third-party algorithmic software as a threatened category Personal opinion: The risk of vibe coding and why spec-driven development is the right alternative Four-question framework to classify your company's software stack _____________________________________ FREQUENTLY ASKED QUESTIONS Q: What is moat in enterprise software and why does it matter for AI decisions? A: Moat is the barrier that protects a system from being replaced. In enterprise software, the relevant moat isn't the code, but three things that agents don't easily replicate: accumulated historical data that only exists in that system, embedded regulatory compliance that took decades to certify, and switching cost—the real cost of migrating data, retraining teams, and reconnecting vendors. A fourth component is detection scale: vendors with thousands of customers detect bugs and vulnerabilities much faster than any single instance could. Q: What is vibe coding and what are the risks for companies? A: Vibe coding is software development guided by prompts and agents without a well-thought-out architecture, without clear specifications, and without structured technical review. The three main risks are invisible technical debt—code that works in expected cases but breaks when scaling; untested security—vulnerabilities that a vendor with a bug bounty program would have found sooner; A: The absence of a detection scale means you only discover the problem when you experience it, not before. Q: What is spec-driven development and how does it differ from vibe coding? A: Spec-driven development starts with specification: what the system needs to do, what the edge cases are, what the security requirements are, what the acceptance criteria are. Only then does it use agents to generate code against that specification, and validate whether the code meets the specification, not whether it appears to work in superficial tests. It's slower at the beginning and much safer and more scalable in the end. Q: Will SAP and other ERPs be replaced by AI? A: The answer depends on the type of use. Systems of record with accumulated historical data, built-in compliance, and high switching costs have real moat that agents don't easily replicate in the short term. Third-party algorithmic software lacking transparency, point tools without deep integration, and products without accumulated data history are genuinely threatened. The selection is already happening. The S&P 500 software index is still 21 percent below its peak six months after the event. _____________________________________ AI strategic advisory or training for your team: micah6ai.com #SaaS #ArtificialIntelligence #AI #SAP #Salesforce #Estudio68 #AIManagement #VibeCoding #EnterpriseSoftware #AIAgents