<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Venkat London26</title>
    <description>The latest articles on DEV Community by Venkat London26 (@venkat_london26_3d9fc8eeb).</description>
    <link>https://dev.to/venkat_london26_3d9fc8eeb</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4086912%2F669f1a68-1e5a-451a-8a7f-f36cce5d5919.png</url>
      <title>DEV Community: Venkat London26</title>
      <link>https://dev.to/venkat_london26_3d9fc8eeb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/venkat_london26_3d9fc8eeb"/>
    <language>en</language>
    <item>
      <title>AI Agents in Business: What They Are, Where They Fit, and How to Start Safely"</title>
      <dc:creator>Venkat London26</dc:creator>
      <pubDate>Thu, 12 Nov 2026 11:26:05 +0000</pubDate>
      <link>https://dev.to/venkat_london26_3d9fc8eeb/ai-agents-in-business-what-they-are-where-they-fit-and-how-to-start-safely-592o</link>
      <guid>https://dev.to/venkat_london26_3d9fc8eeb/ai-agents-in-business-what-they-are-where-they-fit-and-how-to-start-safely-592o</guid>
      <description>

&lt;p&gt;Most people have used a chatbot by now. You type a question, it gives an answer, and that's it.&lt;/p&gt;

&lt;p&gt;AI agents work differently. You give them a goal, and they work out the steps, use tools, check their own progress, and keep going until the job is done or they need help. That shift, from answering to doing, is why agents are getting so much attention in business technology.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.infoplusltd.co.uk/services/it-services/artificial-intelligence" rel="noopener noreferrer"&gt;Artificial Intelligence &lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This post explains what an AI agent is, where agents are useful, where they need care, and how to get started. No heavy jargon.&lt;/p&gt;

&lt;p&gt;Chatbot vs. agent: the simple difference&lt;/p&gt;

&lt;p&gt;A chatbot responds. An agent acts.&lt;/p&gt;

&lt;p&gt;Say a supplier in&lt;/p&gt;

&lt;p&gt;voice arrives by email.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A chatbot can explain what an invoice is, or summarise the text if you paste it in.&lt;/li&gt;
&lt;li&gt;An agent can open the email, read the attached invoice, pull out the amount and due date, check it against the purchase order in your system, and flag it for a person if the numbers don't match.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The model behind both may be similar. The difference is that the agent is connected to your tools and has permission to use them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four parts of a working agent
&lt;/h2&gt;

&lt;p&gt;Every useful agent, simple or complex, has the same four parts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. A clear goal.&lt;/strong&gt; "Help with finance" is too vague. "Match incoming invoices to purchase orders and flag mismatches" is something an agent can work on.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Tools.&lt;/strong&gt; These are the things the agent is allowed to use: your email, CRM, ERP, a database, a search function, an internal API. No tools means no actions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Context.&lt;/strong&gt; The agent needs the right information at the right time: company rules, past records, the current task. Poor context is the most common reason agents give poor results.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Guardrails.&lt;/strong&gt; Limits on what the agent can do, when it must ask a person, and what gets logged. This is the part teams most often skip, and the part that matters most.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the loop looks like in code
&lt;/h2&gt;

&lt;p&gt;Here is a simplified sketch in Python. It is not production code, but it shows the basic shape: decide, act, record, repeat, with a human check for sensitive actions and a hard limit on steps.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;run_agent&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;task&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;tools&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;max_steps&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;history&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;task&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;step&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nb"&gt;range&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;max_steps&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="c1"&gt;# The model looks at the history and picks the next action&lt;/span&gt;
        &lt;span class="n"&gt;action&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;decide_next_action&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;history&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;tools&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="s2"&gt;"finish"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;result&lt;/span&gt;

        &lt;span class="c1"&gt;# Sensitive actions need a person to approve them&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;needs_approval&lt;/span&gt; &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="nf"&gt;ask_human&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="n"&gt;history&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Action rejected by reviewer"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="k"&gt;continue&lt;/span&gt;

        &lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;tools&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

        &lt;span class="c1"&gt;# Keep a record of every step for later review&lt;/span&gt;
        &lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;step&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="n"&gt;history&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"Stopped: step limit reached, needs human review"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three things in this sketch are worth copying in real projects:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A step limit&lt;/strong&gt;, so the agent cannot loop forever.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An approval gate&lt;/strong&gt;, so risky actions (sending money, deleting records, emailing customers) always pass through a person.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A log&lt;/strong&gt;, so you can see exactly what the agent did and why.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where agents fit well
&lt;/h2&gt;

&lt;p&gt;Agents suit repetitive, rule-based work spread across several systems. Common examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Document handling.&lt;/strong&gt; Reading invoices, contracts, or forms, pulling out key fields, and sorting them into the right place.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Customer support.&lt;/strong&gt; Sorting incoming requests, answering routine ones, and passing complex ones to a person with the background already written up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;IT operations.&lt;/strong&gt; Watching alerts, grouping related ones, and suggesting or running standard fixes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Supply chain.&lt;/strong&gt; Tracking stock levels, spotting likely delays, and preparing reorder suggestions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HR processes.&lt;/strong&gt; Preparing onboarding steps, scheduling, and answering routine staff questions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In all of these, the agent takes over the routine steps, and people keep the decisions that need judgment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where to be careful
&lt;/h2&gt;

&lt;p&gt;Agents can also go wrong, so it helps to know how before you start.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;**Wrong answers delivered confidently. Language models can state mistakes as facts. Important outputs need checks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Too much access.&lt;/strong&gt; An agent with broad permissions can cause broad damage. Give it the minimum it needs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Messy data.&lt;/strong&gt; If your records are inconsistent, the agent will be inconsistent too. Data quality comes first.&lt;/li&gt;
&lt;li&gt;**No ownership. Someone on your team should own each agent, the same way someone owns any other process.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Privacy and compliance.&lt;/strong&gt; Be clear about what data the agent can see, where it is processed, and which rules apply to your business.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A practical way to start
&lt;/h2&gt;

&lt;p&gt;You do not need a large programme. A small, careful start works better.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Pick one narrow process.&lt;/strong&gt; Choose something frequent, boring, and low-risk, such as sorting incoming documents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write down how it works today.&lt;/strong&gt; List the steps, the systems, and the people involved. If you can't describe it, an agent can't do it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check your data.&lt;/strong&gt; Make sure the information the agent will rely on is accurate and accessible.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run a small pilot.&lt;/strong&gt; Let the agent suggest actions while people approve them. Measure accuracy and time saved.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Widen access slowly.&lt;/strong&gt; Only allow more automation once the results hold up over several weeks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep reviewing.&lt;/strong&gt; Check logs, collect feedback, and adjust the rules as the process changes.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  A quick readiness checklist
&lt;/h2&gt;

&lt;p&gt;Before building an agent, ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is the goal specific enough to write in one sentence?&lt;/li&gt;
&lt;li&gt;Do we know which systems and data it needs?&lt;/li&gt;
&lt;li&gt;What is the worst thing it could do, and have we blocked that?&lt;/li&gt;
&lt;li&gt;Who approves sensitive actions?&lt;/li&gt;
&lt;li&gt;Who owns it after launch?&lt;/li&gt;
&lt;li&gt;How will we know it is working?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you can answer all six, you are in a good position to begin.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final thoughts
&lt;/h2&gt;

&lt;p&gt;AI agents are not magic, and they are not a replacement for good process design. They let you hand routine, multi-step work to software while people stay in charge of decisions. The teams that get value from them tend to start small, set clear limits, and treat agents like any other part of their operations.&lt;/p&gt;

&lt;p&gt;If you are looking at AI for your own organisation, the areas above, from strategy and integration with existing ERP and CRM systems to document analysis and agent-based operations, are the kind of work covered by the AI services at &lt;a href="https://infoplusltd.co.uk/" rel="noopener noreferrer"&gt;Infoplus Technologies UK Limited&lt;/a&gt;, an IT services and AI solutions company based in Borehamwood, UK.&lt;/p&gt;

&lt;p&gt;What process in your team would you hand to an agent first? Tell me in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>infoplustechnologies</category>
    </item>
    <item>
      <title>SAP, Master Data and AI: A Practical Guide to Modernising Enterprise IT</title>
      <dc:creator>Venkat London26</dc:creator>
      <pubDate>Mon, 05 Oct 2026 11:34:00 +0000</pubDate>
      <link>https://dev.to/venkat_london26_3d9fc8eeb/sap-master-data-and-ai-a-practical-guide-to-modernising-enterprise-it-38dh</link>
      <guid>https://dev.to/venkat_london26_3d9fc8eeb/sap-master-data-and-ai-a-practical-guide-to-modernising-enterprise-it-38dh</guid>
      <description>

&lt;p&gt;title: SAP, Master Data and AI: A Real-World Approach to Modernising Enterprise IT&lt;/p&gt;

&lt;p&gt;description: A no-nonsense guide to &lt;a href="https://www.infoplusltd.co.uk/services/it-services/sap-consulting" rel="noopener noreferrer"&gt;SAP support&lt;/a&gt;, management of master data, AI readiness, and software development for growing businesses.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqrjiz5t7g0iy46k0p374.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqrjiz5t7g0iy46k0p374.png" alt=" " width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Most businesses aim to transform digitally, with a focus on AI readiness. In reality, most enterprise IT issues stem from poor data management and insufficient support. Lack of clarity on priorities creates its own set of problems.&lt;/p&gt;

&lt;p&gt;In my 25+ years of experience in enterprise IT, I've learned the most important lesson: if the foundations aren't established properly, everything built on top becomes problematic.&lt;/p&gt;

&lt;p&gt;The following outlines the most important lessons learned in an easy-to-understand format.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Support your ERP systems: SAP and Oracle
&lt;/h2&gt;

&lt;p&gt;Your ERP systems (SAP or Oracle E-Business Suite or similar) are the backbone of your finance, supply chain, and operations. Poor support can cause issues such as wasted reporting time, workarounds, and a lack of faith in the system among end users.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An effective support system usually includes:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;A clear plan on how your system will be&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Support staff that are onsite or nearby to quickly resolve issues&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Continuous improvements and upgrades to the system&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A support system that is flexible and can scale with the business&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Organisations also use a mix of onshore consultants and offshore support centres to keep costs reasonable while still providing 24/7 support. &lt;a href="https://www.infoplusltd.co.uk/" rel="noopener noreferrer"&gt;Infoplus Technologies UK&lt;/a&gt; uses this model, having SAP-certified support staff in offshore centres and leadership staff in the UK.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; Treat master data as an asset.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Master data refers to essential business data such as materials, suppliers, customers, and assets. Data duplication, inconsistency, and incompleteness present risks at multiple levels of a business. For instance, the reports and automation tools built on master data carry the same defects.&lt;/p&gt;

&lt;p&gt;This is particularly problematic in asset-heavy industries such as manufacturing, utilities and energy, where MRO (maintenance, repair and operations) master data impacts purchase and maintenance decisions. Good data practice includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Data cleansing&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Standardised cataloguing&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Data governance&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Inspection of plant and equipment to ensure records are up to date.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Better data helps eliminate stockouts, duplicative purchasing, and improves reporting.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Build custom applications only when required.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;There are many packaged applications, and it is worth evaluating off-the-shelf applications for the processes you want to develop a custom application for. Custom application development is required when:&lt;/p&gt;

&lt;p&gt;-There are no packaged applications to suit your business processes&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Integrating multiple applications is the real problem&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;-You want to differentiate your business from competitors&lt;/p&gt;

&lt;p&gt;Custom applications should be small in scope. Testing and documentation should occur early and continuously and support for the application should be planned for. Outsourcing product development and testing can help deliver applications faster.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Get AI-ready (without the hype)
&lt;/h2&gt;

&lt;p&gt;AIs are only as powerful as the data and systems that back them. Before investing in AI, you should consider:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Is our data accurate and structured?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Are our core systems integrated?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;What specific problem are we solving with AI?&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the answer to the first two is “no”, then the best AI investment is to improve the basics from sections 1 and 2.&lt;/p&gt;

</description>
      <category>sap</category>
      <category>ai</category>
      <category>webdev</category>
      <category>security</category>
    </item>
    <item>
      <title>The chatbot phase is finished. What's going to replace it isn't a chatbot.</title>
      <dc:creator>Venkat London26</dc:creator>
      <pubDate>Thu, 20 Aug 2026 15:12:11 +0000</pubDate>
      <link>https://dev.to/venkat_london26_3d9fc8eeb/the-chatbot-phase-is-finished-whats-going-to-replace-it-isnt-a-chatbot-41g7</link>
      <guid>https://dev.to/venkat_london26_3d9fc8eeb/the-chatbot-phase-is-finished-whats-going-to-replace-it-isnt-a-chatbot-41g7</guid>
      <description>&lt;p&gt;For the last few years, the majority of "[AI in the enterprise]&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fle8koka964spphrffiqz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fle8koka964spphrffiqz.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;(&lt;a href="https://www.infoplusltd.co.uk/)" rel="noopener noreferrer"&gt;https://www.infoplusltd.co.uk/)&lt;/a&gt;" conversations revolved around the same issue: a chatbot grafted onto a support website or a copilot that creates an email that a human is required to send. Effective, but not enough -it waits for an event, then does one thing, and then ceases.&lt;/p&gt;

&lt;p&gt;The phase that was closed is over. What's coming in its place is software that doesn't need to be contacted. It analyses a goal and breaks it down into steps, and then uses the APIs and tools it requires, and only calls an individual when something goes outside its permission boundaries. This is the change people mean when they talk about "agentic AI," and it's not just a research demonstration—it's appearing in core enterprise applications at a rate most IT teams didn't anticipate.&lt;/p&gt;

&lt;p&gt;If you design, manage or protect enterprise systems, it's not a trend that you can observe from a distance. It affects how you create integrations, the way you think about access control and the way you define a "feature" in the first place.&lt;/p&gt;

&lt;p&gt;What is the reason this is happening right now? It was not even two years ago&lt;br&gt;
Three elements had to mature before agents could be able to move beyond demos:&lt;/p&gt;

&lt;p&gt;Orchestration became standardised. Protocols like MCP (Model Context Protocol) provided agents with a uniform way to find and use external tools instead of each team rolling out brittle integrations. This one change took away large chunks of plumbing that was used to create multi-step automation that was expensive to develop and impossible to maintain.&lt;/p&gt;

&lt;p&gt;Models have become sufficiently reliable to allow chaining. A single bad output from a five-step chain could turn into chaos. The quality of reasoning across models of the current generation has improved to the point that multi-step task execution has become sufficient for specific and well-bounded workflows -not for general autonomy, but more specific ones such as reconciling invoices or triaging tickets and updating data across different systems.&lt;/p&gt;

&lt;p&gt;Governance is no longer an add-on feature. Early pilots failed not so much due to the quality of models and more due to the inability of anyone to determine "what is this agent allowed to touch, and can we prove it after the fact?" Permission scoping, action logs and approval checkpoints are included in the architecture of agents beginning from day one, instead of being retrofitted following an incident.&lt;/p&gt;

&lt;p&gt;In the end, it's because analysts are coming to the same issue from various perspectives this year: agent-integrated applications are growing from a tiny fraction to a significant portion of enterprise software and the gap that exists between "we tried an agent" and "we run one in production" is slowly beginning to close; however, it's much larger than the marketing claims.&lt;/p&gt;

&lt;p&gt;The place it's actually going to land (not where the hype claims it's)&lt;br&gt;
The pattern in real deployments is more granular and boring than the demos that are used for the keynotes:&lt;/p&gt;

&lt;p&gt;Finance and operations reconciling, detection of anomalies and reporting, which used to take days to complete, operates as a bounded agents workflow, with a sign-off by a human step.&lt;br&gt;
Customer service - resolution and triage of tickets for clearly defined categories, with clear pathways to escalate any ambiguity.&lt;br&gt;
Delivery of software -- updates to dependencies, routine quality checks for code, and PR triage where the impact radius of a mistake is very small and can be reversed.&lt;br&gt;
Industries that are regulated -Banking and insurance outshine healthcare and public administration in this area because the workflows can be more standardised, and conformity tools are more advanced.&lt;br&gt;
Note the common theme: each one of them is a specific, well-defined job with a clearly defined boundary and not an all-purpose "AI employee." The businesses that are gaining value are those that resist the urge to create an AI that is broad, and instead offer something that is specific enough to effectively test, monitor and then roll back.&lt;/p&gt;

&lt;p&gt;What does this mean for the way you design&lt;br&gt;
If you're designing for this, a few attainable changes are more important than choosing the right model.&lt;/p&gt;

&lt;p&gt;Design to allow access to tools that goes beyond the prompts. An agent is only as secure as the permissions it's given. Consider every connection to a tool as an API key with the lowest privilege, expiring credentials as well as the audit trail.&lt;br&gt;
Create a human-controlled checkpoint when the price of error is significant. Full autonomy isn't the ultimate goal of most businesses at the moment. A pause-and-approve process for any process that involves customers' data, financial transactions, as well as production equipment is cheap insurance.&lt;br&gt;
Test every aspect before you take it to scale. Decision logs and observation aren't just optional extras; they're what differentiates an operation you can defend against a pilot that you must stop.&lt;br&gt;
Begin by defining a workflow that you are able to evaluate. Time saved, error rate and costs per transaction. Agent projects that are cancelled are typically the ones that no one can tie to a specific number.&lt;br&gt;
A multi-vendor plan for reality. Locking into one orchestration layer or model provider can be a more serious danger with agents than basic chat functions, as your business logic is being embedded into the way that agents communicate with tools and not only in an interface that you could change out.&lt;br&gt;
The real caveat&lt;br&gt;
It's not likely that every agent initiative is likely to succeed. It's important to state that out loud. A substantial portion of the pilots that are currently in production fail, and not due to bad designs, but rather from a lack of clarity on control, ownership or ROI or insufficient risk control after a product is in production. Think of "agentic AI" as an architecture decision that comes with real operational costs, not just as a checkbox option. The teams that reap the most value are those that have a clear scope while also establishing early instrumentation and being transparent about what a particular workflow actually requires autonomy to.&lt;/p&gt;

&lt;p&gt;This is the less thrilling and more practical version of the story, which is the one worth constructing around.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.infoplusltd.co.uk/" rel="noopener noreferrer"&gt;Infoplus Technologies UK Limited&lt;/a&gt; is a specialist across AI automation, automation, and enterprise IT delivery, from the design of agentic workflows as well as RPA up to cybersecurity and cloud. If you're planning an agentic AI pilot project and require a second set of eyes to examine the architecture, contact us.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
