<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Revenue-Operations on Erik MacKinnon | AI-Native GTM Operator</title><link>https://erikmackinnon.com/tags/revenue-operations/</link><description>Recent content in Revenue-Operations on Erik MacKinnon | AI-Native GTM Operator</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 25 Apr 2026 18:50:04 +0000</lastBuildDate><atom:link href="https://erikmackinnon.com/tags/revenue-operations/feed.xml" rel="self" type="application/rss+xml"/><item><title>Your revenue team's tribal knowledge is about to become a huge liability</title><link>https://erikmackinnon.com/revenue-tribal-knowledge-liability/</link><pubDate>Sat, 25 Apr 2026 18:50:04 +0000</pubDate><guid>https://erikmackinnon.com/revenue-tribal-knowledge-liability/</guid><description>&lt;p&gt;The more I work to speed up Wynter&amp;rsquo;s GTM process, the more I realize it&amp;rsquo;s not ready for agents if it only exists in Slack, Notion, HubSpot, and people&amp;rsquo;s heads.&lt;/p&gt;
&lt;p&gt;Every revenue team needs a repo.&lt;/p&gt;
&lt;p&gt;Not necessarily a codebase.&lt;/p&gt;
&lt;p&gt;A repo in the operating sense: versioned, reviewed, testable, and clear enough that an agent can pick up a workflow without immediately making a mess.&lt;/p&gt;
&lt;p&gt;Engineers and developers learned this ages ago.&lt;/p&gt;</description></item></channel></rss>