<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ozvyo Labs — Field Notes</title>
    <link>https://ozvyo.com/field-notes/</link>
    <description>Field notes from live client work: what broke in production, what we changed, and what held up. Anonymised under a published editorial policy.</description>
    <language>en</language>
    <atom:link rel="self" href="https://ozvyo.com/field-notes/rss.xml" />
    <item>
      <title>Event-driven beats polling for CRM notes</title>
      <link>https://ozvyo.com/field-notes/event-driven-beats-polling-for-crm-notes/</link>
      <guid isPermaLink="true">https://ozvyo.com/field-notes/event-driven-beats-polling-for-crm-notes/</guid>
      <description>Meeting → CRM automation fails when you poll for work. Latency, cost, reliability, and idempotency all improve when the system reacts to real events.</description>
      <pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why polling OneDrive fails for Teams transcripts</title>
      <link>https://ozvyo.com/field-notes/why-polling-onedrive-fails-for-teams-transcripts/</link>
      <guid isPermaLink="true">https://ozvyo.com/field-notes/why-polling-onedrive-fails-for-teams-transcripts/</guid>
      <description>Sales calls live in Teams; CRM needs the transcripts. Polling OneDrive looks simple and breaks in production — here is the event-driven path that holds up.</description>
      <pubDate>Sat, 25 Jul 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
