<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>SkylerBuilds — Notes</title>
    <link>https://skylerbuilds.com</link>
    <description>Working notes from Skyler. Hospitality data, reservation economics, and notes from inside the work.</description>
    <language>en-us</language>
    <copyright>© 2026 Skyler</copyright>
    <managingEditor>hello@skylerbuilds.com (Skyler)</managingEditor>
    <webMaster>hello@skylerbuilds.com (Skyler)</webMaster>
    <category>Technology</category>
    <category>Hospitality</category>
    <category>Operations</category>
    <generator>SkylerBuilds.com</generator>
    <atom:link href="https://skylerbuilds.com/feed.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://skylerbuilds.com/plumb-mark.svg</url>
      <title>SkylerBuilds</title>
      <link>https://skylerbuilds.com</link>
    </image>

    <item>
      <title>The PREDICT framework: what most CRM teams get wrong about signal</title>
      <link>https://skylerbuilds.com/notes/predict</link>
      <guid isPermaLink="true">https://skylerbuilds.com/notes/predict</guid>
      <description>A seven-step framework for running data-driven CRM organizations, drawn from a decade across hospitality and restaurant brands. Pattern. Receipts. Edges. Drift. Intervention. Counter. Teach.</description>
      <category>Framework</category>
      <pubDate>Thu, 18 Jun 2026 12:00:00 GMT</pubDate>
      <author>hello@skylerbuilds.com (Skyler)</author>
    </item>

    <item>
      <title>Why no-show prediction is the hardest interesting problem in hospitality</title>
      <link>https://skylerbuilds.com/notes/no-show</link>
      <guid isPermaLink="true">https://skylerbuilds.com/notes/no-show</guid>
      <description>Six reasons why a problem that should be easy to solve has resisted thirty years of incremental improvement. Small data, dirty labels, asymmetric costs, political interventions, delayed feedback, and misaligned platform incentives.</description>
      <category>Hospitality</category>
      <pubDate>Thu, 18 Jun 2026 12:00:00 GMT</pubDate>
      <author>hello@skylerbuilds.com (Skyler)</author>
    </item>

    <item>
      <title>Operator and builder: how I think about being on both sides of the table</title>
      <link>https://skylerbuilds.com/notes/operator-builder</link>
      <guid isPermaLink="true">https://skylerbuilds.com/notes/operator-builder</guid>
      <description>A working theory on the rare and useful position of being both an operator and a builder. The two halves don't blend, they alternate. The operator side makes the builder side less stupid. The builder side makes the operator side less trapped.</description>
      <category>Practice</category>
      <pubDate>Thu, 18 Jun 2026 12:00:00 GMT</pubDate>
      <author>hello@skylerbuilds.com (Skyler)</author>
    </item>

    <item>
      <title>Reservation economics: why hospitality is missing a category that should already exist</title>
      <link>https://skylerbuilds.com/notes/reservation-economics</link>
      <guid isPermaLink="true">https://skylerbuilds.com/notes/reservation-economics</guid>
      <description>The reservation is a small economic contract, and hospitality has no software category for it. Naming the gap, and the three layers a real stack would need: prediction, intervention, and monitoring.</description>
      <category>Hospitality</category>
      <pubDate>Thu, 19 Jun 2026 12:00:00 GMT</pubDate>
      <author>hello@skylerbuilds.com (Skyler)</author>
    </item>
  </channel>
</rss>
