The Conversation Has Shifted From "Should We?" to "Why Isn’t Ours Working?"
Twelve months ago, most of my client conversations started with "we know we need to do something with AI, we just don’t know where to start." That conversation is mostly over. The businesses that were going to get started have gotten started. The holdouts are a dwindling group.
The dominant conversation in Q2 2026 is different: "We bought the tools, we ran the pilot, and it’s not creating the value we expected." This is actually a more useful conversation to have, because it gets to the structural questions faster. The tools aren’t the problem. The process underneath the tools is the problem. But that diagnosis requires a different kind of help than the "where do we start" question did.
If you’re in the "why isn’t ours working" camp, the answer is almost certainly one of three things: the underlying process wasn’t documented before the AI was layered on, the team doesn’t have a clear owner for AI outputs and review, or the use cases were chosen for impressiveness rather than for business impact. All three are fixable. None of them are fixed by switching tools.
Agentic AI Is Real, But Most Businesses Aren’t Ready for It
Agentic AI—systems where the AI doesn’t just answer questions but takes sequences of actions autonomously—is the most significant shift happening in the space right now. I’m using it. I’m building with it. It’s genuinely different from what came before.
But here’s what I’m telling clients who are excited about AI agents: they are powerful in proportion to the quality of the systems they operate within. An AI agent running inside a clean, documented, structured workflow creates real leverage. An AI agent running inside an unstructured, manually-held process creates a confident mess.
The businesses getting real value from agentic AI right now have already done the foundational work—clean data, documented processes, defined outputs, clear ownership. The ones who jump to agentic AI without that foundation will spend more time managing the agent than they would have spent doing the work manually. I’ve seen it happen. It’s not a failure of the technology. It’s a foundation problem.
My position: if you can’t describe your workflow clearly enough to train a new employee with a written document, you’re not ready to run an agent in it.
Agentic AI is powerful in proportion to the quality of the systems it operates within. Skip the foundation and the agent makes the mess faster.
The Vendor Consolidation Is Happening and It’s Moving Fast
Eighteen months ago, the AI tool landscape looked like a hundred flowers blooming. Point solutions for every conceivable use case—AI for meeting notes, AI for email, AI for content, AI for CRM, AI for customer service. Distinct tools with distinct pricing for each.
That’s compressing rapidly in Q2 2026. The major platforms are folding the AI layer into their existing products. HubSpot has AI. Salesforce has AI. The marketing platforms have AI. The project management tools have AI. The standalone AI tool that does one thing extremely well is facing serious pressure from "good enough" features inside platforms businesses are already paying for.
What this means for my clients: stop buying new AI tools before you’ve fully used the AI that already exists in your current stack. I would estimate that 70% of the businesses I work with are paying for AI features inside their existing platforms that they’ve never activated. Activate those first. Most of the time, they’re sufficient for the immediate use case.
The vendor consolidation also means pricing pressure is real. Standalone AI tool pricing has compressed meaningfully in the last six months. If you signed a contract for an AI tool at 2024 pricing, it’s worth renegotiating or evaluating alternatives. The market has moved.
AI Coding Assistants Have Changed What’s Possible for Small Businesses
This is the development from the last six months that I don’t think enough small-to-mid businesses are paying attention to. AI coding assistants—tools like Cursor and GitHub Copilot—have made custom-built internal software accessible to businesses that would never have been able to afford custom development two years ago.
What this means in practice: a business that previously had to choose between an expensive custom build and a generic SaaS product that almost-but-not-quite fit their workflow now has a third option. With the right person involved—someone who understands the business process and knows how to direct these tools—you can build a custom internal tool in days rather than months, at a fraction of the previous cost.
I’m not suggesting every business owner become a developer. I am suggesting that the cost-benefit calculation for custom tooling has shifted dramatically, and businesses that aren’t aware of that shift are settling for generic software that fits their workflow imperfectly when they don’t have to.
The "AI Employee" Framing Is Mostly Marketing Noise
There’s been a wave of vendors selling "AI employees" and "AI agents that do the work of a full-time hire." I want to be direct about this because I’m seeing clients make purchasing decisions based on it: the framing is mostly hype calibrated to current hiring anxiety.
AI systems can handle significant portions of what a human employee does in highly structured, high-volume, rule-based work. They cannot handle the relationship judgment, contextual reading, situational adaptation, and genuine accountability that a real employee brings to complex work. If you’re buying an "AI employee" expecting to eliminate a thinking, relationship-managing, judgment-exercising human from your team, you will be disappointed—and you will have a gap in the places that mattered most.
The honest framing is that a well-built AI system can reduce the human time required for certain categories of work by 30 to 50%. That is genuinely valuable. It is not the same as replacing a person.
The honest version of "AI employee" is a well-built system that reduces human time required for certain work by 30–50%. That’s real. It’s not a replacement.
What the Winners Are Doing in Q2 2026
After watching AI implementations succeed and fail across enough businesses to have a clear pattern, the businesses getting real value from AI in Q2 2026 share four characteristics:
**They treated process documentation as a prerequisite, not an afterthought.** Before any AI system went live, they could describe the workflow in writing well enough that someone new could follow it. The AI didn’t create that documentation—they did the work first, then used AI to execute within it.
**They started with the highest-volume, lowest-judgment tasks and expanded from there.** They didn’t try to automate the strategic work first. They automated the administrative overhead, freed up time, built team confidence, then moved to more complex applications.
**They assigned human ownership to every AI output.** Every automated workflow has a named person responsible for reviewing output quality and flagging problems. The AI isn’t running unsupervised. This sounds like extra work. It’s actually what keeps the system from degrading over time.
**They’re iterating monthly.** They review what’s working, what isn’t, and what the next improvement is. They didn’t build the system and walk away. They treat AI implementation as a continuous operational practice, not a one-time project.
The laggards, by contrast, either never started—a dwindling group—or started with too much ambition, hit friction, and quietly let the initiative stall. That stall is expensive in a way that’s hard to see because the cost is opportunity, not spend.
The Platform Wars Are Creating Risk Worth Managing
The major AI platforms are in a serious capability and pricing competition that is good for users in the short term. Capabilities are increasing, prices are falling, and new features are shipping monthly.
The risk is building deep dependencies on a specific platform at a moment when the landscape is still shifting fast. A workflow that depends heavily on a specific model’s particular behavior may behave differently six months from now when that model is updated or deprecated. I’m seeing this cause real disruption for businesses that built without thinking about model dependency.
My guidance: build your workflows to be model-flexible where possible. The business logic—the process, the prompts, the quality standards—should live in your documentation, not inside a specific model’s behavior. That way, when the platform landscape shifts, your intellectual property survives the migration.
What I’d Do Right Now If I Were Running a Mid-Sized Business
This is the question I get most often, and I’ll answer it plainly.
I would not buy any new AI tools for 90 days. I would spend those 90 days auditing what AI capability already exists in my current stack and using it to 80% of its potential. Most businesses I work with have significant unused AI capacity in their existing platforms. That’s free leverage sitting idle.
I would pick one workflow that is high-volume, manual, and clearly documented—or documentable in a week—and build a complete AI-assisted process for it. Not five workflows. One. I would run it for 30 days, measure the time saved, and let that number make the case internally for the next initiative.
I would assign one person on my team to own AI operations. Not a committee. One named person whose job includes monitoring AI output quality, identifying new use cases, and maintaining the system documentation. The businesses that are winning have this person. The businesses that are struggling have a shared ownership model where nobody actually owns it.
And I would stop reading the breathless vendor content about what AI is going to do in three years and spend that time running what actually works right now. The gap between what AI can do today and what most businesses are using it for is enormous. Close that gap before chasing the next capability.
The businesses that will have the strongest AI position in 2027 are not the ones buying the most tools in Q2 2026. They’re the ones building the best operational habits around the tools they already have.
If you want to work through what that looks like for your specific business—what to prioritize, what to stop, and what a realistic 90-day plan looks like—[let’s talk](https://abelsanchez.ai/work-with-me). I work with a limited number of clients on this kind of strategic implementation work, and Q2 is exactly when these conversations are most useful to have.
