<?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 Jake Peters on Medium]]></title>
        <description><![CDATA[Stories by Jake Peters on Medium]]></description>
        <link>https://medium.com/@jakeapeters?source=rss-5f0988ea2f85------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*nCtUdzkXStGo8DbLqs5SFg.jpeg</url>
            <title>Stories by Jake Peters on Medium</title>
            <link>https://medium.com/@jakeapeters?source=rss-5f0988ea2f85------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:22:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jakeapeters/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[Why We’re Forcing Ourselves to Stop Rebuilding Our Product]]></title>
            <link>https://medium.com/helpdocs/why-were-forcing-ourselves-to-stop-rebuilding-our-product-54da68235466?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/54da68235466</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Thu, 18 Jan 2018 16:00:00 GMT</pubDate>
            <atom:updated>2018-01-25T13:09:25.639Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T9MKy75INjan-JskGIfXMg.png" /></figure><p>As a technical founder it’s my job to prioritize what to build, what to improve, and what to chuck away. A.k.a managing “the roadmap”.</p><p>When you’re working inside the product day-to-day, just how do you decide what needs the most attention? We’re a bootstrapped <a href="https://www.helpdocs.io/about/">team of three</a> so our resources are pretty slim.</p><p>And while we’re laser-focused on building and shipping great product, we’re also perfectionists. I’ve learned in the last few years that this combination can be deadly.</p><p>I’m sure I can’t be the only maker that sees their product and just wants to improve what’s already there. It’s <em>never</em> good enough for me and wanting to improve the existing product is part of my process.</p><p>So while making the service faster, more reliable, and easier to use might be great for our users, it’s not so great for our emotional wellbeing. And not for our bottom line, either.</p><p>It’s difficult for us to not try and fix things that aren’t perfect, but also aren’t actually broken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FvwxDmbXkEOtqmmp.png" /></figure><p>But trying to fix what’s not broken means we neglect our marketing. That means we’re letting our customers down in some areas. When we’re rebuilding, we’re not <strong>building</strong>. New features aren’t getting released.</p><p>I’m gonna tell you about the mistakes we’ve made. What’s gone totally awry. Why we’ve gone down certain rabbit holes only to find more, but ultimately stuck with it and made it out the other end with something brilliant.</p><p>But mostly I’m gonna tell you about how we failed so you can watch out for chasing perfection yourself.</p><h3>Time to change our stack?</h3><p>At every startup, there comes a point where you need to think about scale and the technologies you use. Some questions come to mind:</p><ul><li>Is the tech stack I’m currently using gonna cut it or will it slow everything down?</li><li>Is it better to rebuild for the future now rather than panicking and doing it wrong in a few months time?</li><li>Is my current stack even going to be supported in a years time?</li></ul><p>Around 6 months back we came to this crossroads.</p><p>I hacked together our initial frontend in Angular 1 (for non-technical folks, that’s something that was cool 3 years ago — today not so much). I’d kept relatively up to date with security patches and updates, built out a bunch of developer tooling to make building Angular fun tolerable.</p><p>Our largest customer at the time had a few hundred articles. And Angular was flying. I couldn’t understand why everyone was so hard on it — for us it was perfect.</p><p><strong>…until it wasn’t</strong>.</p><p>We started onboarding larger and larger accounts. Our frontend rendering starting slowing. Was this the start of the end for our current tech stack?</p><p>At this point, our largest account now has over 5000 articles. And Angular’s not happy. Not one bit. We couldn’t cope with customers this size. We accepted them prematurely. Partly through greed (they’re big accounts) but mostly naivety.</p><p>We literally didn’t realize how much our platform would struggle.</p><h3>Optimize or die</h3><p>Now, I know what you’re thinking. There’s ways to optimize everything. I feel ‘ya. And we tried.</p><p>But at the end of the day after 3 years of my life working with Angular I didn’t really <strong>want</strong> to spend any more time time hacking around its flaws. Angular was never the right tool for the job. It was just what I knew best. I decided it was time to jump ship.</p><p>Instead of making an informed tech decision I focused on speed of development. That was, in retrospect, dumb. Better to take a couple weeks learning something more appropriate for the job.</p><p>I’d heard about React, Vue, Angular 2 3 4 5, and I wanted something new and modern. Something that was heavily supported and had a great developer community.</p><p>In the end we chose React. It’s a great fit for us, since we display a ton of data at a time. It’s a pleasure to write, and the dev tooling’s stellar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ODMDw3NylKIMgizD.png" /></figure><p>We started the rewrite. Like any developer, I was cocky at the beginning. I thought it’d take maybe a month. Probably less. Easy.</p><p>It took 6 months.</p><p>Only maybe 2.5 of those were actually working on React. And I’ll be honest — rewriting this app broke me.</p><p>I totally gave up. I stopped working on it for weeks at a time (focusing on literally <em>any other HelpDocs task I could find</em> instead). But eventually, 6 months down the line we’ve shipped it. And I have to say, it’s pretty darn awesome.</p><h3>We made a bunch of mistakes, but one was the worst</h3><p>Right at the start I decided — against the advice of several incredibly smart peers and colleagues — to do a <strong>big bang rewrite</strong>. I’d branch off our code, write the whole app in React, then merge back in a couple weeks. How hard could it be?</p><p>Don’t do this.</p><p>That’s the <strong>single biggest reason</strong> this project was so soul-destroying.</p><p>Before HelpDocs I’d only <em>ever</em> done rewrites like this. Even at the start of our journey with this product I’d always rewritten things all at once.</p><p>It’s always been fine, because the scope of the projects has been small. But now we have a fairly significant codebase things aren’t so easy.</p><p>Making small changes takes a little while. Making big changes like this? <strong>Forever</strong>.</p><p>And with a big bang rewrite, we had all this React code hanging around in progress, but the only thing customers were integrating with was the old Angular.</p><p>Any bugs we fixed had to be fixed in Angular once, then again in React. Any new features had to be implemented twice.</p><p>It was hell.</p><h3>Why carry on?</h3><p>Now that I’ve waxed lyrical about how awful an experience it was, you might be wondering <em>why</em> we bothered at all. I mean, once I realized it was going to hell, we could’a stopped.</p><p>The problem is, we’re product perfectionists. Marketing and sales we’re not so great at, but product is our baby. We love building products that make customers happy. And we weren’t proud of what we had.</p><p>Eventually our customers wouldn’t be happy with it either. And if there’s one thing I care about more than my own happiness, it’s theirs.</p><p>I’ve used enough terrible web apps before to know I don’t want HelpDocs be one of them.</p><p>We wanted to add a bunch of new things, and fighting against my former self’s poor framework choice was counterproductive.</p><p>Adding new features in React will save us a ton of time. And from now on we can ship quicker than ever.</p><h3>Time to stop rebuilding and start shipping</h3><p>Despite all the heartache of rebuilding our admin app in React, I’d totally do it again. But the biggest lesson I learnt is to tone it down a little.</p><p>Don’t go all in, especially when you’re scaling at the same time. Instead, rewrite a little at a time. It may take longer, but having the flexibility to transition parts of our app when we wanted would’ve been a weight off of our minds.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMo_802xujzQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMo_802xujzQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMo_802xujzQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1291b781e1fc0a36372b5ed2424e6300/href">https://medium.com/media/1291b781e1fc0a36372b5ed2424e6300/href</a></iframe><p>Now we’ve got a solid, modern, framework to build our app on top of, it’s time to get shipping. Stay tuned to see what we build next.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/"><em>The HelpDocs Blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54da68235466" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/why-were-forcing-ourselves-to-stop-rebuilding-our-product-54da68235466">Why We’re Forcing Ourselves to Stop Rebuilding Our Product</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We’re Rejecting Freemium and Building a Sustainable Business Instead]]></title>
            <link>https://medium.com/helpdocs/why-were-rejecting-freemium-and-building-a-sustainable-business-instead-4b590d540517?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b590d540517</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[freemium]]></category>
            <category><![CDATA[pricing]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Wed, 30 Aug 2017 08:00:00 GMT</pubDate>
            <atom:updated>2017-09-02T08:17:23.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ElqHjclhVxt5hM8m73gGA.png" /></figure><p>Startup pricing’s a touchy subject. Nobody’s quite sure <a href="https://news.ycombinator.com/item?id=13840282">how to do it best</a>. And at the end of the day it’s very dependent on your exact situation. But the general consensus is to just double your prices.</p><h3>Patrick McKenzie on Twitter</h3><p>Marc Andreessen answered questions from Atlas startups: https://t.co/K4PbNSo9vv My favorite bit of advice was regarding SaaS pricing.</p><p>Recently we did (almost) just that, and released <a href="https://www.helpdocs.io/pricing?ref=freemiumblogpost">a couple new plans</a> with slightly different features, and a little higher pricing. Our metrics all improved: higher ARPU, less support/sales needed to close new accounts, less objections overall.</p><p>From my past startup experience I was confident that price is almost never the biggest objection a prospect has when discovering new software. Features, yes. Support, definitely. Pricing, usually not.</p><p>Then this morning I was paging through our support emails in <a href="https://frontapp.com/">Front</a> and my heart sank. I ended up having a conversation a little like this:</p><blockquote><strong><em>Prospect</em></strong><em>: Your pricing is way off</em></blockquote><blockquote><strong><em>Me</em></strong><em>: Oh no! I’m really sorry to hear that 😔 How do you think we could improve it?</em></blockquote><blockquote><strong><em>Prospect</em></strong><em>: Why not do a freemium model? Or reduce your entry price? Competitor X starts at $y/m. Why would anyone use HelpDocs?</em></blockquote><p>Sure, our metrics all look great. 📈 But “way off”? I’d be remiss to not investigate a little further. So I dug out my graphs, put on my data science cap, and sent over a (very lengthy) reply.</p><p>And it got me thinking. How <em>do we</em> think about pricing? Why do we charge so much (or so little, depending on where you stand)?</p><h3>A good comparison</h3><p>Since <a href="http://blog.helpdocs.io/helpdocs-has-acquired-helpman/">our acquisition of Helpman</a>, we’re lucky to have a few more data points than we had before. We can actually see first-hand how a model works with an unlimited free trial, and a slightly lower price point.</p><p>Combining that with our own 16 months of pricing experiments and growth data, we can make some interesting conclusions.</p><h3>Freemium’s really hard for bootstrappers</h3><p>As a bootstrapped startup that hasn’t raised a cent from investors, freemium’s a really tough model to get working.</p><p>Digging into our post-acquisition data, we can actually work out exactly how many more customers we’d need using a freemium model. For every 1 customer we have now, we’d need a whopping 110 freemium users.</p><p>That’s 110 people we’d need to support. We’d need to scale the platform 110 times faster to keep up with demand. And we’d still end up with the exact same revenue out the other end.</p><p>At a very small scale, than can work fine. With VC funding, that can work great. But for us as a bootstrapped team of 2 (<strong>we’re hiring!</strong>), we literally couldn’t afford to support that many extra customers. 💸</p><p>Having a higher entry price lets us provide better support to fewer customers, and still get to the same revenue.</p><p>It also lets us build a sustainable, profitable business, that we can 100% guarantee will be alive next month. Something it’s sometimes difficult to say about a funded startup.</p><h3>Embrace your competitors, then do better</h3><p>Comparing our price to competitors, we end up at the higher end. Especially since our price increase. We’re not the most expensive by a long stretch, but we’re far from the cheapest.</p><p>So why can/do we charge so much?</p><p>On the surface it’s a tough one. We have some <strong>great</strong> competitors. They make awesome products that’re a very good fit for some customers. In fact, I often recommend our competitors’ products over our own to prospects when I think they’ll be a better fit.</p><p>For instance, there’s certain competitors I recommend when people are looking for just a cheap simple knowledge base. Or when they’re looking for something super well integrated with a certain platform. And when they have really complex and niche requirements.</p><p>But there’s some areas that we really excel.</p><p>From my incredibly bias point of view, a bundled knowledge base is never going to be as good as a standalone one. We have a very specific ability at making great knowledge bases. It’s our whole company, our lifeblood, so we can focus on making it the best darn knowledge base there is.</p><p>Many of our competitors make their knowledge base software out of necessity, and don’t dedicate a ton of engineering effort to it. People choose them because they need just a knowledge base, nothing super custom.</p><p>People choose HelpDocs because they need a <strong>great</strong> knowledge base. That’s why we get a significant amount of customers switching <em>to us</em> from other platforms.</p><h3>Holding your own while charging more</h3><p>I think we do a pretty great job of holding our own against our competitors, despite us sometimes being the more expensive option.</p><p>We do that through very advanced, niche features, like more SEO optimization (we do a ton of stuff under the hood), multilingual doc support, and <a href="https://support.helpdocs.io/article/4gjXw4YhxS-creating-a-custom-html-template">full custom templating</a>. And even through simpler things like an easier to navigate dashboard, one-click custom branding, <a href="https://www.helpdocs.io/integrations/">awesome integrations with other platforms</a>, and really excellent support.</p><p>So yep, we charge more than a lot of our competitors (although way less than some). But we more than make up for it in product and support.</p><p>We have a ton of happy users, and the biggest thing we hear is how much money we save them on support. We only have to save support reps from a few tickets a month before the software pays for itself. And we actually save dozens / hundreds, depending on how large the customer base is.</p><h3>Sometimes you still need to compromise</h3><p>All that said, I do remember what it’s like getting started and finding everything’s so damn expensive, especially for software.</p><p>We like to take a fairly liberal approach to pricing in these edge cases. We have programs for that offer discounts to bootstrapped startups, nonprofits, charities, and more. We try and help out wherever we can.</p><h3>Pricing’s really hard, and it just gets harder</h3><p>Pricing’s really hard, and I don’t believe we’ve got it right yet. We’re still just getting started. As we scale, new pricing challenges come up, and we have to refine our model.</p><p>Right now we’re more likely to add features and have higher plans than we are to go freemium. If we raised money, that could definitely change.</p><p>Unfortunately it just requires more funds than we have available to capture the whole market, so we miss out on some awesome accounts that we could otherwise host.</p><p>If you’re reading this, I’d love to know what you think about it.</p><p>Any suggestions on how we could improve our approach? Any examples of freemium working for companies without VC funding (other than behemoths at Mailchimp scale). Are we still <em>way off base</em> with everything?</p><p>I’d love your input in the comments, or tweet me <a href="https://twitter.com/jakeapeters">@jakeapeters</a>.</p><p><em>Originally published at </em><a href="http://blog.helpdocs.io/rejecting-freemium-for-profitability/"><em>The HelpDocs Blog</em></a><em> on August 30, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b590d540517" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/why-were-rejecting-freemium-and-building-a-sustainable-business-instead-4b590d540517">Why We’re Rejecting Freemium and Building a Sustainable Business Instead</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Surprisingly Good Support Wins Us Customers]]></title>
            <link>https://medium.com/helpdocs/how-surprisingly-good-support-wins-us-customers-89f5fa0a2b89?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/89f5fa0a2b89</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Fri, 28 Apr 2017 10:48:40 GMT</pubDate>
            <atom:updated>2017-04-28T10:48:40.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_tvU3yQ91OxN961u." /></figure><p>At HelpDocs we’re kinda great at customer support. If you’ve ever sent us a support request (or just a hello) you’ll have seen this yourself.</p><p>Almost all our chats are replied to within 30 waking minutes. Usually way quicker.</p><p>It’s safe to say our customers <strong>love</strong> our support. And our software of course. But mostly our support. 🤓</p><p>In fact, our support’s so good we get messages like this <strong>every day</strong>:</p><blockquote>Wow! The quality &amp; speed of your support leave me speechless, really! :-)</blockquote><p>Come for the knowledge base, stay for the support.</p><p>Often, though, people assume our customer support’s great because we’re a huge team. I mean, sub-5 response time means there must be a <strong>full-time support team</strong>, right?</p><p>Wrong.</p><p>It’s just two guys in a shed in the UK. <em>Long story…</em></p><p>And if you have some passion (or a shed) you can do it too. Here’s how we deliver surprisingly good support at HelpDocs, and how it wins us customers time and time again.</p><h4>The Magic of a Sub-5 Response</h4><p>It’s not uncommon for us to respond immediately to leads and support requests.</p><p>Recently we had an incident with one of our providers. It was stopping people from signing up. The <strong>worst kinda incident</strong>, for sure!</p><p>People started letting us know pretty much right away, which was great. We got to work immediately, and sent out emails to all the affected users within minutes.</p><blockquote>Sweet — that sub 5 response time is gold standard!</blockquote><p>Less than 10 minutes later the problem was fixed, but the thing that stuck in people’s mind wasn’t the fix itself. No. It was the <strong>communication</strong>.</p><p>Today people want a reply <em>now</em>. And there’s never a case where waiting is better. Acknowledge the problem / ticket / request right away, then sort it out quickly. Your customers will love you for it.</p><h4>Go the Extra Mile</h4><p>Since we added custom HTML templates to the Pro plan earlier this year, we’ve been getting a ton of cool companies making their HelpDocs look super custom.</p><p>But customizing everything takes time. Time that some companies <em>just don’t have</em>.</p><p>We saw the problem and launched a done-for-you template service. We build the whole thing from scratch, add the CSS, HTML and JavaScript to your account, and you have a custom knowledge base. Best of all, that’s usually in less than 24 hours.</p><p>We don’t make a ton of money from it. In fact, factoring in our time it’s probably a loss-leader. But making great templates in no-time-flat gets us feedback like this.</p><blockquote>Thanks Jake! You kind of rock 😏</blockquote><p>That’s the kinda comment that makes it all worth it.<br> All it takes is a little extra effort from you. Do one little thing above and beyond what the customer’s expecting.</p><h4>Always Overdeliver</h4><p>Running a SaaS company we’re asked for new features <strong>all the time</strong>. Everyone has slightly different requirements, so it’s difficult to figure out the right things to work on.</p><p>I’d love to make everyone happy and build the things they want, but adding too many features to HelpDocs would leave us with a bloated, crappy, platform.</p><p>Working out which features to build is a whole other blog post though. The point is you need to deal with customer feedback the right way.</p><p>Often I’ll give feedback or feature requests to other companies, and I’ll be told something like “that’s a great idea, I’ll discuss it with the team!”.</p><p>That loosely translates to “err, we’re never going to do that”. And you’ll probably <strong>never</strong> hear back from them.</p><p>A better way to deal with suggestions and feedback is to set expectations right away. Say “great idea! That’s not something we’re looking at building right now, but I can at least look into it for the future.”.</p><p>If you’re literally <strong>never building that thing</strong>, just say so. Customers would rather be told a definite no than an irritating maybe.</p><p>And if you do say you’ll talk to the team, actually talk to the team. Then send a followup with some kinda plan. It doesn’t have to be concrete, but at least it’s progress.<br> Set reasonable expectations of what your customer can expect, then overdeliver on those expectations.</p><h4>Tying it All Together</h4><p>Great customer support doesn’t have to be tough, and it doesn’t take a team. All it takes is fast replies and careful word choice.</p><p>Make your best effort to delight your customers, throw some emoji into your support messages, and you’ll do great. 🎉</p><p><em>This article was originally posted on </em><a href="http://ift.tt/2nIgDVH"><em>The HelpDocs Blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89f5fa0a2b89" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/how-surprisingly-good-support-wins-us-customers-89f5fa0a2b89">How Surprisingly Good Support Wins Us Customers</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enjoy Work, Love Life, Don’t Sweat the Details]]></title>
            <link>https://medium.com/@jakeapeters/enjoy-work-love-life-dont-sweat-the-details-8596d9d7d4f?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/8596d9d7d4f</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[founders]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Sun, 16 Apr 2017 14:01:01 GMT</pubDate>
            <atom:updated>2017-04-16T14:01:01.362Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first got into startups I thought success came from working on something lucrative.</p><p>So I thought of problems people had, how I could solve them, and hacked away at a few projects that looked promising.</p><p>On paper I was <em>changing the world</em>.</p><p>In practice, <strong>I hated my life</strong>.</p><p>There’s nothing worse than waking up every day knowing you don’t enjoy what you do.</p><p>Applying for startup accelerators in full knowledge that you don’t see the value in your product.</p><p>Sending pitch decks to investors, even though you don’t need the money, don’t want their help, and don’t want to work on the product tomorrow.</p><p>It really <strong>doesn’t have to be that way</strong>.</p><p>Start by working on things you <em>actually enjoy</em>. Then worry about making money later.</p><p>I mean, obviously don’t work on something you think will never succeed. Unless you really don’t care about your future sanity. Or it’s a side/passion project.</p><p>But don’t sweat the details of the success.</p><p>There’s literally hundreds of projects out there that I’ve looked at recently and thought “wow, that’ll never work!”. Or “that’s just a tiny side project, right?”. Then heard a few weeks later they’ve been acquired.</p><p>The defining trait there is that they <strong>enjoy what they do</strong>. If you love your work, it’s easy to get others to love it too. And that’s really what success is all about.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8596d9d7d4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Giving Your SaaS Away For Free]]></title>
            <link>https://medium.com/@jakeapeters/stop-giving-your-saas-away-for-free-e6cde3ace67a?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6cde3ace67a</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[pricing-strategy]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 16:02:01 GMT</pubDate>
            <atom:updated>2017-04-04T16:02:01.148Z</atom:updated>
            <content:encoded><![CDATA[<p>I run support at HelpDocs. So I deal with a ton of customers every day. The tickets never stop (although weekends are easier!).</p><p>One common theme, obviously, is that almost everyone <em>wants something</em>. It might be a bug fix, or a new feature.</p><p>All too commonly though? <strong>Freebies</strong>.</p><p>Whether it’s an application upgrade or a free account, I’m used to people asking for things that’re often unreasonable.</p><p>It’s not their fault. People have been conditioned to expect free stuff. Google, Apple, Facebook, they’re all shipping <em>excellent</em> software for free.</p><p>Sure, they might sell all your private data for it. So there’s probably some hidden costs. But it’s at least free at the point of sale.</p><p>That’s ok for huge tech companies. They can afford it. It’s like engineering as marketing to them. And I get it.</p><p>But for bootstrapped startups like us <strong>it hurts</strong>. I’d actually love to give people free shit. I like making people happy. If I could, I’d probably be giving out the software for free too.</p><p>Problem is, free doesn’t pay the bills.</p><p>Free doesn’t pay for our servers, our time, anything.</p><p>I’d take one paying customer over 1,000 free users any day.</p><p>Software may be cheap, but it costs money.</p><p>The software we’ve built, you’ve built, that talented engineer at Google’s built, is worth something. Probably <em>more than you think</em>.</p><p>So don’t be afraid to charge a fair price for it.</p><p>I mean, don’t go out and charge two hundred dollars for a service you can get for twenty five. But don’t charge nothing, either.</p><p>Charging a fair price lets you spend more on making the software better. That’s great for you, and awesome for your users. If you explain that, they’ll understand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6cde3ace67a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things That Surprised Me Running a Startup as a First-Time Founder]]></title>
            <link>https://medium.com/@jakeapeters/things-that-surprised-me-running-a-startup-as-a-first-time-founder-3c41010dfe44?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c41010dfe44</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Sun, 02 Apr 2017 13:01:42 GMT</pubDate>
            <atom:updated>2017-04-02T13:01:42.466Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MDAaDDJV3c6uC1Q_7ecsYQ.jpeg" /></figure><p>3 years ago I was in my final year of college. I sat down with an old colleague to talk about building an exciting new app that was going to change the world.</p><p>A few months later I jumped straight outta college into my first startup.</p><p>We didn’t change the world. In fact, I left soon after we launched. We were both awful founders, and didn’t exactly bring out each other’s best qualities.</p><p>Since then it’s been a whirlwind of starting up, shutting down, incorporating, dissolving, marketing, selling, growth, developing. You name it, I’ve done it.</p><p>Running startups has easily been the most rewarding experience of my life so far.</p><p>I guess at 24 that’s not really saying much, but it’s been so long now I don’t remember a time where I <strong>didn’t</strong> run my own business.</p><p>My latest project, HelpDocs, is making it easy for businesses to <a href="https://www.helpdocs.io/">write awesome looking help documentation without a developer</a>. Or even fancier help documentation with one. If you run a startup, you need it.</p><p>But I digress.</p><h4>Running a startup is all-consuming</h4><p>Everyone says startups take over your life. They’re right, but not in the way I imagined.</p><p>I thought <strong>one startup </strong>would take over my life. But in fact, it’s <em>startups in general</em>.</p><p>Every week I start out with 168 hours. Nearly half of that’s in bed sleeping or reading. I eat one (admittedly gigantic) meal a day, work out for 30 minutes, walk a few miles, and take 2–5 30 minute breaks for coffee or green tea.</p><p>The rest of the time is thinking about startups. HelpDocs, side projects, everything. <em>Balancing those, though, is a topic for another day.</em></p><p>I take breaks during dinner to deal with customer support tickets.</p><p>I read programming articles while I’m brewing coffee.</p><p>I triage my emails first thing in the morning, last thing at night, and 100 times in between.</p><p>I use Twitter constantly, but for work, not for fun.</p><h4>It’s a love/hate relationship</h4><p>If you’re thinking all of that sounds like crap, you’d be right.</p><p>I hate 90% of the things I do every day.</p><p>So why do it at all?</p><p>Because the other 10% is totally worth it.</p><p>Sometimes I’ll get a comment from a customer that makes me smile. They’ll be so surprised at the level of support that they just <em>had to let me know</em>. And it makes it worth the pain.</p><p>Or I’ll go to someone’s knowledge base and find out it’s one of ours.</p><p>Maybe I’ll write a piece of code that’s so beautiful it makes me cry. 😿</p><p>Ok, probably not that last one. But you get the picture.</p><p>The struggle’s real, but the struggle’s worth it.</p><h4>Rejection’s a daily occurrence</h4><p>My biggest surprise as a startup founder so far, though, has been the emotional rollercoaster.</p><p>The highs are incredibly high, the lows are incredibly low. And there’s not a huge amount in between.</p><p>Rejection’s part of startup life. We applied to accelerators at least 20 times with other projects. Most of them rejected without a word.</p><p>Then we started getting through to the final round of interviews for these things, still getting rejected. I think that was worse.</p><p>Even now, I send emails to customers, or reply to live chats, and I rarely get replies back.</p><p>Sales emails go unanswered, or replied to with undue rudeness.</p><p>But you get used to it. I did. I get surprised when people reply to me, and it’s a nice surprise. Maybe even nicer than if everyone did. So every cloud, right? ⛅️</p><p>So there’s a few things. Startups are rewarding, but they’re like a 💩 sandwich. You’ll struggle more than you excel, and it’s often depressing.</p><p>But I wouldn’t change a thing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c41010dfe44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Multilingual Translation]]></title>
            <link>https://medium.com/helpdocs/introducing-multilingual-translation-37d049588c0d?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/37d049588c0d</guid>
            <category><![CDATA[knowledge-base]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[language]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Sun, 12 Feb 2017 18:34:30 GMT</pubDate>
            <atom:updated>2017-02-12T18:34:30.742Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Introducing Multilingual Translation" src="https://cdn-images-1.medium.com/max/1024/0*bhfZcHvJivh3k3Lc." /></figure><h3>HelpDocs Now Supports Multilingual Translation</h3><p>I’m thrilled to announce that HelpDocs now has full support for multiple languages. 🎉</p><p>Now you can write your docs in as many languages as you can think of, and your visitors can choose the version they want.</p><p>Until now, making a multilingual knowledge base has been painful at best. The UX is incredibly tough to get right, and generally, it isn’t right at all. That’s if you’ve even found a provider that offers a multilingual knowledge base in the first place.</p><p>Now it’s all changed. Write a master copy of your docs in your preferred language, then easily translate it into as many as you choose.</p><h4>Why Support Multiple Languages?</h4><p>At HelpDocs we have customers from around the world.</p><p>And <strong>our customers’ customers</strong> are from even further afield.</p><p>In fact, this month HelpDocs-hosted knowledge bases will be viewed by people from dozens of countries, who speak dozens of different languages.</p><p>I’ve lost count of the number of times I’ve been asked about multiple language support. I didn’t really understand the problem, to be honest, until I started looking into it more.</p><p>Turns out there wasn’t a great solution.</p><p>Sure, there’s some knowledge bases out there that allow multiple languages. But I tried them. And you wouldn’t want to.</p><p>Because while they <strong>sound</strong> great, actually trying to translate docs into a different language is clunky and horrible. As soon as I tried it out, I knew why people were so passionate about finding a solution.</p><h4>How We’ve Made Multilingual Knowledge Bases Great</h4><p>We’ve learned from others’ mistakes. Their UX problems. The clunky interfaces.</p><p>And we’ve built something awesome.</p><figure><img alt="Introducing Multilingual Translation" src="https://cdn-images-1.medium.com/max/772/0*O0Gm5wabA1193zkb." /><figcaption>It’s literally just a checkbox to enable multilingual</figcaption></figure><p>When you log into your account, you’ll find an option in <strong>Settings</strong> &gt; <strong>General</strong> to enable multilingual support.</p><p>Once you’ve ticked that you can set a default language and as many secondaries as you like. The autocomplete will help you out — there’s a ton to choose from.</p><p>Then you’ll see a dropdown on the navbar. You set your <strong>working language</strong> there.</p><p>Once you do that, everything changes. We’ve added a little grey label to everything that’s localizable. It shows you exactly what’ll change for each language.</p><p>In the Settings views that’s things like nav bar items and internationalization strings.</p><figure><img alt="Introducing Multilingual Translation" src="https://cdn-images-1.medium.com/max/1024/0*X1uZwgSugFyje368." /><figcaption>Labels, labels, everywhere!</figcaption></figure><p>The Articles tab is where it gets really interesting. In your default language, nothing changes. When you switch your working language to a secondary, you’ll see a label on everything that you still need to translate.</p><p>Once you’ve written a version for your new language, you can mark it as <strong>Translation Complete</strong>. We’ll show it in the frontend knowledge base under the right language automatically.</p><figure><img alt="Introducing Multilingual Translation" src="https://cdn-images-1.medium.com/max/1024/0*2CZ0AbT9O7zMqqh2." /><figcaption>Users can pick a language. Hopefully one they understand.</figcaption></figure><p>We’ve added a language dropdown to the knowledge bases too. Your users will easily be able to switch language at any time on the site.</p><p>Plus we handle all the redirects, and make everything super SEO-friendly as usual.</p><p>It’s all incredibly intuitive. You <strong>have to</strong> <a href="http://ift.tt/2gFWWcZ">check it out</a>.</p><h4>What’s Next for Multilingual?</h4><p>I think we have the <strong>best knowledge base for multiple languages</strong> around. But we’re not stopping there.</p><p>We’re already thinking of ways to make it better. In the short term, that means auto-detecting languages and displaying just the right pieces of content. We also have a little way to go to get feature parity between editing docs in your default language and in secondaries.</p><p>Longer-term, we’re finding new ways to integrate the multilingual docs into the HelpDocs workflows you’re already using. Like our <a href="http://ift.tt/2fLrpSj">Front plugin</a> and <a href="http://ift.tt/2fLtwFt">Google Chrome Extension</a>.</p><h4>How to Check it Out</h4><p>If you’re an existing HelpDocs customer, or you’re on a trial, I’d love to add the new multilingual feature to your account. Ping me an email or a live chat and I’ll hook you up.</p><p>If not, you should <a href="http://ift.tt/2gFWWcZ">sign up for a trial</a>. I promise <strong>these are the multilingual docs you’ve been looking for</strong>.</p><p>I hope you enjoy using the new multilingual translation features as much as I enjoyed building them. 🙌</p><p><em>This article was originally posted on </em><a href="http://ift.tt/2l47Z1B"><em>The HelpDocs Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37d049588c0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/introducing-multilingual-translation-37d049588c0d">Introducing Multilingual Translation</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Sharing Your Startup Idea Online Really a Good Idea?]]></title>
            <link>https://medium.com/startingup/is-sharing-your-startup-idea-online-really-a-good-idea-39c0a8d358ac?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/39c0a8d358ac</guid>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 11:42:22 GMT</pubDate>
            <atom:updated>2016-11-19T05:58:43.192Z</atom:updated>
            <content:encoded><![CDATA[<p>I still remember when I started my very first business.</p><p>Well, I call it a business. Really that should be in air quotes. Maybe a better word would be <strong>hobby</strong>. It never made money, and I shut it down after a couple weeks.</p><p>Anyway, back to the story.</p><p>I’d gone out, done a tiny bit of research, and decided the world <em>just had to have</em> a standalone service for developers to send dynamic emails to customers.</p><p>Yeah, I know. The idea sucked.</p><p>But even then, I was terrified about sharing my idea online. I didn’t want some massive corporation swooping in and <strong>stealing my idea</strong>.</p><h3>It’s actually pretty common</h3><p>Now that I’ve been in the startup world for a while, turns out this is a pretty common thought.</p><p>New founders are <em>always</em> worried about sharing their startup ideas online.</p><p>It’s not atypical for a founder to spend months in <em>stealth mode</em>. Then maybe a <em>private alpha</em>, a couple<em> betas</em>, maybe a <em>public preview</em>.</p><p>Six months in, and only a handful of people know about you and your startup.</p><p>You’re quickly running out of money. That friends and family round you raised? Well, they ain’t your friends anymore.</p><p>You still have no idea whether people actually need the thing you’re building. But it’s OK, you tell yourself, because it’s <em>only been six months</em>. Even <strong>AirBnb took longer</strong> than that to make money, right?</p><p>The months keep ticking by. Then one awful day you realize a simple startup truth: <strong>nobody cares about your idea</strong>.</p><p>It shouldn’t even come as a surprise. People like me have been shouting it at you for years. But did you listen? When I was in your position, I know <strong>I didn’t</strong>.</p><h3>What happens when you share your ideas</h3><p>The reality is that when you share your idea online, there’s only two possible outcomes:</p><ol><li>Someone actually <em>does</em> “steal” your idea</li><li>Nobody notices your idea at all</li></ol><p>Say the former happens. Maybe it was a crap idea anyway and you should stop. I doubt that. More likely it’s a <strong>great idea</strong>. Theft is the ultimate form of validation.</p><h4>Competition’s a good thing</h4><p>People copying you just goes to prove you’re not crazy. That you’re working on something important enough to steal.</p><p>Remember that first startup I mentioned?</p><p>Nobody was in the market. There was <strong>very little competition</strong>. I was ecstatic. No competition means we could take the whole market, right?</p><p>Wrong.</p><p>No competition meant <em>no market</em>. It usually does.</p><p>We were trying to carve out a market for our product that just didn’t exist. Still doesn’t, really. We’d built a cool feature and called it a product.</p><h4>You’re not that important</h4><p>The second — much more likely — scenario when you share your ideas online is that nobody will care.</p><p>They’ll see your <strong>amazing world-changing idea</strong>, and write it off as <em>just another crazy startup idea</em>.</p><p>People aren’t too bothered that you’re making <em>Uber for x</em>, <em>AirBnb for y</em>, or a <em>better z</em>.</p><h3>People care more about themselves.</h3><p>What’s in it for them? Why should they listen to you? Why should they give a damn?</p><p>In fact, you’ll probably have to shove your idea down people’s throats until they listen.</p><p>You’ll have a constant struggle to get people to give your product the time of day. And an even tougher struggle to get them to <strong>actually pay you</strong> for it.</p><p>What’s in an idea anyway?</p><p>At the end of the day you need to decide how much ideas <em>really matter</em>.</p><p>You don’t own an idea.</p><p>Anything that you can think of right now, someone else has thought of before. Either they’re currently working on it (competition, great!) or they’ve discarded it.</p><p>I have dozens of startup ideas written in my notebook. I think of 10 a day.</p><p>Sometimes I even go buy a domain for one because I’m so excited about it.</p><p>Then I come to my senses and forget about it. I might even have done that with <em>your idea</em>.</p><p>The truth is it doesn’t matter. Even if you’re building a clone of someone else’s product, that’s usually not a problem.</p><p>There’s a hella lot of customers out there, and a ton of huge markets.</p><p>It’s not unusual for markets you consider to be monopolies, like search, to still have a ton of players. Bing might suck, but they still make money. Probably. I’ll Google it later.</p><p>Focus on making your company <strong>great</strong>. As great as it can possibly be.</p><p>Execution is 99% of your future success. The idea makes up a fraction of that last percent.</p><p>Be the best at what you do, and you can beat out people that started building your idea 7 years ago. No need to worry about someone starting right now.</p><p>When you focus on building a great company, the rest falls into place.</p><p><em>This article was originally posted on </em><a href="https://www.startingup.co/blog/sharing-startup-ideas-online/"><em>Starting Up</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39c0a8d358ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startingup/is-sharing-your-startup-idea-online-really-a-good-idea-39c0a8d358ac">Is Sharing Your Startup Idea Online Really a Good Idea?</a> was originally published in <a href="https://medium.com/startingup">Starting Up</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 Win at Startups by Learning Fast]]></title>
            <link>https://medium.com/startingup/how-to-win-at-startups-by-learning-fast-eda42d322725?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/eda42d322725</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Sun, 13 Nov 2016 14:38:55 GMT</pubDate>
            <atom:updated>2016-11-13T14:38:55.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AUI1yIp1Dz9uEMzZUlzwJg.jpeg" /></figure><p>Learning’s something that we take for granted.</p><p>It starts as soon as you’re born. You learn to writing. To read. To speak. Even <strong>to think</strong>.</p><p>Then school, college. You start to learn higher level skills. Maybe some math. Or…the recorder.</p><p>And college. Well, that <em>should</em><strong><em> </em></strong>be more of the same. You should become a voracious learner. Right?</p><h3>What’s so wrong with college</h3><p>For most of us, college isn’t really about learning skills. In fact, it’s usually secondary to learning general human functions. It’s where you grow up.</p><p>Instead of learning to solve <strong>big</strong> problems, we’re learning to play beer pong.</p><p>It’s more than possible to scrape your way through college — do well, even — without doing much <em>work</em>.</p><p>Professors want you to do well. They set the same exams every year. They’re judged by your success. You get the drill.</p><p>Sometimes it seems like there’s not even a point in trying to excel. After all, if you’re scraping a B without trying, what’s encouraging you to do better?</p><h3>After college? It gets worse</h3><p>So if college isn’t for learning, what happens next?</p><p>That’s usually when your learning really starts.</p><p>You have to learn skills. A lot of them.</p><ul><li><strong>Life skills</strong><br> Like setting up and paying for utilities. Paying the rent. Finding an apartment. Arranging movers.</li><li><strong>Social skills</strong><br> Making friends when proximity’s not on your side is way harder. Most kids come out of college with no idea.</li><li><strong>Job hunting skills</strong><br> Because college seems strangely lacking in those too. They’ll tell you <em>roughly</em> how to get a job, but nothing specific. That’d be too helpful, right?</li><li><strong>Applied academic skills</strong><br> The worst of all — learning how to actually <em>apply</em> any of the academic stuff you’ve been taught. Unless you were super lucky, you’ll have ended up being able to solve an equation on a whiteboard but have no idea what that means in real life.</li></ul><p>Oh, and there’s that <em>small task</em> of working out who <strong>you are</strong> after college. Because being free from education for the first time tends to change a person.</p><p>Your likes, dislikes. Your values. You need to figure it all out.</p><p>And that’s all in the first few months. You’re really chucked in at the deep end.</p><h3>Doing a startup makes everything worse</h3><p>Wanna skip the job hunting and build your own company?</p><p>That’s what I did. And I’ll tell you now, the path’s fraught with danger.</p><p>Not only do you have to learn all that other stuff, but you need to be able to <em>make decisions</em>. Good ones. Really fast.</p><p>Startups are almost impossibly risky. So you’ll need a way to manage that risk. And great execution (through great decision making) is the best risk management there is.</p><p>That’s not even starting to think about the stuff you’ll need to know to actually <strong>run</strong> the damn thing. Accounting, fundraising, software development, hiring, firing. The list goes on.</p><p>The best founders have a passion for learning. In fact, I’d go as far as to say they have a <em>hunger</em> for it.</p><p>This weekend I’m getting back to basics. I’m building out a new site for my personal branding (hi!). I’m diving into WordPress for the first time in years.</p><p>I’m also migrating the HelpDocs homepage to a new web host, and playing with some IoT and AI stuff on the side. And I’ve still got the gym to look forward to.</p><p>I know very little about how to achieve most of those tasks. Yet. So much of my week’s going to be spent learning.</p><p>I don’t do these things just because I <em>want to</em>. There’s a compulsion. A drive to learn more.</p><p>Find that drive, apply it, and it’ll make you a better founder. It’s sure helped me.</p><p><em>Originally published at </em><a href="https://www.startingup.co/how-to-win-at-startups-by-learning-fast/"><em>www.startingup.co</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eda42d322725" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startingup/how-to-win-at-startups-by-learning-fast-eda42d322725">How To Win at Startups by Learning Fast</a> was originally published in <a href="https://medium.com/startingup">Starting Up</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Took Our Startup from Idea to Paying Customers in 4 Weeks]]></title>
            <link>https://medium.com/helpdocs/how-we-took-our-startup-from-idea-to-paying-customers-in-4-weeks-952695ee023b?source=rss-5f0988ea2f85------2</link>
            <guid isPermaLink="false">https://medium.com/p/952695ee023b</guid>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Jake Peters]]></dc:creator>
            <pubDate>Tue, 25 Oct 2016 05:04:34 GMT</pubDate>
            <atom:updated>2016-10-25T05:04:34.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8chIXfGr6gaeLD4rObRoCg.png" /></figure><p>Since we launched HelpDocs 5 months ago I can safely say I’ve learned more than ever before.</p><p>We’ve taken our fledgling idea from nothing to profitable with over 100 users on paying teams. Getting to this stage, though, has been one of the hardest things I’ve ever done.</p><p>I’ll explain…</p><h4>The Idea</h4><p>It’s not my first rodeo. I’ve built startups from nothing before.</p><p>In fact, my cofounder and I were working on another startup when we first thought of HelpDocs. That startup was profitable and growing. From the outside, everything looked great.</p><p>But inside we were struggling. With product, with growth, and especially with support.</p><p>We tried just about every knowledge base there is out there to reduce the number of tickets we were getting. We found some <em>good</em> platforms, but nothing <strong>great</strong> enough to really make a dent.</p><p>Knowledge bases are usually relegated to <strong>features</strong> in big applications. They’re not allowed to thrive and stand on their own. They feel pretty unloved.</p><p>It was a simple enough idea. A standalone knowledge base that looked great, was easy to customize, and a breeze to maintain.</p><p>While the idea was sound, it seemed too small. Could a knowledge base really be a whole product?</p><p>I didn’t think so. For over a year I held off. I kept trying new software hoping it’d make the difference.</p><p>But I still couldn’t shake it. It was something I <em>couldn’t not</em> build. It kept me up at night. Yeah, I know how sad that sounds.</p><h4>v1: A Terrible Product Made Quickly</h4><p>Startups almost always make the mistake of launching too late.</p><p>They keep their products secret, working in dark rooms, not getting people on board until everything’s just <strong>perfect</strong>.</p><p>Except it never is.</p><p>Products built in silos never work out. You need to promote yourself tirelessly to get anywhere, and that starts by getting people involved on day 1.</p><p>Your product will probably suck. Ours did. But if you don’t validate it quickly, you can’t even know the market <em>exists</em>.</p><p>So how minimal should your product be?</p><p>Turns out <strong>very</strong>. You can get away with a lot less than you think.</p><p>I hacked together the first version of HelpDocs in about a fortnight.</p><p>Looking back on it, it was awful. I mean, take a look for yourself. But it was good enough to get us to revenue.</p><figure><img alt="How We Took Our Startup from Idea to Paying Customers in 4 Weeks" src="https://cdn-images-1.medium.com/max/1024/0*PCsOUHs-f-yLSkb1." /></figure><h4>Launching a Knowledge Base SaaS</h4><p>We shut down our previous startup to start building our Minimum Viable Product (MVP) in June 2016, and launched it to the public less than 3 weeks later.</p><p>We promoted on Twitter, Facebook, and Medium. We told everyone we knew. We sent out a hundred requests for feedback.</p><p>We have some great friends, and they helped us squish some bugs. They gave us some crucial early feedback.<br> But nobody wanted to pay for it.</p><p>We spent the week frantically fixing things and adding new features. It was pretty scary. We’d just shut down another startup to work on this, and I was worried we’d made a mistake.</p><h4>Validating Demand</h4><p>It took a few days, but I got over myself. We had no audience, no real network, so it’s not a huge surprise we weren’t an immediate success.</p><p>I thought about how to validate the demand a little quicker, and decided to start running some (very small) paid marketing experiments.</p><p>AdWords was my platform of choice.</p><p>I was a bit of an advertising newbie. I’d experimented with paid acquisition before, but it’d never worked out. Either we had the wrong product or the wrong marketing message, but something was wrong for sure.</p><p>So I set aside a few hundred dollars from our bootstrappers budget and got to work.</p><p>One campaign was all it took. Less than $100 in ad spend acquired us 2 customers.</p><p>Sure, $50 in MRR’s hardly enough to pay for my coffee habit. Or our servers. Or the software <em>we buy</em>.</p><p>But the ROI from our marketing was enough to prove that people actually <strong>needed</strong> better knowledge bases. And that was good enough for me.</p><h4>What We Should Have Done Better</h4><p>In the end, moving on to HelpDocs was a great decision. We’re making more money from happier customers, and we’ve <strong>finally</strong> found a knowledge base product that works for us.</p><p>But we still made a ton of mistakes along the way. Not least of which was not validating the market sooner.</p><p>I’d asked around some friends to see if it’s something they’d use. They almost all said yes, and yet none of them gave us money.</p><p>That’s not because they were lying. Or because they’re cheap. It’s because they’re our friends. They wanted to encourage us, so they said what we wanted to hear. And that’s OK!</p><p>Next time I’d start out with paid acquisition, funneling traffic to a landing page where I’d presell subscriptions. I’d get money up front to validate the thing I was trying to sell.</p><h4>What Now?</h4><figure><img alt="How We Took Our Startup from Idea to Paying Customers in 4 Weeks" src="https://cdn-images-1.medium.com/max/1024/0*VOw7GiOsjUfUCsrX." /></figure><p>We’re still finding our way. HelpDocs is a great knowledge base product already (and 1000 times better than that first version), but it’s not perfect.</p><p>Today I finished a huge development sprint. I’ve been adding features and refining the platform for a while now, and it’s finally at a stage where I’m happy with it.</p><p>Marketing’s something we’ve previously been terrible at, something that I <strong>particularly</strong> hate. So that’s the next frontier. And more sales, which is luckily something we’re better at.</p><p>In that vain, I’ll be writing some more about our journey, and what’s working for us.</p><p>If you’re interested you should <a href="http://ift.tt/2f0dAEz">sign up to our digest</a> — we send out interesting startup reads from around the web (and some of our own) about once a month.</p><p><em>This article was originally posted on </em><a href="http://ift.tt/2eBFNi4"><em>The HelpDocs Blog</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=952695ee023b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/how-we-took-our-startup-from-idea-to-paying-customers-in-4-weeks-952695ee023b">How We Took Our Startup from Idea to Paying Customers in 4 Weeks</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>