<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Elm on Jeff Geiser</title>
    <link>https://jeffgeiser.dev/tags/elm/</link>
    <description>Recent content in Elm on Jeff Geiser</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 15 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jeffgeiser.dev/tags/elm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>account-intelligence-7b-v1: A Small Model That Writes Account Briefs</title>
      <link>https://jeffgeiser.dev/posts/account-intelligence-7b-v1/</link>
      <pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://jeffgeiser.dev/posts/account-intelligence-7b-v1/</guid>
      <description>&lt;p&gt;&lt;strong&gt;I fine-tuned a 7B model to turn raw enterprise account data into structured briefs. It&amp;rsquo;s on Hugging Face now, with the numbers and the gaps.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;By Jeff Geiser — October 2026&lt;/em&gt;&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;The model&amp;rsquo;s up on Hugging Face now: &lt;a href=&#34;https://huggingface.co/jgeiser/account-intelligence-7b-v1&#34;&gt;jgeiser/account-intelligence-7b-v1&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;You hand it a bundle of account signals (support tickets, usage metrics, contract terms, stakeholder notes, etc..) and it gives you back a structured JSON brief across six surfaces: meeting prep, QBR pack, handoff, renewal alert, onboarding, and escalation context. Nobody is supposed to read the output like an essay.. it&amp;rsquo;s JSON, and downstream systems consume it directly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
