<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Beevyl — Blog</title>
    <link>https://www.beevyl.com/blog</link>
    <atom:link href="https://www.beevyl.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Essays on the work between two companies — handoffs, blockers, decisions, and what a neutral system of record changes.</description>
    <language>en</language>
    <item>
      <title>The bus factor is two</title>
      <link>https://www.beevyl.com/blog/the-bus-factor-is-two</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/the-bus-factor-is-two</guid>
      <description>Six weeks in, every joint project runs on two people — one on each side. Everything that matters is in their heads, and neither company has a copy.</description>
      <category>Product</category>
      <pubDate>Sat, 08 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Scope arguments are memory arguments</title>
      <link>https://www.beevyl.com/blog/scope-arguments-are-memory-arguments</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/scope-arguments-are-memory-arguments</guid>
      <description>Nearly every dispute between two companies about what was agreed is a dispute about a record that was never written. By the time money is involved, both sides remember honestly — and differently.</description>
      <category>Perspective</category>
      <pubDate>Thu, 06 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Two plans and a slide</title>
      <link>https://www.beevyl.com/blog/two-plans-and-a-slide</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/two-plans-and-a-slide</guid>
      <description>Each company plans in its own tool. The joint plan is a slide, and it's wrong by Wednesday. The dates that slip are almost always the handful of dependencies that cross the line.</description>
      <category>Design</category>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The status call is a symptom</title>
      <link>https://www.beevyl.com/blog/the-status-call-is-a-symptom</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/the-status-call-is-a-symptom</guid>
      <description>Every joint project between two companies grows a recurring call whose real job is to reconstruct what happened. That's a storage problem being solved with attendance.</description>
      <category>Perspective</category>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Unlimited people is the point</title>
      <link>https://www.beevyl.com/blog/unlimited-people-is-the-point</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/unlimited-people-is-the-point</guid>
      <description>Per-seat pricing makes every collaborator a cost. Beevyl prices per active workspace — unlimited people on both sides, and the invited company never pays.</description>
      <category>Pricing</category>
      <pubDate>Sun, 26 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The art of ending well</title>
      <link>https://www.beevyl.com/blog/the-art-of-ending-well</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/the-art-of-ending-well</guid>
      <description>Collaboration software never wants your project to end. Beevyl treats the wind-down as a feature — and stops charging when the work stops.</description>
      <category>Product</category>
      <pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Escalation without villains</title>
      <link>https://www.beevyl.com/blog/escalation-without-villains</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/escalation-without-villains</guid>
      <description>When two companies share no manager, every escalation is a social risk. Beevyl makes it mechanical: visible clocks and blockers that escalate themselves.</description>
      <category>Perspective</category>
      <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Handoffs deserve to be objects</title>
      <link>https://www.beevyl.com/blog/handoffs-deserve-to-be-objects</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/handoffs-deserve-to-be-objects</guid>
      <description>Why the handoff, not the task, is the atomic unit of cross-company work — and what changes when it gets acceptance criteria, a lifecycle, and clocks.</description>
      <category>Design</category>
      <pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The joint layer</title>
      <link>https://www.beevyl.com/blog/the-joint-layer</link>
      <guid isPermaLink="true">https://www.beevyl.com/blog/the-joint-layer</guid>
      <description>Why work between two companies falls into email and memory — and why the joint layer needs its own neutral system of record, owned by neither side.</description>
      <category>Manifesto</category>
      <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
