Separating Signal From Noise in 2026
Every major technology wave produces the same pattern: genuine capability advances, followed by overclaiming, followed by a correction, followed by actual adoption at scale. We went through it with cloud computing, mobile, and big data. We're going through it with AI now.
The challenge for developers and engineering leaders is calibrating correctly. Dismissing AI as hype means missing genuine capability shifts that will change competitive dynamics in your industry. Believing everything means building on foundations that aren't ready, burning engineering time on features users won't adopt, and making technology decisions you'll regret when the dust settles.
This post is an attempt at calibration — a clear-eyed look at what AI is actually changing in business software, what timelines are realistic, and where the current claims outrun the evidence.
What Is Actually Changing (With Evidence)
1. The cost of generating structured content has collapsed
Three years ago, producing a personalised, well-formatted document — a proposal, a report, a contract summary — required significant human time. Today, a well-prompted language model can produce a first draft that requires light editing rather than full authorship.
This is real and it's being adopted. The categories where it's showing clear ROI:
- Customer-facing documents: Proposals, quotes, summaries, follow-up emails
- Internal documentation: Meeting notes, incident reports, status updates
- Code first drafts: Boilerplate, test scaffolding, repetitive CRUD operations
- Data interpretation: "Explain what this chart means" at the analyst tier
The productivity gains are real but unevenly distributed. People who work heavily with structured text — writers, analysts, developers — see meaningful productivity improvements. People whose work is primarily relational, physical, or requires deep domain expertise see smaller gains.
2. Search is being replaced by retrieval-augmented generation in knowledge-heavy applications
Enterprise search has always been disappointing. You search a knowledge base and get a ranked list of potentially relevant documents. You then have to read those documents to find the actual answer.
RAG changes the contract: you ask a question in natural language, and you get an answer — ideally with citations so you can verify it. For knowledge-heavy applications (legal, compliance, customer support, internal IT), this is a genuine step function improvement.
The technology is real. The implementation challenge is data quality. RAG systems are only as good as the documents they retrieve from. If your knowledge base is a graveyard of outdated policies and inconsistent formatting, RAG makes it faster to get wrong answers.
3. Autonomous agents are beginning to handle narrow, well-defined workflows
The agent hype cycle peaked around 2024 with claims of fully autonomous software engineers and self-managing businesses. Reality is more modest but genuinely interesting: agents that handle specific, well-scoped workflows with human oversight checkpoints are working in production.
The categories where this is real today:
- Data enrichment pipelines: Agents that look up information, cross-reference sources, and populate structured records
- Tier-1 support triage: Classification, routing, and initial response — with human escalation paths
- Code review assistance: Automated checks for security issues, style consistency, and common bugs
- Report generation: Pulling data from multiple sources and producing narrative summaries
The key word in all of these is "narrow." Agents that work are doing one well-defined thing with clear success criteria and bounded failure modes. Agents that fail are trying to do too much in domains that aren't well-specified.
What Is Being Overclaimed
"AI will replace most knowledge workers within 5 years"
This claim collapses when you look at what knowledge work actually consists of. Most knowledge worker time is spent on: relationship management, judgment calls in ambiguous situations, navigating organizational politics, and communicating with stakeholders. AI assists with the documented, text-based portions of this work. It doesn't handle the rest.
The more accurate framing: AI will handle the rote, repetitive, and document-heavy portions of knowledge work, raising the floor for what each worker can produce. This will reduce headcount growth in some functions. It is unlikely to cause mass displacement in the near term.
"You can replace your entire data team with AI"
This one is being sold hard. The reality: AI can accelerate data analysis, surface anomalies, and generate draft interpretations. It cannot replace the domain expertise required to know which questions are worth asking, why a metric moved, or whether a pattern represents a real business signal or a data quality issue.
Data teams that integrate AI tools well become more productive. They are not eliminated.
"Fully autonomous AI coding will end software development"
GitHub Copilot and similar tools are genuinely useful for certain tasks. They write boilerplate well. They autocomplete familiar patterns. They can generate test cases.
What they cannot do: design systems, make architectural tradeoffs, understand business context, manage technical debt across a large codebase, or navigate the gap between what a specification says and what was actually meant. Software development is not primarily about typing code — it's about understanding problems and making decisions. AI assists with the expression layer. The reasoning layer remains human.
The Business Adoption Curve: Where Different Industries Actually Are
Different industries are at different points in genuine AI adoption, and understanding where your industry sits matters for technology decisions.
Early majority (real ROI being measured now):
- Financial services: Fraud detection, credit risk, regulatory reporting
- Healthcare: Diagnostic imaging assistance, clinical documentation, drug discovery
- Legal: Document review, contract analysis, research assistance
- Software development: Code assistance, test generation, documentation
Early adopter phase (pilots showing promise, scale unclear):
- Manufacturing: Predictive maintenance, quality control
- Retail: Demand forecasting, personalisation at scale
- Professional services: Proposal generation, project scoping
Still experimental (genuine capability, adoption friction high):
- Education: Personalised tutoring, automated grading
- Government: Citizen services, policy analysis
- Construction: Project planning, safety monitoring
The distinction matters because early majority means you can study competitors' implementations and learn from their mistakes. Early adopter means you're figuring things out yourself. Still experimental means the technology is ahead of the deployment infrastructure.
The Infrastructure Layer That Determines Everything
The thing most business AI discussions miss is the infrastructure question. AI capabilities are advancing fast. The infrastructure required to use those capabilities reliably in production is advancing more slowly.
The gaps that matter most right now:
Evaluation infrastructure: How do you know when your AI system is working correctly? The testing tools for AI systems are immature compared to those for traditional software. Most teams are flying partially blind.
Cost management: AI API costs are unpredictable and can scale non-linearly with usage. Teams that haven't built cost monitoring and circuit breakers into their AI architecture routinely get surprised by bills.
Data governance: Which data can you send to external AI APIs? For regulated industries, this is not a minor compliance checkbox — it's a fundamental constraint on what AI you can use and where.
Change management: AI features change user workflows. The organisational challenge of getting people to use AI tools effectively is often larger than the engineering challenge of building them.
What This Means for Engineering Decisions Today
If you're making technology decisions with a 2-3 year horizon, the framework we use:
Build now, with confidence:
- RAG pipelines for knowledge-heavy applications
- LLM-assisted content generation with human review
- Narrow workflow automation with defined scope and human oversight
- AI-assisted code review and testing
Build now, but architect for change:
- AI-powered search and recommendation systems (models and providers will change)
- Customer-facing AI features (user expectations are shifting fast)
- Anything using frontier model APIs (pricing and capability are moving targets)
Wait for the infrastructure to mature:
- Fully autonomous agents for open-ended business processes
- AI systems making consequential decisions without human review
- Multi-model orchestration for complex reasoning tasks
Evaluate carefully before building:
- Replacing human roles wholesale (usually premature and often counterproductive)
- Training proprietary models (expensive, requires data infrastructure most companies don't have)
- Real-time AI in latency-sensitive critical paths
The companies that will be best positioned in three years are not those who adopted AI fastest. They're the ones who adopted AI thoughtfully — building on genuine capabilities, maintaining flexibility as the landscape shifts, and solving real problems rather than demonstrating AI adoption for its own sake.
For a deeper look at how these trends are playing out across different business functions, our team at Lycore has written about the practical implications for software businesses — including what the timeline for genuine agentic automation actually looks like when you look past the marketing.
The Honest Summary
AI is changing business software meaningfully and durably. The changes are real but more incremental than the hype suggests, more dependent on data quality than vendors admit, and more constrained by organizational factors than technologists acknowledge.
The developers and engineers who will navigate this well are those who stay close to evidence — who look at what is working in production rather than what's impressive in demos, who measure adoption rather than capability, and who maintain enough technical foundation to switch approaches as the landscape evolves.
The wave is real. Riding it well requires keeping your feet on the ground.
What AI bets are you making in your current projects? I'm particularly interested in hearing from people who've tried things that didn't work — those stories are usually more instructive than the success cases.