Agentic AI in the enterprise: Why architecture matters more than marketing claims

Date:
Tue, 21 Jul 2026 10:17:24 +0000

Description:
Most "AI-powered" marketing tools are just rule engines in disguise. Here's how to tell the difference.

FULL STORY ======================================================================Copy link Facebook X Whatsapp Reddit Pinterest Flipboard Threads Email Share this article 0 Join the conversation Follow us Add us as a preferred source on Google Newsletter Subscribe to our newsletter If youve done any shopping for marketing automation tools these days, youve probably noticed they all claim to be powered by AI. Apologies for splitting hairs, but thats just not true. Hatem Ayed Social Links Navigation

CTO at Clarvos. A significant portion still rely primarily on rule-based automation, work identically to the platforms they replaced, triggering if/then workflows created by human engineers years ago. Give their systems an edge case to parse and youll soon see them send an inappropriate email , crash, or output some stale nonsense that wouldnt matter to any living
person. Same label. Same old architecture. The problem? A rule bottleneck. Latest Videos From Watch full video here:

Traditional marketing automation relies on knowing rules ahead of time. A
lead hits a score? Send an email. A prospect completed behaviors A, B, and C? Trigger sequence Y. Wait Z days, send the follow-up email.

A rules engine can execute these commands flawlessly but it can only execute what it knows. When a situation arises that doesnt fit the rules, what do you do? You update the rules. You may like Why single-player AI is holding back the agentic enterprise How AI is exposing enterprise operating models Why autonomy alone fails and what truly builds trustworthy AI systems Why this matters Marketing is messy. Prospects take unpredictable journeys, trends
come and go overnight, and audiences who loved your message last week dont care about it this week. But rule-based systems can only improve when given new rules to fire. Engineers cant possibly keep writing rules faster than the world changes.

The industry has been papering over this problem with AI buzzwords. Sprinkle some Neural Network magic on a rule engine, and suddenly youve got yourself
an AI platform. Engineers who look past the updated sales brochures still
find the same good old-fashioned if/then statements, patched up with trendy new nomenclature for the latest round of funding. Are you a pro? Subscribe to our newsletter Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed! Contact me with news and offers from other Future brands Receive email from us on behalf of our trusted partners or sponsors By submitting your information you agree to the Terms & Conditions and Privacy Policy and are aged 16 or over.

The difference between legacy automation and true agentic AI is that true agentic AI wont just patch up the last generation of marketing automation tools it will replace them. Agentic AI isnt defined by capabilities so much as by the way decisions are made.

Rules engines ask, what rule should fire next, given this input? Agents ask, what action should I take to get closer to my goal? This is subtle but critical. Agent theory holds that the system knows its goal, its current context, and a list of available actions it can take.

Based on those three pieces of information, it can reason as to which action will bring it closer to accomplishing its overall objective. This extends far beyond executing canned responses - its deciding what to do. What to read
next Why security leaders are cautious about agentic AI AI agents wont transform commerce until retailers redesign how decisions get made AI is no longer borderless

Agentic systems maintain goals, reason over available actions, invoke tools, evaluate intermediate results, and adapt their plans as new information becomes available. The architecture is fundamentally iterative rather than purely reactive.

You know where this is going.

An agent can adapt if a campaign stops performing. It can coordinate with other agents who manage different subsets of that workflow. And it can do so without a human engineer going back into the system to rewrite the rules
every time the world changes. The system manages its goals. Why
specialization matters One important architectural decision that separates good agent implementations from the rest is specialization. Should you build one big generalist AI system to handle everything or many specialized agents, each performing their own task?

Specialization comes up often in discussions around AI, from medical doctors to Renaissance men. There is broad utility in generalization, but singular accuracy in specialization. The family doctor can handle any symptoms you throw at them. But when you need to be absolutely certain about your diagnosis, you see a specialist.

Thats because specialists arent smarter than the generalist theyre just trained on narrower data . Likewise, generalist AI models arent going to produce great results for highly specific use cases. OpenAIs models can write you a marketing strategy. They can craft creative assets. But they cant produce marketing assets that: Fit the pixel ratio requirements of a given publisher Match your brands color palette Align with your target audiences emotional affinity profile Incorporate mentions of trending topics from the previous day They cant do all of those at once, either. And you shouldnt expect them to. For hard problems with specific solutions, you should build specialized agents (sometimes called agent crews) that own a narrow subset of your workflow.

One crew might specialize in strategy generation, while another focuses on creative writing. One might select publishers while another analyzes performance. Separately, these crews create atomic workflows that a
generalist system would struggle to manage. How not hosting your models affects data privacy Theres another argument for specialized, privately
hosted models that isnt made enough: data privacy .

Whenever you use a public large language model (LLM) to write marketing copy, your data is being uploaded to someone elses infrastructure. We dont use customer data for training is easy to say but barely offers any assurance. Inputs are still being ingested, processed, stored, and handled according to what that providers internal policies dictate.

And those policies can change most corporate lawyers have never looked at the data use section of public AI providers Terms of Service, let alone dissected it line-by-line.

But what about controls your organization can enforce? Do your developers scrub data for PII before generating content with an LLM? That only works if everyone in your company memorizes your data policies and uses tools responsibly. One rogue employee attaching a spreadsheet full of internal pricing to a prompt breaks your compliance.

But if the model itself is hosted privately, thats one major source of exposure that goes away. Your data never leaves your infrastructure . Theres no ingestion point to transmit it to a third-party, no training feedback loop that will process it, and no agreement to parse about how that company will handle your data moving forward. Governance is a system property Because AI
in the enterprise has reached a maturity level where governance is a legitimate concern, many teams treat it as a bulk edit at the end of AI-generated content. Have humans review and approve. Thats fine, and many teams require this today. But governance should be built into the system at a fundamental level.

Well-built agents have guardrails at every stage of the decision-making process. That means models that make predictions within set bounds. That
means observability that can trace every word generated back to its origin.

That means third-party benchmarking to prove your models perform well against industry standards, not just internal testing. Governance shouldnt just be applied to outputs it should be inherent in the architecture. What
enterprise buyers should actually be asking about Buying criteria for agentic AI will vary by company, but as requests for proposal accelerate to keep pace with innovation in the industry, here are a few considerations every enterprise buyer should ask about: Goals vs. rules - Is this system actually agentic? Or is it just automating workflows with AI tools bolted on? The
first step is asking vendors point blank what their system does when it encounters data it doesnt know how to parse. Rules engines will point to specific fallback rules that execute. Agents will talk about reassessing
their goal and weighing their available actions until they decide on the next best step. Models and hosting - Where are the models hosted? Are they specialized and trained on domain-specific data? This answers two questions
at once vendor capability, as well as data privacy concerns. Long-term
memory and context - Enterprise agents become dramatically more useful when they retain organizational context over time. Rather than treating every interaction as a new conversation, they can accumulate institutional knowledge, remember previous decisions, and personalize future actions while remaining within governance boundaries. Persistent memory allows agentic systems to improve continuously without requiring engineers to encode new rules after every edge case. Hallucination - No current LLM is immune to hallucinations. The important architectural question is how the system detects, bounds, and mitigates them before they affect downstream business processes. Specialists hallucinate less in their domain of expertise. Prediction window guardrails limit how far an AI system can go outside the data. Human approval gates before sending anything live catch anything that slips through. Governance / auditability - Can the system provide
traceability for every output it generates? Is the systems accuracy benchmarked against a third-party, or just internally verified? The economic case for getting this right There's an additional argument that often gets overlooked in discussions focused on capability: cost structure.

Token-based pricing from large model providers creates a fundamentally unpredictable cost model for enterprise deployments. Every question, every generation, every iteration costs tokens and iterating toward an acceptable output for a complex campaign task can consume a significant volume of them.

Enterprise subscriptions impose usage caps that create their own operational friction. The more AI-dependent your workflows become, the more acute this pressure grows.

Organizations that own and host their own specialized models are not subject to this dynamic. There is no token meter running. The economic relationship
is closer to infrastructure than to a metered service - you bear the cost of building and maintaining the system, and in return you have predictable marginal cost. For organizations at scale, that math changes substantially. Dont fall victim to marketing speak AI marketing platforms will continue to flood the market with AI-sounding languages attached to rules engines. But
for enterprises who truly want to deploy agentic AI, theres a far better solution. Domain specific, privately hosted agents that dont leave your organization exposing itself to risk.

As agentic systems mature, the organizations that differentiate between genuine autonomous architectures and AI-enhanced workflow engines will be better positioned to capture sustainable competitive advantage. We've
featured the best business intelligence platform. This article was produced
as part of TechRadar Pro Perspectives , our channel to feature the best and brightest minds in the technology industry today.

The views expressed here are those of the author and are not necessarily those of TechRadarPro or Future plc. If you are interested in contributing find out more here: https://www.techradar.com/pro/perspectives-how-to-submit



======================================================================
Link to news story: https://www.techradar.com/pro/agentic-ai-in-the-enterprise-why-architecture-ma tters-more-than-marketing-claims


--- Mystic BBS v1.12 A49 (Linux/64)
* Origin: tqwNet Technology News (1337:1/100)