<?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 Ben Sears on Medium]]></title>
        <description><![CDATA[Stories by Ben Sears on Medium]]></description>
        <link>https://medium.com/@ben_sears?source=rss-edd57178d1c3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xiAhayxJrOxdEHoGrXh7mw.png</url>
            <title>Stories by Ben Sears on Medium</title>
            <link>https://medium.com/@ben_sears?source=rss-edd57178d1c3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:18:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ben_sears/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[Best practices for integrating Stripe Billing with your SaaS]]></title>
            <link>https://medium.com/swlh/best-practices-for-integrating-stripe-billing-with-your-saas-559747ae7062?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/559747ae7062</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[stripe]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Wed, 19 Sep 2018 17:09:11 GMT</pubDate>
            <atom:updated>2018-09-19T17:09:11.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MbiTI_U2iZIkKeTg.png" /></figure><p>Stripe has quickly become one of the leading billing solutions on the market, especially preferred by businesses selling Software-as-a-Service. By reading this guide you will understand how to ensure PCI compliance and the best way to build front-end and back-end integration with Stripe.</p><h3>Security — Ensure PCI Compliance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YXnRiyt4Loeb2iBIjIOohg.png" /><figcaption>The Stripe PCI Compliance Dashboard</figcaption></figure><p>Any company that stores, transfers, or processes credit card data must adhere to the <a href="https://www.pcisecuritystandards.org/">Payment Card Industry (PCI) Data Security Standards</a>. If you integrate with Stripe using <a href="https://stripe.com/docs/security">their security standards</a>, you will automatically qualify as PCI compliant and they will automatically generate the required <a href="https://www.pcisecuritystandards.org/document_library?category=saqs#results">Self Assessment Questionaire</a> (SAQ) and Attestation of Compliance which you can download from your <a href="https://dashboard.stripe.com/account/compliance">compliance dashboard</a>. Stripe recommends adhering to the following items to remain PCI compliant:</p><blockquote>Use <a href="https://stripe.com/docs/checkout">Checkout</a>, <a href="https://stripe.com/docs/stripe-js">Stripe.js and Elements</a>, or our <a href="https://stripe.com/docs/mobile">mobile SDK libraries</a> to collect payment information, which is securely transmitted directly to Stripe without it passing through your servers</blockquote><blockquote>Serve your payment pages securely using <a href="https://stripe.com/docs/security#tls">Transport Layer Security</a> (TLS) so that they make use of HTTPS</blockquote><blockquote>Review and <a href="https://stripe.com/docs/security#validating-pci-compliance">validate</a> your account’s PCI compliance annually</blockquote><p>When integrating with the Stripe API, the secret keys you use must be stored in a safe place. Avoid storing keys in version control; this could lead to a security breach of customer data and could cause massive problems for your business.</p><h3>Front-end — Use Stripe Elements</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AE-G1-JXkw0megUg.png" /><figcaption>An Example Site Using Stripe Elements</figcaption></figure><p>For a SaaS, <a href="https://stripe.com/elements">Stripe Elements</a> is a great tool to create a great checkout page customized to fit your specific use-case. They have pre-built UI components such as credit card input and payment buttons. These handle credit card data while maintaining PCI compliance by sending the data directly to Stripe — without it having to pass through your own servers. They are responsive to screen size, customizable to fit your business’s style, and can be localized to your customers’ preferred language.</p><p>Stripe Elements is only a tool to give customers a way to enter payment information. As a SaaS company you still need to develop a front-end solution to handle other functions, such as when a customer upgrades or downgrades to a different subscription plan, cancels their service, or resubscribes.</p><h3>Back-end — Use a Stripe API Library and Webhooks</h3><p>A Stripe integration on the back-end consists of two parts: an active integration and a reactive integration. <strong>Active</strong> being direct calls to the Stripe API to perform actions like cancelling a subscription and <strong>Indirect </strong>being event handlers that respond to events in Stripe such as a credit card payment failing.</p><p>The best way to make API calls is to use an official <a href="https://stripe.com/docs/libraries">Stripe API library</a>. With this you can start building logic needed to handle all the use-cases you want to cover for your particular SaaS.</p><p><a href="https://stripe.com/docs/webhooks">Webhooks</a> are API calls that Stripe can send to an endpoint of your choice to alert you when events happen in Stripe. This is most useful for allowing you to respond to payment failures and automatically restricting access to your app when a customer’s credit card is failing.</p><p>When building your integration, be mindful of the following:</p><ul><li>Keep your Stripe secret key out of version control to prevent your Stripe account from being hacked</li><li>Do all development using Stripe test keys, ensuring you do not break your production customer data</li><li>When using webhooks, check the <a href="https://stripe.com/docs/webhooks/signatures">Stripe signature</a> to ensure the requests are valid</li><li>Make sure your integration keeps a 1 to 1 mapping of user in your database to customer in Stripe. Some businesses mistakenly create multiple customers using the same email and this can cause issues when trying to make more complex integration code later on.</li><li>Lock the API version to what you developed and tested with; Stripe can change their API and break your code if you are not locked on a specific version; <a href="https://stripe.com/docs/building-plugins#set-api-version">here’s how you do it</a>.</li></ul><h3>Using a Stripe Partner to avoid development</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FPDCEbVmo13roSLi.png" /><figcaption><a href="https://servicebot.io/">Servicebot</a> Generates PCI Compliant UI Components connected to Stripe</figcaption></figure><p>Stripe does a lot out of the box, but most SaaS companies will need more than just the bare bones. Features such as pricing pages and billing settings pages where customers can manage their own subscriptions.</p><p>If you don’t want to spend a lot of resources developing and maintaining your own integration with Stripe, there are <a href="https://stripe.com/works-with/type/platform/category/recurring-payments">Stripe verified partners</a> which can provide a ready-made integration you can drop-into your app. <a href="https://servicebot.io/">Servicebot</a> makes it easy to connect your SaaS to Stripe without spending time developing by generating embeddable components such as pricing pages, billing management, and check-out pages.</p><h3>Conclusion</h3><p>When building a Stripe integration for a SaaS, there are a lot of moving parts that need to be built. Developing a front-end using Stripe Elements and a back-end with one of Stripe’s libraries, and handling events sent by Stripe webhooks are the building blocks of a solid Stripe integration.</p><p>If you are looking to minimize development on your SaaS billing solution, you should look at Stripe partners such as <a href="https://servicebot.io/">Servicebot</a></p><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by + 370,107 people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=559747ae7062" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/best-practices-for-integrating-stripe-billing-with-your-saas-559747ae7062">Best practices for integrating Stripe Billing with your SaaS</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to figure out the best pricing for your SaaS]]></title>
            <link>https://medium.com/hackernoon/how-to-figure-out-the-best-pricing-for-your-saas-ac9bfbf2f6b3?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac9bfbf2f6b3</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas-pricing-page]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[saas-pricing]]></category>
            <category><![CDATA[pricing-for-saas]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Wed, 29 Aug 2018 23:25:24 GMT</pubDate>
            <atom:updated>2019-04-26T04:59:47.954Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XXymKahmEjxycZ8s" /></figure><p>You just finished building your MVP. Now you’re looking to launch and start getting paying customers. The problem is, you have no idea how you should be pricing your product. You are probably asking yourself:</p><p>“Do I create multiple tiers?”</p><p>“Should I be charging less than my competitor, or more?”</p><p>“Should I gate off specific features, or charge by a metric like number of users — or maybe both?”</p><p>And the list of questions goes on…</p><p>This article aims to help you find answers to all your pricing questions by asking: <strong>Who is your ideal customer? </strong>Having a deep understanding of your ideal customer will enable you to build pricing which directly targets them by showing them the value they need to get from your product at a price they feel comfortable with.</p><h3>You must know your customers to know your pricing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*IC3h3EmFVj4qI_Zt.jpg" /><figcaption><a href="https://blog.mailchimp.com/new-mailchimp-user-persona-research/">Mailchimp’s buyer personas</a></figcaption></figure><p>A Buyer persona is a representation of who your ideal customer is with as much detail as you can muster. Some of the things you should be thinking about when coming up with your buyer persona are:</p><ul><li><strong>What is your buyer’s role in their organization</strong></li><li><strong>Which of your features do they care the most about</strong></li><li><strong>What marketing channels can you find your buyer in?</strong></li><li><strong>What value does your buyer hope to get from using your product?</strong></li><li><strong>What price are they willing to pay?</strong></li></ul><p>Ideally, you would research this information by interviewing your customers and giving out surveys asking questions about themselves, and worst-case you just have to make estimates yourself and fill in the blanks as you gain customers. Beware asking non-paying customers for any information — these people are usually not going to be an ideal customer and will affect your strategy by optimizing for people who don’t pay.</p><p>The more details you can get, the better; these personas are useful not only for your pricing model but also as a framework for every single decision you make for your product.</p><h3>What does your customer care about?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*3uX2_MV8nGe74CdT.jpg" /></figure><p>One of the most important things to consider when it comes to pricing strategy is what your different customers actually care about when they use your product.</p><p>When building buyer personas for <a href="https://servicebot.io/">Servicebot</a>, we made a spreadsheet mapping value propositions to personas, giving us an understanding of what parts of the product our potential customers care the most about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytuyzR5JTKU7nRUJqbkTvw.png" /><figcaption>A basic mapping of value proposition to buyer persona for <a href="https://servicebot.io/">Servicebot</a></figcaption></figure><p>By realizing who wants what, you can understand which features all customers should have, and which features can be gated by tiers. If you can <a href="https://hackernoon.com/tagged/figure">figure</a> out that the CFO of a large organization is one of the few that cares about a specific value proposition, you may consider gating that value behind a higher tier because you can expect them to have a larger budget than, say, the bootstrapping startup founder.</p><h3>Build your pricing strategy on top of your personas</h3><p>In doing this exercise of fleshing out your buyer personas, you now have the information you need to build a logical pricing strategy. It’s tricky figuring out what your different pricing tiers should look like.</p><h4>Pricing By Value Proposition</h4><p>Having more expensive tiers offering more features is a strategy a lot of companies use price their <a href="https://hackernoon.com/tagged/saas">SaaS</a> product. When executing this strategy, you need to pay close attention to which customers care about what features and create a logical progression of company size to the need of a specific value proposition your product offers.</p><h4>Pricing By Value Metric</h4><p>Pricing your tiers based on value metric(s) is another common strategy. A great value metric is one that as it increases (causing the cost of the product to increase), will also increase in the value the customer receives from your product. For example Stripe charges based on the amount of revenue processed.</p><p>Finding a combination of bundling features with value metrics is the essence of coming up with an effective pricing strategy. The goal is to create a logical, easy to understand pricing model which will allow you to grow as your customers grow.</p><h3>What prices should you actually be setting?</h3><p>Now that you have a strategy formulated, we need to finally plug in prices. There are three different approaches pricing models generally take:</p><h4>Cost-based Pricing</h4><p>A cost-based approach takes your product’s internal costs and adds a margin on top. For example, if each customer costs you $100/month you could price your product at $120/month, giving you a $20 profit per customer. The problem with this approach is that it only looks at your company’s costs and does not take into account the customer’s feelings about price.</p><h4>Competitor-based pricing</h4><p>A lot of startups end up pricing themselves compared to their competitor, which may or may not be effective. Trying to match or undercut your competition’s prices can suffer from problems like a race to the bottom (think of how Uber subsidized their prices to drive out competition). It is generally better to optimize your price for your own value provided to customers, especially if you are offering more value than the competition.</p><h4>Value-based pricing</h4><p>Value-based pricing is the most effective (but hardest to implement) type of pricing model because it’s tailored uniquely for your company. You need to understand how much value your customer is getting out of your product and price in accordance to that. Many companies use the <a href="https://sixteenventures.com/saas-pricing-strategy">“10x rule”</a> when it comes to value pricing: Give your customers value worth 10x the price you are charging them.</p><h4>How do you figure out what people are comfortable paying?</h4><p>To figure out what people are willing to pay, you can’t just ask them directly “what do you want to pay.” Dutch economist Peter van Westendorp recommends asking four questions to gather valuable price data from a specific customer segment:</p><blockquote>At what price would you consider the product to be so expensive that you would not consider buying it? (Too expensive)</blockquote><blockquote>At what price would you consider the product to be priced so low that you would feel the quality couldn’t be very good? (Too cheap)</blockquote><blockquote>At what price would you consider the product starting to get expensive, so that it is not out of the question, but you would have to give some thought to buying it? (Expensive/High Side)</blockquote><blockquote>At what price would you consider the product to be a bargain — a great buy for the money? (Cheap/Good Value)</blockquote><h4>Be wary of freemium</h4><p>A lot of companies offer a “free tier” which has limited features. The idea is that people will start using the product, get value out of the free tier but see a lot more value if they were to start paying and eventually upgrade. In theory this sounds great and for some companies it is. The problem with the free tier is that you may start running into problems such as the high cost of providing support to the free customers, the free tier bringing in the wrong type of customer, and requiring you to spend resources to try and convert the cheapest customers to actually pay you. Early-stage startups feel this pain the greatest since they can only afford spending resources on critical operations. Look at your buyer personas and product — sometimes the freemium model works well and sometimes it does not.</p><h3>Pricing your product is an ongoing process</h3><p>You will never be done with your pricing strategy. As you get more data and feedback from your customers you will change your personas to be more accurate and change your pricing strategy to better target those people.</p><h4>Trying to sell your SaaS? <a href="https://servicebot.io/">Servicebot</a> offers extremely simple drop-in components for pricing pages, billing management, and more.</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac9bfbf2f6b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-figure-out-the-best-pricing-for-your-saas-ac9bfbf2f6b3">How to figure out the best pricing for your SaaS</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Servicebot Open-Source v0.9: Webhooks, Payment Scheduler, Major UI Changes]]></title>
            <link>https://medium.com/hackernoon/servicebot-open-source-v0-9-webhooks-payment-scheduler-major-ui-changes-6104453bbfdb?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6104453bbfdb</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Sun, 06 May 2018 03:21:00 GMT</pubDate>
            <atom:updated>2019-04-26T05:00:50.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Rp9z4lC5dUJ0tCf6mmTs3g.png" /></figure><p>We are happy to announce our v0.9 release for <a href="http://servicebot.io/">Servicebot</a>, an <a href="https://github.com/service-bot/servicebot"><strong>open-source</strong></a> subscription management <a href="https://hackernoon.com/tagged/platform">platform</a>. This article will show you the latest additions to the platform and how to get the most value out of your <a href="https://hackernoon.com/tagged/servicebot">Servicebot</a>.</p><p>Since we started Servicebot last year, our goal has been to create an open-source platform that takes a <a href="https://en.wikipedia.org/wiki/Service-oriented_architecture">service-oriented</a> approach to subscription management. This approach allows for complete control over the <a href="https://medium.com/@ben_sears/understanding-the-lifecycle-of-a-saas-subscription-5169307fd0c8">different steps</a> of the subscription lifecycle.</p><p>In this release, we have finished our custom payment scheduler as well as made major changes to the UI and the internals of Servicebot.</p><p>For full release notes, check out our <a href="https://github.com/service-bot/servicebot/releases/tag/v0.9.0">GitHub</a>.</p><h3>Platform Internals</h3><h4>More functionality moved into plugins</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6xLrSPDYzmwwtz6Y." /><figcaption>Photo by <a href="https://unsplash.com/@steve_j?utm_source=medium&amp;utm_medium=referral">Steve Johnson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Since we added <a href="https://github.com/service-bot/pluginbot">pluginbot</a> to Servicebot back in September of 2017, we have slowly been migrating functionality from a monolithic architecture into a more service-oriented plugin architecture. We plan on eventually migrating all the code from the monolith to plugins, as well as allowing the plugin system to be controlled from the front-end, as commonly seen in CMS like Wordpress or Drupal.</p><p>In this release we added a file manager plugin, which we are using in production to push uploads such as logos or user avatars to S3 instead of the filesystem.</p><h3>Webhooks</h3><p>There is now an option to send event data to integration points such as Jenkins, Zapier, or your own applications. These events will allow you to tap into the <strong>service lifecycle </strong>of Servicebot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZxC0yrsQ1s2ZH35y_vWpOw.png" /></figure><h4>Example Webhook use case: SaaS billing automation</h4><p>A SaaS business has a free trial registration form on their website which, when requested, will create an account in their app and attach an access token to the response so they can be logged in.</p><p>Using Servicebot to manage their subscriptions, they can easily have a webhook connect to their app, or build automation service such as Jenkins. This will allow for service lifecycle events, in this case a “requested” event which triggers whenever a new subscription is requested. Going further, the “cancellation” and “trial expiration” events can trigger app access to be restricted until they add a funding source.</p><h3>Custom Payment Schedules</h3><p>With this latest release we added a new feature for allowing much more customizable payment plans. Here’s how it works — First, you set the billing type of a service to be “scheduled payments,” then you can set the number of payments desired, when each payment should occur, and the amount each payment should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YK4EYbEU0QheLgODJOPOA.png" /><figcaption>Payment schedules allow you to customize how many payments and the cost of each</figcaption></figure><p>There are two main points to building this feature: The ability to split up a one-time payment into multiple payments, and the ability to have a more flexible payment structure.</p><h4>Example payment schedule use-case: Consulting Service</h4><p>Let’s say you are a business that provides a $6,000 consulting service over three months. The obvious choice would be to split up that payment into a monthly $2,000 payment over three months. But with Servicebot, you can tweak how much each payment should be. An easier sell to a potential customer would be making that first payment at $1000, giving them a chance to “try out” your service for a month before committing to the more expensive second and third month payments of $2,500.</p><h3>UI Redesign</h3><p>There are three major UI changes in the version 0.9 release. Each change was developed based on feedback and analytics.</p><h4>Request Form UI</h4><p>We improved the way customers interact with the request forms to be more embeddable and more in line with how an invoice looks, as well as making the request form easy to embed in any existing site for a seamless customer experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nddYh-_sZU_lJGKBGySBHg.png" /><figcaption>The new request form — also can be embedded easily in any site</figcaption></figure><h4>Admin Dashboard UI</h4><p>Our initial administrator dashboard page was very simple without any real data calculations. In our v0.9 release, we have added a whole new set of analytical calculations and designed an intuitive dashboard page to view this data. Charts are also included. This has been a major change in the v0.9 release, however, there are still more changes we would like to make to the dashboard for future releases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8LZuEj5u0T6FYbmV." /><figcaption>The new dashboard with more analytics</figcaption></figure><h4>New Theme</h4><p>Based on our hosted solution usage, we realized that most people didn’t change the initial black theme that Servicebot came with. Since the August 2017 release, the theme has been customizable using the system options on the system settings page. To make this change more apparent, we have added a new blue colored theme that comes with some usage guides. For example, the dashboard will walk admins through a three step process of setting up their Servicebot. We are looking to develop more pre-defined themes, which admins can choose without manually selecting system colors.</p><h3>What’s next?</h3><p>Our major milestones for 2018 and beyond are:</p><ul><li>Support for payment gateways other than Stripe</li><li>Improve the embeddability of request forms on existing apps (in progress)</li><li>Usage-based billing</li><li>Improve automated testing</li></ul><p>Our goal is to make it easy for businesses to sell subscriptions to customers through our open-source automation platform.</p><h4>Need to solve the challenges of subscription billing? You can try Servicebot free at <a href="https://servicebot.io/">https://servicebot.io</a></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6104453bbfdb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/servicebot-open-source-v0-9-webhooks-payment-scheduler-major-ui-changes-6104453bbfdb">Servicebot Open-Source v0.9: Webhooks, Payment Scheduler, Major UI Changes</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to manage SaaS subscription billing using Servicebot]]></title>
            <link>https://medium.com/hackernoon/how-to-manage-saas-subscription-billing-using-servicebot-open-source-4901301dfbe8?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4901301dfbe8</guid>
            <category><![CDATA[stripe]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[bot-services]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 09:56:00 GMT</pubDate>
            <atom:updated>2019-04-26T05:01:31.902Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nEG2QwijfpcBDaiYDKZbmg.png" /></figure><p>In this article I will explain how to use <a href="https://servicebot.io/">Servicebot</a>, a platform for automating <a href="https://hackernoon.com/tagged/saas">SaaS</a> billing. <a href="https://hackernoon.com/tagged/servicebot">Servicebot </a>is designed to be the billing engine enabling businesses to sell software as a service.</p><h3>Servicebot Manages the Subscription Lifecycle</h3><p>Being able to manage the <a href="https://medium.com/@ben_sears/understanding-the-lifecycle-of-a-saas-subscription-5169307fd0c8">subscription lifecycle</a> is paramount to selling a SaaS. This means having automated processes which react to specific billing events, such as subscribing or cancelling a service. Typically, subscription billing is made up of the following events:</p><ul><li><strong>Subscribe — </strong>A new customer signs up for your service.</li><li><strong>Trial Expiration — </strong>The free trial period expires and the customer is billed or access is restricted to the app.</li><li><strong>Upgrade/Downgrade — </strong>The customer changes their subscription to a differently priced tier of service. For example, upgrading to premium Netflix for access to ultra HD video at a higher price.</li><li><strong>Cancellation — </strong>The customer cancels their subscription.</li><li><strong>Resubscribe — </strong>A former customer returns to your service.</li></ul><p>The ability to set an application to react to these events (for example, restricting access if a free trial expires without a payment source), is the core to billing management for SaaS.</p><p>Servicebot is designed with this in mind and gives a company the ability to add business logic around these events.</p><h3>Service Templates and Service Instances</h3><p>Servicebot powers SaaS billing with two main constructs. The <strong>Service Template</strong>, containing the details of what customers are subscribing to, and the <strong>Service Instance</strong>, which represents the service a customer has subscribed to.</p><h4>Service Template</h4><p>The Service Template is the blueprint needed to deliver an application to a customer. The template contains details such as the pricing and field definitions the end customer needs to fill out. For example, a business may want to collect a phone number or other information when on-boarding new customers. Their service template would contain a required input field that needs to be filled out in order to create a new <strong>service instance</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyxEuzmHeLPd5pj3tiw0CA.png" /><figcaption>Setting up a Service Template’s payment details and tiering using Servicebot</figcaption></figure><h4>Service Instance</h4><p>Once a customer subscribes, a service instance is created based on the service template and the information they filled out. For SaaS billing, hooking into the lifecycle of the <strong>service instance</strong> is key. Instances can be upgraded, cancelled, or trialing — meaning all a company needs to do to implement billing is integrate their application with the different events that occur within Servicebot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*Qyakh15vgHds2_AAxLHLJA.png" /><figcaption>The Service Instance Information in Servicebot, details pricing, user inputted information</figcaption></figure><p>Here are some of the important features that make service instances a great fit for SaaS:</p><ul><li><strong>Upgrade capability — </strong>If a SaaS offering has different pricing tiers, modifying the tier will change the price and apply proper proration.</li><li><strong>Cancellation — </strong>Cancellation of a service instance should stop all subscriptions as well as restrict access in the SaaS.</li><li><strong>Custom Charges — </strong>If a SaaS offers professional services, or various one-time charges, a service instance can have charges applied to it and be paid automatically.</li><li><strong>Free trials — </strong>With free trials being one of the best ways to sell a product, service instances support the ability to offer a trial service, as well as the power to credit users with extra trial time.</li></ul><h3>Embeddable SaaS Subscription Form</h3><p>Servicebot makes it easy for you to embed forms to your website. Just copy and paste the code into your site and immediately start selling your product. All you need to do is specify what happens after a customer presses “subscribe.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nddYh-_sZU_lJGKBGySBHg.png" /><figcaption>Generate complex forms that you can embed in your site to easily onboard customers</figcaption></figure><h3>Embeddable Billing Management</h3><p>The other embeddable which Servicebot provides is an account management form. When you embed this in your SaaS, your customers can add their credit card, change their plan to a higher tier, cancel their subscription, or resubscribe. You just have to paste pre-generated code into your application and Servicebot takes care of the rest.</p><h3>Webhooks for Lifecycle Management</h3><p>One of the best ways to alert your app to billing changes, such as a trial expiring, is with webhooks. Webhooks allow apps to communicate real-time information to other apps. In this case, Servicebot would be providing your SaaS with billing information.</p><p>Using Servicebot, webhook endpoints can be defined so whenever a billing event occurs, the endpoint will be notified and action can be taken. For example: if a trial expires, a webhook will be sent to the SaaS and the customer can be locked out of the software until they pay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZxC0yrsQ1s2ZH35y_vWpOw.png" /><figcaption>Easily integrate with anything using Servicebot’s webhooks</figcaption></figure><h3>Conclusion</h3><p>We at Servicebot believe that the process of getting paid for your software should not be a difficult task. Many tools focus on the payment aspect of billing; Servicebot is different by focusing on the service being provided, making it much easier to tap into the subscription lifecycle.</p><h4>Need a billing solution for your SaaS? <a href="https://servicebot.io/contact">Let’s talk</a></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4901301dfbe8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-manage-saas-subscription-billing-using-servicebot-open-source-4901301dfbe8">How to manage SaaS subscription billing using Servicebot</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 5 Stages of a SaaS Subscription]]></title>
            <link>https://medium.com/free-code-camp/the-5-stages-of-a-saas-subscription-5169307fd0c8?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/5169307fd0c8</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Mon, 09 Apr 2018 04:34:53 GMT</pubDate>
            <atom:updated>2018-04-09T04:35:54.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*84sMP7J-xYwJZXk5." /><figcaption>Photo by <a href="https://unsplash.com/@gkumar2175?utm_source=medium&amp;utm_medium=referral">Ganapathy Kumar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This article will go into detail on what you need to automate in order for your SaaS company to have a functional subscription billing solution.</p><p>One of the problems SaaS companies face when selling subscriptions is connecting their application to a billing process.</p><p>Some of the things that are need to be considered are:</p><ul><li>How will cancellations be handled</li><li>Free trials</li><li>Granting access to new customers</li></ul><p>The challenge in managing these billing processes is handling these events, such as restricting access to an application when a trial expires or if there no longer has a valid funding source attached to an account.</p><h3>The SaaS Subscription Lifecycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5LMqoyX6p0MAbcV7ZdKwWg.png" /></figure><p>The process a customer goes through when doing business with a SaaS company can be broken down into the five events above. Managing these events is the key to integrating a billing system with a SaaS.</p><h4>Subscribe 📝</h4><p>This is the first stage in the journey a user takes with a subscription. In this step, the customer has just signed up for a subscription which needs to trigger an automated process.</p><p>The process generally looks something like this:</p><ol><li>A customer orders a subscription for your application.</li><li>The customer is granted access to your application.</li><li>After the trial period is over (if there is a free trial), the customer is charged on a recurring basis.</li></ol><p>From a DevOps perspective, these are considered “<strong>Day 1</strong>” operations. These are the steps that a service goes through after being requested in order to be considered “provisioned,” such as installation and configurations of software.</p><h4>Trialing ⏳</h4><p>In the trialing stage, a customer has subscribed to a service, but is not paying until their trial expires.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kqQncQAHAZNDCslsH9VpcQ.png" /></figure><p>Approximately <a href="https://www.chargify.com/blog/increase-free-trial-conversions/">75% of SaaS companies</a> offer free trials. Although free trials are almost guaranteed to bring you more paying customers, one of the trickier things about offering them is deciding what happens when a trial expires without a customer adding a funding source.</p><p>At this stage of the service lifecycle, a company will need to build logic around trials which will, upon expiration, restrict access to an application and alert the customer that they need to pay.</p><h4>Upgrade 👍</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z_J4G3jPmgWUNFvu8iSlSg.png" /><figcaption>Netflix offers different tiers</figcaption></figure><p>Many SaaS businesses support multiple tiers of service. If a customer pays a premium, they have access to additional features. This is considered a “<strong>Day 2</strong>” operation, actions which can be taken after a service has been provisioned which affect the end user.</p><p>Generally, it follows the pattern below:</p><ol><li>A customer submits a request to upgrade their subscription.</li><li>The customer’s subscription rate will be increased.</li><li>The customer will be granted access to new features within the application.</li></ol><p>While this usually takes the form of strict pricing tiers, sometimes customers pay “per user per month” or have “thresholds” which if passed will trigger higher rates.</p><h4>Cancellation ❌</h4><p>Inevitably, there will be cancellations of subscriptions, also called <a href="http://chaotic-flow.com/saas-metrics-faqs-what-is-churn/">churning</a>. The steps which occur in order to fulfill a cancellation go as follows:</p><ol><li>A customer requests a cancellation of a SaaS subscription.</li><li>They will no longer be charged on a recurring basis.</li><li>Access to the application will terminate at the end of the current billing cycle.</li></ol><p>Reaching out to your former customers after they have cancelled will also require some sort of process. It’s recommended that cancellation triggers a process which sends an automated email to the former customer, perhaps with an attempt to recover the customer or a feedback survey to see what reasons they may have had for canceling.</p><h4>Resubscribe ↪️</h4><p>When a former customer decides to return after canceling, a company can’t just go through the original process to subscribe them as a new customer — they need to reactivate the previously terminated access so that they retain all their former data. This process can be described in three steps:</p><ol><li>A customer resubscribes by adding a valid funding source to their account.</li><li>Access to the customer account and data is reactivated.</li><li>The customer will be charged on a recurring basis once more.</li></ol><p>Some complex scenarios might include limited time discount codes for resubscribers, a free trial, or part of another service as part of a combo deal.</p><h3>Conclusion</h3><p>The key to selling software-as-a-service is connecting software to a billing system that can support the lifecycle I just described. Being able to automate this process is a boon to businesses, since manual processes are one of the biggest barriers to scaling.</p><p>Trying to manage the challenges of SaaS billing? <a href="https://servicebot.io/contact">Let’s Talk</a>.</p><p>We solve challenges SaaS companies face when billing customers by providing easy to integrate hooks which can trigger automated processes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5169307fd0c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/the-5-stages-of-a-saas-subscription-5169307fd0c8">The 5 Stages of a SaaS Subscription</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to know if Kubernetes is right for your SaaS]]></title>
            <link>https://medium.com/free-code-camp/how-to-know-if-kubernetes-is-right-for-your-saas-315dfffe0a25?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/315dfffe0a25</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Sat, 03 Mar 2018 11:29:49 GMT</pubDate>
            <atom:updated>2018-03-03T11:29:49.605Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tJXXWOYkuMF3RkqZxMmvFw.png" /></figure><p>Kubernetes is an awesome technology, and I personally have seen great gains in my ability to scale, deploy, and manage my own SaaS because of it. But, not everyone would immediately benefit from adopting it for a number of reasons:</p><ul><li>Lack of familiarity with container technology</li><li>Application architecture not being conducive to utilizing the benefits of Kubernetes</li><li>Increased amount of effort versus time spent</li></ul><p>If you are interested in Kubernetes but aren’t sure about investing the time/resources needed, this article is for you.</p><h3>What is your experience with containers? 📦</h3><p>In order to understand what Kubernetes can do for you, you first need to know what benefits containers provide. Before spending time on Kubernetes you should first:</p><h4>Containerize your application</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*UPoxdocrOq6jG0okDQmGTA.png" /></figure><p>First and foremost, your application must be containerized. This means defining the steps needed to take a base OS image and install your application on it in a file (usually a Dockerfile).</p><p>Going through this process as well as defining environment variables needed to configure your application (such as the URL, username, and password of the database your app uses) will be critical to making your container image usable by Kubernetes.</p><p>Also make note of any dependencies your application needs to function and learn how to use the containerized versions of those.</p><h4><a href="https://docs.docker.com/engine/admin/volumes/">Understand how storage works</a></h4><p>Containers are designed to hold only the code needed to run an application. Any persistent data needs to be stored elsewhere, as the process of tearing down and spinning up containers (very common when dealing with containers) also destroys any data stored within the file system of that container.</p><p>Knowing how container storage is supposed to work and how to handle things like backing up data, moving that data between containers, and accessing the data from outside the container is very valuable when considering Kubernetes.</p><p>Kubernetes makes storage management easier with features such as auto-provisioning. This has the ability to have your storage provider (such as AWS EBS) create new volumes on the fly as new containers are created, automatically mounting them.</p><h4><a href="https://docs.docker.com/engine/userguide/networking/">Understand how networking works</a></h4><p>How you implement networking can play a large role in how you use Kubernetes. Knowing how to open specific systems to the public internet and hiding others, such as databases, while maintaining communication between services is important to understand for starters. Some more complicated operations which I’ve needed to learn were how to integrate load balancing as well as giving each customer’s instance a custom hostname (things which Kubernetes makes a lot easier).</p><h3>Does Kubernetes solve problems you are currently facing? 🔧</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*x19oVdiueoNINl-eZ6QUAg.png" /></figure><p>If you are not using containers to deploy your application, you probably shouldn’t be using Kubernetes yet. The problems Kubernetes aims to solve are problems that arise when you try and scale a container-based infrastructure.</p><p>Here are a few of the problems I think Kubernetes is great at solving when trying to deal with containers at scale.</p><h4>Scaling up resources</h4><p>Kubernetes is basically a cluster of nodes which provide compute resources that can be consumed by container workloads. This clustered architecture allows for a very easy scale-up or scale-down of resources. You just add or a remove nodes from the cluster, and Kubernetes will automatically utilize those resources or reassign workloads on your existing resources.</p><p>This solved a major problem I faced, because I went from having a single server I had to keep scaling up (an annoying manual process) to having the ability to scale up or down my infrastructure with a single command using the CLI.</p><h4>Performing mass updates</h4><p>Another problem that Kubernetes solves is the ability to update all your containers. Before, I was writing shell scripts which would pick each relevant container and recreate it using a new image tag. The process would take over an hour, and I had no way of validating that the update was successful. With Kubernetes I was able to perform an update with a single command as in the example below:</p><pre>// Update all the pods of frontend to a new image tage<strong><br></strong>$ kubectl rolling-update frontend --image=image:v2</pre><p>Kubernetes also allows you to update any part of Kubernetes (networks, storage, etc.) with commands based on any criteria. This is a huge step up from writing your own scripts to enact changes to your infrastructure.</p><h4>Self-healing</h4><p>The last and one of the most important pieces of Kubernetes I’d like to talk about is the ability to self-heal. If Kubernetes detects something wrong with part of its infrastructure, such as a node not responding or a container not passing its health check, it will perform steps to recreate those parts of itself until things start working again.</p><p>This is extremely useful because if a piece of the cluster goes down for any reason, the workload will be reassigned and you can even have Kubernetes recreate entire servers to fix the problem.</p><h3>Will your application architecture need to change?🚧</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*bCt6en9N-PHfVRCzSBrAHA.png" /><figcaption>Sometimes adapting your app to Kubernetes is like fitting a square peg in a round hole</figcaption></figure><p>When I migrated to Kubernetes, there weren’t that many changes I had to make because it was originally architected to be a multi-instance platform deployed via containers.</p><p>Here are some of the things I’ve learned while moving my own workload to Kubernetes.</p><h4>Startup time of your app is important</h4><p>When you create a new deployment, you have to wait for your app to start before it becomes available to the end-user. This becomes a problem if your deployment process involves creating new instances when an end-user presses a button or if you are performing updates on all your customers instances, as that requires a rebuild of the pods.</p><p>When moving to Kubernetes you may need to make some changes to your codebase to make the startup process more efficient so the end-user doesn’t have a degraded experience using your product.</p><h4>Adapting multi-tenant architectures is difficult</h4><p>A multi-tenant architecture means you have a single instance of your application which manages all your end-users in partitioned tenants, usually with a single database being shared between everyone.</p><p>If your application is not built to utilize clustering (multiple servers acting as a single instance) you should not be using Kubernetes yet.</p><p>Generally I see two types of architectures when working with Kubernetes:</p><ul><li>Multi-instance with one instance of the app for each customer</li><li>Multi-tenant architecture with clustering capabilities as they can utilize scaling up and down resources</li></ul><p>I personally prefer multi-instance because they are much easier to implement compared to a clustered multi-tenant architecture. Also, the work involved in moving from multi-tenant to multi-instance isn’t too bad compared to adding cluster capabilities to a multi-instance architecture.</p><h4>Moving to a stateless application is a large amount of effort</h4><p>One of the great features of Kubernetes is the ability to scale up or down the number of pods in a deployment. But, if your application is not clustered or not stateless, this functionality is wasted since extra pods in a deployment wont be configured properly and can’t be utilized.</p><p>The process of utilizing statelessness in Kubernetes is often more trouble than it’s worth, since most times you will need to completely rework the way you handle configurations within your application.</p><p>Don’t be discouraged if you don’t want to spend the time to make your application stateless or clustered as there are many ways of adapting stateful deployments to use Kubernetes. But those have their own problems which I will not get into in this article.</p><h3>Should you adopt Kubernetes? 🚢</h3><p>After asking yourself these questions, you should have a pretty good idea if Kubernetes will be a good fit for you at this time. Most early stage startups are probably not going to need it, and more mature ones may have a lot of investment in other technologies so it wouldn’t be feasible to switch.</p><p>I think the best case for someone moving to Kubernetes is a startup looking to move from having a Minimum Viable cloud infrastructure that is using containers to power production workloads to something more stable. That was my case, and I can say I went from having periodic downtimes due to resource mismanagement and overworked servers to not having to worry at all about my infrastructure thanks to the power of Kubernetes.</p><p>Looking to connect Kubernetes to your SaaS? Lets talk - <a href="/service/mailto:ben@servicebot.io">ben@servicebot.io</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*MEXGx_BgpHlbweOcuPBUZw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=315dfffe0a25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/how-to-know-if-kubernetes-is-right-for-your-saas-315dfffe0a25">How to know if Kubernetes is right for your SaaS</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Build and Scale Your SaaS Billing Solution]]></title>
            <link>https://medium.com/free-code-camp/how-to-build-and-scale-your-saas-billing-solution-d6111b9ae253?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6111b9ae253</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 21:12:45 GMT</pubDate>
            <atom:updated>2018-02-26T21:28:37.039Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tnIp6GZjyfJRU2sCnea_tA.png" /></figure><h3>What you need for a Minimum Viable Product</h3><p>When you are building your Software as a Service (Saas) Minimum Viable Product (MVP), there is <strong>a lot</strong> of work that needs to be done. It can be difficult to balance this workload.</p><p>Oftentimes you are so focused on developing the product that you forget that you still need to sell it to people. This guide is meant to help you get your billing system off the ground to start making revenue, and show what you should be doing when you are ready to scale up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mir-VAoZAqfyV14jSQN8VA.png" /><figcaption>Like the functionality of your product, your billing system should scale as you grow</figcaption></figure><h4>Subscriptions</h4><p>Subscriptions are key to an effective billing strategy. The ability to charge a credit card on a recurring basis makes payment more efficient for both you and the customer.</p><p>To start selling subscriptions to your clients, you need:</p><ul><li>A form users can fill out to enter their credit card</li><li>A backend process that can be called after the payment is successful</li></ul><p>If you don’t have the development cycles to do this, you will be stuck with a painful process of sending invoices manually, giving customers access manually, and adding friction to the on-boarding process.</p><h4>Free Trials</h4><blockquote>For many SaaS companies, 100% of their customers come in through their Free trial system. — <a href="https://sixteenventures.com/saas-free-trial-benchmarks">Lincoln Murphy</a></blockquote><p>Offering free trials is considered by many to be one of the best ways to find early adopters of your SaaS.</p><p>When someone is given the opportunity to try your product before committing to a subscription, they are far more likely to become a regular customer.</p><p>It is good practice to treat your trial users with the same level of support and respect as you would your paying customers. Not only are they experiencing your product, they are also experiencing the quality of your service.</p><h4>What to integrate with</h4><p>At the end of the day, you will end up integrating with an external system to handle these use cases. I highly recommend looking at <a href="https://stripe.com/"><strong>Stripe</strong></a> because they have an excellent API to integrate with and a wide range of functionalities.</p><p>If you don’t want to develop the integration with Stripe yourself, take a look at <a href="http://bit.ly/2CbF5FE"><strong>Servicebot</strong></a> — It comes fully integrated with Stripe and has great Customer Relationship Management (CRM) functionality so you can better manage your customers and subscriptions from a dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*osFh-QjsiHZxCL-npeSMDQ.png" /><figcaption>Designing a service in <a href="https://servicebot.io/">https://servicebot.io</a></figcaption></figure><h3>Automation is the key to scaling</h3><p>During your early stages, <a href="http://www.ycombinator.com/">Y Combinator</a> founder Paul Graham says, “<a href="http://paulgraham.com/ds.html">Do things that don’t scale.</a>” Although this may sound counter-intuitive, this is the best way to grow your customer base before you begin to even think about scaling.</p><p>What scaling boils down to is automating the manual processes you’ve found to be effective at growing your startup.</p><p>When you’re ready to scale your billing solution, here are a few things to consider:</p><h4>Billing Process Automation</h4><p>Automating the processes involved with billing — such as what happens when a user requests a trial, adds a funding source, or requests a cancellation — is one of the most important parts of scaling your billing solution.</p><p>You should first take a look at how you are currently doing your billing. Identify all the manual processes that currently are a part of your system, like restricting access if trials expire or reactivating accounts after they’ve been cancelled. Once you make that list you can start figuring out how much time is spent performing these and start iterating to reduce the most painful parts.</p><p>Another big part of automating your process is automating customer outreach based on their status in the billing system.</p><h4>Automatic customer outreach</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vM12EvwZbOkio09fK_nDkw.png" /></figure><p>Customer outreach is key to converting customers from free trials to paid. When starting out, this process is mostly manual. Email people when they sign up, remind them when their trial is ending soon, or ask if they need help getting started.</p><p>This is not scalable — you need to eventually automate this process, and the best place to focus on is the billing side because so many steps are processed there</p><ul><li><strong>On-boarding</strong> — When a new user signs up, your system should automatically send an email explaining how to get started. <br>More advanced systems follow the customer’s journey and send specific help articles for things they haven’t done yet.</li><li><strong>Trial Conversion</strong> — When a trial is created, there are a few things that should be sent to the user to convince them to convert. Things like a “3 days left” reminder or a message asking for a 1-on-1 call can really make the difference. <br>Automating these messages is important to insure scalability.</li><li><strong>Lead recovery</strong> — When a trial expires or a user cancels, all is not lost. Sending emails a specific duration after they leave explaining new features, asking for feedback of what you can do better, and articles about your product may be enough to bring them back around to give you another chance.</li></ul><p>To ensure seamless communication between your system and the customer, it is important for your system to be tightly integrated with your billing.</p><h3>Integrating with other systems</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDm4rtQefJUjG5pcfqvRfw.png" /></figure><p>One of the best ways to automate your businesses with minimum development effort is to integrate with third-parties who have already solved the problems you are facing.</p><p>Here are my favorites which I’m using for my own SaaS startup:</p><h4>Stripe — Payment processing</h4><p>Stripe has become the staple of SaaS payment providers. With a developer-friendly API and constant new features, I (and countless others) feel it’s an obvious integration point.</p><p>Some of the features you can integrate with to automate more of your billing are:</p><ul><li>Webhooks to alert your system of failed payments</li><li>No credit card free trials</li><li>Add charges to existing subscriptions</li></ul><p>There is much more you can do with Stripe, it should be up to you and your startup’s needs to determine how deep of an integration you need.</p><h4>Intercom — Communication automation</h4><p>The staple of <a href="https://www.intercom.com/">Intercom</a> is the live chat widget that you embed on your site to enable communication with your customers. What many people don’t realize is that Intercom also provides an automation platform. If you integrate with Intercom, you can send customized messages to your customer based on what they do with your product.</p><p>This allows you to automate the communication with your customer so you don’t have to manually email anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7AoIRo4Bw7Uttk3cDY1P4w.png" /><figcaption>Example of intercom outreach automation</figcaption></figure><h4>Servicebot — Subscription Management</h4><p><a href="https://servicebot.io/#1">Servicebot</a> comes out-of-the-box with a Stripe and Intercom integration. When a customer requests a free trial, Servicebot creates a new trialing subscription and customer in Stripe and a new user in Intercom, and directs them to a newly-created instance to use.</p><p>Intercom will send automated messages with the goal of converting to a paying user while Stripe will manage the subscription automatically.</p><p>A good first step to begin scaling is with automating your billing process. When it all comes together, you can connect parts of your business to a centralized location, as well as integrate it with third parties. The result of all this will be massive gains in productivity and efficiency that make the effort well worth it.</p><p>If you are interested in automating parts of your SaaS billing solution to do things like automate customer on-boarding and connecting business processes to your billing system, <a href="https://servicebot.io/contact">Let’s talk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6111b9ae253" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/how-to-build-and-scale-your-saas-billing-solution-d6111b9ae253">How To Build and Scale Your SaaS Billing Solution</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make recurring revenue as a freelancer]]></title>
            <link>https://medium.com/swlh/how-to-make-recurring-revenue-as-a-freelancer-7c6112229789?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c6112229789</guid>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Fri, 16 Feb 2018 17:37:12 GMT</pubDate>
            <atom:updated>2018-02-16T17:37:12.696Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*nTEjAhpF5ZH1qVOGDq3UHQ.gif" /></figure><p>As a freelancer, one of the biggest problems you face is keeping your income stream consistent. You are always searching for the next gig to pay the bills and the periods of time you have nothing lined up can be incredibly stressful. Offering subscription services solve this problem as well as opens the door to much more lucrative business opportunities.</p><p>In this article we will explore what makes subscriptions great and how freelancers can tap into the business model.</p><h3>Why Subscriptions?</h3><blockquote>Subscription programs are a particularly effective way to turn one-time buyers into loyal customers and increase customer lifetime value by 200–400%<br>— <a href="https://nrf.com/resources/retail-library/unleashing-the-power-of-subscription-commerce-industry-overview-insights">OrderGroove</a></blockquote><p>There are many aspects of the subscription business model that are appealing. Freelancers who focus on their subscription offerings experience a much more predictable stream of income, more customers, and make more money overall because of it.</p><h4>Increased customer lifetime value 📈</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zTt7cjnAqaZO23bKfFwtyg.png" /><figcaption>Repeat customers are worth a lot more to your business over time</figcaption></figure><p>According to the <a href="https://success.adobe.com/assets/en/downloads/whitepaper/13926.digital_index_loyal_shoppers_report.pdf">Adobe Digital Index</a>, <strong>40% of revenue</strong> comes from returning or repeat purchasers, who represent <strong>only 8% of all visitors</strong>. Repeat customers are worth much more to a company than one-offs and one of the best ways to get repeat purchasers is to sell them subscriptions.</p><p>Being able to have customers over a long period of time gives you more opportunities to sell them on your other services and upsell them as they grow along with you.</p><h4>Predictable income 🔮</h4><p>The unpredictability of income is one of the hardest parts of being a freelancer.</p><p>When you start selling your services as subscriptions, your income becomes more stable as you are guaranteed a certain amount each month. This gives yourself peace of mind and as well as insight into what your workload is going to look like at any given time, allowing you to manage your time effectively between delivering services and looking for new customers.</p><h4>More customers 👨‍👩‍👧‍👧</h4><p>Customers love the subscription model; they gain more control over their interactions with businesses and get billed automatically, and you as a business owner benefit from a steady income.</p><blockquote>“In the month of April 2017, subscription company websites had about 37 million visitors. Since 2014, that number has grown by over 800%.” — <a href="https://www.forbes.com/sites/richardkestenbaum/2017/08/10/subscription-businesses-are-exploding-with-growth/#4aab5f486678">Forbes</a></blockquote><p>Being able to utilize new marketing tools such as free trials and tiered pricing makes the barrier to entry much lower compared to traditional freelance business models that offer quoted pricing.</p><h3>How to sell subscription services</h3><h4>Productize your services 📦</h4><p>One of the key points of a subscription service is the “Deliverables”; what the customer will get each month. For example, a freelance blog writer may charge $100 for 3 blogs each month as part of their service, or a growth hacker might offer a set number of videos and social media posts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*guAsj_VQPxUNQnqitvHIXg.png" /><figcaption>Selling services as easy to consume “boxes” is important when selling subscriptions</figcaption></figure><p>The first step to growing your recurring revenue is to design your service offering as something that can be tiered into different pricing levels. This is useful to the customer if they have different “packages” they can choose from, so that they are not paying extra for features they do not want. Be specific with your product descriptions to ensure the customer is aware of exactly what will be delivered to them.</p><h4>Give out free trials 🎁</h4><p>Free trials are a great way to show potential customers the value you have to offer. The best SaaS businesses can expect to see <a href="https://sixteenventures.com/saas-free-trial-benchmarks"><strong>over 60% of their trial users </strong></a><strong>convert to paid users</strong>.</p><p>A strategy for those businesses that can’t afford to give free trials to everyone should consider offering free trials of their higher tiered services to existing customers. Show them what they can get if they pay you more money and the trust you have already built will often be an easy sale.</p><h4>Offer different pricing tiers 📶</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ctY5GxbouoYTUBFexNuYgw.png" /><figcaption>Customers enter the ladder through cheap services and spend more as they trust you to provide value</figcaption></figure><p>Being able to have pricing anyone can afford is one of the best reasons to sell subscriptions. Selling different services at different prices allows you to build a “value ladder”. The value ladder is a classic marketing strategy where customers are enticed to your business through free or very cheap services and as they gain value from these they become more willing to spend more money on services that promise higher value. Offering a wide range of priced services allows you to gain trust and later upsell on your higher value services.</p><h3>What do you need to start?</h3><p>The only major barrier to entry when it comes to selling subscriptions is the platform you use. Make sure you can support functionalities such as free trials and automatic billing to get the most out of the subscription model.</p><h3><a href="http://bit.ly/2E9BmpE">ServiceBot</a> gives you all the tools you need to sell subscriptions, <a href="http://bit.ly/2E9BmpE">Try it out for free</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*cYNxPlG5jBa53Ms4SW6Zdg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gfnVvkMRFtjVsWF7vkClA.png" /></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by 297,332+ people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gfnVvkMRFtjVsWF7vkClA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c6112229789" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-to-make-recurring-revenue-as-a-freelancer-7c6112229789">How to make recurring revenue as a freelancer</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You need to be selling subscription services]]></title>
            <link>https://medium.com/swlh/you-need-to-be-selling-subscription-services-f651fc53ce88?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f651fc53ce88</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Tue, 06 Feb 2018 18:06:18 GMT</pubDate>
            <atom:updated>2018-02-06T18:06:18.278Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X2F6-fawH23QTs8DCXGvWA.png" /></figure><p>Not too long ago, software was almost always sold as a piece of software you purchased at a store and installed on your computer to run. Today almost all software is sold as a subscription service on the cloud.</p><p>It hasn’t stopped with software, everything is now available as a subscription service.</p><h4><a href="https://www.forbes.com/sites/richardkestenbaum/2017/08/10/subscription-businesses-are-exploding-with-growth/#4aab5f486678">From Forbes</a></h4><blockquote>In the month of April 2017, subscription company websites had about 37 million visitors. Since 2014, that number has grown by over 800%.</blockquote><p>If you are a business owner you should look at moving to this model or risk losing out on major benefits that can be gained from selling your services as subscriptions.</p><p>The Subscription model gives you more predictable income, more value out of your customers, and more opportunities to upsell on premium packages.</p><h3>Why should you be selling your services as a subscription?</h3><p>Businesses who switch to a subscription model generally see three main benefits right away.</p><h4>Predictable Income Stream</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NHm_dx8TZ-PHBCc8dWau7A.png" /></figure><p>One of the biggest complaints of people trying to start service-based businesses is the unpredictability of income. They aren’t always sure when the next project will come and can go periods of time without making any money.</p><p>When they move to a subscription model, a lot of this instability goes away as you are guaranteed a certain amount each month. This is not only a great way to give yourself peace of mind but is also a good indicator of what your workload is going to look like at any given time, allowing you to allocate resources optimally.</p><p>You also stop chasing down clients to pay their invoices as the money gets deducted from their accounts automatically each month, putting payment responsibility on the customer’s shoulders instead of your own, saving you time.</p><h4>Increased Upselling potential</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*u58xrD8fgdjPKZe9Umiqzg.png" /></figure><p>When a customer subscribes to your service, you get an opportunity to show them your quality. One of the biggest barriers to people pulling the trigger on expensive services is trust, they do not trust they are going to get the value being promised to them. As a business selling cheap subscriptions, you can show your customers they can trust you with more expensive items by being given the opportunity to build great relationships with them.</p><p>A few tips on how to upsell customers while using a subscription model:</p><ul><li>Give current customers free trials of premium services to give them a sample of your more expensive solutions</li><li>Inform your customers on related services they may be interested in.</li><li>Put gates on your tiers so when your customers are doing well, they will need to upgrade, for example a SaaS company may price their subscription options based on number of paying customers.</li><li>Give customers a large discount for purchasing annual subscriptions, a year commitment is a very valuable asset.</li></ul><h4>Data driven business</h4><p>One of the best things about selling subscriptions is the amount of data you can utilize to make decisions. You can accurately gauge marketing efforts immediate through the number of subscribers gained as well as how your decisions impact the services you provide by looking at the churn rate.</p><p>The more information you arm yourself with the better decisions you will be able to make.</p><p>When using subscription data to make decisions:</p><ul><li>Keep track of your MRR (Monthly recurring revenue) and ARR (annual recurring revenue)</li><li>Make sure paid advertising is netting you more than you are spending, pay close attention to the conversion rate</li><li>Ask customers for feedback on what they like and dislike about your service to reduce churn.</li></ul><h3>How do you get started selling subscriptions?</h3><p>If you want to sell subscription services but don’t know how to start,</p><h4>Find a platform to sell your services</h4><p>Not everyone’s website will support the “ideal” set of features needed to start selling subscription services, be sure that you can get the following features for the best experience for both you and your potential customers.</p><ul><li><strong>Automatic billing</strong> — This is a must, being able to put in a credit card and be charged on a monthly basis is the core of any subscription business.</li><li><strong>Advanced forms</strong> — Depending on your business model, the data which your potential customers need to input could get quite complex, especially if they impact billing.</li><li><strong>Free trials</strong> — Giving customers a trial of your service is a good way to gain the trust of your clients, if you want to get people in the door, giving something out for free almost always works.</li></ul><p>If you don’t have all of these features with your current website, check out <a href="http://bit.ly/2nEIkN3">ServiceBot</a>, a platform which makes selling subscription services extremely easy.</p><h4>Design your services</h4><p>The first step to selling a service as a subscription is to design a “productized” version of your service. This boils down to coming up with a standardized package of features to be delivered each payment cycle.</p><p>This will give the customer a good idea of what will be delivered and will also keep your workload predictable due to having standardized the amount of work (eliminating scope creep)</p><p>Here are a couple of tips to keep in mind</p><ul><li><strong>Offer options for any budget</strong></li><li><strong>Offer free trials, especially when just starting out, to encourage early adopters and build trust.</strong></li><li><strong>Show your commitment to quality early and often, happy customers will stay with you and spend more money in the future</strong></li></ul><h3>The results speak for themselves</h3><h4>In the US, <a href="https://success.adobe.com/assets/en/downloads/whitepaper/13926.digital_index_loyal_shoppers_report.pdf">40% of revenue comes from returning or repeat purchasers</a>, who represent only 8% of all visitors</h4><p>Moving to a subscription model is good for your business by tapping into the growing subscription economy. It’s good for you by giving you a predictable revenue stream and workload. It’s also good for your customers, by giving them more control over how they spend money and gives them a chance to build trust with businesses before pulling the trigger on more expensive engagements.</p><h3>Looking to start selling subscription services? <a href="http://bit.ly/2nEIkN3">Try out ServiceBot</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gfnVvkMRFtjVsWF7vkClA.png" /></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by 293,189+ people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gfnVvkMRFtjVsWF7vkClA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f651fc53ce88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/you-need-to-be-selling-subscription-services-f651fc53ce88">You need to be selling subscription services</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with Kubernetes for your SaaS]]></title>
            <link>https://medium.com/free-code-camp/getting-started-with-kubernetes-for-your-saas-91e91116dd7d?source=rss-edd57178d1c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/91e91116dd7d</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Ben Sears]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 16:21:53 GMT</pubDate>
            <atom:updated>2018-01-29T16:21:53.223Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZx56ZEx75a9_xlC1smdOQ.png" /></figure><p><a href="https://kubernetes.io/">Kubernetes</a> is a platform to manage and orchestrate your cloud infrastructure. It provides a configuration-driven framework where you can define a few different pieces and with one click get an entire network, disk, and application spun up in a way that’s scalable and easy to manage.</p><p>Moving your application over to Kubernetes is a high-effort activity if you haven’t designed your app with containers in mind from the start. The goal of this article is to help you on your path towards containerizing your applications with Kubernetes integration in mind.</p><p>Be aware that if you try and force your application into Kubernetes without the proper architecture, you will be essentially shooting yourself in the foot by wasting time and accruing technical debt.</p><h3>Step 1 — Containerize your application 📦</h3><p>A container is basically a partitioned section of the operating system that can function as an independent machine. Unlike traditional virtual machines, which rely on a hypervisor to simulate an operating system, containers use a variety of kernel features to provide an environment isolated from the host machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yn1HpaQO2QVRrMrJ7rjLHw.png" /><figcaption>Containerized apps can run predictably on all machines, not just yours</figcaption></figure><p>Containerization is a fairly simple process — using Docker, just define a Dockerfile which lays out the steps needed to install your application on an OS (download packages, install dependencies, and so on).</p><p>Then, build an image which can be used by developers. More information about the containerization process can be found on <a href="https://docs.docker.com/engine/examples/">Docker’s website</a>.</p><h3>Step 2 — Adopt a multi-instance architecture 🔠</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*umRbD6euqnJI4PRESEwOAQ.png" /><figcaption>The decision to go with multi-tenant or multi-instance architecture will take you down different paths</figcaption></figure><p>Before you move to Kubernetes, you need to take a hard look at the current way you deliver your application to the end-user.</p><p>Traditional web applications use a <strong>multi-tenant</strong> architecture. This means all your users will be sharing a single database instance and a single instance of an application. This can be made to work in Kubernetes — however, I urge you to consider implementing a <strong>multi-instance</strong> architecture to fully utilize the power of Kubernetes and containerized applications.</p><p>Some major benefits of adopting a multi-instance architecture are:</p><ul><li><strong>Stability</strong>— Instead of a single point of failure (the single application instance), each customer can exist in their own instance. If one instance fails, the others will remain unaffected.</li><li><strong>Scalability — </strong>With a multi-instance architecture, scaling up is a simple matter of adding more resources. However, with a multi-tenant architecture, you could reach a point where you need to come up with a clustered application architecture whose deployment is usually far from trivial.</li><li><strong>Security</strong> — When you are using a single database, all your data lives together. This becomes a major problem in the event of a security breach because all customers’ data can become vulnerable when a single account is compromised. With a multi-instance architecture, only a single customer’s data can be at risk.</li></ul><h3>Step 3— Determine your app’s resource consumption ⛽</h3><p>In order to have the most cost-effective infrastructure, you need to pin down how much CPU, memory, and storage are going to be required to run a single instance of your application.</p><p>This way, you can set limits so you can get an accurate reading of how much space your Kubernetes nodes need, as well as making sure your nodes aren’t going to become overloaded and unreliable.</p><p>This is usually a trial-and-error process, but you can use a monitoring solution such as <a href="https://github.com/kubernetes/heapster/">Heapster</a> to give a straightforward breakdown of the resources your pods are consuming. This will let you gauge how much to allocate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*09ZFxIZp9Dec7D--6UfPxg.png" /><figcaption>Heapster provides visualizations for your workload’s resource usage</figcaption></figure><p>After you figure out your resource allocation, you can calculate optimal server sizes for your Kubernetes nodes so you get the most bang for your buck.</p><p>You take the memory or CPU each instance needs to function, and multiply it by 100 (the maximum number of pods a node can hold). This will give you a ballpark estimate of how much memory/CPU your nodes should have.</p><p>Still, you should always stress test your application to ensure it runs smoothly when the node fills up.</p><h3>Step 4— Integrate with Kubernetes ⚙️</h3><p>Once your Kubernetes cluster is up and running, there are a lot of DevOps practices you can begin developing to make your life easier. Some of these integration points take the following forms:</p><h4>Automatic scaling of Kubernetes nodes</h4><p>When your nodes become full, generally you want to provision more nodes so everything can keep chugging along smoothly. One way you can do this is with a tool like <a href="https://github.com/kubernetes/kops">kops</a>.</p><h4>Automatic scaling of applications</h4><p>Some applications will need to be scaled up or down based on the current usage. Kubernetes provides this function out of the box using triggers which automatically scale deployments. For example, running this command:</p><pre>kubectl autoscale deployment myapp --cpu-percent=50 --min=1 --max=10</pre><p>will set the <em>myapp </em>deployment to scale up to 10 pods when the CPU percentage goes above 50.</p><h4>Automatic provisioning of instances upon user action</h4><p>For a multi-instance architecture, end-users will ultimately be requesting applications be deployed in Kubernetes. To provide this, you should be looking at integrating your app with the <a href="https://kubernetes.io/docs/api-reference/v1.9/">Kubernetes API</a>, or using a third-party solution such as <a href="https://servicebot.io/">ServiceBot</a> to provide a portal to request instances.</p><h4>Custom Hostname definition by user action</h4><p>A growing trend lately has been end-users attaching their domain to applications. Kubernetes has tools in place to make this process easier and even get to the point where it becomes self-service (users pressing a button to get their domain pointing to the pod). You can use a system such as <a href="https://github.com/kubernetes/ingress-nginx">Nginx Ingress</a> to accomplish this.</p><h3>Conclusion</h3><p>Kubernetes is a great way to manage your cloud infrastructure. If you are in a position where you are having trouble scaling your application, consider moving to a Kubernetes-based architecture. You will see a large increase in your DevOps productivity when it comes to deployments, clustering, and overall stability.</p><p><a href="https://servicebot.io/"><em>ServiceBot</em></a><em> is a platform that helps you manage your SaaS by automating billing, deployments, and your sales pipeline.</em></p><h4>Are you looking to scale up your SaaS? <a href="http://bit.ly/sbotconsult">Let’s talk</a>.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91e91116dd7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/getting-started-with-kubernetes-for-your-saas-91e91116dd7d">Getting started with Kubernetes for your SaaS</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>