<?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: Yash Asija</title>
    <description>The latest articles on DEV Community by Yash Asija (@yash_asija).</description>
    <link>https://dev.to/yash_asija</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%2F3971571%2F12da2951-d593-4b7d-938c-bff8ce7b31bb.png</url>
      <title>DEV Community: Yash Asija</title>
      <link>https://dev.to/yash_asija</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yash_asija"/>
    <language>en</language>
    <item>
      <title>I Built an AI Sales Agent That Learns From Every Deal — Here's How</title>
      <dc:creator>Yash Asija</dc:creator>
      <pubDate>Sat, 06 Jun 2026 17:07:13 +0000</pubDate>
      <link>https://dev.to/yash_asija/i-built-an-ai-sales-agent-that-learns-from-every-deal-heres-how-3ip8</link>
      <guid>https://dev.to/yash_asija/i-built-an-ai-sales-agent-that-learns-from-every-deal-heres-how-3ip8</guid>
      <description>&lt;p&gt;The problem nobody captures&lt;br&gt;
Every experienced sales rep is a walking memory bank. They remember that the CFO at one account kills anything over $100K without board sign-off. They remember that a particular buyer cares more about integration depth than price. They remember the compliance question that surfaced three calls ago and quietly became a deal-breaker.&lt;br&gt;
That knowledge lives in one person's head. When they're out sick, switch territories, or leave the company, it disappears — and the next rep starts from zero. This is the institutional-knowledge problem, and it costs sales teams real revenue every quarter.&lt;br&gt;
What I built&lt;br&gt;
SalesIQ is an AI sales intelligence engine that treats memory as the product, not a feature. Instead of a chat history, it maintains a structured, evolving understanding of each buyer that any rep can pick up and run with. You can try it here: [your demo url].&lt;br&gt;
How the memory works&lt;br&gt;
Most "AI with memory" is just retrieval — a lookup table dressed up as intelligence. SalesIQ organizes what it knows into three distinct layers, which is what makes it feel like it understands a deal rather than just recalling facts:&lt;/p&gt;

&lt;p&gt;World Facts are the static parameters: the buyer's role, company size, budget constraints, and legal or procurement rules. This is the foundation — without it, the agent restarts every session.&lt;br&gt;
Experiences are episodic — what happened in each call, which objections came up, what excited the buyer, what was committed to. This is the evidence base.&lt;br&gt;
Mental Models are the highest-value layer: synthesized beliefs like "this buyer decides on integration depth, not price." They're generated from patterns across multiple experiences and updated as new evidence arrives.&lt;/p&gt;

&lt;p&gt;The Gemini API does the synthesis and tagging work — turning raw negotiation logs into clean, categorized memory entries and surfacing the heuristics that become Mental Models.&lt;br&gt;
The before/after that matters&lt;br&gt;
Ask a generic AI assistant about a specific deal and it tells you, honestly, that it knows nothing. Ask SalesIQ about the same buyer after a full account history is loaded and it answers with specifics: the budget cap, who has to approve the deal, the objection most likely to come up next, and why. Same question, completely different answer — that gap is the entire point.&lt;br&gt;
Making memory visible&lt;br&gt;
The single most important UI decision was the Memory Inspector — a live sidebar that shows everything the agent knows about the active buyer, split across the three memory tabs. Reps can read it, edit it, and delete entries (with a safety confirmation, because deleting a deal assertion shouldn't be a one-tap mistake). Memory that you can't see and can't correct isn't trustworthy. Making it inspectable is what turns a black box into a tool a rep will actually rely on.&lt;br&gt;
I also added Focus Rooms — switching the active account instantly re-anchors the whole dashboard and memory ledger to that buyer, so a rep juggling several deals never mixes up context.&lt;br&gt;
The stack&lt;/p&gt;

&lt;p&gt;Frontend: React (TypeScript), Vite, TailwindCSS, Framer Motion&lt;br&gt;
Backend: Node.js API layer with a simulated data store&lt;br&gt;
Auth &amp;amp; data: Firebase Authentication and Firestore, with offline/mock fallback for demos&lt;br&gt;
AI: Gemini API for summarization, tagging, and synthesis&lt;/p&gt;

&lt;p&gt;What I learned&lt;br&gt;
The difference between memory-as-lookup and memory-as-belief is enormous. Storing transcripts is easy. The hard and interesting part is synthesizing scattered experiences into a belief the agent can act on — and then showing the rep that belief so they can trust or correct it. The visible, editable memory layer did more for the product's credibility than any amount of model tuning.&lt;br&gt;
Try it&lt;/p&gt;

&lt;p&gt;Demo: [your demo url]&lt;br&gt;
Code: &lt;a href="https://github.com/YashAsija/SalesIQ" rel="noopener noreferrer"&gt;https://github.com/YashAsija/SalesIQ&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you've felt the institutional-knowledge problem on your own team, I'd genuinely like to hear how you've handled it.&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>productivity</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
