<?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>Forem: Milind Garge</title>
    <description>The latest articles on Forem by Milind Garge (@milind_garge_3f68a36224ad).</description>
    <link>https://forem.com/milind_garge_3f68a36224ad</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3645313%2Ff8fb16c5-64ec-43ea-bb2e-ca5adaf23e92.png</url>
      <title>Forem: Milind Garge</title>
      <link>https://forem.com/milind_garge_3f68a36224ad</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/milind_garge_3f68a36224ad"/>
    <language>en</language>
    <item>
      <title>Can Small AI Agents Work Like a Finance Team? I Tried It.</title>
      <dc:creator>Milind Garge</dc:creator>
      <pubDate>Thu, 04 Dec 2025 07:50:11 +0000</pubDate>
      <link>https://forem.com/milind_garge_3f68a36224ad/can-small-ai-agents-work-like-a-finance-team-i-tried-it-7if</link>
      <guid>https://forem.com/milind_garge_3f68a36224ad/can-small-ai-agents-work-like-a-finance-team-i-tried-it-7if</guid>
      <description>&lt;p&gt;🛡️ What We Created&lt;/p&gt;

&lt;p&gt;A lightweight, multi-agent system called InvoiceShield mimics how a finance team assesses invoices for risk.&lt;br&gt;
Rather than relying solely on one AI, we developed several tiny agents that:&lt;br&gt;
Organize invoice-style information.&lt;br&gt;
Examine the risk of vendors.&lt;br&gt;
Score anomalies repeatedly.&lt;br&gt;
Confirm your confidence.&lt;br&gt;
Write investigation summaries.&lt;br&gt;
Communicate outcomes.&lt;br&gt;
It is not a single prompt but rather a process model.&lt;/p&gt;

&lt;p&gt;🤝 Why This Problem&lt;/p&gt;

&lt;p&gt;Finance jobs are repetitious, error-prone, and high-stakes:&lt;br&gt;
·        Invoices that are duplicates&lt;br&gt;
·        Unknown merchants&lt;br&gt;
·        Manual reconciliation&lt;br&gt;
·        Unexplained decisions&lt;br&gt;
Our goal was to determine whether several little AI agents might divide labor into distinct tasks, exactly like people do.&lt;/p&gt;

&lt;p&gt;🧠 Architecture Snapshot&lt;/p&gt;

&lt;p&gt;The interactive_finops_agent, which powers a pipeline of:&lt;br&gt;
·        data_ingest_agent: arranges input;&lt;br&gt;
·        research_agent: utilizes Google_search;&lt;br&gt;
·        anomaly_detector: loop-based scoring;&lt;br&gt;
·        validation_checker: threshold gate;&lt;br&gt;
·        investigation_agent: reports results;&lt;br&gt;
·        communications_agent: produces summary&lt;br&gt;
Each agent does a single task effectively. When combined, they yield an understandable outcome.&lt;/p&gt;

&lt;p&gt;🔄 The Loop: Small but Powerful&lt;/p&gt;

&lt;p&gt;The anomaly detector doesn’t guess once—it:&lt;br&gt;
·        Scores the invoice&lt;br&gt;
·        Checks confidence&lt;br&gt;
·        Repeats until threshold is satisfied&lt;br&gt;
This makes decisions deliberate, not spontaneous.&lt;br&gt;
Occasionally:&lt;br&gt;
“Retry, confidence too low.”&lt;br&gt;
Occasionally:&lt;br&gt;
“Escalate, looks suspicious.”&lt;/p&gt;

&lt;p&gt;💡 What We Learned&lt;/p&gt;

&lt;p&gt;·        Workflows involving multiple agents are more dependable than those involving a single mega-agent.&lt;br&gt;
·        Orchestration plus small roles equals scalable logic&lt;br&gt;
·        Iteration is a straightforward yet powerful tactic.&lt;br&gt;
·        Hallucinations are lessened by grounding.&lt;br&gt;
·        If you design for explainability, it is simple.&lt;br&gt;
·        "Genius AI" is not what it is. There is a small office crew that never gets bored.&lt;/p&gt;

&lt;p&gt;🌟 Why It’s Interesting &lt;/p&gt;

&lt;p&gt;InvoiceShield demonstrates the following capabilities of autonomous agents:&lt;br&gt;
·        Divide up the cognitive work&lt;br&gt;
·        Verify decisions&lt;br&gt;
·        Produce results that can be explained&lt;br&gt;
Not ostentatious, but somewhat similar to actual corporate automation.&lt;/p&gt;

&lt;p&gt;What We Learned from the 5-Day AI Agents Intensive &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.amazonaws.com%2Fuploads%2Farticles%2Fdb85ko42vi5lr79fiwmi.jpg" 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.amazonaws.com%2Fuploads%2Farticles%2Fdb85ko42vi5lr79fiwmi.jpg" alt=" " width="800" height="446"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Day 1: Basics We learned what makes an AI system an agent: perception, reasoning, action, and autonomy. We investigated the significance of multi-agent systems for practical processes. Conclusion: Agents act like independent workers rather than chatbots.&lt;br&gt;
Day 2: Resources &amp;amp; Activities We looked at how agents act outside of language using tools, APIs, and the Model Context Protocol. Conclusion: When agents are capable of doing more than just talking, they become valuable.&lt;br&gt;
Day 3: Context &amp;amp; Memory We researched short-term and long-term memory and how context supports multi-step activity. Conclusion: Memory transforms agents into strategic systems rather than reactive responses.&lt;br&gt;
Day 4: Quality and Assessment We gained knowledge about how to log, track, and assess agents for dependability, security, and openness. Conclusion: Additionally, smart agents need to be consistent, auditable, and traceable.&lt;br&gt;
Day 5: From Prototype to Production We examined agent deployment, scalability, agent supervision, and agent-to-agent communication. Conclusion: Converting a demo into a reliable, functional solution is challenging.&lt;/p&gt;

&lt;p&gt;⭐ Overall Learning&lt;/p&gt;

&lt;p&gt;We discovered how to create agents that act, think, and use tools.&lt;br&gt;
Keep in mind to integrate the performance scale into actual workflows.&lt;br&gt;
Production-oriented agent systems replaced LLM prototypes.&lt;/p&gt;

&lt;p&gt;🧠 Mindset Shift&lt;/p&gt;

&lt;p&gt;Agents aren’t merely better chatbots. They are autonomous, cooperative systems that can accomplish worthwhile tasks.&lt;/p&gt;

&lt;p&gt;Team:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Milind Garge&lt;/li&gt;
&lt;li&gt;Ayush Malwatkar&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Link to Code&lt;/p&gt;

&lt;p&gt;GitHub Repository:&lt;br&gt;
👉 &lt;a href="https://github.com/MilindGarge07/InvoiceShield" rel="noopener noreferrer"&gt;https://github.com/MilindGarge07/InvoiceShield&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Demo Video&lt;br&gt;
YouTube Link:&lt;br&gt;
👉 &lt;a href="https://youtu.be/qEoCgYzlcGM" rel="noopener noreferrer"&gt;https://youtu.be/qEoCgYzlcGM&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🙏 Closing Thoughts&lt;/p&gt;

&lt;p&gt;We designed InvoiceShield to explore a simple idea: “What if AI worked like teammates—not oracles?”&lt;br&gt;
Even with simulated data, the system feels structured, careful, and collaborative.&lt;br&gt;
Feedback, suggestions, or enhancements would be greatly appreciated, particularly from those developing in the agent space.&lt;br&gt;
I appreciate you reading! &lt;br&gt;
— Milind and Ayush &lt;/p&gt;

</description>
      <category>googleaichallenge</category>
      <category>ai</category>
      <category>devchallenge</category>
      <category>kaggle</category>
    </item>
  </channel>
</rss>
