<?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: Alex Handsaker</title>
    <description>The latest articles on DEV Community by Alex Handsaker (@alex_semarize).</description>
    <link>https://dev.to/alex_semarize</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%2F3927832%2Fc2a04cf1-35cc-4cce-a3a2-69c13d24f101.png</url>
      <title>DEV Community: Alex Handsaker</title>
      <link>https://dev.to/alex_semarize</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alex_semarize"/>
    <language>en</language>
    <item>
      <title>Semarize - The Conversational Intelligence API</title>
      <dc:creator>Alex Handsaker</dc:creator>
      <pubDate>Fri, 29 May 2026 16:29:20 +0000</pubDate>
      <link>https://dev.to/alex_semarize/semarize-the-conversational-intelligence-api-3idi</link>
      <guid>https://dev.to/alex_semarize/semarize-the-conversational-intelligence-api-3idi</guid>
      <description>&lt;p&gt;Companies record everything now. Every sales call, every support chat, every email thread gets captured and transcribed, and then it just sits there. The data is right in front of you and almost none of it is usable. If I wanted to answer something as basic as "did the buyer confirm budget on this call" across two hundred deals, the only real answer was to get a human to read the transcripts. That isn't conversation intelligence, it's conversation storage with a nicer front end.&lt;/p&gt;

&lt;p&gt;The tools on the market didn't fix this. They gave you a prettier summary and another dashboard, when what I wanted was the underlying data. So I built it. &lt;a href="https://semarize.com" rel="noopener noreferrer"&gt;Semarize&lt;/a&gt; is an API.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;Semarize is a conversational intelligence API. You send it a transcript - a call, an email, a chat, whatever - and it sends back structured, typed data. Not a paragraph for someone to read, but fields your systems can use directly. A boolean for whether a next step was agreed. A score for discovery quality. An extracted string for which competitor came up. Every field comes back with a reason and the exact span of the conversation it was pulled from, so you can audit it instead of trusting it blindly.&lt;/p&gt;

&lt;p&gt;The output is just JSON:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"discovery_quality"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;68&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"budget_confirmed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"next_step_confirmed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"reason"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Buyer agreed to a technical demo on Friday"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"evidence"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"...let's get the whole team on a call Friday."&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"competitor_mentioned"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Gong"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That lands in a CRM field, a BI table, a Slack alert, or an automation step, the same shape every time. No parsing, no prompt babysitting, no one reading transcripts.&lt;/p&gt;

&lt;h2&gt;
  
  
  How you actually use it
&lt;/h2&gt;

&lt;p&gt;Two concepts, that's it.&lt;/p&gt;

&lt;p&gt;A &lt;a href="https://semarize.com/product/bricks" rel="noopener noreferrer"&gt;Brick&lt;/a&gt; is a single semantic check that returns a predictable typed output. "Was a quantified pain identified." "What objection was raised." "Did the rep quote current pricing." You define what matters to you; the NLP side is handled.&lt;/p&gt;

&lt;p&gt;A &lt;a href="https://semarize.com/product/kits" rel="noopener noreferrer"&gt;Kit&lt;/a&gt; is a reusable, versioned bundle of Bricks for a stage, team, or workflow. A discovery Kit, a MEDDICC Kit, a compliance Kit. You point a Kit at a conversation through &lt;a href="https://semarize.com/product/api" rel="noopener noreferrer"&gt;the API&lt;/a&gt; and get every field back in one run.&lt;/p&gt;

&lt;p&gt;No ML engineers needed. You write the logic in plain terms, version it like you would anything else, and call it on every conversation that comes through.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bit I care about most
&lt;/h2&gt;

&lt;p&gt;You can ground the whole thing in your own knowledge. Upload your playbooks, pricing, and product docs, and Bricks evaluate against your business rather than generic assumptions. A Brick can tell the difference between a rep quoting the live rate card and a deprecated one. Keyword matching never could, and a summary model just makes something up that sounds plausible. When your pricing or messaging changes, you refresh the docs and the evaluations move with you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who it's for, and who it isn't
&lt;/h2&gt;

&lt;p&gt;It's for people who want conversation data as infrastructure. RevOps wiring CRM enrichment, GTM engineers building internal tools, data teams who want clean signals in the warehouse. It plugs in behind whatever you already record with - Gong, Zoom, Teams, Fireflies, your own pipeline - so there's no new bot and no rip-and-replace. The same engine runs across &lt;a href="https://semarize.com/solutions/enterprise-sales" rel="noopener noreferrer"&gt;enterprise sales&lt;/a&gt;, &lt;a href="https://semarize.com/solutions/financial-services" rel="noopener noreferrer"&gt;financial services&lt;/a&gt; compliance, and &lt;a href="https://semarize.com/solutions/contact-centers" rel="noopener noreferrer"&gt;contact centres&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It is not a meeting recorder, a coaching dashboard, or a CRM. If what you want is a rep-facing UI to rewatch calls in, Semarize isn't that, and I'd rather tell you now than waste your trial.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;If any of this matches a problem you've got, the fastest way to see it is to throw a transcript at it and look at what comes back. &lt;a href="https://app.semarize.com/signup" rel="noopener noreferrer"&gt;Start for free&lt;/a&gt;, no card, testing in a few minutes.&lt;/p&gt;

&lt;p&gt;Happy to answer anything in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>sales</category>
      <category>revops</category>
    </item>
  </channel>
</rss>
