<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Malek Damiri</title>
    <description>Head of Revenue Operations, based in Atlanta, Georgia. I work on revenue analytics, executive reporting, and the data infrastructure behind them, and I write about it at malekdamiri.com.</description>
    <link>https://speakerdeck.com/malekdamiri</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/malekdamiri.rss"/>
    <lastBuildDate>2026-10-05 16:10:21 -0400</lastBuildDate>
    <item>
      <title>Revenue reconciliation: a practical operating model for finance and sales, by Malek Damiri</title>
      <description>Finance, sales, and analytics each report a different revenue number, and usually none of them is wrong. This deck lays out an operating model for reconciling them: what each system is authoritative for, who owns each number, a monthly cadence tied to the close, tolerance thresholds, and default answers for timing, scope, and identity disputes. Condensed from the essay by Malek Damiri at https://malekdamiri.com/writing/revenue-reconciliation-operating-model/</description>
      <media:content url="https://files.speakerdeck.com/presentations/e9ca3e6a169f4049ace22a3239add0f1/preview_slide_0.jpg?40800256" type="image/jpeg" medium="image"/>
      <content:encoded>Finance, sales, and analytics each report a different revenue number, and usually none of them is wrong. This deck lays out an operating model for reconciling them: what each system is authoritative for, who owns each number, a monthly cadence tied to the close, tolerance thresholds, and default answers for timing, scope, and identity disputes. Condensed from the essay by Malek Damiri at https://malekdamiri.com/writing/revenue-reconciliation-operating-model/</content:encoded>
      <pubDate>Mon, 05 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/malekdamiri/revenue-reconciliation-a-practical-operating-model-for-finance-and-sales-by-malek-damiri</link>
      <guid>https://speakerdeck.com/malekdamiri/revenue-reconciliation-a-practical-operating-model-for-finance-and-sales-by-malek-damiri</guid>
    </item>
    <item>
      <title>The RevOps metric dictionary, by Malek Damiri</title>
      <description>Every company has a metric dictionary, and in most of them it lives in people's heads, in the SQL behind the dashboards, and in the slide where a number was last explained. This deck covers how to write it down: the eight fields each entry needs, example entries for bookings, recognized revenue, and active customer, source-of-truth rules, and three habits that keep it current. Condensed from the essay by Malek Damiri at https://malekdamiri.com/writing/revops-metric-dictionary/</description>
      <media:content url="https://files.speakerdeck.com/presentations/54df73c3f9d5424682d37a796af5bcc1/preview_slide_0.jpg?40800241" type="image/jpeg" medium="image"/>
      <content:encoded>Every company has a metric dictionary, and in most of them it lives in people's heads, in the SQL behind the dashboards, and in the slide where a number was last explained. This deck covers how to write it down: the eight fields each entry needs, example entries for bookings, recognized revenue, and active customer, source-of-truth rules, and three habits that keep it current. Condensed from the essay by Malek Damiri at https://malekdamiri.com/writing/revops-metric-dictionary/</content:encoded>
      <pubDate>Mon, 05 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/malekdamiri/the-revops-metric-dictionary-by-malek-damiri</link>
      <guid>https://speakerdeck.com/malekdamiri/the-revops-metric-dictionary-by-malek-damiri</guid>
    </item>
  </channel>
</rss>
