<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Briefi blog</title>
    <link>https://briefi.sh/blog</link>
    <atom:link href="https://briefi.sh/rss.xml" rel="self" type="application/rss+xml" />
    <description>Field notes, product deep-dives, operator playbooks and comparisons from the team building Briefi — AI meeting intelligence for operators.</description>
    <language>en-AU</language>
    <lastBuildDate>Thu, 18 Jun 2026 08:27:51 GMT</lastBuildDate>
    <generator>briefi-rss-generator</generator>
    <item>
      <title>Your workspace is not a flat trust zone</title>
      <link>https://briefi.sh/blog/workspace-is-not-a-flat-trust-zone</link>
      <guid isPermaLink="true">https://briefi.sh/blog/workspace-is-not-a-flat-trust-zone</guid>
      <description>Briefi now ships meeting visibility levels, private mailboxes, teams, a database-enforced viewer role, and an audit log API. Here&apos;s why we rebuilt the access model before the team features, not after.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Product</category>
      <pubDate>Thu, 11 Jun 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Briefi vs Granola — the multi-workspace difference</title>
      <link>https://briefi.sh/blog/briefi-vs-granola</link>
      <guid isPermaLink="true">https://briefi.sh/blog/briefi-vs-granola</guid>
      <description>Granola is the best single-workspace notetaker I&apos;ve used. Briefi is built for operators working across multiple workspaces. Here&apos;s the specific point where they diverge.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Comparisons</category>
      <pubDate>Tue, 26 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Multi-workspace setup for operators running multiple ventures</title>
      <link>https://briefi.sh/blog/playbook-multi-workspace-setup</link>
      <guid isPermaLink="true">https://briefi.sh/blog/playbook-multi-workspace-setup</guid>
      <description>If you work across more than one workspace — consulting clients, side projects, brands, board roles — this is the order to do things in.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Playbooks</category>
      <pubDate>Tue, 26 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to set up Briefi for a 5-person sales team in 30 minutes</title>
      <link>https://briefi.sh/blog/playbook-5-person-sales-team-30-minutes</link>
      <guid isPermaLink="true">https://briefi.sh/blog/playbook-5-person-sales-team-30-minutes</guid>
      <description>A minute-by-minute setup walkthrough for a small sales team — workspace, seats, CRM, discovery guides, first run. No consultant required.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Playbooks</category>
      <pubDate>Mon, 25 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>AI meeting tools for solar sales teams — what to look for</title>
      <link>https://briefi.sh/blog/ai-meeting-tools-solar-sales</link>
      <guid isPermaLink="true">https://briefi.sh/blog/ai-meeting-tools-solar-sales</guid>
      <description>Solar sales has a specific shape — site visits, quotes, finance, decision-maker presence. Most AI meeting tools are tuned for generic B2B and miss it. Here is what actually matters.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Industry</category>
      <pubDate>Mon, 25 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Briefi vs Otter — when transcription is not the bottleneck</title>
      <link>https://briefi.sh/blog/briefi-vs-otter</link>
      <guid isPermaLink="true">https://briefi.sh/blog/briefi-vs-otter</guid>
      <description>Otter solves transcription. Briefi solves the meeting loop. They get compared, but they answer different questions. Here&apos;s how to pick the one your workflow actually needs.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Comparisons</category>
      <pubDate>Sun, 24 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How Briefi briefs work — what the AI reads, what it writes</title>
      <link>https://briefi.sh/blog/how-briefi-briefs-work</link>
      <guid isPermaLink="true">https://briefi.sh/blog/how-briefi-briefs-work</guid>
      <description>Inside the pre-meeting brief: the calendar event, the contact history, the chosen discovery guide, the optional web research, and the prompt that ties them together.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Product</category>
      <pubDate>Sun, 24 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Founder pricing — locked forever, for the first wave</title>
      <link>https://briefi.sh/blog/founder-pricing-locked-forever</link>
      <guid isPermaLink="true">https://briefi.sh/blog/founder-pricing-locked-forever</guid>
      <description>A time-limited offer that locks Solo at $9, Pro at $19, and Business at $39 per month, structurally permanent via Stripe coupon. Here&apos;s how the lock works, why it&apos;s time-limited, and what happens after the window closes.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Inside Briefi</category>
      <pubDate>Fri, 22 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The MCP server — your AI agent has meeting context now</title>
      <link>https://briefi.sh/blog/mcp-server-meeting-context</link>
      <guid isPermaLink="true">https://briefi.sh/blog/mcp-server-meeting-context</guid>
      <description>Briefi ships a hosted MCP server. Drop https://mcp.briefi.sh/mcp into Claude Desktop and your agent gets eleven tools to read meetings, generate briefs, and push outcomes to your CRM.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Product</category>
      <pubDate>Wed, 20 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why I built Briefi — five workspaces, one chair</title>
      <link>https://briefi.sh/blog/why-i-built-briefi</link>
      <guid isPermaLink="true">https://briefi.sh/blog/why-i-built-briefi</guid>
      <description>Nine months ago I was forty meetings behind on my own follow-ups. I built the loop I wished existed and shipped it to my own calendar before I shipped it to anyone else.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Inside Briefi</category>
      <pubDate>Mon, 18 May 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What a weekly review actually looks like across five workspaces</title>
      <link>https://briefi.sh/blog/what-a-weekly-review-actually-looks-like</link>
      <guid isPermaLink="true">https://briefi.sh/blog/what-a-weekly-review-actually-looks-like</guid>
      <description>A walk-through of the Monday-morning ritual that runs five workspaces in twenty minutes — and why I rebuilt it after three years of doing it wrong.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Field notes</category>
      <pubDate>Tue, 28 Apr 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why discovery guides beat checklists for sales conversations</title>
      <link>https://briefi.sh/blog/why-discovery-guides-beat-checklists</link>
      <guid isPermaLink="true">https://briefi.sh/blog/why-discovery-guides-beat-checklists</guid>
      <description>After 200 sales calls I stopped using a checklist and started using a guide with rationale. Close rate went up by about a third. Here&apos;s what changed.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Operators</category>
      <pubDate>Tue, 21 Apr 2026 23:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Multi-workspace is not multi-tenancy (and why operators care about the difference)</title>
      <link>https://briefi.sh/blog/multi-workspace-is-not-multi-tenancy</link>
      <guid isPermaLink="true">https://briefi.sh/blog/multi-workspace-is-not-multi-tenancy</guid>
      <description>A quiet pattern Briefi got right that most CRMs got wrong: separation of data, not separation of accounts. The architecture behind a single login that supports five distinct working lives.</description>
      <author>hello@briefi.sh (Briefi)</author>
      <category>Inside Briefi</category>
      <pubDate>Tue, 14 Apr 2026 23:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
