<?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[Scale MRR - Medium]]></title>
        <description><![CDATA[Business  principles for API and Cloud Infrastructure Platforms - Medium]]></description>
        <link>https://medium.com/scale-mrr?source=rss----ee6d961f9437---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Scale MRR - Medium</title>
            <link>https://medium.com/scale-mrr?source=rss----ee6d961f9437---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:16:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/scale-mrr" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[‘Use Case’-ing]]></title>
            <link>https://medium.com/scale-mrr/use-case-ing-86b5bd0c9f99?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/86b5bd0c9f99</guid>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Thu, 29 Nov 2018 16:55:27 GMT</pubDate>
            <atom:updated>2018-11-29T16:55:26.598Z</atom:updated>
            <content:encoded><![CDATA[<h4>Marketing and Selling API’s Beyond Developers</h4><p>A major go to market challenge API and platform businesses face is how to market and sell to constituents who are not developers.</p><p>One approach that can work well is called ‘Use Case-ing’ — a technique to articulate and prioritize <strong>what </strong>businesses can build with your service, and <strong>why </strong>they are building it.</p><p>Done well, Use Case-ing can be used to create, execute, and measure a go to market strategy with clear buying personas, influencing personas, and value propositions.</p><p>Below is a framework that can be used in this process.</p><h3>Start with Existing Customers</h3><p>API and platform capabilities are by definition pieces of a broader application. The first step should be to classify the types of applications your current customers have built. As you do this, you’ll want to identify the following:</p><h4>What Apps Have been Built</h4><p>This should be the description of the applications that have been composed using your service. Ideally, it’s a non technical description — something an end user of an application can comprehend.</p><h4>Who Paid (or will Pay)</h4><p>You want to identify the role of the person or team who is footing the bill (or will foot the bill at scale). If it’s the developer that’s paying for it from their corporate card, don’t stop there. Explore the spend threshold at which some other team would need to get involved.</p><h4>Who Benefits</h4><p>Within your customer account — identify what departments, teams, and individuals are benefiting from the application that has been built. Go deep here, and be sure to identify all the teams that benefit. As with who paid (above), focus on job titles.</p><h4>Outcomes</h4><p>Surface the business outcomes that have been realized from the deployment of the application your service was used in — and try to carve out the specific part of that benefit your service drove. Specifically , try to understand what was being done before your service came into the picture, and what’s changed since your service was deployed.</p><p>One note — there is no shortcut to collecting this data. Your sales and customer success teams should be deeply engaged with your customers to surface this information directly from customers.</p><h3>Name The Use Case</h3><p>Common patterns will emerge as you look at the types of apps your current customers are building. All customers may not use the same words to identify a similar use case — so you’ll have to be a bit creative in pulling together a description that can be used. Name the use cases in play across your customer base, and choose your words carefully. The name of the use case will be central to your overall go to market messaging.</p><h3>Prioritize</h3><p>It’s unlikely you’ll be able to invest resources into every use case category you identify. You’ll want to go through a prioritization exercise to understand where to place your bets. Top down market sizing and bottoms up growth rates are a couple techniques you can use to help you prioritize.</p><h3>Execute and Measure</h3><p>With a prioritized set of use cases now in hand — you can begin to execute your demand gen and sales efforts against the buying personas, influencing personas using the value propositions you’ve identified through this process.</p><h3>Iterate</h3><p>The nature of a fast growing business is that use cases you focus on in one planning cycle may change as your business evolves. Thats Ok — go to market strategies can be a bit more agile that the underlying products you are building. As long if you have instrumented your business to measure inputs and outputs — the numbers will guide how you evolve the set of use cases you go to market with any given planning cycle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86b5bd0c9f99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/use-case-ing-86b5bd0c9f99">‘Use Case’-ing</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Land and Expand ]]></title>
            <link>https://medium.com/scale-mrr/land-and-expand-a58523a20e8?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/a58523a20e8</guid>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 16:18:24 GMT</pubDate>
            <atom:updated>2014-04-26T14:21:22.606Z</atom:updated>
            <content:encoded><![CDATA[<h4>Guidelines for Effective Bottoms-Up Selling </h4><p>Seed and Grow. Bottoms Up. Land and Expand.</p><p>These terms refer to the sales strategy that begins with one small win, followed by a sequence of efforts that expand revenue within an account.</p><p>In the early days of a SAAS business, top line growth may provide an illusion of land and expand working well.</p><p><strong>You won’t know for sure, however, until you define a sales framework to measure expansion into additional lines of business.</strong></p><p>Executing such a framework, at scale, requires a business to:</p><ul><li>Segment sales resources by landing and expanding efforts</li><li>Segment expansion by selling-across,selling-within, and selling-up</li></ul><p>Its worth looking at each half of land and expand in more depth.</p><h3>Landing</h3><p>In securing your initial win, speed is paramount. The sooner you can get to dollar one, the less friction you will have in pursuing a larger footprint within an account. Some principles for optimizing the landing:</p><h4><strong>Avoid Deal-Creep</strong></h4><p>In the early stages of a sales cycle, it can be easy to paint a broad picture of the dozen ways your technology can be used. It can be tempting to loop in additional groups across the business that may be interested in your product. It can be tempting to up-sell your feature set into areas beyond your prospects initial pain points.</p><p>Don’t do this. It will add complexity to your deal, while increasing risk to the larger opportunity.</p><p>Narrow in on a specific problem and do not rest until your customer is delighted with your solution. Map out the decision makers and influencers for the first win, and focus your efforts on this team.</p><h4><strong>Specialize Sales Teams</strong></h4><p>The sales motion of securing initial wins (new logos) is very different from the sales motion of expansion within accounts (existing logos).</p><p><em>New logo reps</em>, often called account executives, are adept at overcoming first-time customer hurdles. These center on proving company credibility, demonstrating the reliability of your technology, and working through red-lining of commercial terms.</p><p><em>Existing logo reps</em>, often called account managers, are focused on establishing longer term relationships with your install base. They should be adept at ensuring extremely high customer satisfaction — and<strong> </strong>understand how to navigate across an organization as they execute longer duration cross-sell and up-sell opportunities.</p><p>The incentive plans, and the candidate profile for each of these two selling motions will differ. Specializing teams will help you develop expertise, and iterate on sales processes tailored to the unique stages of you customer lifecycle.</p><h4>Specialize Playbook</h4><p>There are typically two opportunity profiles you’ll be pursuing, and segmenting your approach for each one will help you accelerate time to the first win.</p><p><em>Takeouts </em>are opportunities to displace a competitive solution already deployed at a prospect. These sales cycles focus on educating and proving <em>why</em> <em>you have the better platform, and why you are the better vendor. </em>Budget already exists for these opportunities, and your goal is to transfer this revenue stream.</p><p><em>Greenfield</em> opportunities focus on educating prospects <em>why your technology solves a business problem they don’t have a solution for.</em><strong><em> </em></strong>Your sales motion will focus on the problem domain itself, and building a business case for why a solution is needed.<strong> </strong>Budget may not exist upfront, but if you build a compelling enough business case with a high enough sponsor, budgets can often be found.</p><p>Identifying the type of opportunity you are pursuing, and customizing your sales playbook to the profile will allow you to accelerate the time to landing.</p><h3><strong>Expanding</strong></h3><p>The average life time value (LTV) of your customer base should be growing. Three techniques to accomplish this, each of which should be measured independently: <em>Selling-Across, Selling-Within, and Selling-Up.</em></p><h4><strong>Selling-Across</strong></h4><p>Larger businesses have multiple functional departments (i.e. Finance,Sales, Marketing) and multiple business units (i.e Software, Hardware, Services). Your cross-sell strategy should systematically track progress across each across these departments within an account.</p><p><em>Functional Cross Sell:</em> Seek out functional teams across the org that are similar to your landing team. Your landing business case has a high probability of resonating with these groups. Assume, for example, your first win was the Sales team of Acme Co’s Software business. Pursuing all Sales teams across the organization is your next step. Ask your landing sponsor for warm referrals into these groups.</p><p><em>Departmental Cross Sell: </em>If your technology is horizontally applicable (i.e. file sharing), you’ll have an opportunity to expand to other functional teams within the landing business unit. Going back to Acme Co — you’ll want to prioritize all departments within the Software Business Unit who could leverage your tool. Once again, seek the assistance of your landing sponsor for warm intros to these teams.</p><h4><strong>Selling-Within</strong></h4><p>There is enormous opportunity to expand revenue within your initial landing group. Two paths to consider:</p><p><em>Up- Sell : </em>Expedience in the pursuit of the initial landing likely led to a baseline roll-out of your technology. There will be additional features your customers have not yet adopted . Prioritize your ongoing education and enablement activities on how these new features can enhance the value of the initial implementation.</p><p><em>Organic Growth: </em>Many of your customers will growing fast— and will naturally use more of your product as their business expands. If your landing department’s sales team doubles, for example, your license revenue will follow a similar path. This can be a great sign of an excellent product, solid account management, and great customer service. It’s not, however, a metric of how well you’re expanding across an account.</p><p>Distinguishing between organic growth and up-sell growth is critical as you measure the results of your cross-selling activities. Some business will customize incentives around organic growth vs. cross-sell to optimize account management investments.</p><h4><strong>Selling-Up</strong></h4><p>Once you have at least one business unit on your platform, you’ll be in a position to explore and accelerate a corporate wide standard. This can take many forms. One structure is the ‘site-wide’ license. This is often accompanied by a top down mandate of your technology becoming the corporate standard for your category. The details of this deal type will vary, but a couple high level points to keep in mind:</p><p><em>Start High. </em>Identify the highest ranking role within the account who would be interested in your domain, typically C-level (and often CIO’s). Educate them on how your technology is being used within the organization, and explore how they see your tool fitting in the longer term vision of their company’s IT strategy. You will also want to learn what process they have in place for becoming a corporate wide ‘blessed’ tool . Your goal is to gain this individuals trust, and have them champion your growth across the business over time.</p><p><em>Play the Long Game. </em>Selling-Up should happen in parallel to your selling-across activities. Top down sales cycles for large organizations can often exceed 12 months, even in the best case. The advantage of having a bottoms up playbook is you can pursue new revenue opportunities as the longer term scenario plays out. Approach the top-down process with a long term horizon, but don’t let it slow down your cross-selling efforts across the lines of business for shorter term wins.</p><h3>Execute. Measure. Iterate.</h3><p>As with any business strategy, the most difficult part is execution. Land and Expand is no different.</p><p>Once you’ve defined your expansion framework, invest upfront in the tools to measure how well you’re doing against plan. Establish a regular cadence to review whats working well , and remain flexible to adjust as you learn more about the business.</p><p>Do this well, and you’ll have sales levers to keep your customers happy, while growing the average life time value of your customer base to it’s full potential.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a58523a20e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/land-and-expand-a58523a20e8">Land and Expand </a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The New Rules of Developer Sales]]></title>
            <link>https://medium.com/scale-mrr/the-new-rules-of-developer-sales-8e86e58fc853?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/8e86e58fc853</guid>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 16:18:02 GMT</pubDate>
            <atom:updated>2014-03-20T14:54:23.247Z</atom:updated>
            <content:encoded><![CDATA[<h4>Modern Sales Principles  for Developer-First Platforms</h4><p>Developers hate being sold to.</p><p>Traditional sales paradigms are intentionally opaque, mired in friction and non-customer aligned incentives. Contrast this to common developer principles of transparency, ease of use, and doing (vs. talking) — and the animosity is easily understood.</p><p>Self-service, pay-as-you-go business models have emerged as the de-facto standard for developer platforms. Companies like AWS, Heroku, Twilio, and Stripe are leading examples of this. These platforms are also fueling the rise of developer influence in purchasing decisions, revealing a new path into enterprise IT budgets.</p><p>In this context, it’s fair to ask: Is Self-Service alone a sufficient sales strategy?</p><p>The simple answer is no.</p><p>An intelligent and developer-focused sales strategy is essential to:</p><ul><li><strong>Successfully onboard new prospects</strong></li><li><strong>Ensure long term customer success</strong></li><li><strong>Deliberately pursue untapped opportunities</strong></li></ul><p>So how does one design a sales strategy that developers won’t hate?</p><h4><strong>1. Embrace Self-Service</strong></h4><p>In a world where prospects can learn about, evaluate, and eventually deploy your platform without intervention, a sales team’s responsibility is to focus on adding value beyond the self-serve offering.</p><p>This value comes in many forms:</p><p><em>Business Advisor. </em>Understanding the business problem a prospect is looking to address, providing education on how similar customers have approached the problem, and building a tailored business case for the challenge at hand.</p><p><em>Technical Advisor. </em>Once a business problem has been identified, helping prospects think about implementation strategies, relevant best practices, and how to make efficient use of the platform and its array of features.</p><p><em>Organization Advocate. </em>Prospects will inevitably have rigid procurement processes, legal requirements, and payment preferences (among other things) that will not map directly to your self-serve model. Your sales team needs to educate prospects about the benefits of your business model, while always considering the fastest way to onboard a specific customer. In some instances, this may require flexibility on your side, i.e. working through a custom contract to meet a unique procurement need.</p><p><strong>Not all customers will need this level of engagement. And that’s the point.</strong></p><p>Don’t add friction to the selling process when unnecessary. Implement a sales process that can intelligently engage prospects, with the right resources, at the appropriate stage of their evaluation cycle.</p><h4><strong>2. Align Sales Process to Customer View of Success</strong></h4><p>In traditional software license models, vendors earn revenue when customers <em>select </em>a product . They pay up front, at contract signature, regardless of the project’s ultimate success. With pay-per use , vendors book revenue only when customers s<em>uccessfully use a product. </em>This requires re-evaluating key aspects of the traditional sales process:</p><p><em>Incentive Plans: </em>Pay-as-you-go forces sales teams to focus on opportunities that provide <strong>tangible and recurring benefits </strong>for a customer. Take for example the scenario where a sales rep over-sells a solution early in the sales cycle. Even if the customer chooses the technology — there will still be no revenue to recognize if the project fails to gain traction. Another reality is most production applications gradually ramp into their expected steady state volume. Appropriately incenting that early revenue traction, at the inflection point where you know it will drive a long-term successful customer, is what you want to point your sales team towards.</p><p><em>Sales Stages. </em>Creating a sales methodology that closely mirrors a software development lifecycle is critical- once again because no revenue will be recognized unless an application <em>successfully</em> launches. Clear entry and exit criteria at the <strong>analysis, design, pilot, development, and launch phases of a project </strong>will help you deploy the appropriate sales resources to help customers evaluate, choose, and successfully use your technology.</p><p><em>Continuous Improvement. </em>To ensure you are helping customers progress in their evaluation as efficiently as possible, you will want to measure how you are executing on key metrics within each stage of your sales cycle( i.e. sales cycle duration, time to revenue ramp, etc.). This will provide you a framework to understand which areas you can tweak to improve the efficacy of your sales program.</p><h4><strong>3. Build Sales Teams with Developer-Aligned Competencies</strong></h4><p>Perhaps the most important component in creating an effective developer-focused sales strategy comes from hiring sales professionals who understand how to work with developers. Some important attributes I’ve seen in successful reps over the years:</p><p><em>Curiosity. </em>The skill of asking good questions and being able to deeply understand problems prospects are exploring. Also, in hyper-growth markets, it’s likely that your sales team will be expanding into new market segments rapidly. The ability of your team to pattern-match and <em>quickly </em>draw analogies across new customer profiles will be important.</p><p><em>Ability to Teach. </em>Educating a prospect on how your technology can be used in their business context—and articulating why your platform uniquely solves their problems . Teaching is half of the selling process. In the platform business, this is need is exaggerated by the freedom customers are afforded when applying your technology.</p><p><em>Ability to Problem Solve. </em>Customer environments (across technical, business, &amp; political landscapes) and competitive mix (between traditional vendors and new entrants) are constantly in flux. The playbook on how to solve a specific problem in the sales process will often not be written. Reps who can embrace this ambiguity and proactively solve problems for their customers will succeed.</p><p><em>Drive to Help Customers Succeed. </em>The desire to help customers solve real business problems, while laying the foundation for a long term business relationship. Also having the fortitude to overcome technical and business challenges/objections that are inevitable in any complex sale.</p><h4><strong>4. Embrace Seed and Grow</strong></h4><p>In 2007, a Fortune 500 CIO asked me to keep him updated as new developer accounts were created within his company. While it was still early days of self-service APIs — it was a sign of the increasing decentralization we see today. Individuals within lines-of-business are able to operate much more autonomously from central IT than ever before. Optimizing for this has some important considerations:</p><p><em>Address Immediate Pain. </em>Individual business units will often come across tactical challenges that haven’t been specifically budgeted — but are critical to overcome in a short period of time. Developers will often take on these tasks, seeking creative solutions. This provides a unique entry point for you to solve a high priority problem.</p><p><em>Less Red Tape. </em>With a top down sales process , there will be multiple levels of bureaucracy to navigate, with an evaluation process than can often take a year (or longer). In contrast, a bottoms up approach will involve fewer decision makers and influencers. Just as important — lines of business will often have a greater urgency to address problems, which can facilitate a shorter sales cycle.</p><p><em>Built Trust &amp; Expand. </em>There is no better reference than an internal advocate within an organization. By addressing a need for one business unit, and executing well, you will be in a position of credibility when you seek to expand across the business. Once you are in multiple business units, a top down roll out becomes becomes much simpler.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e86e58fc853" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/the-new-rules-of-developer-sales-8e86e58fc853">The New Rules of Developer Sales</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rise of the Developer]]></title>
            <link>https://medium.com/scale-mrr/rise-of-the-developer-1bed7e518066?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/1bed7e518066</guid>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 16:17:41 GMT</pubDate>
            <atom:updated>2014-04-19T13:34:34.978Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why The Enterprise Sales Game is Changing</h4><p>We are witnessing a significant paradigm shift in how businesses evaluate and buy technology.</p><p>Influence, clout, and authority for technology purchases, which have long been shifting from IT to Line of Business (thanks to SAAS) , are <strong>now shifting to developers.</strong></p><p>Entire technology categories are being disrupted by the rapid rise of developer focused platforms. Some examples:</p><ul><li>Datacenter via <em>Amazon Web Services</em></li><li>Communications via <em>Twilio</em></li><li>Payments via <em>Stripe</em></li><li>Email via <em>Sendgrid</em></li><li>Shipping via <em>EasyPost</em></li><li>Mobile Middleware via <em>Firebase</em></li></ul><p>These developer centric businesses are characterized by three key attributes:</p><ol><li>Cloud API’s</li><li>Self-Service</li><li>Pay-per-Use</li></ol><p>The question is — how are these simple axioms changing the landscape of how enterprise IT decisions are made?</p><h4><strong>Cloud API’s empower developers with capabilities historically reserved for central IT</strong></h4><p>Simple API’s, that abstract highly complex and arcane technology stacks, allow developers to tap into domain areas previously unimaginable — <em>all while</em> <em>using their existing skill sets. </em>And by virtue of being in the cloud, there are no physical constraints to access. Take a typical .Net web developer, for example, who is looking to customize payment and shipping workflows of his e-commerce application. Historically, he might defer to central IT and procurement to explore possibilities, as these are areas outside his core expertise (web development). Today, however, he can tap into API services like Stripe (for payments) and EasyPost (for shipping), without having to become an expert on any one of those domain areas (he only needs to know how to access an API).</p><p><em>The availability of previously arcane technology stacks, via simple API’s,are fueling the rising influence of developers in the enterprise.</em></p><h4><strong>Self-Service expedites and decentralizes evaluation</strong></h4><p>Today, enterprises complete on average 60% of the technology evaluation process before engaging a vendors sales team. Self-Service business models are pushing this number even higher. Through<em> hyper transparency </em>on pricing, documentation, commercial terms— <em>and instant access to product</em> — developers are able to thoroughly vet a vendor’s ability to meet their needs before engaging internal IT, or their external vendors sales team. Jeff Bezos said it best:</p><blockquote><em>“When a platform is self-service, even the improbable ideas can get tried, because there’s no expert gatekeeper ready to say ‘that will never work!’ And guess what—many of those improbable ideas do work, Allowing customers and prospects to immediately access value.</em></blockquote><p><em>The ability to understand and vet the full economic, technical, and commercial scope of a vendor’s solution, with no friction, is fueling the rising influence of developers in the enterprise</em></p><h4><strong>Pay- Per- Use eliminates capital expense risk</strong></h4><p>By transferring traditionally large cap-ex budgets to op-ex, with no contractual lock in required, developers are easily able to justify the cost of experimentation. When use cases move from pilot into production — the ability to map IT spend as a variable expense to the real time needs of a business has added benefits (lower average cost over the course of a business with natural ebbs and flows).</p><p><em>Reducing the business and financial risk of experimentation frees developers to explore new initiatives and ideas, easily.</em></p><p>As ‘Software eats the world’, developers will have a much larger influence on technology decisions made within businesses.</p><p>We are still in the early phases of this transition — but what’s clear is enterprise technology companies should be thinking through how this shift will impact their product, go to market, and sales strategies in the coming years.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bed7e518066" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/rise-of-the-developer-1bed7e518066">Rise of the Developer</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SKU to Scale]]></title>
            <link>https://medium.com/scale-mrr/sku-to-scale-aab62d64661c?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/aab62d64661c</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 16:16:07 GMT</pubDate>
            <atom:updated>2018-12-04T04:47:33.236Z</atom:updated>
            <content:encoded><![CDATA[<h4>Accelerating Growth Past $100M</h4><p>Once you’ve found your core product market fit, many of your go to market investments will center on incremental verticals, geographies, and customer segments to attack.</p><p>The best platforms don’t stop here. They focus on creating new capabilities existing customers can easily adopt, and just as important, purchase.</p><p>The process of building new capabilities customers will (a) use and (b) pay for is process I like to call SKU to Scale.</p><p>Doing this well can result in a business maintaining (or accelerating) growth rates into and beyond $100M arr.</p><p><strong>Product + Sales Balance</strong></p><p>There needs to be tight alignment in planning and execution between sales and product. This will ensure product is building what sales believes (and ideally private beta customers prove) can be monetized.</p><p>Obviously not everything in your road map should be SKU’d. It is, as with many early investments in a business, more art than science. There is a framework that I’ve used that can drive focus to the process: Vertical and Horizontal SKU’s.</p><p><strong>Vertical SKUs: Premium Features</strong></p><p>This is the notion of adding a deeper set of features on top of a core product. If you have a healthy feedback loop from customers, the list of possibilities here is typically long. Further, in a world where your core product competes on price — these premium features can be a critical driver of higher margin revenue. Of course, not all new capabilities should be charged for. Customer retention and competitive differentiation are a couple reasons you may not want to sku a feature. The decision will ultimately be determined by customer feedback, competitive context, and cost considerations.</p><p><strong>Horizontal SKU’s: Adjacent Products</strong></p><p>By virtue of solving a core problem with your primary product, you’ve established a level of expertise, technical know how, and market insights that should make it easier to expand into adjacent categories. Salesforce has done this well. Over the last decade have expanded from what was originally Sales Cloud to now Marketing Cloud, Service Cloud, and Communities Cloud (to name a few).</p><p>Buyers and end users in adjacent categories will likely vary, but you have many advantages from your core product traction. On the technical side — you have core product capabilities and data insights that can be leveraged to accelerate such a move. On the business side, you are a trusted brand and have commercial relationships already in place to further ease horizontal expansion.</p><p><strong>Execution: Incent Customer Success\Sales Teams</strong></p><p>Getting to the point of launching new SKU’s is half of the equation. To fully execute this strategy — you’ll need to ensure your sales and customer success org is appropriately motivated and held accountable to drive the adoption of these new capabilities within their accounts.</p><p>One way to do this is by overweighting incentives and goals towards these new capabilities. You may be paying higher commission rate for these new SKU’s — but the benefits of an accelerated growth rate, increased competitive differentiation, and ‘stickier’ customers can often be well worth the price.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aab62d64661c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/sku-to-scale-aab62d64661c">SKU to Scale</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pricing Principles]]></title>
            <link>https://medium.com/scale-mrr/pricing-principles-26b7e58ff73a?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/26b7e58ff73a</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Thu, 25 Oct 2018 20:40:56 GMT</pubDate>
            <atom:updated>2018-11-25T22:20:57.968Z</atom:updated>
            <content:encoded><![CDATA[<p>Pricing plans have significant implications for all aspects of your go to market strategy.</p><p>It will influence how prospects perceive your value, how efficiently you can acquire new leads\customers, how sales teams run their deals, and the cash flow of your business — just to name a few.</p><p>This post unpacks some of the critical topics when thinking through a pricing strategy:</p><h4>Transparency</h4><p>It’s amazing to me how much business will invest in deep content around a product highlighting the simplicity, short time to value, and ease of use — and then require a prospect to schedule a 30 minute call with the sales team to understand the cost of their solution.</p><p>While this approach may allow your sales team to maximize the deal size for a single opportunity — it can hurt a business in three ways:</p><ul><li>You will introduce friction to the SMB, Mid Market, and departmental Enterprise prospects who want to move quick.</li><li>Your Product and on-boarding experience will suffer as fewer customers come through low touch channels (you’ll soon ignore optimizing this funnel).</li><li>It’ll create an environment where too many deals are dependent on custom pricing processes — which is difficult to scale.</li></ul><blockquote>The best performing cloud businesses focus on ease of customer adoption and low cost of customer acquisition. Pricing transparency plays an important role towards these ends.</blockquote><p>This doesn’t mean one should be transparent with all pricing plans — it is important to have a call out for ‘enterprise’ or for the small segment of larger customers who will require pricing that may not make sense for the vast majority of your customer base.</p><p>The one caveat for this approach is a new product\service\feature that has zero customers. In this scenario, I’d recommend launching it as a ‘public limited beta’ — with no public pricing. This will allow you to begin the critical customer feedback loop on what type of pricing makes sense. Once you’ve validated with 5–10 paying customers — then launch a version publicly.</p><h4>Consumption and Utility Pricing</h4><p>‘Seat’ based pricing models are common SAAS pricing plans. The benefits of this model are simplicity, and makes a lot of sense for end user heavy applications.</p><p>The downside of these types of models is that your upside is not directly correlated to business outcomes of your customer. Head count, for example, rarely grows at the same pace of your customers business , which will mute your long term expansion rates relative to a consumption based model.</p><p>For platform businesses — I highly recommend a structure where billable event is tied directly to a usage metric of your service. These range from events which drive your cost (i.e. storage fees) to events that drive the business outcome for your customer (i.e. an API event where customers derive value). The mix will vary depending on the type of business, but I’ve found the benefit of consumption based pricing models to outweigh seat based pricing for the following reasons:</p><ul><li>100% alignment — customers pay when they benefit from your service, and you make money when you provide value (or trigger a direct cost)</li><li>No ‘shelf-ware’\low churn — consumption based billing requires customer usage. This forces your org to center on providing tangible value (vs. some future promise)</li><li>Higher ARR — as your customers succeed usage models more directly correlated to their success</li></ul><h4>Minimums and Long Term Commitments</h4><p>Higher minimums and longer commits mean more friction in the buying\sales process.</p><p>That’s not always a bad thing. A couple scenarios I’ve found friction helpful to both the customer and the vendor:</p><ol><li>Customers procurement process is heavy (i.e traditional enterprise buyer) — requiring significant upfront legal, financial, and technical due diligence investment by both parties before the service can be used. Low friction won’t help this segment of customers.</li><li>Longer Technical Integration\ Time to Value — If you’re investing non-trivial technical pre-sales efforts to help your customers realize value from your product, a minimum charge that aligns to this will allow you focus on the right places to invest.</li></ol><p>These scenarios aside — removing every possible friction point for your customers to try your product is the higher order operating principle.</p><p>If you have reason to believe customers will love your product, the integration or usage of product will be much sticker than any long term commitment you’ve signed up for. Combine this with the consumption based billing model above — you have a recipe for long term healthy mrr per customer.</p><h4>Trials</h4><p>In your brand building phase, you need to give yourself every possible chance to prove your worth. Depending on the complexity of your solution — this could mean a free trial period, or it could mean some limited subsidized trial period.</p><p>While it will vary by business, give every reason for your customers to experience your products magic. Don’t over optimize for first month billing. If you fulfill your promise , you will have many years ahead to recapture that trial period revenue.</p><h4>Volume Discounts</h4><p>The more customers spend with you, the better deal they should get. I’m a big fan of signaling this benefit through volume pricing tiers publicly shared.</p><p>If you’re on consumption based billing, make the pricing segments true tiers (i.e. the lower price point kicks in for just the transactions above that tier). This will prevent the odd scenario where you have a disincentive for a customer to grow because the next tier will cause their overall bill with you to drop (which will be a problem for your account teams). Instead, stick to your principles of giving customers lower overall average unit price as they grow with you — while not shooting yourself in the foot.</p><h4>Summary</h4><p>You’ll note I don’t touch on how to decide on an actual price point for your product. That part is more straight forward, as it will be dictated by your cost structure, competitive environment, and positioning strategy (i.e. value based pricing). Instead, I highlight principles of pricing that have served some of the fastest growing cloud platforms well over the last decade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26b7e58ff73a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/pricing-principles-26b7e58ff73a">Pricing Principles</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enterprise]]></title>
            <link>https://medium.com/scale-mrr/enterprise-77a68bc2ad00?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/77a68bc2ad00</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Tue, 16 Oct 2018 21:41:11 GMT</pubDate>
            <atom:updated>2018-10-16T21:41:11.005Z</atom:updated>
            <content:encoded><![CDATA[<h4>Moving Upmarket and the ‘Ilities’</h4><p>Many of today’s largest cloud platforms started with an SMB focus. A few reasons this is a great place to begin:</p><ul><li>Drives the lead and customer volume required to improve a platform with real market feedback.</li><li>Forces improvement of operational, technical, and domain expertise required for upmarket credibility.</li><li>Facilitates a quicker and more predictable MRR path (less dependencies on single large deals to hit plan).</li></ul><p>You can’t stop here though. Continuously moving upmarket should be a focus of every fast growing platform. Why?</p><ul><li>Even a few larger deals layered on top of your current business can materially impact overall ARR.</li><li>Larger organizations have larger budgets. More of your revenue pie should be coming from these businesses over time.</li><li>Many of the reasons SMB customers use your product will still apply upmarket — you don’t want to cede this opportunity to competition.</li></ul><p>The rest of this post explores three topics:</p><p>1\ Whats different about selling upmarket?</p><p>2\ Upmarket Prerequisites</p><p>3\ How to get started</p><h4>Enterprise <em>Is</em> Different</h4><p>Moving upmarket requires careful consideration — as it will be different than your typical SMB sell. Specifically:</p><ul><li>Selling across multiple personas across an organization and multi-level sign off up an organization.</li><li>More complex technical integrations (more legacy systems to work with).</li><li>Longer pilots. More teams and more numbers involved in proving value.</li><li>Stringent security, compliance, auditing, and procurement processes.</li><li>Ecosystem dependencies (support of 3rd party systems).</li><li>Deeper customer support requirements (i.e. 24x7 response times)</li><li>Longer sales cycles (a natural by product of the all the above).</li></ul><p>While these differences will require building a new organizational muscle — there are some basic capabilities you need to be prepared to invest in.</p><h4>Prerequisites — The ‘Ilities’</h4><p>Before you staff sales and marketing resources against the enterprise opportunity — you need to assess if your business and core product is ready. This is not about domain specific features.</p><p>Rather, its the set of capabilities that speak to how you operate your service and business. Specifically — Security, Reliability, Scalability, Availability, and Liability.</p><p><strong>Security</strong></p><p>Stating you’re secure, and sharing a white paper of your security posture, will not be enough. There will likely be requests from the dedicated security teams of your prospects who want to understand in depth how you address security and compliance topics important to them. Its imperative to have a senior credible technical professional, ideally one with a interest and expertise in security, who can help your customers understand the depth of your current posture. This person will also be point on helping to guide your product road map for security and compliance related needs. This is not an ‘ility’ to take lightly. <em>If you’re not ready to dedicate engineering resource to these efforts — you may not be ready for enterprise</em>.</p><p><strong>Reliability</strong></p><p>Enterprises will not be forgiving with up-times that don’t meet their needs, no matter how great your features are. Its important to have clear documentation that shows your historical uptime. In an ideal world, you can go above and beyond by describing how you’re architected to achieve that uptime — and then make those updates publicly available for customers to consume. While some of this can be addressed with SLA’s, no contract in the world can make up for a service that struggles to remain online. <em>If you’re not achieving good to great uptime for your service — you may not be ready for enterprise</em>.</p><p><strong>Scalability</strong></p><p>Enterprises want to know you can handle their volume and performance needs. Ideally you have existing customers that you can use to signal some of the scalability and performance thresholds that matter to your enterprise prospects. The world is filled with high growth companies with scale\performance needs similar to (if not larger than) many enterprises. <em>If you don’t have at least a few of customers at larger operational scale already in place — you may not be ready for enterprise.</em></p><p><strong>Availability (Support and SLA’s)</strong></p><p>Enterprises will have requirements defining how technical support issues are addressed. In some cases (i.e. system down), they will require you be available to them 24x7 within a few minutes of submitting such a request.</p><p>Ideally, you have through your existing business created a technical support process that can be leveraged. While the first few iterations can be bootstrapped, at some point you’ll want to think about your support offerings as a standalone product (i.e. <a href="https://aws.amazon.com/premiumsupport/">AWS premium support</a>).</p><p><strong>Liabilities (and Contracts)</strong></p><p>Enterprise deals require a lot of heavy lifting on the legal front. Some common items negotiated:</p><ul><li>Liability Amounts</li><li>Contract Minimum Value</li><li>Commit Durations</li><li>SLA’s</li><li>Volume Pricing</li></ul><p>Enterprise will require you to hit thresholds across these vectors that you haven’t had to do for SMB. It’s critical to have account executives who understand how to navigate these points, and to have seasoned legal resources available. <em>If you don’t have these resources in place — you may not be ready for enterprise</em></p><h4>How to Start</h4><p><strong>Define Your Enterprise</strong></p><p>There are two ways to define the enterprise segment of your business:</p><p>1\ Deal Size</p><p>2\ Company Size</p><p>Some recently public SAAS businesses, like Coupa, have a direct enterprise sales force that specifically targets organizations with more than 1,000 employees. Zendesk, on the other hand, uses a combination of usage and ACV metric: (&gt;= 100 agents and $50k acv) to define enterprise.</p><p>While deal size alone can be appealing — I don’t recommend this approach. If you’re scaling well, it’s likely you’ll already have (or will soon have) some customers at very large spend. It’s too easy to draw false conclusions about your organizational capabilities from this set of customers.</p><blockquote>Instead, I recommend defining your enterprise go to market efforts with a specific target company size and target persona. These tend to be the repeatable variables in complex selling that you will need to solve for.</blockquote><h4>Focused GTM Investment</h4><p>As you move upmarket, it’s important to resource, measure, and iterate against these plans separate from your core go to market motion. Ideally, this means you have well dedicated operating plan (across sales, marketing, and product) highlighting specific investments against this segment.</p><p>However long you think it’ll take to gain traction in this segment — double it. Enterprise reps take longer to higher, longer to ramp to a full pipeline, and will take longer to draw out customer requirements that you may not be able to address today (i.e. product requests).</p><p>As with any emerging effort across your business, you’ll need cross functional support to make progress. Your CEO, Product Heads, Marketing Heads, and Board should be aligned with the investments and the timeline of progress you are making.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77a68bc2ad00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/enterprise-77a68bc2ad00">Enterprise</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Sales Strategy]]></title>
            <link>https://medium.com/scale-mrr/pragmatic-selling-5e4e7a164443?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/5e4e7a164443</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 16:43:58 GMT</pubDate>
            <atom:updated>2018-10-09T20:19:34.922Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to Build a Realistic Market Attack Plan</h4><p>Building a successful business requires step wise iteration towards the long term promise of your company. Many platforms stumble by attempting to sell too far ahead of their current strengths and capabilities.</p><p>Target market segmentation is the process of creating realistic market attack plan of how to drive revenue today — <em>anchoring on current capabilities and strengths.</em></p><p>Executed well, it will allow you to build the crucial momentum, customer proof points, and revenue to get to the next stage of growth (where you then get to repeat the process).</p><p>Lets unpack:</p><h4>Outcome</h4><p>When complete, your plan will contain (at a minimum):</p><ul><li>Target businesses you will reach out to in the coming period</li><li>Target personas within the accounts you will target (with names + contact)</li><li>Horizontal Buying Reason — the most important value per persona</li><li>Segment Buying Reason — the<strong> most important </strong>impact you can have for that type of business</li></ul><h4>Starting Point — Key Buying Signals (KBS)</h4><p>The best place to begin is to unpack where you are today — and classify your customer base by <strong><em>key buying signals (KBS’s)</em></strong>. Whether your customer base is 5–10 private beta customers, or a few thousand customers, tag each of your customers by the following:</p><p><strong>Vertical Niche</strong></p><p>Identify the specific vertical segment each of your customers fall into. Hyper-niche category definition is the goal here. For example, if you have a customer in the on-demand space (i.e. instacart) — you’ll want to define it as ‘mobile first grocery delivery’. The more niche you define your categories, the easier it will be to identify peers.</p><p><strong>Primary Horizontal Value (PHV)</strong></p><p>Identify the single most important persona that influenced the decision to adopt your service <em>and </em>the reason they bought your solution. The reason should be specific to that role. For example, an early value prop of EC2 was elastic compute capacity for batch processing. This value resonated with any software engineer with that use case — regardless of industry (i.e. media, oil and gas, etc).</p><p><strong>Primary Vertical Value (PVV)</strong></p><p>This value statement should tie to specific business outcomes for that industry vertical. You know you’ve selected a good PVV’s when any persona (finance, marketing, or engineering) in that industry would immediately recognize the value.</p><p><strong>Company Size</strong></p><p>Company head count often reflects complexity of sale — which can be a key factor when assessing your organizational selling capabilities. Classify your customer base by # of employees (Using the company size ranges as shared on linkedin can be useful here).</p><h4>Target Building — Prioritize and Pattern Matching</h4><p>Once you have your existing customers classified by Vertical Niche, PHV, PVV, and Company Size — you can stack rank the mix of key buying signals that reflect where you’re strong today.</p><p>With this mold in place — you can now start to research new companies that closely match.</p><p>There are no short cuts here— through brute force googling , list buying, linkedin searching — you’ll need to identify target companies and target that closely match your priority target market segments.</p><p>The number of targets you ultimately settle on will be highly dependent on your stage. Once you’ve identified these targets, you can begin your go to market motions on these targets.</p><h4>New Verticals — Use PHV</h4><p>What happens if you want to sell into a new market where you have no presence today? You’ll want to start with your PHV — the most important value you provide to a specific persona.</p><p>The benefit of a PHV is that your messaging should appeal regardless of what industry vertical that person is in. You may not have the reference customers needed for that new vertical (or the specific vertical messaging) — but your message should land with a well targeted persona specific message.</p><h4>Moving Upmarket — Punch (slightly) Above Your Weight</h4><p>Leverage the same Vertical Niche, PVV, and PHV — but expand your company size target into the next layer of company you don’t have a large presence in today. For example, if your current sweet spot is companies with up to 1000 employees — layer in a target market segmentation with companies between 1000 and 2500. This will allow you to start learning what additional capabilities you will need (i.e. sales skills, product gaps etc) — while still putting your self in a position to yield some fruits from the effort.</p><h3>Iterate</h3><p>I’ve seen this framework work well at each stage of revenue growth. Done well, you should be picking new segments to cross into each planning cycle. This allows you to grow your core business — while still making incremental progress into the new markets you’ll need for future growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e4e7a164443" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/pragmatic-selling-5e4e7a164443">Pragmatic Sales Strategy</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selling Self-Serve]]></title>
            <link>https://medium.com/scale-mrr/north-star-184e4edfeca2?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/184e4edfeca2</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 16:39:50 GMT</pubDate>
            <atom:updated>2018-10-08T21:13:08.723Z</atom:updated>
            <content:encoded><![CDATA[<h4>North Star Principles for Best in Class Platforms</h4><p>Self-Serve does not<em> </em>imply your product will sell itself, or you that you won’t need a skilled go to market and sales team organization to drive your business. Rather, Self Serve is a</p><blockquote>foundational business principle that can fuel better product, better customer acquisition, and ultimately a better business than traditional paradigms.</blockquote><p>This is evident with companies like Zendesk, Dropbox, and Atlasssian ( just to name a few). They have a core self-serve business ethos — yet still have large go to market teams driving tremendous growth in enterprise and mid market.</p><blockquote>Businesses with a self-serve north star, complimented intelligently with traditional go to market , can drive sustainable long term competitive advantages in their respective markets.</blockquote><p>To unpack:</p><h3>Better Product</h3><p>Self serve businesses assume no human should have to intervene to (1) explain how to use a product or (2) how to benefit from a product. This requires hyper focus on creating products that are:</p><ul><li>Easy to integrate</li><li>Intuitive for end users</li><li>Self-evident in value</li></ul><p>In the early stages of a product these principles might seem trivial to deploy against commodity functionality. What happens over time, however, is a product continues to evolve against customers’ more sophisticated requirements — albeit with the same self-serve principles.</p><blockquote>As feature gaps against the incumbents narrow — ease of use and simpler integration become a competitive advantage as a business moves upmarket.</blockquote><h3>Better Customer Acquisition</h3><p>Self Serve can accelerate growth compared to business employing only traditional acquisition models (direct sales and partnerships). Some key factors:</p><h4>Access to Self Serve Buyers</h4><p>Much of the SMB market, and portions of mid market and enterprise line of business, prefer completing large portions of the buyer journey on their own. Why cut these customers out?</p><h4>Customer Velocity</h4><p>As an emerging platform — its critical to get frequent customer feedback on your product, as it will drive your road map and improve your operational capabilities. A self serve channel gives you access to SMB buyers, and a higher volume of businesses using your service.</p><h4>Lead Funnel for Enterprise</h4><p>All the self serve investments you are making will pay off as you move upmarket. Enterprise decision makers, or the engineers they rely on to implement projects, will benefit from the self education capabilities you make available. This will create more qualified inbound leads for your sales team, which can at times also accelerate sale cycles.</p><h4>Access to Global Customers</h4><p>Self Serve enables earlier and more intelligent international expansion. Non US customers, many of whom read and understand english will find their way to your service. These early adopters can inform your more intentional international expansion efforts (i.e. local language support, 24x7 support, field resources in geo, etc).</p><h4>Clarity of Value</h4><p>Self Serve demands clarity of thought. Because there is no assumption that a sales or customer service rep will be there to walk a customer through your value prop — self serve forces an optimization of messaging, positioning, and over all value prop of your service. This in turn drives more qualified leads with better educated prospects.</p><h4>Efficient Scale</h4><p>Ultimately, serving tens of thousands of customers across the globe can be done more efficiently with a self serve businesses. Superior products mean fewer support tickets and fewer competitive battles. Clarity of value prop fuels better educated prospects and shorter sales cycles. Transparency of pricing reduces negotiation friction….just to name a few.</p><h3>Self-Serve — Principles</h3><p>So what attributes are key in a self-serve business? A few of the important ones:</p><h4>Instant Access</h4><p>Friction to access a product is removed. There is typically a sign up button to register for the service, so some form of product engagement can begin immediately.</p><h4>Documentation</h4><p>No NDA’s are required to understand the depth of the product, or access documentation. What the product is, how it works, and how to integrate are all easily accessible from a website.</p><h4>Pricing Transparency</h4><p>Initial pricing and volume pricing are available on the website. This does not imply every possible customer scenario or the largest enterprise volumes need can’t be negotiated — you can have a contact sales button for those scenarios.</p><h4>Contact Sales</h4><p>Don’t forget that many customers, especially your larger ones, will need sales engagement. Make it dead simple for prospects to get in touch with your sales team. At the same time, make sure you have a well defined internal process to quickly respond.</p><h4>Status Page</h4><p>Ideally you have a status page where customers can get real time updates on the health of your service. Done right, it should also be the place where service updates are posted in real time as you’re working through an issue.</p><h4>Customer Support</h4><p>Customers should have a simple channel to engage and get their questions answered. This could range from public forums to high SLA response time customer service tickets.</p><h4>Compliance and Security</h4><p>You’ll reduce friction in the sales process if you can document your security processes and compliance standards. Make it easy for customers to find this. At the very least, it will be a valuable tool for your sales team to refer to as they engage prospects.</p><h4>Legal</h4><p>If done well, many businesses will be ok with click through terms of service. Work on optimizing the click thru for your most standard legal objections. Provide a clear link to your terms of service, and work to keep it as simple as possible.</p><h4>Billing</h4><p>Make it simple for customers to understand their bill, and how they are trending at any given time.</p><h4>SLA’s</h4><p>Like pricing , It’ll be impossible to create custom SLA’s for every one of your customers if you are building a business for scale. Try to craft service level agreements that make sense for your customers and your business — and make them accessible and default to your customers. As with pricing — there may be some SLA’s you reserve for unique or large customers.</p><h3>Self-Serve is Hard</h3><p>Make no mistake, adhering to a self serve go to market philosophy is difficult. It takes much more thought and longer cycles to design, market, and sell under this paradigm.</p><p>Done well, however, a platform will be in a tremendous position to both move upmarket and scale efficiently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=184e4edfeca2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/north-star-184e4edfeca2">Selling Self-Serve</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scale MRR]]></title>
            <link>https://medium.com/scale-mrr/scale-mrr-366eb133dd84?source=rss----ee6d961f9437---4</link>
            <guid isPermaLink="false">https://medium.com/p/366eb133dd84</guid>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Zeeshan Yoonas]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 16:30:08 GMT</pubDate>
            <atom:updated>2018-10-05T00:39:43.421Z</atom:updated>
            <content:encoded><![CDATA[<h4>An Introduction</h4><p>Between Sift Science, Twilio, and AWS, I’ve been fortunate to build revenue from the ground floor for three global cloud platforms.</p><p>Through these experiences, I’ve developed a set of go to market principles that I believe are table stakes for any developer or cloud infrastructure business looking to build revenue <em>quickly, predictably, and efficiently.</em></p><p>Through this series of posts, I’ll explore some of the business, sales, and marketing topics I’m frequently asked about.</p><p>In the coming weeks, I’ll dive deeper into the following:</p><h4>North Star</h4><p><strong>Self Serve Principles For Best In Class Cloud</strong></p><p>Self-Serve does not<em> </em>imply your product will sell itself, or you that you won’t need a skilled gtm\sales\customer success organization to drive your business. It is, however, a principle that can fuel sustainable competitive advantages, even with the ‘high touch’ sales driven segments of a business.</p><h4>Pragmatic Selling</h4><p><strong>Creating a Market Attack Plan</strong></p><p>Building a nascent business requires step wise iteration towards the long term promise of your company. Many businesses stumble by attempting to execute too far ahead of their current strengths and capabilities. This post covers how to create a realistic market attack plan.</p><h4>SKU to Scale</h4><p><strong>Accelerating Growth into $100M+</strong></p><p>New logos and organic base expansion are not sufficient to build a best in class business. ‘SKU’ing is the process of introducing new features and products your customer base will happily pay for. This not only increases the slope of your growth curve, but can also improve retention.</p><h4>Enterprise</h4><p><strong>When, How, and the ‘Ilities’</strong></p><p>If you’re executing well in the smb and mid market segments, you should be proactively thinking about how to tackle the enterprise. This post provides a framework for <em>when and how </em>to make this move.</p><h4>Pricing Principles</h4><p><strong>Accelerate new logos and overall growth</strong></p><p>Pricing will influence how prospects perceive your value, how efficiently you can acquire new leads\customers, how sales teams run their deals, and the cash flow of your business — just to name a few.</p><h4>Sales Compensation</h4><p><strong>MRR is King</strong></p><p>Hyper-growth businesses should goal on MRR vs. Revenue, as it more accurately reflects a true state of the business. While this can introduce complexities in compensation plans, it drives the right long term behavior.</p><h4>Hiring Builders</h4><p><strong>Competencies of Great Candidates</strong></p><p>Reflecting on close to 1,000 interviews I’ve done of over the last decade, I’ve identified four specific competencies that can significantly improve the odds of someone succeeding in a hyper growth business. These traits apply to candidates any level in an organization from C-level to IC’s.</p><h4>Revenue Plan</h4><p><strong>A How To</strong></p><p>A monthly revenue plan segmented by customer type (new vs. existing), customer size (spend), and sales channel (i.e. direct, self-serve, channel), is a critical tool to align your GTM efforts and manage the business. This post walks through how to create this.</p><h4>‘Use Case’-ing</h4><p><strong>How to Market and Sell Building Blocks</strong></p><p>‘Use Case’-ing is a technique to define, market, and sell <em>what </em>customers are building with your api’s/service/platform. It’s an import technique to (1) focus messaging, positioning, and sales investments beyond technical benefits and (2) helps business personas better recognize your value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=366eb133dd84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scale-mrr/scale-mrr-366eb133dd84">Scale MRR</a> was originally published in <a href="https://medium.com/scale-mrr">Scale MRR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>