<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ahin on Medium]]></title>
        <description><![CDATA[Stories by Ahin on Medium]]></description>
        <link>https://medium.com/@Ahin?source=rss-2d60810a4425------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Q-475drwuaFCwfsQ.jpg</url>
            <title>Stories by Ahin on Medium</title>
            <link>https://medium.com/@Ahin?source=rss-2d60810a4425------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:33:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Ahin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Business Runner’s Guide to Rev Ops]]></title>
            <link>https://medium.com/@Ahin/revenue-operations-c38428f6160b?source=rss-2d60810a4425------2</link>
            <guid isPermaLink="false">https://medium.com/p/c38428f6160b</guid>
            <category><![CDATA[revenue-operations]]></category>
            <category><![CDATA[sales-operations]]></category>
            <category><![CDATA[marketing-operations]]></category>
            <category><![CDATA[saas-go-to-market]]></category>
            <category><![CDATA[go-to-market-strategy]]></category>
            <dc:creator><![CDATA[Ahin]]></dc:creator>
            <pubDate>Wed, 18 May 2022 21:49:48 GMT</pubDate>
            <atom:updated>2022-06-11T17:46:54.379Z</atom:updated>
            <content:encoded><![CDATA[<h4>Best Practices for Revenue Operations</h4><h3>The Business Runner’s Guide to Revenue Operations</h3><p>How to scale growth &amp; solve your analytics challenges</p><figure><img alt="A treasure map (metaphor for how Rev Ops can be the final piece to your business’ puzzle)" src="https://cdn-images-1.medium.com/max/1024/0*Pw3oPLvIFS7O4iW3" /><figcaption>Photo by <a href="https://unsplash.com/@depthcontroller?utm_source=medium&amp;utm_medium=referral">Nadjib BR</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>“That’s the holy grail.”</blockquote><blockquote>“Nah, it’s just Rev Ops.”</blockquote><p>This year, operators and investors have been struggling with any number of headwinds. One recurring topic has been ‘growth’ — the need to find and scale it. While the problems have been explored, not enough time has been spent understanding what’s replicable from the companies that have achieved escape velocity.</p><p>As the same conversation re-occurred for the umpteenth time with a friend, I decided to create this artifact on the topic of Revenue Operations.<a href="#a9c6">¹</a> My goal is to provide the foundational playbook of how great companies orchestrate a harmonious Go-To-Market. It’s not a ‘holy grail’, rather a deliberate and purposeful approach. I make no claim to any innovation in this approach — the folks that have ‘figured it out’ tend to have the same pattern. Given that, it ends up being an opinionated view based on how I’ve personally applied this “playbook” from industries ranging from cloud storage to frozen pizza.</p><p>Before going further, let me provide a table of contents for folks that are trying to reference specific sections.</p><p><strong>Table of Contents<br></strong>* <a href="#f637">What is Rev Ops?</a><br>* <a href="#7cef">A Cross Functional Discipline</a><br>* <a href="#60c4">Recommended Org Structure</a><br>* <a href="#e38c">Hiring Rev Ops (checklist)</a><br>* <a href="#3a1f">Key Tech Principles for Rev Operations</a><br>* <a href="#dcb7">The Systems Level View of an Aligned GTM</a><br>* <a href="#375c">The Holy Grail</a></p><p>This paper shares the best practices of Revenue Operations discipline. The term itself, “Rev Ops”, may be new to some — it’s primarily used in B2B context. But the problems Rev Ops addresses are universal:</p><ul><li><strong>“Growth” efforts aren’t leading to growth</strong>. A related side effect are the endless meetings regarding opaque return on marketing spend and intradepartmental squabbles on lead quality.</li><li><strong>Reports conflict and struggle to deliver actionable insights</strong>. Multiple systems house many dashboard with conflicting, incomplete information. As an example, Google Analytics defines “Revenue” as “$s from the initial transaction”; but Salesforce has it as ‘total dollars generated from Account X’. Tableau has might have an account level ARR projections but no knowledge of NRR. Multiple sources of truth lead to internal friction and paralysis (and exacerbated Finance teams).</li><li><strong>Scaled personalization of customer journeys are closer to alchemy than reality.</strong> Millions of dollars are spent on allegedly enabling technology (and the people to run the tech), but the customer experience gets increasingly <em>less</em> relevant as the company scales. Great stories focus on the ‘why’ not the ‘what’. But teams with impaired vision and blunted tools are reduced to communicating glorified functionality — they can’t express <em>why</em> Product X or Module Z solves the <em>customer’s </em>problem.</li></ul><p><strong><em>What is Rev Ops?<br></em></strong>Revenue Operations is the <em>strategic orchestration of</em> <em>Go-To-Market processes and technology</em>.</p><p><em>Strategic: </em>Too often, systems get in the way (or encumber) strategy. The best companies understand that strategy leads process / technology. Rev Ops is a trusted advisor to the other GTM leaders in defining and refining the strategy to make sure it’s clear and actionable. Among other things, Rev Ops brings to the table the art of the possible (here’s a way to structure a quicker test of your idea that will let us make the business case to scale).</p><p>With that strategy honed, Rev Ops then purposefully tunes the system for enablement.</p><p><em>Orchestration</em>: Making stuff do what it’s supposed to do. There are actually two critical concepts within the idea of <em>orchestration:</em></p><ul><li><em>Implementation:</em> Everything exists within a context. To <em>orchestrate</em> an ecosystem, component pieces must be placed within the ever-evolving constellation that exists for your given company.</li><li><em>Configuration: </em>Good intentions are not sufficient for flawless execution. From field definition, through workflows and syncs, your environment must be continually tuned to enable business strategy within your competitive market. This can take the form of ensuring that ‘strategy’ has been honed to the point of clarity. It also means that concepts are well documented and synced across systems (there should be one, and only one, definition of ‘Revenue’ in the systems).</li></ul><p><em>Processes &amp; Technology: </em>With the strategy well understood, and the tooling purposefully tuned, process and technology are then built up with the goal of removing as much friction as possible for the GTM team.</p><p><strong><em>A Cross Functional Discipline<br></em></strong>Rev Ops is an inherently cross function discipline that extends into:</p><ul><li><em>Marketing Operations (“Mktg Ops”)</em>: Marketing Technology (“MarTech”), Content Management, Ideal Customer Profile(s), Marketing strategy and the processes associated with generating Marketing Campaigns.</li><li><em>Sales Operations (“Sales Ops”)</em>: Sales Technology, Sales Motion(s), and the policies associated with Deal Support (discounts, quotes, etc).</li><li><em>Business Intelligence (“BI”)</em>: Data Governance, Data Engineering, and Analytics.</li><li><em>Forecasting</em>: Revenue, Headcount, and Marketing Spend.</li></ul><p>We’ll go into more detail in the section on <a href="#60c4">Recommended Org Structure</a>, but one of the biggest mistakes companies make is thinking the Sales Operations exist discreetly from Marketing Operations, At its core, Rev Ops = (Mktg Ops + Sales Ops).<a href="#8c21">²</a> Why push the two functions inside of Rev Ops? Because neither function, in isolation, can enable a business. In concert, they form your enabling infrastructure. The way to ‘glue’ Marketing &amp; Sales Ops is the Data Infrastructure (including Analytics), usually owned by BI.</p><p>One of the biggest secrets of Revenue Operations? It’s a <em>support</em> function that exists to enable the GTM strategy. The best Rev Ops leaders are thought partners for the Heads of Sales &amp; Marketing while understanding that GTM strategy comes first, tech/processes support the strategy.</p><p><strong><em>Recommended Org Structure<br></em></strong>When creating org structures, it’s best to make sure everyone is on the same page about what we’re trying to achieve. A synthesis of what’s been discussed above: Rev Ops is a support function intended to, among other things, transform GTM <em>effort</em> into coherent <em>strategy</em> that is then ruthlessly <em>executed</em>.</p><p>There are 3 different models — Centralized, Federated, and Hybrid — that are applicable.<a href="#56f1">³</a></p><figure><img alt="2x2 Matrix, “Efficiency” as the X, “Quality” as the Y. Centralized is upper right, Hybrid is middle, Federated is lower left." src="https://cdn-images-1.medium.com/max/494/1*o_dKYL9Yb4PVUq885BQ3pQ.jpeg" /><figcaption>There are different org structure options. But, assuming one can manage the human egos involved, Centralized emerges as the ideal.</figcaption></figure><p><em>Centralized (recommended)<br></em>In this model, Rev Ops is aligned under a single leader. The biggest strength of a Centralized approach is predictability in how things are defined (metrics, processes, and roles). The clear lines of accountability have the benefit of creating high quality control. Finally, it’s the most efficient in that role redundancy is low.</p><p>Every strategy has a weakness, be wary of one if you don’t understand it. In the Centralized approach, the GTM Functional Leaders lack direct control of the Operations. This is an ego problem that, while real, can be managed. We’ll explore how to minimize that problem after a quick exposition of the other structural options.</p><p><em>Federated<br></em>This approach pushes responsibility into all major functions. A Federated structure’s biggest strength is giving each function the most control over its direct responsibilities.</p><p>The biggest weakness of a Federated model is the lack of cohesion at hand off points (technical and process). In addition, the likelihood of role redundancy across the organization is high. That this is the favored structure of organizations struggling to scale their GTM is no coincidence.</p><p><em>Hybrid<br></em>With Centralized and Federated anchoring either end of a spectrum, sitting in the middle is the Hybrid organization. Here, functions and personnel that are core to a given team reside directly within that team; things that are common to the business are pulled into an umbrella “Rev Ops” organization.</p><p>While conceptually appealing, in practice, Hybrid organizations run the ‘worst of all worlds’ danger. The opportunity for risk of poor orchestration is high. Often, the Rev Ops team is reduced to a corporate ‘bad cop” function.</p><p><em>Recommendation: Centralized<br></em>To create an enabling, support function for the entire GTM team, the ideal model is Centralized. However, ideal in theory is different than ideal in practice.</p><p>So the next question: What’s the best way to ensure the Functional Leads get the support they need to they can stay focused on their core responsibilities?</p><p>The answer to that is less of a structure conversation than a personnel one. The best Rev Ops leaders embrace their support role. She is a ‘customer first’ sort of operator and appreciates the dynamics of her internal customers.</p><p>Yes, the Functional Leads lose some control over the non-core aspects of their departments. But, a Rev Ops leader that embraces the support and enablement ideals should overcome those objections in a well-run organization.</p><p>With that said, Rev Ops needs to report to somebody… and the CEO simply does not need more direct report. To solve for that, look at the background of your Rev Ops leader — she will have their roots either in Marketing or Sales. Given our goal of achieving organizational alignment, the route to success is to have the Rev Ops leader report to the Functional lead of her non-background function. A Rev Ops leader that came up in Marketing will be a strong proxy for Marketing needs and capabilities. Having her directly reporting to the Head of Sales is the best bet for organizational equilibrium. There is a burden then on the Head of Marketing in that Rev Ops is ‘dotted line’ into Marketing. However, with this example of Rev Ops having a natural Marketing tendency, The Head of Marketing is more likely to be satisfied with dotted line than the other way around.</p><p>Before moving on to how to hire for this role, a quick but important reminder that this is an intentionally opinionated piece. I have conviction that the Centralized model is ideal and have first hand experience addressing its inherent weaknesses (as well as those of the other models). But, importantly, without context, we’re simply playing the odds. Context can easily tilt the odds one way or another. As an example, if you have a technical culture with discipline around documentation, the weaknesses of the Hybrid model are minimized and the benefits of keeping support close to the Functional leads are accentuated. If you are a massive ($5B+) global enterprise, the weaknesses of the Centralized model are more potentially pronounced. Context matters.</p><p>Both to choose the right model and to make Rev Ops highly functional, choosing the right leader is essential. Rev Ops is not an academic pursuit — the best operators know how to parse the context and build the best solution for the identified challenge. How, then, does one find the right leader for the Rev Ops organization?</p><p><strong><em>Hiring Rev Ops (checklist)<br></em></strong>While your Rev Ops leader most likely has deeper roots in either Sales or Marketing, there are common traits among the best Rev Ops leaders:</p><ul><li><em>Lateral Thinking:</em> The complexity in Rev Ops arises as one tries to assemble a variety of commodity parts into a high performing race car that is to be driven on a track with unpredictable twists and turns. The race car you need is unlikely the to be the one built for the last company. ‘Lateral Thinking’ is the capacity to <em>creatively</em> problem solve (less out of the box, more realizing that there is no box).</li><li><em>Technologist:</em> Rev Ops is a technical job. While it is not about writing code, it does require applied engineering concepts. Rev Ops leaders help translate GTM wishes into technical requirements and act as the business primary for engineering.</li><li><em>Seasoned Operator:</em> At their core, Rev Ops leaders belong to the ‘get sh*t done’ community. The sports metaphor is a glue/great locker room person. As a seasoned operator, she understands that perfect is the enemy of the good. And, with the goal of being a force for <em>enablement, </em>she knows that speed matters… but at a fixed level of reliability.</li></ul><p>In hiring a Rev Ops leader, the best organizations create knowledge based tests to determine the applicant’s capacity within the discipline (not specific system expertise). While most organizations of scale will have systems in place, your goal is rarely to freeze your organization in stasis. Your Rev Ops leader needs to be adaptable to evolving circumstances and create high performing environments 6–12 months in advance of the business’ needs.</p><p>At Backblaze, we asked candidates how they would tackle a specific problem that was answerable by reading Hubspot’s knowledge base. We felt the right candidate, without Hubspot specific experience (but with requisite Martech expertise), would be able to answer the question in ~60 minutes. At least one person in the hiring process needs to be able to take the test and create an answer key. If you do not have that person in your organization, work with your board and network until you have the help to get it done correctly.</p><p>The leader we hired, Shannon, was a homerun. Interestingly, she misunderstood the question and got her answer completely wrong. But, from her response, it was clear that she excelled on the above desired dimensions. That she got the answer ‘wrong’ was secondary to being a great at her craft. The second validation point came when we explained to her the question was about x, not y. Her enthusiasm to give it another shot reinforced our impression of her. Her “redo”, once she understood the question, was better than the one in the answer key I had provided.<a href="#77ab">⁴</a></p><p><strong><em>Key Tech Principles for Rev Operations<br></em></strong>Traditional Rev Ops environments are idiosyncratic, monolithic things. There rarely exists a shared, documented understanding of these black boxes, but the radiating pain is acute.</p><p>Today’s Rev Ops leaders think about their technologies as a series of complementary, purpose built tools. This mindset borrows heavily from our Engineering counterparts- specifically, Service Oriented Architecture. The idea is to break down what you are trying to achieve into functions. Treat each of these functions as unique, re-usable tools.</p><p>As an example, your CRM system is probably a great fit for your sales team’s CRM needs. However, just because it’s a great CRM does not inherently translate to reporting (even though there is a fancy reporting module thrown in for ‘free’).</p><p>To be purposeful in your selection (and negotiations) necessitates having a honed understanding of the requirements of the GTM strategy, which is one of the reasons your Rev Ops leader needs to be a seasoned operator.</p><p>By breaking down the tech stack into complementary pieces, one moves from a ‘brain surgery’ type environment to one akin to legos — a set of tools that can be snapped together in a variety of configurations depending on what your trying to achieve (and, yes, extension packs can be acquired, if needed).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E3fYXiFuF3r0j0xS" /><figcaption>Photo by <a href="https://unsplash.com/@rhowerter?utm_source=medium&amp;utm_medium=referral">Ryan Howerter</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>.</figcaption></figure><p>Take another look at the lego record store. Fun, manageable, and I bet we could turn that thing into a disco in under an hour. Your tech stack is supposed to be a key piece of <em>enablement. </em>For far too many entities, it is a place of frustration.</p><p>Besides the joy that this evolved approach brings, there are other advantages:</p><ul><li><em>Reliability:</em> Accountability creates reliability. When it’s clear who or what is responsible for activity X, then you know where to test. And, when something involving X breaks, you know what part of the engine to go work on.</li><li><em>Reusability:</em> This area mostly relates to your data infrastructure &amp; governance. By approaching your stack as an interconnected system, one can create data definitions and re-use them (rather than error prone re-builds). This eliminates the “depends what you mean by revenue” response to a seemingly simple question. A tool like <a href="https://www.avo.app/">Avo</a> is ideal for governance of your data layer; a tool like <a href="https://www.castordoc.com/">Castor</a> has an exponential effect on your efforts to ‘democratize’ data within the organization by centralizing definitions of various data fields.</li><li><em>Resilient</em>: Within the GTM tech stack, no technology is permanent or canonical.<a href="#e38b">⁵</a> Legacy approaches to acquiring monolithic systems created vendor reliance/lock in. While migrations are never the goal, they are an omnipresent reality — your requirements evolve, your vendor gets acquired, emerging regulatory frameworks insist on throwing curve balls. A service level approach minimizes your dependence on external forces as you adapt to changing times. It creates a resilient platform that maximizes GTM ‘uptime’.</li></ul><p><strong><em>The Systems Level View of an Aligned GTM<br></em></strong>To demonstrate how all this gets put into action, let’s take a look at a system diagram.<a href="#dbd9">⁶</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eCeSrk3qdGGVIozvZq30RA.jpeg" /><figcaption>Diagram courtesy of Inclined. While the Applications outlined are common for a D2C context, the architecture is applicable across any transactional business. For full post on the Modern Data Stack, please <a href="https://medium.com/weareinclined/the-modern-data-stack-an-overview-7f4fcfb58355">read their post</a>.</figcaption></figure><p>As you can see, the majority of the real estate is taken up by the data tooling. That is purposeful. The systems for any given GTM function — Marketing, Sales, etc — are pieces of technology. Orchestrating them around a common view of a customer requires data to be consistent and meaningful.</p><p>The relative weighting of the diagram also accomplishes another qualitative goal — too often, a given function (Marketing) thinks it has primacy. The thinking is that us Marketers operate in a very complex environment — ad servers, analytics, marketing automation. The other teams (Sales) have ‘stuff’, but that stuff only comes into play after Marketing has brought the lead in. Therefore, Sales’ ‘stuff’ can be considered after Marketing is squared away.</p><p>While the jargon in this paper borrows heavily from B2B vocabulary, the concepts are applicable to any business that is trying to generate a transaction. In fact, the systems diagram of a modern data stack provided towards the end comes from a real life implementation for a pizza company.</p><p>The biggest impact for most organizations of the modern purposeful approach? A breaking down of Functional silos to create an orchestrated GTM. One tactical example of this is decreased reliance on tool to tool synching in favor of a purpose selected data pipelining tool (example <a href="https://segment.com/">Segment</a>, <a href="https://airbyte.com/">Airbyte</a>, etc). By being prescriptive in what carries data where, we not only greatly simplify changing tools in and out (legos!!!) but we also achieve the elusive ‘single source’ of truth for our data. And if our systems and teams all have the same truth, then they are more likely to act in harmony.</p><p><strong><em>The Holy Grail<br></em></strong>I’m as big of a fan of Indiana Jones as any other self-respecting child of the 80’s (and am quite good with anything Jay-Z/Justin Timberlake related). But I hope, if nothing else, the last 15 minutes of your life has eliminated the idea that great GTMs are some sort of mythical quest.</p><p>It’s just a down the middle business challenge of aligning teams, enabling folks to focus on their core responsibilities, and putting the customer first.</p><p>Great companies are fueled by high performing Revenue Operations — the <em>orchestration of</em> <em>Go-To-Market technology and processes</em>. The right leader to evolve your organization is a lateral thinking technologist and seasoned operator. That’s the sort of person that will knock down organizational silos and, in the process, <em>enable</em> your business’ strategy.</p><p>Thanks for taking the time to read! Please leave any feedback or followups in the comments and I’ll do my best to address them (or find someone who can!).</p><p><em>Footnotes</em></p><p>¹ This became particularly clear after a conversation with one of my favorite tech investors, Joanne from Turn/River. Thanks for the inspiration, Joanne! <a href="#6e46"><em>(back to article)</em></a></p><p>² A quick aside on ‘Growth’ teams — Some organizations, primarily within SaaS, have created a discreet group dedicated to ‘Growth’. Where that occurs, the organization is carving out pieces of Mktg Ops and Sales Ops and putting them within one team (usually under Marketing, Sales, or Product). While it’s a discreet team, the Technology and Processes of that team are not materially incremental to a more traditional org structure. In fact, it tends to create a 3rd silo to be managed. For simplicity, this paper keeps those component pieces within Marketing &amp; Sales. <a href="#eb37"><em>(back to article)</em></a></p><p>³ A tip of the cap to Summit Partners’ Peak Performance Team. A good chunk of the thinking in this paper comes from conversations with Kevin and Cody from Summit. And, specifically, the framework for organizational models specifically ̶s̶t̶e̶a̶l̶s borrows from work Kevin has done. <a href="#375b"><em>(back to article</em></a><em>)</em></p><p>⁴ A fact that Shannon has reminded me of on more than a few occasions. <a href="#2139">(back to article)</a></p><p>⁵ The possible exception here is Salesforce’s CRM, but that’s a debate for another time. <a href="#d2dc">(back to article)</a></p><p>⁶ My friends over at <a href="https://weareinclined.com/">Inclined</a> created that great diagram synthesizing the approach of the <a href="https://medium.com/weareinclined/the-modern-data-stack-an-overview-7f4fcfb58355">Modern Data Stack</a>. It is the fundamental architecture we implemented at Lou Malnati’s/Tastes of Chicago. While this specific stack was architected for a consumer facing business, the components are applicable to any business with transactions.<a href="#dcb7">(back to article)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c38428f6160b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>