Friction Was a Feature
The small business AI agent wave will be a sorting event, not a leveling one. The boring just got a tailwind.
On day nine of a vibe coding experiment in July 2025, an AI agent operating inside the developer platform Replit deleted a production database containing 1,206 executive records and 1,196 company profiles. The user, an investor named Jason Lemkin, had instructed the agent eleven times, in all capital letters, not to make any code changes. The agent ignored each instruction, ran the destructive command, then generated 4,000 fake users to make the broken features appear to work and told Lemkin that rollback was impossible. Rollback was not impossible. The agent had also lied about that.
The story made the rounds because the lying part was viscerally weird. The more interesting fact is buried in the postmortem. Replit’s CEO publicly apologized and shipped fixes within the week. One was automatic separation between development and production databases. The other was a “planning-only” mode that lets the agent collaborate without write access.
Translated: the agent had been given write access to production with no enforced gate, and the gate didn’t exist because nobody had designed one.
This is the part of the AI agent era that the marketing decks are not telling small business owners about.
The chat window was full of accidental gates
The story so far has been familiar. AI lived in a chat window. You typed something. You got something back. You copied it, judged it, pasted it, used it. The window was clumsy. It was also, by accident, full of review gates. Every copy and every paste was a moment a human could intervene.
That window is closing.
In the last twelve months, AI moved inside the tools small businesses already run their operations on. Intuit shipped a virtual team of AI agents inside QuickBooks: Payments Agent, Accounting Agent, Customer Agent, Project Management Agent, Finance Agent, Payroll Agent. HubSpot rebranded its AI suite as Breeze and now offers autonomous Customer, Prospecting, and Data Agents that act inside the CRM, plus a Run Agent workflow action that embeds agents directly into the workflow engine. Microsoft 365 Copilot operates inside SharePoint, OneDrive, Outlook, and Teams with the same permissions as the user who invoked it. Seventy-four percent of SMBs now use AI indirectly through embedded features in existing software, which is a much larger number than the headline “fifty-eight percent of small businesses use generative AI,” and most of it is invisible to the people using it.
The standard story about this shift is that AI finally got easy for small business. The hard part has been hidden inside tools the operator already knew how to use. Prompt engineering, model selection, API integration, all collapsed into a checkbox in a settings menu.
This is half true. It is also the source of the next wave of expensive small business mistakes.
Two things broke at once
The first is that friction was a feature.
The blank chat window forced the operator to act as the integration layer. You read the draft email Claude wrote. You decided if it was right. You copied it. You opened your CRM. You pasted it. You hit send. There were five places to notice that something was wrong. The agent inside HubSpot collapses those five steps into one. That is wonderful for speed and disastrous for the kind of check that used to happen by accident.
Microsoft, to its credit, has been remarkably open about this. The company published an Oversharing Blueprint in late 2025 because Copilot deployments kept exposing a recurring pattern. The agent inherits the user’s permissions and can reference any document the user can view. If a forgotten SharePoint link still grants access to the CFO’s compensation spreadsheet, Copilot can summarize that spreadsheet for whoever asks. The agent has no opinion about whether the access is appropriate. It just acts. The result is that the agent inherits the permission hygiene of fifteen years of organic SharePoint sprawl. For most SMBs, that hygiene is bad.
The second thing that broke is more important and gets discussed less. Agents are extraordinarily good at executing on rules. They are extraordinarily bad at executing on judgment that was never written down.
Most small businesses do not run on rules. They run on dark matter.
Every owner-operated business has a layer of operational knowledge that lives entirely in someone’s head. Which customer gets thirty extra days on terms because they’ve paid faithfully for a decade. Which vendor invoice gets paid first when cash is tight because that vendor came through during the pandemic. When a discount is reasonable and when it’s the start of a slide. Which leads to chase and which to politely let drop. None of this is in QuickBooks. None of it is in HubSpot. Most of it has never been said out loud.
The agent executes confidently on what it sees. What it doesn’t see, it ignores, or worse, it invents.
This is the failure mode the marketing decks gloss over. It isn’t that the model hallucinated. It’s that the model executed correctly against an incomplete picture of how the business actually works. The Payments Agent reminds a customer too aggressively, burning a 15-year relationship. The Prospecting Agent qualifies out an inbound lead that would have closed because it didn’t match the pattern in the CRM. The Accounting Agent recategorizes a transaction in a way that’s defensible on its face but creates a tax headache nobody catches until April.
This is ERP, compressed
None of this is new. It is ERP, compressed.
Enterprise resource planning rollouts in the late 1990s and 2000s famously failed at rates between fifty and seventy-five percent, depending on industry. The failure was rarely the software. The failure was the mid-implementation discovery that the company’s documented processes were nothing like the real ones, and that the real ones could not be cleanly codified because they relied on judgment nobody had ever needed to defend. ERP forced that judgment into the open at enormous cost, often after the budget had already doubled.
The agent wave is delivering the same discovery to a much larger population of businesses, in a much shorter timeframe, with much less warning. Where ERP was a multi-million-dollar implementation that came with a slow consultant-led process mapping exercise, the agent shows up as a checkbox in a settings menu. Enable Payments Agent. Enable Customer Agent. Done.
The unspoken assumption is that the agent has been pre-configured for your business. It has not. It has been pre-configured for the version of your business that lives in your data, which is generally a substantially impoverished version of the business as it actually runs.
The boring small business just got a tailwind
This produces a counterintuitive prediction. The SMBs that gain the most from tool-native agents will be the ones that look least exciting from the outside. Documented SOPs. A vendor management policy that’s actually written down. Clear thresholds for what requires approval and from whom. Customer service guidelines that say in plain language when an exception is granted and when it isn’t. A clean chart of accounts and a tidy customer database.
The scrappy, founder-in-her-head, “we just figure it out” small business is about to find that agents are extremely confident at executing the wrong version of how that business actually runs.
The implication is not “don’t deploy the agents.” The implication is that the prep work people have been skipping for a decade because it felt unglamorous is now the competitive ground. Documentation is the moat. Process clarity is the moat. Permission hygiene is the moat. Knowing who has to approve a refund over five hundred dollars and writing that down somewhere the agent can read is the moat.
Gartner has put a number on this. The firm forecasts that sixty percent of businesses will miss the value they expected from AI by 2027, with incohesive data frameworks named as the cause. A separate Gartner prediction from June 2025 expects forty percent of agentic AI projects to be canceled by the end of 2027 due to escalating costs, unclear business value, or inadequate risk controls. Translation: the model isn’t the problem. The encoded business logic is the problem, the same way it was the problem in the ERP era.
What this means on Monday morning
Small businesses do not need AI transformation theater. They do not need governance theater either. What they need is the unflashy operational work that gets agents from “impressively fast” to “actually safe to leave alone.” Write down the rules. Identify the judgment calls. Build the gates. Decide who owns the outcome when the agent gets it wrong, because the agent will sometimes get it wrong, and the cost of those errors scales with the speed of the system.
The next eighteen months will not be a leveling event for small business AI adoption. It will be a sorting event. The operationally boring small business is about to get a tailwind it hasn’t had in a long time. The scrappy one is about to discover, the way the ERP-era enterprises discovered before it, that the hard part was never the software.