<?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 Jeff Ignacio on Medium]]></title>
        <description><![CDATA[Stories by Jeff Ignacio on Medium]]></description>
        <link>https://medium.com/@jeffignacio?source=rss-4e644a4189db------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gAwFvn9kpRppfF0c.</url>
            <title>Stories by Jeff Ignacio on Medium</title>
            <link>https://medium.com/@jeffignacio?source=rss-4e644a4189db------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:06:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeffignacio/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[What is in a Revenue Operating Model?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/revops-impact-newsletter/what-is-in-a-revenue-operating-model-a30c3c619595?source=rss-4e644a4189db------2"><img src="https://cdn-images-1.medium.com/max/1456/0*q__m3rm4kLDDkNe-.png" width="1456"></a></p><p class="medium-feed-snippet">This article is for #startup operators, founders, and leaders. I&#x2019;ve lived this scenario out a few times. I relish the opportunity to work&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/revops-impact-newsletter/what-is-in-a-revenue-operating-model-a30c3c619595?source=rss-4e644a4189db------2">Continue reading on RevOps Impact Newsletter »</a></p></div>]]></description>
            <link>https://medium.com/revops-impact-newsletter/what-is-in-a-revenue-operating-model-a30c3c619595?source=rss-4e644a4189db------2</link>
            <guid isPermaLink="false">https://medium.com/p/a30c3c619595</guid>
            <category><![CDATA[annual-planning]]></category>
            <category><![CDATA[revenue-operations]]></category>
            <category><![CDATA[excel]]></category>
            <category><![CDATA[business-plan]]></category>
            <category><![CDATA[sales-planning]]></category>
            <dc:creator><![CDATA[Jeff Ignacio]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 03:26:32 GMT</pubDate>
            <atom:updated>2024-02-16T03:26:32.033Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Duct tape and Bubblegum: Simple Cohorts]]></title>
            <link>https://jeffignacio.medium.com/duct-tape-and-bubblegum-simple-cohorts-df9366bed863?source=rss-4e644a4189db------2</link>
            <guid isPermaLink="false">https://medium.com/p/df9366bed863</guid>
            <category><![CDATA[sales-operations]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[revenue-operations]]></category>
            <category><![CDATA[cohort-analysis]]></category>
            <dc:creator><![CDATA[Jeff Ignacio]]></dc:creator>
            <pubDate>Fri, 25 Dec 2020 00:52:41 GMT</pubDate>
            <atom:updated>2020-12-25T00:52:41.909Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a bit rusty with the tech skills. Time to brush up and flex a little to remind myself that we all started somewhere. I started with learning technical skills before climbing up the ladder.</p><p>There are some things you just cannot build within Salesforce. It’s maddening! It’s one of the reasons Tableau was acquired. The data visualization and business intelligence arms race continues.</p><p>So for those businesses earning $1M in ARR…</p><p>The founder is probably doing everything themselves.</p><p>I’m hopeful a series like this will be helpful to someone out there on operating on a shoestring budget.</p><p>We’re going to try to build an <strong>extremely</strong> simple cohort analysis using:</p><ul><li>PythonAnywhere.com</li><li>Google BigQuery</li><li>Google Data Studio</li></ul><p>Here’s what we’ll try to build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PLcNCstCOth_nH8_.png" /></figure><p><strong>First, set up your PythonAnywhere account</strong></p><ol><li><a href="https://www.pythonanywhere.com/?affiliate_id=001fd3a8">Sign up here</a>! Yes that’s a referral link.</li><li>Install the appropriate Python packages by clicking on the big blue button called <strong>BASH </strong>under the section titled <strong>NEW CONSOLE</strong></li><li>Type in the following commands to install the appropriate packages</li><li>pip3 install simple_salesforce</li><li>pip3 install pandas</li><li>pip3 install numpy</li></ol><p><strong>Second, set up your Google BigQuery account</strong></p><ol><li>Visit <a href="https://console.cloud.google.com/">https://console.cloud.google.com/</a></li><li>At the top you’ll see <strong>Google Cloud Console</strong> with a dropdown. Click on it and select “New Project”. This will create a new workspace to store your data tables.</li><li>You’ll need to create an access key for your PythonAnywhere account to access Google BigQuery</li><li>To the left, select <strong>Service Accounts</strong></li><li>Click <strong>Create Service Account</strong></li><li>Give them <strong>Project</strong>, <strong>Owner</strong> access (Viewer is also just fine)</li><li>Click <strong>Continue</strong></li><li>Click <strong>Done</strong></li><li>Now highlight over the newly created Service Account and click on it</li><li>Click <strong>Add Key</strong></li><li>Select <strong>JSON</strong></li><li>This will download a file</li></ol><p><strong>Third, go back to your Python Anywhere account</strong></p><ol><li>Create a new directory called <strong>Keys</strong></li><li>Upload your file into the newly created directory</li></ol><p><strong>Fourth, we’ll set up a simple CSV file</strong></p><ol><li>Create a csv file with the following columns: Customer ID, Amount, First Order Date, Last Order Date</li><li>OR use this <a href="https://drive.google.com/file/d/1m1xhtztOlvG-qo-NqVy5sIf2gAo_WlOh/view?usp=sharing">sample file</a> I’ve created for you</li><li>Prepping the data (CSV sample). Download the file then upload it into your Python Anywhere file directory</li></ol><p><strong>Fifth, in Python Anywhere use this code:</strong></p><ol><li><a href="https://drive.google.com/file/d/1KsgfvwbspIPxW-wBr-3_JtLMLeZ9kUv7/view?usp=sharing">OR simply use the code in this file</a></li></ol><p><strong>Sixth, access Google Data Studio</strong></p><ol><li>Visit <a href="https://datastudio.google.com/">https://datastudio.google.com/</a></li><li>Create a report</li><li>Add the BigQuery table as a data source</li><li><a href="https://datastudio.google.com/u/1/reporting/412c54a2-8969-49f6-ad0d-a39224dca393/page/9kVuB">Set up your dashboard similar to this dashboard</a></li></ol><p>Hopefully this will set you up to creating a very basic cohort report in a cost effective fashion!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df9366bed863" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A few ideas around Sales Compensation]]></title>
            <link>https://jeffignacio.medium.com/a-few-ideas-around-sales-compensation-ddb5476f95e6?source=rss-4e644a4189db------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddb5476f95e6</guid>
            <category><![CDATA[sales-operations]]></category>
            <category><![CDATA[revenue-operations]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Jeff Ignacio]]></dc:creator>
            <pubDate>Mon, 07 Sep 2020 20:52:32 GMT</pubDate>
            <atom:updated>2020-09-07T20:52:32.359Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m releasing an article on <a href="http://www.saassales.io/">SaaSSales.io</a> in a week or two debating whether or not Revenue Operations, in all its varieties (Sales Ops, Marketing Ops, CXOps), should or should not be on a leveraged plan. Without recreating the article let’s just go over my general framework around compensation.</p><p>But first… why am I qualified to talk about this at all? It might help to break down the segments of my career where I touched on compensation. I was unsuccessful and successful in different sales roles. When I worked in commercial real estate I completely bombed. In fact, for an entire year I was on a 100% leveraged compensation plan. I did not successfully sell or represent a buyer with any properties that year.</p><p>Zilch. Nada. I had to be creative on how to generate income that year. Sidebar: I learned how to install open source software such as SugarCRM (my first exposure to CRM), Drupal, and WordPress for small businesses. That’s how I generated income that year. Who knew that years later that information systems experience would help me in RevOps.</p><p>Then I was an agency recruiter. Selling people their dreams jobs. This is where I succeeded! I focused on technical roles such as systems administrators, network engineers, solution architects, etc. I learned the surface of each and every one of those roles. I knew the certifications that were shortcuts for me to see if that person was uniquely qualified. The relationships I fostered with my candidates taught me the value of building relationships. They may not have bought from me then, but eventually they did. I loved working as a recruiter.</p><p>But then I went to get my MBA at the University of Michigan. I fostered dreams of working at a strategic consulting firm such as BCG or McKinsey. But I found myself at a great company called Intel. I was placed in their venture capital team, Intel Capital. My summer project focused on developing an M&amp;A strategy around media assets. Intel? The chip company? Going into media? Tech was blurring the lines between traditional industries and high technology. Even more so, Intel the hardware/chip company was trying to break into the software game.</p><p>After that I went to Google. I was in a Sales FP&amp;A role supporting the Americas, EMEA, and APAC. I supported over 200 sales reps selling horizontally across vertical product lines. Google Apps (if you remember Postini it was lumped in). Google Maps For Enterprise. Google Cloud. Chomebook. All of these products and services were sought after by up and coming companies looking to disrupt traditional technical architecture with lighter weight, remote cloud services. The division I worked for was a “startup” within a larger company.</p><p>Intel had near 75,000 employees compared to Google’s 40,000 employees. It felt like the pace of business went to warp speed for me. Hilariously, I ended up moving to a 1,500 employee company called Meltwater a few years later. I had no idea what warp speed meant. UpKeep, my current company, is around 100 employees. I still have no idea what warp speed is apparently.</p><p>Anyway.</p><p>At Google the comp plans featured multiple product buckets, overlays, overassignment, tiers, accelerators, decelerators, windfall policies. You name it. Plus it had to account for static FX rates.</p><p>There was no better place to cut my teeth into compensation.</p><p>Here’s how I see the elements of a comp plan. Everyone knows I love frameworks and mnemonics. So here’s one more for you. BOCAS! It means <em>mouth</em> in Spanish. So here is how I would grade comp plans broken down by elements.</p><ul><li><strong>B</strong>ehavior — Motivate and continually reinforce good behavior</li><li><strong>O</strong>utcomes — Clear relationship between outcomes and incentives</li><li><strong>C</strong>ulture — Develop and maintain cultural cohesiveness</li><li><strong>A</strong>lignment — Alignment with the overall business and GTM strategy</li><li><strong>S</strong>imple — Simple to understand and execute</li></ul><p>Now that we have our “rubric” or guiding principles let’s look at tactical execution.</p><p>Compensation design can look like this from a <strong>Process </strong>perspective.</p><ol><li>Define principles (see BOCAS above)</li><li>Align stakeholders</li><li><strong>Design. </strong>Design comp plan variations</li><li><strong>Test. </strong>Scenario plan by backtesting and extrapolating future results based on Plan</li><li>Confirm plans.</li><li>Signature collection.</li><li>Countersign and store with Finance, HR, and management hierarchy.</li></ol><p>Compensation execution should feature</p><ol><li>Established dispute resolution process</li><li>Period closing procedures</li><li>Calculation timeline, let’s say Business Day 3 through Business Day 5</li><li>Send out commission statements for feedback to AEs and Management</li><li>Build in buffer time for feedback: Business Day 6</li><li>Payroll submission: Business Day 7</li><li>Attainment reporting and publication: Business Day 8</li></ol><p>More things to think about:</p><ol><li>Type of plan: company bonus, Management by Objective (MBO), leveraged plan (commissions for example)</li><li>Leverage ratio: $100K base + $100K variable = 50/50 leverage. Lower ‘at risk’ roles could look more like 90/10</li><li>Overassignment: layer 1 board-to-management = 8–10%, layer 2 management-to-frontline = 8–10%. Therefore Board commit of $100M would have a layer 1 overassign of $110M, and $121M to the frontline rep</li><li>Expected Performance: In the example above to hit Board target we would need 83% average attainment ($100M / $121M)</li><li>Quota-to-OTE ratio: let’s say for example that we use a 5x ratio; in this example the OTE of $200K above would mean a $1,000,000 quota. Further yet the idea of a “coverage” ratio would call for 4x — 5x rolling pipeline to hit target ($4M to $5M at any one point in time).</li><li>Accelerators, some will use the term ‘kickers’</li><li>Tiers</li></ol><p>If done well you’re looking at calendar day 10 or 11 for statements issued, feedback incorporated, and payroll submission.</p><p>For those of you who are in the compensation game. I completely feel you! Reach out if you ever want to talk.</p><p><strong>More musings</strong> at <a href="http://www.revengine.substack.com/">http://www.revengine.substack.com</a></p><p><strong>Follow me on LinkedIn</strong>: <a href="http://www.linkedin.com/in/jeffbethechange">www.linkedin.com/in/jeffbethechange</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddb5476f95e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>