Ajith Sankaran, Executive Vice President, C5i.
Agentic AI has emerged as a game-changer, with the potential to fundamentally transform how organizations operate and scale. Agentic systems are designed to break down complex objectives into subtasks, then select tools, execute actions and iterate based on outcomes—often without human review at each step.
This shift from static generation to iterative execution introduces a new class of requirements businesses must consider, including reliability, cost predictability, low latency, explainability and security under constrained scope. While general-purpose models were designed to maximize versatility, I have found in my work with agentic systems that these models demand the opposite: controlled capability within a defined domain. This is leading more companies to adopt a narrow LLM system instead of relying solely on general-purpose LLMs.
Challenges With General-Purpose LLMs In Developing Agentic Systems
1. Rising Costs
As AI systems evolve from passive generation tools to autonomous agents, the economic and security math changes dramatically. When an AI agent executes millions of decisions daily across distributed workflows, with each decision journey consuming hundreds of token calls, the total cost of ownership can quickly become unsustainable. A recent BCG study of 1,250 firms found that only 5% are achieving AI value at scale, while 60% report minimal gains despite “substantial investment.” According to Gartner, “Over 40% of agentic AI projects will be cancelled by the end of 2027, due to escalating costs, unclear business value or inadequate risk controls.”
2. Hallucinations
I’ve observed in my own work how hallucinations can compound in execution loops. In interactive copilot scenarios, hallucinations stand a decent chance of being caught by humans; however, in autonomous agents, they tend to propagate. General-purpose models are optimized for fluent, compelling text but often fall short when it comes to truthfulness under constraint.
3. Data Security Challenges
Every token sent to a general-purpose model travels to an external API endpoint. For enterprises handling regulated data (such as healthcare records or financial information), this can create an uncontrolled liability. AI vendors’ terms of service often permit model improvement using customer data, creating a hidden compliance risk.
4. Operational Fragility
Relying on third-party APIs can also introduce systemic risks. I’ve seen multiple cases where service downtime or unpredictable shifts in rate limits, pricing or model versions paralyzed production.
Defining Narrow, Task-Optimized LLMs
A narrow LLM is a language model trained or fine-tuned for a specific domain, task or constrained set of workflows. For example, it might be optimized for financial document classification, customer support resolution or software testing. The output format is often structured and deterministic.
According to Gartner, “by 2027, organizations will implement small, task-specific AI models, with usage volume at least three times more than those of general-purpose large language models (LLMs).” I believe this will be the case because of several ways in which narrow LLMs can benefit agentic systems:
• Reliability Over Breadth: An AI agent tasked with making supply chain decisions does not need linguistic flair or expansive reasoning styles. It needs consistency: accurate variable selection, sound logic and outputs that downstream systems can act upon. Narrow, domain-trained models can deliver precisely that; for example, research has found that smaller models trained exclusively on specific data significantly outperform general-purpose models in text classification.
• Better Cost Economics: General-purpose models expend vast computational capacity solving narrowly defined tasks, which can drive unnecessary latency and cost. By contrast, narrow models concentrate capability, potentially lowering cost per action and enabling agentic systems to operate at scale.
• Operational Advantages: I’ve observed that models trained for specific functions tend to integrate more cleanly with enterprise tools, produce structured outputs and behave predictably. This bounded behavior can also make testing, auditing and validation easier to manage, which is important for systems that act autonomously.
• Better Security: Narrow models can support enforceable security boundaries, including private and on-premise deployments, making them viable for regulated industries where control is not optional.
Challenges To Consider
While narrow LLM models can offer distinct advantages, there are practical limitations that can occur when using them for agentic systems. Narrow LLMs can break down as the tool surface area grows beyond the “known” API patterns they were tuned for, and their accuracy can degrade sharply if fine-tuned on imperfect or mismatched data. Also, it’s important to note that research has found LLMs to be less reliable when it comes to long-horizon planning across many steps and edge cases.
As with any technology, it’s important to be aware of the potential challenges so that you can better assess if this type of system is right for your needs, as well as how to use it most effectively.
Best Practices For Utilizing LLMs
• Evaluate each use case. For agentic workflows in support, finance or ops, start by testing whether a smaller domain model (or routed mix of specialists) meets your accuracy target at lower cost and latency; then move to a large general model only where complexity demands it.
• Treat fine-tuning as a strategic investment. Use disciplined adaptations such as high‑quality proprietary examples, clear train/test splits, and eval‑driven iteration. This can help ensure that the system’s behavior is measured, repeatable and optimized for the workflow, not just “smarter” in general.
• Design for flexibility and control from day one. Avoid architectures that lock critical workflows into a single vendor’s platform. Build agentic systems that can switch models, operate in private or on-premise environments, and preserve long-term operational independence.
• Measure what matters. Model accuracy is necessary but insufficient. Track cost per action, response time under peak load, error rates in live workflows, and the completeness of audit trails; in my experience, these are the metrics that determine whether or not an agent can be trusted at scale.
Conclusion
I believe the shift toward narrow, task-optimized LLMs is not a reaction against scale or capability, but rather a maturation of how enterprises deploy AI in production. Just as general-purpose models opened the era of practical AI, narrow, orchestrated models could define the economics and security of autonomous AI systems going forward.
Forbes Business Council is the foremost growth and networking organization for business owners and leaders. Do I qualify?

Leave a comment