<?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 Clifford Oravec on Medium]]></title>
        <description><![CDATA[Stories by Clifford Oravec on Medium]]></description>
        <link>https://medium.com/@cliffordoravec?source=rss-55e9fd9a459------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3mnfx1jRfrsbytj8.jpeg</url>
            <title>Stories by Clifford Oravec on Medium</title>
            <link>https://medium.com/@cliffordoravec?source=rss-55e9fd9a459------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 05:10:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cliffordoravec/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[From SaaS Idea to Launch In a Week (An Epic Guide Post)]]></title>
            <link>https://medium.com/tamboo/from-saas-idea-to-launch-in-a-week-an-epic-guide-post-a49ae9970da4?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/a49ae9970da4</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Tue, 29 May 2018 14:39:30 GMT</pubDate>
            <atom:updated>2018-05-29T14:58:14.647Z</atom:updated>
            <content:encoded><![CDATA[<p>And getting paid in the first 24 hours— without a launch list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jhufk2bywbq06weGq5q4FA.jpeg" /><figcaption>(And no, I have no idea who this dude is.)</figcaption></figure><p>Hey kiddos!</p><p>It’s been <em>a while</em>, I know.</p><p>And for that, I (kinda) apologize.</p><p>After all (if you recall) I <em>did</em> have a <a href="https://medium.com/@cliffordoravec/how-2017-completely-kicked-my-saas-c42540fb4ba2">pretty rough year last year</a> and I’ve still been nursing myself back to health (while continuing to pummel myself in new and fascinating ways — cause that makes sense, right?)</p><p>But enough of that trendy boostrapped startup self-loathing pity and misery.</p><p>Today, we’re here to talk about <strong>GOOD STUFF.</strong></p><p>About <strong>SUCCESSFUL STUFF.</strong></p><p>You know — the kind of STUFF that Startup Dreams are <em>supposed</em> to be made of?</p><p>And I promise you — it isn’t going to disappoint. (Unless you were just hoping to see me fall on my face some more for your amusement. In which case, just give that one a little more time — I don’t disappoint either way 🙃)</p><p>Because this is the story of how I conceived, built, launched, and made <em>real money</em> from <a href="https://consentjs.com/">ConsentJS — A GDPR Consent Forms as a Service application</a>— in one week flat.</p><p><strong>Origin Stories Are Overrated — But Your Pitch Deck Needs One! 😉</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*NyhwtIIuWMvBzF98nXsflQ.png" /><figcaption>“So does that mean you could have prevented ‘Arachnophobia’ from happening?”</figcaption></figure><p>It was a dark and stormy night, and I was feverishly expending every sleepless night I could in an attempt to ward off the impending doom that awaited any of those <em>foolish</em> enough to be unprepared for a day that will go down in infamy — May 25th, 2018 — The Dawn Of GDPR.</p><p>(Actually, it was a pretty nice day, but in an origin story, a little dramatic effect can’t hurt…)</p><p>I flexed my muscles as I hefted the tome of regulation text that would doom me to failure and ruin and regarded my implements of internet business warfare with fondness.</p><p>My IDE, my build tools, my <em>codebase</em>.</p><p><em>These</em> were all that could be counted on in times like these.</p><p>As I glanced at my mailing lists, my analytics, my tracking tools — those bastions of light that I clung to in better times — I solemnly knew that their days were numbered.</p><p>The world had lost its mind — and I — a mere denizen of the Net — would have to find a way to persevere and survive the impending desolation in order to rebuild anew.</p><p>The dark times were coming.</p><p>The Powers-That-Be in a foreign land were threating to send us back to the dark ages before analytics, before attribution — before marketing intelligence.</p><p>A Time of Marketing Without Data.</p><p>A time known as… the 90s.</p><p>A shiver crept down my spine at the very thought.</p><p>I knew that in order to rebuild, I would first have to survive. And so I cracked open the nefarious tome and began to read its hideous and cryptic words under the waning light of the darkening sky as a foreboding strike of white lighting filled the air…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*pLWsUg0Hm04tn5-D2zfYJw.jpeg" /><figcaption>“And behold! Any data you have ever collected without consent shall BURN and you shall no longer know your website visitors! Your backups shall be PURGED and your server logs rendered USELESS! So it once was, and so it shall be again — for ever more!” — The Book of the GDPR Beast, Chapter VI, Verse LXVI</figcaption></figure><p>It took me about three days to read through the whole text part-time while taking notes and doing research.</p><p>And yeah, parts of it definitely didn’t give me the warm fuzzies as I took the time to consider the implications.</p><p>As far as I could see, most marketing tools would be rendered near useless in the EU. Marketing lists would be reduced to a <em>fraction</em> of their former enrollments. Hundreds of thousands of ad-driven websites would probably fold in the coming months.</p><p>And <em>all</em> of us bootstrappers would be buried under an avalance of website updates, legal documents, and mind-numbing processes we would have to implement.</p><p>The icing on the cake?</p><p>There was absolutely <em>no</em> guidance on any of it, and many of the requirements came across as technically infeasible, contradictory, or just downright <em>stupid</em> (with respect to business operations and information security).</p><p>Grimacing from the knowledge of the impending lost productivity I would experience, I set my jaw and got to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/1*Hs1jKhXA1VKjLWCU9WYTrA.jpeg" /><figcaption>It’s not nearly as inspiring when you’re your own Number One.</figcaption></figure><p>It took me 23 back-to-back days to implement the GDPR requirements.</p><p>No days off. No weekends.</p><p>For <strong>one</strong> of my web apps.</p><p>It was in those moments of pure productivity-killing hell that I <em>truly</em> began the glimpse the beast facing all of us down.</p><p>I’m not going to lie — I almost gave up.</p><p>On everything.</p><p>Here I was, staring this thing down, trying to appease its every whim and mandate, and the <em>whole time</em> I’m thinking “My businesses are <em>dead</em> with this thing in the same room. It’s over. The beautiful ‘anyone can build a business’ internet that I knew is <em>gone.</em>”</p><p>Among other thoughts, at the forefront of my mind was how <em>every</em> business that uses <em>any </em>kind of analytics or tracking software would need to get consent from their website visitors for that software — and that <em>no one</em> was going to opt-in to these things.</p><p>All of us internet business owners view these kinds of tools as “standard” and “necessary” — but to website visitors, “tracking tools” look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*bPw7jtCilU_W9EinWOdZHg.jpeg" /><figcaption>You Privacy Is Important To Us: Enable us to deliver a personalized experience for you by consenting to the installation of this creepy eyeball tracking device into your hand. Our website may not work properly without your agreement to these terms.</figcaption></figure><p>(Yeah, let me hit “I consent” on that, right?)</p><p>I’m not going to lie, it took me (more than) a few days to come to grips with reality.</p><p>Preliminary reports were estimating that only 20% of people would give consent to analytics and tracking tools when given the option (and let me tell you what — that number is <em>eerily</em> accurate based on the data I’ve now seen).</p><p>After all, the fact that I run <a href="https://gettamboo.com/">a session recording service</a> means that I’m probably a <em>tad</em> bit more sensitive to these kinds of things than others might be.</p><p>Because I’m thinking about how the value of my service to customers might be rendered completely useless if they can’t get consent from their website visitors to use it.</p><p>(Not to mention the fact that <em>I</em> don’t want to be giving up valuable analytics and insights on my websites if I don’t necessarily have to.)</p><p>And that got me thinking.</p><p>Was there maybe a way that I could create a consent form that could <strong>both</strong> satisfy the GDPR <em>and</em> still make it so that I wasn’t going to have to give up <em>80% </em>of my website visitor insights?</p><p>Here’s what we know:</p><ol><li>GDPR is happening, whether we like it or not.</li><li>As part of being compliant, you must get consent from EU natural persons for any personally identifying or identifiable data you collect— regardless of where they’re located (you can’t just IP target them).</li><li>Only 20% of people are going to give consent to analytics and tracking tools, given the option.</li></ol><p>But what that <em>really</em> means is that <strong>you just need to get consent from EU natural persons to be compliant. </strong>There’s no reason to prompt <em>everyone </em>for their consent. There’s no reason to have to give up <em>all</em> of those tasty analytics.</p><p>So I set to work building out a consent form for <a href="https://gettamboo.com/">Tamboo</a> that would do just that: It would ask people to self-identify as EU natural persons. And based on that response, they would either get prompted to provide consent for each analytics and tracking tool I wanted to use per the GDPR, or they would just get <em>all </em>the analytics and tracking tools dropped like normal, and it would be business as usual.</p><p>It took me three (long) days to build a consent form that worked the way that I had envisioned.</p><p>I put it up on Tamboo and watched to see if I was right about the numbers — and I was.</p><p>This form not only fulfilled the GDPR consent requirements — it also meant that I wasn’t going to have to give up my analytics for non-EU visitors.</p><p><strong>The Flicker of an Epiphany: That Sucked Balls</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*6tGI7j3I3o1-7WKusuuH9w.jpeg" /><figcaption>Well, that’s <strong><em>one</em></strong> down…</figcaption></figure><p>Once I had completed one round of GDPR implementation on one of my websites, I knew I was going to have to do this same song and dance on <em>every</em> website that I owned.</p><p>There were roughly five categories of activities that would need to be done for each:</p><ol><li><strong>Backend changes</strong>. I would have to modify my backends to be compliant with the various security and PII requirements.</li><li><strong>Policy and procedure changes</strong>. I would have to update my policies and procedures on the backend and frontend, including changes to Privacy Policies, Terms of Service, and the creation of Data Processing Addendums.</li><li><strong>Tooling</strong>. I would have to create tools to help my customers fulfill their GDPR Controller requirements.</li><li><strong>Notifications</strong>. I would have to notify customers of these changes and make sure that they knew what their responsibilities were and get their acceptance of the new terms, etc.</li><li><strong>Consent</strong>. I would need to get consent for processing wherever I acted as a Controller — including on my websites.</li></ol><p>(In case you’re thinking this is everything you have to do — don’t. There might be more I had written down on my checklist, but these are the ones I remember off the top of my head. This isn’t meant to be a comprehensive GDPR compliance article, so don’t treat it like one.)</p><p>Of those, there was no real way to streamline the backend changes or tooling that would need to be created. That was just something I was going to have to suck up and do for each.</p><p>The policy and procedure changes and notifications would be pretty similar between the different applications and websites, so I was pretty sure I could have those tweaked as needed without too much of a hassle.</p><p>When it came to the consent forms, it <em>seemed</em> like it was something that could be streamlined (ala copy and paste), but as I had hacked together the one I had, I secretly knew that it wouldn’t be as cut and dry as I’d like it to be. Not only did each website I have have a different “theme” to it, but they all had different analytics and tracking tools that would need to be managed. Given that the codebase I had was just one giant wet box of spaghetti, there would probably be some effort there. Writing a new consent form from scratch for each site wasn’t going to be an option, either — there was surprisingly <em>a lot</em> of work that went into getting that first version out.</p><p>So I decided to put the consent form work on hold — until I could create something that <em>could</em> be reusable for all of my websites — and tackled all of the other changes that needed to happen en masse.</p><p><strong>Cue the GDPR Mass Hysteria</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*0haFZu-9jK3wU9pPDS5ftA.jpeg" /><figcaption>I’m pretty sure the “D” in GDPR is for “Danger” — Just like my middle name!</figcaption></figure><p>When I finally came back up for air, it was one week out from GDPR Day, and we were in the thick of the GDPR fear-mongering news cycle.</p><p><em>Everyone </em>and their grandmothers were up in arms about GDPR.</p><p>Newspapers, TV, podcasts, the Twitterverse, Slack groups — <em>everyone</em> was talking about GDPR like it was a fucking asteroid headed to wipe out the entire internet.</p><p>And for many people, this was the first time they had even <em>heard</em> of GDPR!</p><p>Top executives of major corporations (not to mention us mere proletariats running web-based businesses) were <em>completely blindsided</em> by this impending regulation that they had no idea was a mere <em>week away.</em></p><p>And let’s not foget <em>all</em> of the GDPR emails that were flooding everyone’s inbox, forcing the electric power grid to the brink of failure from all of the servers working overtime to churn out email after privacy protecting email.</p><p>Given that I was pretty far into the game and only needed to get my consent forms up and running, I was feeling pretty good about where I was at, and was able to sit back and watch the drama unfold with a healthy sense of amusement.</p><p>I’ll admit, the GDPR memes and jokes were quite enjoyable, particularly the American Choppers one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/1*ErlQFrRojIVZ63Utk4NDVw.gif" /></figure><p>And let’s not forget the GDPR pirates:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*SVSF1zawNte5PPe04wTDIQ.jpeg" /></figure><p>I even threw my hat into the mix as well:</p><h3>Clifford Oravec 👊💥 on Twitter</h3><p>The GDPR Drinking Game 🍻🎉 Receive a GDPR email: Drink half a beer. Encounter a cookie consent form: Finish your beer. Agree to a Privacy Policy: Take a shot. Countersign a DPA: Take two shots. If a service you use shuts down because of GDPR: Do a flaming shot. https://t.co/UC5hBrYbX3</p><p>(I’ll be honest, I spent more than a few nights ROFL-coptering at these kinds of shenanigans…)</p><p>There were even people joking about “GDPR-as-a-Service”.</p><p>As I sat down one night to start working on a common consent form solution for my websites, I saw in a moment of serendipitous information alignment all of the cards on the table.</p><p><strong>A “Guess” is Born.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*oeEsOYd81OytYly20UgkQg.jpeg" /><figcaption>- Tom Smykowski: The Patron Saint of Ideas.</figcaption></figure><p><em>“What if…”</em></p><p>That’s how most ideas start, and this one’s no different.</p><p>(Except <a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1">I call them guesses</a> — and treat them as such.)</p><p>One week out from the GDPR deadline, there was no denying that GDPR was <em>hot</em> and at the forefront of everyone’s minds.</p><p>So many people were scared and intimidated by all of the <em>work</em> they would have to do to “get compliant”. (Not to mention the complete lack of <em>guidance</em> on any of it.)</p><p>I knew I was going to have to build and implement a common consent form solution for my websites — and that I had a week to do that in.</p><p>But <em>what if</em> I could take what I was planning on building and turn it into a SaaS (that I could use) instead?</p><p>After all, pretty much <em>everyone</em> would need one of these things. So why not be the person to give it to them?</p><p>There were four big questions in my mind:</p><ol><li><strong>Could I even <em>build this thing </em>in just a week?</strong> Because come hell or high water, I needed those consent forms myself. And if I <em>didn’t</em> get this out there by then, I would probably miss out on the opportunity I thought I saw.</li><li><strong>Would people even use this thing?</strong> As a developer, I tend to assume that most other people are like me and can just cobble together their own solutions. Was this thing valuable enough to non-developers that they would want to use it? Was it hard enough for them to cobble together a consent form that they’d be more willing to use one “out of the box” than trying to do it themselves? Was this a painful enough problem for them that they would seek out a solution for it? And would they be willing to use it once they found it?</li><li><strong>Would people <em>really</em> pay for it — and how much would it be worth to them?</strong> Sure, this might be able to solve their problem — but were they willing to drop coin down to have that problem solved? What would have to be there for them to do that? And how much would they be willing to pay?</li><li><strong>Could I even get enough traffic to this thing in that kind of timeframe?</strong> At some point in the very near feature GDPR hysteria would wear off. Would I miss that cut off and miss out on the opportunity? I felt that this was a <em>super</em> tricky timeline to work with — hit it, and you could be golden. Miss it, and you just wasted a week of your life.</li></ol><p><strong>Let’s go Branson on this shit.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*GGIU_4zVFGsDM_O2lfLaQw.jpeg" /><figcaption>I wonder how many times this quote was used as the basis of a failed startup…</figcaption></figure><p><strong>No time for propriety.</strong></p><p>Normally, I’d follow<a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1"> a different playbook for launching a startup</a> than just coding my brains out and throwing it against the wall to see if it’ll stick.</p><p>But with a timeline of <em>one week</em> to get this thing out the door or miss the opportunity, there was just no way that I could do that.</p><p><strong>But you better know your downside.</strong></p><p>One thing that Sir Richard says about the “Screw it, let’s do it” decision-making framework is that you better know about and protect against your downside before pulling the trigger.</p><p>What that means is knowing what can go wrong and having a plan to gracefully recover from it before throwing yourself into the fray.</p><p>I knew that I would have to build this thing in one week — <strong>max</strong>.</p><p>So from a time investment perspective, I could potentially lose one week of my time.</p><p>Having already lost well over a month of my nights and weekends implementing GDPR, I was willing to do the same for one more week. (Besides, there aren’t any good shows on anyways — and even if there were, I don’t watch TV. So.)</p><p>I also knew that if I didn’t have this thing built within the week, that I could be in a bad position myself and not have my consent forms ready for GDPR Day.</p><p>So I decided to follow a strict order of events that would guarantee that <em>my</em> ability to have consent forms for my websites didn’t get overrun by the requirements of having a functioning SaaS.</p><p>That meant that I would first build out the consent form logic, even if it meant that I had to hack things together to get it to run across my different sites. And <em>only after</em> that was done would I even <em>think</em> about touching the other things I would need in place to have a functioning Saas — like the form builder, the analytics, the account creation and management, the payment processing, and the marketing site.</p><p>After making these assessments — and <em>only</em> after making them — I dove in.</p><p><strong>What should I call this thing?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*sDIVMHFM13SvBHQ1zmoT4w.jpeg" /><figcaption>That would actually make it a hell of a lot easier…</figcaption></figure><p>Coming up with names for things is <em>hard.</em></p><p><em>Really</em> hard.</p><p>And boy do I suck at it.</p><p>I hate those clever brands that come out that make it look just so <em>effortless</em> and <em>obvious</em> with how cool their brand names are.</p><p>I’m not one of those guys.</p><p>But I didn’t have time to dwell on that.</p><p>I came up with five names having to do with “consent” (since we’re building consent forms here!), including “ConsentJS” (because adding “JS” to anything makes it cool, right? [and I thought it might appeal to the developer crowd]) and asked my girlfriend which of the five she liked best.</p><p>I didn’t like her answer, so I registered domains for all five and started to build a project for “ConsentJS” because it was the first one I came up and I figured “trust your gut”, right? (Caveat: She’s usually right, so only time will tell if that was the right call or not.)</p><p>The moral of the story? Pick and name and run with it. It doesn’t matter, and you shouldn’t wrack your brain over it for weeks on end. You can always change it later. (Even “Stripe” used to be called “/dev/payments” at one time, so there.)</p><p><strong>What the fuck am I building?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*mOhmATCzB4TirVKbRpjVzA.jpeg" /><figcaption>It always starts with “a good idea”…</figcaption></figure><p>Because time was of the absolute essence, the next thing on the list was to get a <em>clear</em> idea of what the fuck it was I was going to build.</p><p>There was <em>no sense</em> in just starting coding this thing without having a <em>clear</em> idea of what it would — and would not — do.</p><p>Consider this my “criteria for success” or my “MVP” — what was the <em>least </em>amount of functionality that would be necessary to make this thing valuable? What would I need to have in place in order to make it worth paying for?</p><p>And that was part of this exercise, too — to figure out what needed to be there to make it valuable enough that people would pay for it.</p><p>Given that I only had a week to build this thing, I was <em>very</em> unsure about what needed to be there to make that whole “people are willing to pay for this” thing work.</p><p>So I got to thinking: <em>What if I </em><strong><em>can’t</em></strong><em> get people to pay for this? How do I make it so that I can still get </em><strong><em>something</em></strong><em> out of this until I get the time (and input) to learn what’s needed in order to make it worth paying for?</em></p><p>My mind went back to one of the main concerns/obstacles that I had with this whole endeavor— being able to get this thing in front of enough people in as short a period of time as possible before it was too late.</p><p>And the answer came to me: Marketing.</p><p>If I could get <em>marketing</em> out of this thing to help drive traffic to it until I <em>could</em> figure that whole “it’s good enough to pay for” thing, then <em>that </em>would be worth it. (Aside from just having a common consent form solution for me to use.)</p><p>And so I decided that — in order to protect the downside of <em>not</em> being able to build something that people would be willing to pay for in under a week — that I would do a freemium play with a free tier and a “Powered By” link to try and “make it go viral”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/293/1*tj0lhdN8Nc183i8c5a-nwg.jpeg" /><figcaption>(Don’t worry, I’m not <strong>that</strong> fucking stupid.)</figcaption></figure><p>After all, it’s better to walk away with something instead of nothing.</p><p>Aside from that, I determined that the “constraints” I would force on this project were (in no particular order):</p><ul><li>There would be a basic form builder that would allow people to provide their own text and colors for their consent forms (but that’s <em>it).</em></li><li>The form builder would let people specify the different items they needed to get consent for, including the JavaScript tracking codes for those items.</li><li>The form would behave like my “prototype” form did — it would ask people if they were EU natural persons and based on their response, it would only execute JavaScript for providers where consent was given, or it would simply execute <em>all</em> of the JavaScript on file.</li><li>There would be a free tier and at least one paid tier (for the time-being). The free tier (at the very least) would have a “Powered By” link.</li><li>There would have to be a <em>clear</em> “separation of value” between the free tier and the paid tiers.</li><li>The free tier would be a “minimal” offering — it would get the job done, but would not have any bells and whistles that a serious business would want.</li><li>It would be a centralized service — meaning, the service would be responsible for serving up the consent form. This was in contrast to a “here, you can download this and run it yourself”. It’s also necessary to justify the paid SaaS offering.</li><li>The entire thing had to be <em>completely</em> anonymous — that means no personally identifying or identifiable information collected <em>at any point</em>. I couldn’t log <em>anything</em> that wasn’t 100% anonymous from customers’ websites.</li><li>The paid tier would have anonymous consent reporting — so that they could get statistics and metrics on what people were giving consent for (or not giving consent for), and which could be used to demonstrate compliance. The free tier would do no such reporting, and have no such functionality.</li><li>It would be one account and one consent form per website — no way was I going to build out a multi-website solution on the first pass.</li><li>The marketing site and app would share one codebase. I usually split these out into two separate things, but that creates integration work, and I needed to get this thing up and running — fast.</li></ul><p>I listed these constraints and goals out in my notebook and did a quick sketch of the form builder and set to work:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RlGAg-mcrSga4l7sR53anw.jpeg" /><figcaption>(Yes, that’s a “piggy” in the lower right hand corner. And yes, that’s what happens when you leave your startup shit out on the kitchen island.)</figcaption></figure><p><strong>Building This Bad Boy</strong></p><p>So I’m sure you’re sitting here going “How the fuck is he going to pull this off?”</p><p>A full SaaS — in one week?!</p><p>And part-time at that?!</p><p>But I did.</p><p>And here’s how:</p><p>I cheated.</p><p>Because I’ve done this kind of shit before, I was able to piggyback on a lot of my existing codebases and infrastructure. (See why you should “get shit out there” — you never know when you’ll be able to “borrow” from one of your existing projects and get something out the door <em>fast</em>!)</p><p>That being said, it wasn’t nearly as clean (or as effortless) as you might be thinking.</p><p>I had an existing project that served up a JavaScript snippet to customer websites that I thought could be a good base to start from, so I made a copy of it and started taking a scalpel to it to make it work for this project. It was actually quite a bit of work to rip out the parts I <em>didn’t</em> need and only keep the things that I <em>did</em> need.</p><p>I didn’t worry about adding it to source control, I didn’t worry about creating feature branches — I just copied it on my hard drive and dug in, damn it to hell if my 2013 MacBook Pro (the best machine I’ve ever owned, and which I refuse to upgrade from until Apple gets their shit in order) decided to die on me.</p><p>I also didn’t pick a fancy framework I was unfamiliar with.</p><p>There was no time to fuck around with learning <em>anything</em> new. If I couldn’t do this with what I already knew, it wasn’t going to happen.</p><p>Period.</p><p>I used the same version of Node and React that I had used on other projects and got to it. (Yeah, I know that might sound fancy, but I’ve been banging at those for a while, so they ain’t fancy to me — and it doesn’t matter, either. I could have built this thing in Perl and jQuery if I were so inclined. Do what works for you — no one gives a fuck what you’re running but you.)</p><p>And true to my word, I stuck to my build plan.</p><p>Because if you <em>don’t </em>protect your downside, you’ll be kicked to your backside. Guaranteed.</p><p>I built the consent form functionality first — regardless of whether or not that meant that I would have a functioning SaaS.</p><p>Once that was done, I put together the form builder, the basic SaaS infrastructure, and finally the marketing site — in that order.</p><p>It was a whirlwind of activity over the course of a weekend and a bunch of late nights — but I did it.</p><p>And if you think that’s all there was to it, and that <em>this </em>is where the story ends, you’re sorely mistaken.</p><p><strong>Murphy’s Law: Or, throwing my back out, getting sick, and everything else you could want to go wrong.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*VRyK8lfKhy6dQc1oGs7u-Q.gif" /><figcaption>Oh, you have *one week* to do something? Let’s just go ahead and throw everything we can possibly dream of to fuck with you, mkay?</figcaption></figure><p>I started work on ConsentJS the night of Friday, May 18th, 2018 — one week from GDPR Day.</p><p>As is often my habit, I sat out on my deck and played some tropical house while I banged away at my latest enterprise.</p><p>When I tried to rise from my chair around three in the morning, something wasn’t right.</p><p>My fucking back.</p><p>It was <em>shot.</em></p><p>I actually had to call my (sleeping) girlfriend on her phone to get her to come downstairs and help me get out of my chair and into the house.</p><p>It was <em>that</em> bad.</p><p>And it didn’t get any better.</p><p>Each day that I continued to work over the weekend was <em>pain.</em></p><p>Sure, I grabbed some bags of ice to try to make it less painful, but that shit wasn’t helping.</p><p>And that got me pretty pissed off.</p><p>You see, I have this ultramarathon that I’ve been training for for <em>awhile </em>(that’s 100 miles of running, by the way— all at the same time). And with a shot back, I knew that I was now going to have to take <em>weeks</em> off from training, which (at this point in time) could and would completely jeopardize my chances of even being able to finish it.</p><p>But if there’s one thing that bootstrapping has taught me — it’s that emotions are bullshit and will simply serve to destroy you if you let them.</p><p>So I accepted the fact that my back was fucked and moved on. There was no use crying about it — it wouldn’t fix a damn thing.</p><p>And then Monday hit.</p><p>Monday, I got sick.</p><p>And I assure you, there is nothing quite like getting sick while having a thrown-out back. (Use your imagination if you can’t picture it.)</p><p>To top it off, a few days later, <em>everyone</em> got sick.</p><p>Because, you know, <em>why the fuck not</em>?</p><p>As I’m writing this a shade over one week later, my back is <em>still</em> fucked up. I <em>still</em> fucking hurt like hell.</p><p>But I didn’t throw the towel in.</p><p>And I don’t regret it.</p><p>Because if I <em>didn’t</em> persevere through this shit, I wouldn’t have anything to be sitting here writing about, now would I?</p><p><strong>Cue that glorious self-doubt.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*6VaQujESLRkERxXbr3uNYw.jpeg" /><figcaption>Fuck you, you zombie asshole.</figcaption></figure><p>About mid-week, that bullshit nemesis — Self-Doubt — decided to creep up on me.</p><p><em>What the fuck am I doing?</em></p><p><em>Nobody’s going to want to use this thing!</em></p><p><em>You’re killing yourself for </em><strong><em>nothing</em></strong><em>, man!</em></p><p><em>This is a waste of time — and you’re the fucking sucker for wasting </em><strong><em>even more</em></strong><em> of your life on shit like this!</em></p><p><em>You’re going to bust your ass to do this and then </em><strong><em>nothing</em></strong><em> will come of it!</em></p><p><em>You have no life! All you do is </em><strong><em>work</em></strong><em> and </em><strong><em>code</em></strong><em>!</em></p><p>Yeah — fuck you too, buddy.</p><p>I <em>knew</em> that if I missed this opportunity — like I had missed <em>so many</em> <em>others</em> — that I would kick myself.</p><p>I had found a gap in the market — and I needed to <em>exploit that shit.</em></p><p>This opportunity would <em>not</em> come again — after all, there’s only <em>one</em> GDPR Day!</p><p><em>This day would be </em><strong><em>mine</em></strong><em> — I would not sit there and read on Hacker News about how someone else had taken my idea and executed on it and had the success that was </em><strong><em>mine</em></strong><em> for the taking!</em></p><p>Fuck <em>all</em> of y’all, this was <em>going</em> to happen.</p><p>I fired up some music to get my blood pumping. I listened to podcasts that inspired me. I talked to my girlfriend about “my feelings”. And most of all — <strong><em>I FUCKING FORCED MYSELF TO DO THE FUCKING WORK.</em></strong></p><p>Fuck you, Self-Doubt, you fucking zombie asshole.</p><p>I’ll <em>never</em> fucking let you run my life again.</p><p><strong>I’m not going to make it.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*tzFMBY8gWw44FQJ--vBZSg.jpeg" /><figcaption>(::Looks at spice rack:: “Nope — we’ve still got plenty of thyme!” 😜)</figcaption></figure><p>A few days in, and it had become quite clear to me that I had bitten off a monster.</p><p>Even with my little SaaS cheat codes, this was still <em>insanely</em> ambitious.</p><p>I <em>thought</em> I might be done with it on Monday night.</p><p>Come Tuesday, I was <em>pretty sure</em> I’d be done before the night was through.</p><p>Wednesday came, and I was <em>still</em> fairly optimistic that this would be over soon.</p><p>Come Thursday (the 24th), I <em>knew</em> that this shit had to be <em>out the fucking door by midnight</em> or I had missed my window.</p><p>It was in those days that had I realized that I had committed the ultimate developer fallacy: I had been overly optimistic and had completely underestimated the effort involved in building this thing out.</p><p>Realizing that <em>this</em> was what was happening, I started adjusting and compensating so that I would have <em>something</em> to ship come Friday (GDPR Day).</p><p><strong>Welcome to the cutting room floor.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vBn8UF9rGKOQUk9MNDMK5g.jpeg" /><figcaption>And no mobile! And no responsive design! And no self-service management! And no admin screens! Use the fucking database like everyone else, you fucking Web 2.0 hipster!</figcaption></figure><p>It’s at this point that I realized that in order to hit my deadline of Friday that <em>anything</em> that was <em>non-essential</em> would have to be taken out behind the woodshed and be put down.</p><p>Whether that meant trashing a feature or completely ignoring it — they weren’t going to be getting in my way.</p><p>In no particular order, the things that got cut from the final product were:</p><ul><li>Anything “mobile”.</li><li>Anything “responsive design”.</li><li>Anything “self-service management”, including the ability to self-cancel or self-upgrade or change payment information.</li><li>Anything “admin”. There’s a database for that.</li></ul><p>If this was going to happen, it was going to have to be 100% focused on the desktop customers that I was pretty sure I would be able to bring in — and it would have to be focused on the things that they would actually <em>give a fuck about</em> in order to sign up and give me money.</p><p>Everything else could go fuck itself.</p><p><strong>But! But! But!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*EgWHDGr3o9ZdgFL-MWav9A.jpeg" /><figcaption>Yeah, fuck those too.</figcaption></figure><p>You spend your time writing unit tests.</p><p>I’ll spend mine making money, mkay pumpkin?</p><p><strong>The mad dash for a marketing page — and pricing.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*Rn7Eq-2QCfyM91blW_oNNA.jpeg" /><figcaption>You miss 100% of the deadlines you don’t hit.</figcaption></figure><p>By early Thursday night, I had finished the app and the supporting SaaS infrastructure.</p><p>I had mere <em>hours</em> to build out the marketing site and to finalize the pricing tiers that I would be offering.</p><p>In other words, it was <strong>GO</strong> <strong>TIME.</strong></p><p>Some people fire up the coffee pot at this point, but I prefer to bust out some post-hardcore and crack open a six pack of craft beer.</p><p>Regardless of how you do it — even if you’re a tea drinker — you <em>know</em> it’s time to put up or shut up.</p><p>(And as you can tell if you’ve gotten this far, shutting up isn’t one of my strong suites. But <em>boy</em> do I know how to put up.)</p><p>So I got to it.</p><p>I had kept a running list of the benefits (not features!) that I thought ConsentJS might be able to provide over the past week, so I used those as a template and did the best I could to come up with a design and copy in a handful of hours.</p><p>One of the things that I had deferred up until now was nailing down my pricing tiers, and I knew it was time to bite the bullet and come up with my best guess.</p><p>I had thought about this on and off in the back of my head for the past week, and what I was thinking was that:</p><ol><li>There was no way people would <em>want</em> to pay monthly for this kind of thing. I know that I personally hate monthly subscriptions — and that they often can lead to high churn when customers keep seeing a charge on their credit card statement.</li><li>If I went the <em>annual</em> route, that would mean it was like a one-time purchase in essence, and would have less of a churn risk.</li><li>The annual plan would also mean I could get more money upfront than I would in a traditional month-by-month SaaS.</li><li>If I <em>did</em> go the annual route, I would have to have an attractive and affordable annual rate — I couldn’t charge $500 a year and hope to make that work.</li><li>The tiers would need to have some <em>compelling</em> differentiator between them.</li><li>There would be no trial period — if you wanted to buy, you’d buy — otherwise you could hop on the free tier.</li></ol><p>Based on that, what I came up with was this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mj5sh-z1ENRdLoXEefOlzg.png" /><figcaption>(I don’t mean to brag, but it took me like 10 minutes to come up with that — I was on fire 🔥)</figcaption></figure><p>I finished coding everything up by 11:30 PM — just in time to launch this puppy.</p><p><strong>The Finished Product</strong></p><p>Before I move on, I’m going to show off a bit and show you some finished screenshots of <a href="https://consentjs.com/">ConsentJS</a> in action (this is <em>my</em> story, so I get to do what I want 😜)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMTZONJBrE6_Z9s6K54o6g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3FQpUkLjpKTZLzwwLKs4nQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z2vFeXdXFUAe2kOFTsSM9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kFThN4SDIydmMCRrix7ryQ.png" /></figure><p><strong>Deployment (and fucking Murphy’s Law again)</strong></p><p>I had set a deadline of getting this thing out before midnight of GDPR Morning.</p><p>At 11:30 PM, the day before, I was set to do just that.</p><p>I had all of my ducks in a row, and I had even done a test deployment to my staging environment.</p><p>So I kicked off the deployment process to make this thing LIVE.</p><p>And…</p><p>FAIL.</p><p>FAIL.</p><p>FAIL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*sSK3CeJY26tqxjJ9ZBUy9Q.jpeg" /><figcaption>There is only so much kicking that my ass can take.</figcaption></figure><p>The fucking production build was failing for some cryptically “obvious” reason buried in the miles of log files spewed on my screen.</p><p>At this point, I am <em>fucking tired.</em></p><p>I’ve been running on empty, and I feel like <em>absolute shit.</em></p><p>I <em>literally</em> wanted to put my head down on my desk and fall asleep (<em>literally</em>, literally).</p><p>(Now don’t you go blaming that delicious craft beer on this one! Without it, my perfectionist developer inhibitions would have probably gotten the better of me and I wouldn’t be here writing about this whole thing!)</p><p>(But yeah, you’re right — the beer probably didn’t help at this point.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*OKVp51ok7cqtJfLDDps2LA.gif" /></figure><p>I spent the next (blurry-eyed) hour and a half fucking with my build and deployment until I got it up and running and was able to verify that everything was “right” (and finding and fixing elusively last minute bugs — of course).</p><p>Then, knowing that there was <em>no way</em> that I was going to be able to “intelligently” promote this thing until I got some sleep, I sent out a tweet to feel like I at least let <em>someone</em> know that this thing was now out and available for business:</p><h3>Clifford Oravec 👊💥 on Twitter</h3><p>😢 To everyone out there crying last minute tears of #GDPR angst and anguish, I present to you: ConsentJS. https://t.co/1YYnPYnMhW (You&#39;re welcome 😉)</p><p>And then I crashed.</p><p><strong>Holy fuck balls, I was right.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*zGNVKdJc4sTwKhMWnS3YWQ.jpeg" /><figcaption>No way, dude! Dude, no way!</figcaption></figure><p>I woke up about four hours later.</p><p>I grabbed my phone and tried to use it with the one eye I could muster to open.</p><p>And there — at 3 AM — a mere <em>two hours</em> after I had “launched” (if you could even call it that)— I had a signup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*xuz6mwzeWyEkAuzM90U9OQ.jpeg" /></figure><p><strong>Now where do I promote this thing?</strong></p><p>It was the morning of GDPR Day, and I had <em>made the deadline</em>. (Well, okay, I was technically off by one hour. I <em>had</em> wanted to hit it at midnight, afterall.)</p><p>Despite everything that had gotten in my way, I had pushed through and gotten this thing up.</p><p>And people were already signing up for it!</p><p>I knew that I had limited time to make the biggest splash that I could with this thing, and that I needed to get to work.</p><p>The only strategy that would work in this short of a timeframe (24 hours!) was one that leveraged places where there were <em>lots</em> of people already congregating— I would need to go to websites with sizable followings of people who were sweating the fact that it was GDPR Day and <em>try</em> to stand out from the noise. I needed <em>reach. </em>There was just simply no other way.</p><p>There was no time for SEO, no time for fucking around with “growth hacks”.</p><p>This had to be an all-out PR blitz if it was going to work at all.</p><p>At the same time, I told myself that I only needed to make <em>one </em>point of traction work to achieve my immediate goals.</p><p>Whether I liked it or not, this <em>was</em> going to be a long-haul project that would need to ultimately rely on SEO and other channels.</p><p>But I just needed to get <em>one thing</em> to work for today for me to consider it a success and to (hopefully) get a leg up on this whole thing.</p><p>SEO and those others could wait — this had to happen <em>now.</em></p><p>So I got to it and started promoting on social media and in some forums that I thought might jump on it (and they did). This was a good exercise, and I’m glad I did it. I got <em>very</em> positive feedback from these forums, and that kind of gave me the additional confidence that what I had might be a real winner.</p><p>But I knew that I needed to up the ante here. The forums were yielding good and positive results, but they weren’t <em>off the chain.</em></p><p>So I decided to go all in and go after the motherload: Product Hunt.</p><p><strong>Product Hunt</strong></p><p>Now, I’ll be the first to admit that I don’t really “get” Product Hunt like other people seem to.</p><p>I just never saw how I could make it <em>work.</em></p><p>And so I’ve just mostly avoided it (it always seemed to me like another Digg or Hacker News-style lottery in a way).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7tcutXNv5LmLY7anyIP_A.jpeg" /><figcaption>Me trying to figure out Product Hunt. True story.</figcaption></figure><p>But something inside of me said, <em>“You need to try out Product Hunt with this one.”</em></p><p>I knew that this would be <em>insanely</em> topical (it <em>was</em> GDPR Day, after all), so I thought I might have a shot at getting <em>some</em> traffic out of it.</p><p>And since <a href="https://medium.com/@cliffordoravec/the-morning-after-startup-famous-for-24-hours-dab9d6b2c036">I already won the Hacker News lottery once before</a> — why not try this one?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*-sfgbBubxhAUfMSskxbd5Q.jpeg" /><figcaption>Sounds about right to me.</figcaption></figure><p>So I did the only sensible thing I could think of — I researched some of the most recent Product Hunt “top” posts, figured out what was in common between them all, and then ruthlessly applied that same formula to my own post.</p><p>I hit “Post” and…</p><p>Nothing.</p><p>But that was okay, because that’s about what I expected.</p><p>So I got to work promoting the post a bit on Twitter and elsewhere.</p><p>Those efforts, over the course of a few hours, got me something like 13 or 14 upvotes.</p><p>Now, I have no idea if that’s bad or good, so I decide to just keep going with that strategy.</p><p>I was getting half-way decent traffic from the other places I had posted, and I <em>really</em> wanted to try to get a “big win” for today. (That, and I <em>really</em> didn’t want to have to go over to post on Hacker News — I had left my flame retardant suit at the dry cleaners last week).</p><p>So I just kept plugging away.</p><p>A few hours later, I decided to call it quits for the day.</p><p>I was pretty tired from working my ass off all week to get this out the door, and I had felt like I had done an okay enough job at driving some traffic and getting some signups for one day.</p><p>Maybe I didn’t get that massive PR spike that I was hoping for — but I was definitely still walking away with what I considered a successful first day. I’d just have to try to stir up some noise tomorrow in the morning…</p><p><strong>I spoke too soon.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*x9PSkVznQYm7kKr7KEjpkA.jpeg" /><figcaption>Yeah, buddy!</figcaption></figure><p>Earlier Friday night, I had seen this little thing pop up on my Product Hunt page that said something about “FEATURED IN 6 HOURS”.</p><p>Now, considering the fact that this is probably the first time that I’ve used Product Hunt in two years, and that I’ve never really “launched” anything on Product Hunt — I had no fucking idea what that really meant.</p><p>An hour later, it said 5 hours.</p><p>And at midnight, when I decided to throw the towel in for the day, it was at 3 hours.</p><p>So when I woke up in the morning and checked on things, you might be able to imagine my surprise…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/279/1*oq8uIavQ1EZ-4tQVlgLD3g.png" /></figure><p>I had apparently gotten featured on Product Hunt’s homepage at around 3AM.</p><p>And now the Product Hunt Firenado of Awesome was in full effect.</p><p><a href="https://www.producthunt.com/posts/consentjs">ConsentJS had apparently made the #1 Product of the Day</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*pMSMq6_seLIbESOmui7hyg.png" /><figcaption>(Thanks to <a href="https://medium.com/u/4b8e6ae70185">Cory Zue</a> for the heads up and screenshot of ConsentJS’s very brief #1 spot title!)</figcaption></figure><p>But of course, by the time I got to see it, it had dropped to #2.</p><p>😢</p><p>Thankfully, that didn’t seem to affect things too much 😉</p><p>Now, at this point, it’s Saturday — the day <em>after</em> GDPR day. And it’s a holiday weekend. So <em>maybe</em> I might have had more outsized results had I gotten to the top <em>on</em> GDPR day. But I’m not going to go crying about that, because it was still <em>awesome.</em></p><p>Having lived through a Hacker News Tsunami, and now a Product Hunt Firenado of Awesome, I can say this:</p><p>The Hacker News Tsunami is <em>terrifying.</em> It’s <em>way</em> more traffic than you could possibly imagine, and it’s <em>way</em> more attention than is remotely comfortable.</p><p>By contract, the Product Hunt Firenado of Awesome is <em>majestic </em>and <em>inspiring</em>. It’s <em>just the right</em> amount of traffic and attention to make the whole thing honestly fun and enjoyable.</p><p>Traffic was coming in at a steady clip, and — best of all — <em>people were signing up!</em></p><p>The Product Hunt Firenado of Awesome had even brought me my first paying customer — a $99/year Pro purchase! 🍾</p><p>I knew that in order to maintain that #2 spot that I would need to keep promoting my Product Hunt post, so I basically hunkered down and spent all day Saturday doing just that.</p><p>At the end of Saturday, I had gotten somewhere in the neighborhood of 240 upvotes and around 1,071 visits to ConsentJS.</p><p>Best of all, I was able to close out the day with that #2 Product of the Day badge:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2LeiRzo2W6iS5-CQYZCiyA.png" /><figcaption>Boo-yah!</figcaption></figure><p><strong>It’s The Gift That Keeps On Giving, Clark.</strong></p><p>Sunday I had planned on writing this writeup.</p><p>But the Product Hunt Firenado of Awesome was apparently <em>still</em> kicking out awesome.</p><p>So I dug in and ran with it.</p><p>And then the same thing happened on Monday, too.</p><p>(Except I decided to actually start this writeup and to get the next marketing moves ready for the upcoming week.)</p><p>In all, ConsentJS closed out the holiday weekend with 358 upvotes.</p><p>Not bad for my first real go with Product Hunt, right?</p><p><strong>So is my MVP “validated”?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*m_zjmUAeu2z1mZ3kUh_Vfg.jpeg" /></figure><p>Why yes, I’d say it is. 🙃</p><p><strong>Why did it work?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ADvrvJ83FT2fAmHVCKMZUQ.jpeg" /><figcaption>(Here’s a hint — it wasn’t my code.)</figcaption></figure><p>So yeah, I’m pretty pleased with myself right now, but I’m not that much of an egomaniac that I’m going to take credit for my “genius” when there were a lot of factors that contributed to this success that were beyond my control.</p><p>So to be fair and honest, here are some reasons why I think this whole thing actually worked. Consider it a retrospective:</p><p><strong>Timing. </strong>If I didn’t get the timing on this whole thing <em>absolutely right</em>, it probably wouldn’t have gone anywhere. And technically, you could argue that I actually fucked my timing up a bit by not getting this out a day earlier (imagine how much <em>more</em> awesome the Product Hunt Firenado of Awesome <em>could have been</em> if I had gotten featured on GDPR Day!)</p><p><strong>Exploiting a hot news item. </strong>If GDPR <em>wasn’t</em> such a huge topic of interest — and dominating everyone’s news and Twitter feeds — this probably would have only been blip on the radar. I will admit that I saw this and exploited it ruthlessly.</p><p><strong>Being in the thick of it. </strong>I would most likely not have been able to see the potential for this <em>exact</em> thing if I hadn’t been in the trenches, working on solutions for GDPR myself. Sure, I <em>might</em> have been able to think “Man, this GDPR thing is a huge opportunity” — but I most likely would <em>not</em> have been able to see that the consent forms angle was the one I should go for.</p><p><strong>Being open to seeing the opportunity. </strong>If I didn’t allow myself to ask “What if?”, this never would have happened.</p><p><strong>Thinking about the market. </strong>Any idiot can ask themselves “What if?” I took the time to try to <em>logically</em> <em>prove</em> my “What if” by asking myself questions about the size of the potential market, the ways that I could reach that market, whether or not this was something valuable to that market, and how much the market would be willing to pay for such a solution.</p><p><strong>Being prepared. </strong>Already being in the game of having shipped something (anything!) means that I had <em>resources</em> I could draw on. If I didn’t have an existing codebase and infrastructure, I would have spent an inordinate amount of time cobbling those things together, and I would have missed the opportunity. This is why it helps to get shit out there. Once you’ve gotten shit out there, you’ll know how to get <em>more</em> shit out there. So take note, kids — get shit out there, even if it’s total shit. Then use that shit to get less shittier shit out there.</p><p><strong>Not giving up. </strong>I could have thrown the towel in on this like a little baby at any point along the way. I was burned out from doing GDPR implementations, I was in fucking serious pain, I had a household full of sick people (myself included), and I had nagging self-doubt. But <em>none of those</em> could physically stop me from doing this, so <em>I didn’t let them.</em></p><p><strong>Finding a big audience. </strong>This was <em>key. </em>Without being able to tap into the Product Hunt Firenado of Awesome (or a similar source of awesome) — where there were people <em>very</em> interested in GDPR things — this would have been a <em>slog</em> to promote and get traction for (and I was completely prepared to do that, if need be).</p><p><strong>Promoting. </strong>You can’t just expect people to know to check your stuff out. You need to promote your stuff — ruthlessly. Even if it’s on Product Hunt, you need to promote the <em>fact</em> that you’re on Product Hunt!</p><p><strong>Luck and the awesomeness of other people.</strong> Finally, <em>none</em> of this would have been possible if I didn’t have the support of all of the awesome people who upvoted ConsentJS on Product Hunt, and I <em>definitely</em> wouldn’t have gotten nearly as far without the awesome people at Product Hunt choosing to feature ConsentJS on the homepage. Call it luck, call it serendipity, call it what you like — but those aren’t things I could have done for myself. And so here’s a sincere <em>thank you </em>to everyone who helped in any kind of way.</p><p><strong>What’s Next?</strong></p><p>Now that ConsentJS is off to a good start and I can see just how much potential it has, it’s time to take it to the GDPR masses!</p><p>That means more marketing and promotion in places where people are talking about and looking for GDPR solutions.</p><p>And in all honesty, this is the real test of whether or not this product will achieve product-market fit: Whether or not I can build <em>sustainable </em>acquisition channels to the market. Because without that market, you can’t have PMF.</p><p>I’ll keep you posted.</p><p>In the meantime, you can keep tabs on my progress by following me here on Medium @cliffordoravec or on Twitter at <a href="https://twitter.com/cliffordoravec">@cliffordoravec</a>.</p><p>If you haven’t checked out my ongoing masterwork, <em>The Epic Guide to Bootstrapping</em>, you can <a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1">read the Medium series here</a> — or you can check out <a href="https://cliffordoravec.com/">the upcoming full-length book here</a> (which is <em>not</em> a blog to book — it’s an actual, all new, all original, honest-to-goodness, book).</p><p>And of course, if you’re looking for a GDPR consent form solution for your website, you might want to check out <a href="https://consentjs.com/">ConsentJS</a> 😉</p><p><strong>(Epilogue) Coming Around: A Consent Form is Like a Nutrition Label for Your Website</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*8mJ4y4WXwwFqdRV9D9MqtQ.jpeg" /><figcaption>Okay, so what the fuck’s in this shit?…</figcaption></figure><p>I wanted to write a real quick epilogue about my changing views based on being in the thick of GDPR the past few months.</p><p>If you’ve read the article, you’ll know that I don’t think that it’s all lollipops and candy canes.</p><p>But that doesn’t mean that I think it’s all bad — just horribly executed.</p><p>When it comes to the consent form requirements, what I’ve come to realize is that the consent forms are really like nutrition labels for a website. They tell people “here’s what’s inside”, which is <em>not</em> a bad thing.</p><p>This makes it our responsibility as marketers and internet business owners to only choose <em>quality</em> ingredients to put into our websites. And it also makes it the responsibility of marketing tool providers to create more “wholesome” product offerings. Much of the information we as marketers rely on could be anonymized, and I think that we’ll see a trend towards tools that provide that kind of functionality.</p><p>That being said, I don’t think that anyone’s really <em>thought through</em> the ramifications of the GDPR when it comes to (in essence) taking away these marketing tools that online businesses rely on — while simultaneously forcing websites to let visitors “through the door” regardless of being able to get anything in return (like marketing data or targeted ad revenue).</p><p>I predict that (over time) we’ll see marketing and analytics companies fold, a significant drop in online advertising spend, fewer freemium-based online services, and (ultimately) paywalls over once-free news and content sites.</p><p>As of this writing (and only a handful of days into GDPR), The Washington Post now has an “EU Premium Subscription” for EU readers:</p><h3>Maciej Kuziemski on Twitter</h3><p>WTF @washingtonpost? Compliance with GDPR is now called &quot;Premium EU Subscription?</p><p>As everyone seemed to be pretty caught off guard by the GDPR, I would expect to see more things like this in the coming months.</p><p>So in closing, I’ve come to think that there are some good ideas here, but maybe we’ll need to go through a few iterations of it before we get it right for everyone.</p><p>—</p><p>In the meantime, you can keep tabs on my progress by following me here on Medium @cliffordoravec or on Twitter at <a href="https://twitter.com/cliffordoravec">@cliffordoravec</a>.</p><p>If you haven’t checked out my ongoing masterwork, <em>The Epic Guide to Bootstrapping</em>, you can <a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1">read the Medium series here</a> — or you can check out <a href="https://cliffordoravec.com/">the upcoming full-length book here</a> (which is <em>not</em> a blog to book — it’s an actual, all new, all original, honest-to-goodness, book).</p><p>And of course, if you’re looking for a GDPR consent form solution for your website, you might want to check out <a href="https://consentjs.com/">ConsentJS</a> 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a49ae9970da4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tamboo/from-saas-idea-to-launch-in-a-week-an-epic-guide-post-a49ae9970da4">From SaaS Idea to Launch In a Week (An Epic Guide Post)</a> was originally published in <a href="https://medium.com/tamboo">Tamboo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Call It A Comeback]]></title>
            <link>https://medium.com/@cliffordoravec/dont-call-it-a-comeback-8f8a8a55a1c3?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f8a8a55a1c3</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 12:35:25 GMT</pubDate>
            <atom:updated>2018-01-08T12:35:25.309Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been bootstrapping for years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*luvKbbw4GFH7XwQtRqT3lQ.png" /></figure><p>Hey Kiddos,</p><p>Sorry if I left you hanging after my <a href="https://medium.com/@cliffordoravec/how-2017-completely-kicked-my-saas-c42540fb4ba2">earlier missive</a>, but I needed to get that out in the open and take some time to “get right”.</p><p>Over the past couple of weeks, I’ve done basically <em>nothing </em>(and it was everything I thought it could be).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*zLpm-4cmpd4pClO7zr6FlQ.jpeg" /><figcaption>Fuckin’ A.</figcaption></figure><p>I spent time with my family.</p><p>I cooked some Duck a l’Orange (my favorite — hit me up if you want my recipe).</p><p>I read some <a href="https://www.amazon.com/Mistborn-Final-Empire-Book-No/dp/0765350386">bad-ass fantasy novels</a> (which <em>totally</em> need to be turned into a movie — or an HBO series [wink, wink, nudge, nudge]).</p><p>I played a mean-ass game of Pokemon Go (yes, I am definitely a “passenger”, I’m totally not hitting Poke Stops from my car like someone shooting at deer from their open window…)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*EamrECgFrMVi2XJu7Y9uRw.jpeg" /><figcaption>Here’s some Razz Berries, now stop complaining and get in my Poke Ball, you little shit.</figcaption></figure><p>And best of all, <strong>I gave myself permission to just… stop <em>doing</em>.</strong></p><p>(At least for a couple of weeks.)</p><p>Lately, I’ve started rethinking exactly what it is that I want to do with Tamboo.</p><p>So I apologize in advance — this is going to be a little introspective, a little about “me”, and a little about what I hope to accomplish in the coming year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*elPXj4zcA_Pi6Av7jhUQ7A.gif" /></figure><p><strong>Times Have Changed</strong></p><p>I was fortunate enough to get in front of the whole “<a href="https://gettamboo.com/">session recording and replay</a>” movement before it got real legs.</p><p>Early on, the people I pitched Tamboo to didn’t even <em>know</em> that you could record and watch people using your website — they were pretty blown away by the concept.</p><p>I even thought that I had “invented” something at one point early on — before I realized others were “inventing” the same thing I was at the same time (we bootstrappers can be a bit naive at times).</p><p>What’s happened since then is a whole slew of copy cats have caught the scent of fresh canned tuna and converged on it like a murder of crows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*48AgDT8zUc2YGgkFrW-P7g.jpeg" /></figure><p>This explains why it was (relatively) “easy” to grow Tamboo at the onset — and why it’s gotten progressively more difficult.</p><p>What was once a unique “thang” is now a ubiquitous “thing”.</p><p>More and more companies have entered the fray, and I now have “established competitors” in what was once a “wild west” kind of space just a couple of years ago.</p><p>(As an aside, I think we should all agree that a group of competitors should be referred to as a “murder”— just to make it more apropos.)</p><p>And, unlike some of them, I didn’t have a team of founders and a barge load of initial funding to fuck with as I pleased.</p><p>I wrote and built this by myself — I didn’t hire a team of developers or a team of marketers.</p><p>Every line — every <em>single </em>line — was — and is — me.</p><p>Every ad, every content piece, every answer, every article, every <em>everything</em> — was — and is — me.</p><p><strong>Don’t Compete — Adapt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*rQjqZNI1augF9KD4t2cwWQ.gif" /><figcaption>Competition is for losers.</figcaption></figure><p>So while I might have beaten the onset of the session recording gold rush and carved out a nice little tract of land for myself, there’s been a number of other settlers buying up and carving out even larger tracts of land around me over the past year or so.</p><p>Where I went wrong in all of this was being blinded by a shiny new toy — becoming a “semi-famous startup guy” — and wasting far too much time trying to turn that into some kind of an “advantage”.</p><p>(As an aside, let this serve as a lesson to anyone who thinks that they just need to “get famous” or “build an audience”. If your audience isn’t <em>directly</em> aligned with your offering, it isn’t going to do you <em>one ounce</em> of good. It’s like being a world-renowned bass fisherman and trying to use that to build up your fledgling dentistry practice — it just ain’t gonna happen.)</p><p>In the meantime, the landscape changed underneath me. I didn’t tend to my fields as well as I probably should have, and others with a better focus than mine have come in and made themselves at home.</p><p>Fast forward to today, and we’ve got a fair amount of competition going on in the session recording landscape.</p><p>While I’ve still got my own acquisition channels and my own customer segments that fuel my little patch of land over here, it’s not the overly fertile ground that it used to be.</p><p>This is due in part to the growing industry of session replay.</p><p>The more companies that enter into this space, and the larger those companies get, means that there is more competition for the same customers.</p><p>Because this is a newer industry, there was (and still is) untapped demand. Just stepping in and offering a “supply” to that demand was sufficient to do well enough.</p><p>But that’s not really the case so much now.</p><p>Because everyone’s going after the same set of customers, they’re all trying to “one-up” each other to stand out as “the best” option available. This is what competition does. It pushes companies to “be better” (whatever that means) than others in their industry to win more customers.</p><p>Now, this “competitive improvement” follows an optimization curve and eventually succumbs to The Law of Diminishing Returns:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*81ow9xsVl29tKGirhknlVA.jpeg" /></figure><p>Companies choose a set of features to “compete on” and then try to outdo everyone else by making their own version of those features “better” — or even “the best”.</p><p>Usually, this means teaching these features more and more complex tricks — even if customers don’t necessarily <em>need</em> them.</p><p>More and more effort gets put into “improving” those features — but the returns on those efforts become lower and lower.</p><p>But these “features” become the buying criteria that a lot of people use when choosing between one offering or another. Even if we don’t <em>need</em> a particular ability or feature, it can be hard to know that it <em>could</em> be something available to us and then choosing to do without it.</p><p>So even if you’ll never <em>use</em> a feature (but you think you <em>might</em>), you very often still use the <em>knowledge</em> of that feature as a buying criteria. If one offering has that feature, and another doesn’t, well then — the one that does have it must be “better” than the one that doesn’t, right?</p><p>Because of this, everyone feels that they need to “improve” their features and offerings to the point of ridiculousness — in order to “be the better choice”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n0mhEv7HhFfouYT0u7BWMA.jpeg" /><figcaption>It’s so ridiculous it *must* be better, right?!</figcaption></figure><p>This whole “compete each other into the ground” phenomenon happens like clockwork in every industry.</p><p>Everyone starts off “improving” the obvious features. In my world, that would be session recordings themselves.</p><p>Then, once those have been more than sufficiently “improved”, they start branching out to ancillary features to try to use those as “differentiators” from their competitors. In my world, things like live session replay, website chat, heatmaps, funnels, form analytics, surveys, and even issue tracker integration seem to be the ancillary features being targeted the most at the moment.</p><p>These ancillary features are also used to better help a company “position” themselves for a particular customer segment.</p><p>If you wanted to target people who use session replay tools primarily for usability testing, you would most likely focus on things like surveys, advanced search features, UX-specific analytics, and even collaboration tools for teams working on improving UX.</p><p>If you wanted to target people who use session replay tools for conversion rate optimization, you would most likely focus on things like heatmaps, funnels, and form analytics.</p><p>Want to target people using session replay for support? Focus on website chat, live session replay, and issue tracker integration.</p><p>This segmentation approach works for a while.</p><p>By “tailoring” your offering, you can target a segment of a market and carve out a nice little piece of the pie that you can “own”.</p><p>But this approach isn’t static, and it doesn’t come without a cost.</p><p>While segmentation can reduce the strain that competition in the larger market puts on an organization — and can even unlock latent demand from market segments that need a product more “tailored” for their specific use cases — it also means that you’re <em>narrowing</em> the number of possible customers that you can now sell to.</p><p>It’s less competition, but also less of a market.</p><p>But it’s “easier” to profit from.</p><p>Until, of course, <em>new</em> competitors come into the mix.</p><p>And then you start the whole process over again — competing on specific features and offerings, maybe segmenting <em>within</em> your segment, and so on and so forth.</p><p>Until there’s only one “feature” left to compete on — <strong>price.</strong></p><p>And thus starts “the race to the bottom”.</p><p>With no other <em>meaningful</em> features, offerings, or segments to optimize for, price is all that’s left in most cases.</p><p>Because when everyone converges on the same set of features, targeting the same customers in the same markets — that’s when everyone in an industry inadvertently turns their once novel offerings into mere <em>commodities.</em></p><p>Now, we’re not there yet in the session replay industry.</p><p>We’re somewhere a little higher in the process.</p><p>It feels like we’ve already gone through and done the “mainstream optimization” thing already, and that we’re currently “branching out” to align offerings to more specific customer segments.</p><p>At least, that’s what my analysis tells me:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UI7e3-ituKMcae6PXcIm0w.png" /></figure><p>You’ll see certain competitors start to “cluster” around certain feature sets.</p><p>Those clusters become market segments they’re (intentionally or not) targeting through more “tailored” offerings for that segment’s use cases.</p><p>So what I’m seeing is a trend towards segmentation in the session replay industry.</p><p>That segmentation will prove profitable — for a time.</p><p>And then the price wars will start (if they haven’t already — there’s a <em>ton</em> of free tiers creeping up like I mentioned in my earlier missive).</p><p>Right now, session replay companies are still able to command a higher price point — typically in the $100/month range for their core user base (as an aside, <a href="https://gettamboo.com/">Tamboo</a> costs much less than that — but that’s a discussion for another article).</p><p>Eventually, once the segmentation battles dry up (and those segments become “fully served” by the available supply), price sensitivity will become much more important.</p><p>And guess what?</p><p>I’m not going anywhere near that game.</p><p><strong>You Do You — And I’ll Do Me</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*IQI0CnhFk0tBnaLfjeuhkA.jpeg" /></figure><p>When you start to see companies aggressively competing on the same things, that’s usually a good sign that you need to let them waste their time and money duking it out with each other and go find something else to do instead. Especially if they have deeper pockets and more people than you do.</p><p>The only way to win such a war is to stop competing on the same things everyone else is competing on.</p><p>You let them play their games. You let them get caught up in their self-inflicted feature optimization death spiral.</p><p>And then you go do something different.</p><p>And that’s exactly what I plan to do with Tamboo this year.</p><p>Sure, I could sit around a duke it out with everyone else.</p><p>I could probably keep prodding along, picking up customers here and there — maybe even segmenting my offering a tad to pick up some more — but I know where this is going.</p><p>It’s gotten harder, and it’s going to get even harder still (not to mention more expensive).</p><p>In order to “keep up” with the industry and where it’s going, I’m going to have to put more and more effort into things that I don’t feel add real value — at least if I want to stay in the game that everyone else is playing.</p><p>So rather than do that, I’m going to realign my offering based on the competitive landscape (which wasn’t <em>really</em> there when I started this thing — at least not like it is today).</p><p>If this form and size of competition existed in the session replay space when I started Tamboo, I wouldn’t have gone about it the way that I have.</p><p>And so rather than keep plodding along, pretending that nothing’s changed, I’m going to take a look at this from fresh eyes and find the “hidden path” that no one’s looking at and shift gears so that I can “get out of the way” before the <em>real</em> competition wars start in this space — and enjoy my little corner of the internet instead.</p><p>I want to keep Tamboo bootstrapped and not have to go the route of hiring, growing, or maybe even taking on funding just to stay in this ever-evolving game.</p><p>Plus, I don’t feel like working my ass off even more just for the sake of “competing”.</p><p>(Feel free to call it a “lifestyle business” if you want — I just don’t want to get into this stupid “growth game” — that’s not why I’m doing this.)</p><p>When the world changes, we need to change with it.</p><p>While they’re all busy working around the clock and weekends to make improvements to features that don’t need to be improved, while they’re working hard to become “the best” session replay tool for a particular market segment, while they’re spending more and more of their marketing dollars to outdo their competition, I’m going to just go “over here” and do what I did in the first place — find people who need something but can’t find the right solution for their needs.</p><p>While everyone else is running around trying to “win” customers from an ever-shrinking market pool, I’m just going to find another pond to fish in. One that they wouldn’t necessarily find “attractive”. One that doesn’t “fit” their desired business model or feature set. One that they can’t “expand” into — at least not without cannibalizing their existing business.</p><p>And then I’m going to go back to fishing in my happy little pond— like I should have been doing all of this time — instead of chasing some elusive “startup fame” growth hack.</p><p><strong>But What About <em>The Epic Guide</em> And Everything Else?!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*FvWfnDpMAgR7pJlEidOLQA.png" /><figcaption>Worlds are colliding!</figcaption></figure><p>Oh, don’t worry — I’m not throwing the towel in on anything.</p><p>I’m still going to bootstrap.</p><p>I’m still going to write.</p><p>I’m still going to Tweet.</p><p>And I’m still going to (probably) do a podcast soon.</p><p>I’m just going to do what I should have done in the first place — and keep them separate from each other.</p><p>It would be wonderful and beautiful if I could some how “synergize” these two parts of my life, but I just can’t see that working right now, so I’m just not going to try anymore (let me know if you see something I don’t).</p><p>I enjoy bootstrapping.</p><p>And I enjoy writing and hanging out with fellow startup peeps.</p><p>So I’m just going to do that — and stop expecting something “magical” to come out of having two semi-related interests.</p><p>I’m going to give each its own proportionately due time and energy, and I’m going to give myself permission to do more of me and what I think I need to focus on.</p><p>Of course, I probably should have done this from the start.</p><p>But I’ve never done this whole “audience” thing before, so I didn’t know any better.</p><p>But now that I have, I do.</p><p>So it’s time to do just that.</p><p>Thanks for joining me on this journey — now it’s time to get back at it and to go find me a new pond.</p><p>I’ll write along the way 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f8a8a55a1c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 38 Books That I Devoured And Destroyed This Year]]></title>
            <link>https://medium.com/@cliffordoravec/the-38-books-that-i-devoured-and-destroyed-this-year-6f5a6c7bbc87?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f5a6c7bbc87</guid>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[fiction]]></category>
            <category><![CDATA[literature]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Thu, 28 Dec 2017 03:51:32 GMT</pubDate>
            <atom:updated>2017-12-28T03:51:32.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJoB6l4WQNRG6CZnKy51rA.png" /></figure><p>Clocking in at 19,627 pages, these are the books that kept me from getting any real sleep this past year — and kept me sane while <a href="https://medium.com/@cliffordoravec/how-2017-completely-kicked-my-saas-c42540fb4ba2">getting my SaaS thoroughly kicked</a>.</p><p>If you’re looking for the “top business books” I read this past year that helped me grow my SaaS-based businesses, you’ve come to the wrong place.</p><p>Sure, I read some business books. But — like most of the business books I’ve read — I wound up questioning the cost of the book against the actual value I walked away with. (And that’s one of the reasons that I’m writing <a href="https://cliffordoravec.com/the-epic-guide">this monster at the moment</a>.)</p><p>Instead, these are the <em>non-business books</em> that I read this past year — the ones that I attribute to keeping and maintaining my sanity while I slogged and tripped through my most audacious year ever as a bootstrapper.</p><p>Every night before I went to bed, these are the companions that I took with me to sleep — the companions that spoke to me, taught me, and quieted my overactive brain so that I could actually get some REMs before waking up and crushing it again.</p><p>So here they are, complete with my “Cliff’s Notes” 😜</p><p>Enjoy.</p><p><strong>The Prisoner of Zenda | </strong>Anthony Hope</p><p><a href="https://www.amazon.com/Prisoner-Zenda-Oxford-Worlds-Classics/dp/0199555281">The Prisoner of Zenda (Oxford World&#39;s Classics)</a></p><p><em>Cliff’s Notes: </em>A wonderful Victorian-era action and adventure piece. Think “Trading Places” with a Victorian-era English gentleman infiltrating a powerful Eastern European monarchy. It’s in the spirit of Haggard, but (dare I say?) much more satisfying.</p><p>[In case you didn’t know, I have a “thing” for Victorian-era literature. Yes, that makes me a tad bit eccentric I suppose, but did you <em>really</em> expect anything less from me? 🤪]</p><p><strong>Discourses, Fragments, Handbook | </strong>Epictetus</p><p><a href="https://www.amazon.com/Discourses-Fragments-Handbook-Oxford-Classics/dp/0199595186">Discourses, Fragments, Handbook (Oxford Worlds Classics)</a></p><p><em>Cliff’s Notes: </em>If you’re a fan of Stoic writings (such as Marcus Aurelius’s <em>Meditations</em>), you really owe it yourself to go “back to the classics”. Epictetus was a Stoic who lived right around the time of Musonius Rufus yet well before Marcus Aurelius. His writings represent the core principles of Stoicism. Read this if you want to improve your life.</p><p><strong>The Art of Happiness | </strong>Epicurus</p><p><a href="https://www.amazon.com/Art-Happiness-Penguin-Classics/dp/0143107216">The Art of Happiness (Penguin Classics)</a></p><p><em>Cliff’s Notes: </em>Although I love me some Stoic writings and philosophy, I actually consider myself a Hedonist. “Hedonism” tends to get a bad rep, often being synonymous with “excess”, while <em>actual </em>hedonism is more about maximizing pleasure and happiness, while guarding against it turning into excess (which, in turn, actually <em>minimizes</em> pleasure and happiness). Going “back to the classics” on this subject is something that I do annually.</p><p><strong>Walkaway | </strong>Cory Doctorow</p><p><a href="https://www.amazon.com/Walkaway-Novel-Cory-Doctorow/dp/0765392763">Walkaway: A Novel</a></p><p><em>Cliff’s Notes: </em>This is the one book on this list that I struggled with. I tend to heavily vet whatever I read to make sure I don’t waste my time with dross or drivel, but this one found a way to slip through that filter. I didn’t particularly enjoy this book, in all honesty. That might be in part because I’m a staunch capitalist and this thing seemed to have a (more than healthy) smack of Marxism throughout, or maybe because it reminded me of a poorly executed imitation of a Neal Stephenson work (which in and of itself says a lot, as you’ll see). Either way, if you’re into Communist dystopian futures complete with weird-ass singularities that hate on capitalism, this book is for you (it wasn’t for me — I honestly really wanted to “walkaway” from it).</p><p><strong>State of Fear | </strong>Michael Crichton</p><p><a href="https://www.amazon.com/State-Fear-Michael-Crichton/dp/0061782661">State of Fear</a></p><p><em>Cliff’s Notes: </em>I love me some Michael Crichton. To me, he’s the Jules Verne of our time (I told you I had a thing for Victorian literature). That being said, this book was an interesting read from an author I’ve always had mass respect for. In it, he takes a contrarian view towards global warming, taking the side of global warming “detractors”. The scientific community has vociferiously condemned the research and method he extols in this work, but that shouldn’t stop you from reading it. It’s a great storyline, full of suspense and action, and it gives some alternative views and angles to consider in the pursuit of trying to fully understand the climate change phenomenon impacting all of us.</p><p><strong>Under the Black Flag | </strong>David Cordingly</p><p><a href="https://www.amazon.com/Under-Black-Flag-Romance-Reality/dp/081297722X">Under the Black Flag: The Romance and the Reality of Life Among the Pirates</a></p><p><em>Cliff’s Notes: </em>I loved this book. In part, because my original career choice was to become an historian (yes, I’m weird), but also in part because it’s just <em>fascinating</em>. Well researched and detailed, this book will help you get an authentic appreciation for what the piracy age in the Caribbean was <em>really</em> like, expelling common myths and misconceptions (sorry, Jack Sparrow!)</p><p><strong>She | </strong>H. Rider Haggard</p><p><a href="https://www.amazon.com/Oxford-Worlds-Classics-Rider-Haggard/dp/0199536422">She (Oxford World&#39;s Classics)</a></p><p><em>Cliff’s Notes: </em>Simply put: Haggard is the shit<em> </em>when it comes to Victorian-era action and adventure, and this book doesn’t disappoint. In it, Haggard blends adventure and period-appropriate terror in one masterful work. [Caveat emptor: Contains some sensitive subject matter from the period it was written in.]</p><p><strong>The Beautiful and Damned | </strong>F. Scott Fitzgerald</p><p><a href="https://www.amazon.com/Beautiful-Damned-AmazonClassics-Scott-Fitzgerald-ebook/dp/B0756ZQSYT">The Beautiful and Damned (AmazonClassics Edition)</a></p><p><em>Cliff’s Notes: </em>Fitzgerald is a unique writer. While most of us might be familiar with his well-known masterpiece, <em>The Great Gatsby </em>(despite the <em>awful </em>movie bearing its name), there is more depth to the writer than just that. In <em>The Beautiful and Damned</em>, Fitzgerald demonstrates his most masterful skill — that of smashing the jaw of a lesser writer in as few words as he could muster the strength to write. Fitzgerald would have <em>owned</em> Twitter’s 140 character limit with poise and ease — he frequently turns benign-looking statements into existential-shattering prose, without looking like he’s breaking a sweat. Capturing the exuberant yet despondent spirit of the gilded age better than a Polaroid could have, Fitzgerald delivers in this masterwork, which will send you into a spiral of existential examination every other sentence or so.</p><p><strong>The Call of Cthulhu and Other Weird Stories | </strong>H. P. Lovecraft</p><p><a href="https://www.amazon.com/Call-Cthulhu-Other-Weird-Stories/dp/0143129457">The Call of Cthulhu and Other Weird Stories: (Penguin Classics Deluxe Edition)</a></p><p><em>Cliff’s Notes: </em>Lovecraft was a disturbing bloke if ever there was one. Despondent, disconnected, and visionary in a way the world had not seen before, he broke a mold with his writings — when you read them, you can’t help but feel that you’ve been lifted from this simplistically existential plane into something new and <em>strange</em>. The visions he weaves are both simultaneously beautiful and disturbing, leaving you breathless as you finish and contemplate each individual “story” (or hallucination, as your preference may determine).</p><p><strong>The Andromeda Strain | </strong>Michael Crichton</p><p><a href="https://www.amazon.com/Andromeda-Strain-Michael-Crichton/dp/1101974494">The Andromeda Strain</a></p><p><em>Cliff’s Notes: </em>It’s hard to believe that Crichton was only in his early twenties when he penned <em>The Andromeda Strain</em> — and in the <em>60s</em> at that. About a biological alien invasion of sorts, Crichton deftly captures the dawn of the modern scientific age in a novel that simultaneously captures the spirit of his age — complete with red-walled military-industrialist silos equipped with computers that are programmed to kill you and everyone else should anything go wrong.</p><p><strong>Fevre Dream | </strong>George R. R. Martin</p><p><a href="https://www.amazon.com/Fevre-Dream-George-R-Martin/dp/055357793X">https://www.amazon.com/Fevre-Dream-George-R-Martin/dp/055357793X</a></p><p><em>Cliff’s Notes: </em>Another early-year throw back to an exceptional author, <em>Fevre Dream</em> was written by George R. R. Martin (of <em>Game of Thrones </em>fame) back in 1982. It’s a vampire novel (of sorts) that addresses (and tackles) vampiresque topics not fully explored until <em>True Blood</em> hit everyone’s screens decades later. Like his other works, <em>Fevre Dream</em> features rich and in-depth character developments that make you sad when the book is over. Set in the era of steam boats in mid-1800s New Orleans, <em>Fevre Dream</em> is a vampire novel unlike any other you have read (fuck Lestat). [Caveat emptor: Contains some sensitive subject matter from being set in the south in the mid-1800s.]</p><p><strong>The Dinosaur Lords | </strong>Victor Milan</p><p><a href="https://www.amazon.com/Dinosaur-Lords-Novel-Victor-Mil%C3%A1n/dp/0765382113">The Dinosaur Lords: A Novel</a></p><p><em>Cliff’s Notes: </em>I didn’t know what to expect with this book, to be completely honest with you. I was in a Barnes and Noble with my girlfriend looking to see what else George R. R. Martin had available for consumption when she came across this thing. Looking it over, I had decided that it would either be fucking awesome or fucking awful. Sadly enough, it fell somewhere in the middle. <em>Dinosaur Lords</em> held promise — a <em>Game of Thrones</em> with dinosaurs — but it failed to fully deliver on either premise. The character development was lacking (despite throwbacks to <em>Game of Thrones</em>, including a character strikingly similar to Jaime), and the dinosaurs were… <em>disappointing.</em> To top it all off, he ended the first book on an absolute cliff hanger that just plain pissed me off. Sad to say, I won’t be joining him for the second book.</p><p><strong>Dune | </strong>Frank Herbert</p><p><a href="https://www.amazon.com/Dune-Chronicles-Book-1/dp/0441013597">Dune</a></p><p><em>Cliff’s Notes: </em>Dune is <em>fucking</em> amazing. I have rarely found a book that left me as impacted and as satisfied as <em>Dune</em>. Take everything you love about <em>Lord of the Rings</em> (up next), add some Star Wars and other awesome shit while removing all of the <em>cruft</em>, and you get <em>Dune.</em> Dune is <em>amazing</em>, not just because of when it was written (1960s) and the topics that it explored at the time (ecology, terraforming, etc.), but because of how <em>captivating</em> the storyline is. <em>Dune</em> shaped the future — without it, we most likely would not have <em>Star Wars</em>, <em>Tremors</em>, or pretty much any other modern science fiction book or movie. It was <em>that</em> influential (in fact, <em>Star Wars</em> is basically a total rip off of Herbert’s genius). If you haven’t read <em>Dune</em>, you need to stop whatever you’re doing and grab a copy.</p><p><strong>The Lord of the Rings | </strong>J. R. R. Tolkien</p><p><a href="https://www.amazon.com/Lord-Rings-50th-Anniversary-Vol/dp/0618645616">https://www.amazon.com/Lord-Rings-50th-Anniversary-Vol/dp/0618645616</a></p><p><em>Cliff’s Notes: </em>Ugh. <em>The Lord of the Rings</em>. I often ask myself <em>why</em> I decided to undertake this undertaking. It’s wonderfully fantastical, sure. But it’s a <em>fucking slog</em> at the same time. Spoiler Alert: There is a lot of <em>walking. </em>Lots and lots of <em>walking. </em>There were times when I was like “when is thing going to be over?!”, especially when I realized that it was only one-half into the third “book” (it’s considered “one book” with three volumes) that The Ring got dropped into the fucking volanco, leaving <em>another</em> three hundred or so pages of <em>who-the-fuck-knows-what</em> left to go. If you’re hard-core, go for it. If not, watch the movies and save yourself some time.</p><p><strong>The Island of Dr. Moreau | </strong>H. G. Wells</p><p><a href="https://www.amazon.com/Island-Doctor-Moreau-H-Wells/dp/1511731559">The Island of Doctor Moreau</a></p><p><em>Cliff’s Notes: </em>Much better than the Val Kilmer movie of the same name, <em>The Island of Doctor Moreau </em>explores the implications of the pseudo-science vivisection, which is basically a fancy way of describing the random surgical mutilation of animals. Another (late) Victorian era science fiction novel, <em>The Island of Doctor Moreau</em> is a short yet poignant exploration of the human soul in a time when the morality of humanity was being explored and “vivisected” by the authors of the age.</p><p><strong>Cryptonomicon | </strong>Neal Stephenson</p><p><a href="https://www.amazon.com/Cryptonomicon-Neal-Stephenson/dp/0380788624">https://www.amazon.com/Cryptonomicon-Neal-Stephenson/dp/0380788624</a></p><p><em>Cliff’s Notes: </em>Like almost all Neal Stephenson novels, <em>Cryptonomicon</em> had such moments of promise that you couldn’t help but feel completely disappointed by the time it was (finally) over. Decades before Bitcoin, <em>Cryptonomicon </em>explored the concepts and implications of a digital currency — and the unsavory characters who would benefit and profit from it — in a novel that spans from the time of the second World War. Like all of Neal Stephenson’s works, it takes a few hundred pages before you start to “get into it” — only to have whatever feelings you had about it to be destroyed by the last ten pages of the book. (Sorry, not sorry.)</p><p><strong>In a Dark, Dark Wood | </strong>Ruth Ware</p><p><a href="https://www.amazon.com/Dark-Wood-Ruth-Ware/dp/1501112333">https://www.amazon.com/Dark-Wood-Ruth-Ware/dp/1501112333</a></p><p><em>Cliff’s Notes: </em>I saw this title at Barnes and Noble and grabbed it on an impulse. I thought it would be much “scarier” than it actually was, but it wasn’t 100% bad. At the same time, it wasn’t really 100% good either. It was an enjoyable enough diversion, but smacked of a PG version of R. L. Stine’s <em>Fear Street </em>meets some kind of a luxury cabin in the woods mashup.</p><p><strong>Vurt | </strong>Jeff Noon</p><p><a href="https://www.amazon.com/Vurt-Jeff-Noon/dp/0312141440">https://www.amazon.com/Vurt-Jeff-Noon/dp/0312141440</a></p><p><em>Cliff’s Notes: </em>Whatever drugs the cool “cypher” kids were doing in the early 90s were not enough to express whatever Jeff Noon was looking to capture in his novel <em>Vurt</em>, a virtual reality drug fueled dystopian cyberpunk world complete with half-human/half-dog hybrids (who shit all over the floor, just like real dogs). If you want a trip down memory lane to (re)explore early 90s cypher/cyber culture, this might bring back a rush of memories. If you’re not “hip” to that era, maybe you’ll learn a thing or two. If you’re neither nor, you might want to give it a whirl just to expand your mind. Just know it’s a bit of a mindfuck.</p><p><strong>The Russian Debutante’s Handbook | </strong>Gary Shteyngart</p><p><a href="https://www.amazon.com/Debutantes-Handbook-Shteyngart-Riverhead-Paperback/dp/B00DWWC5NI">Russian Debutantes Handbook by Shteyngart, Gary [Riverhead Trade,2003] (Paperback)</a></p><p><em>Cliff’s Notes: </em>Wow, what a great debut novel. Take a fictitiously hip early 90s Eastern European city that silently screams “Prague”, plop in a wimpy yet intelligent expatriate con-artist, and you get this odd menagerie of a story, complete with early 90s hipsters, hucksters, and hustlers. Throw in a set of strangely placed references to Ohio, and you’ve got this entertaining diversion, which I found delightfully humorous and engaging.</p><p><strong>Generation X: Tales for an Accelerated Culture | </strong>Douglas Coupland</p><p><a href="https://www.amazon.com/Generation-X-Tales-Accelerated-Culture/dp/031205436X">https://www.amazon.com/Generation-X-Tales-Accelerated-Culture/dp/031205436X</a></p><p><em>Cliff’s Notes: </em>Coupland is the bomb — simply put, he is the Dostoyevsky of Generation X. He effortlessly captures the humor, wit, and cynicism of my generation, while demonstrating the vulnerability and restrained hope and promise that we all felt in what were some dark and heavy times — full of philosophy, existentialism, and the dying light of individualism.</p><p><strong>Quicksilver | </strong>Neal Stephenson</p><p><a href="https://www.amazon.com/Quicksilver-Baroque-Cycle-Vol-1/dp/0060593083">Quicksilver (The Baroque Cycle No. 1)</a></p><p><em>Cliff’s Notes: </em>Neal, oh Neal. You write these these sprawling epics that make me feel ashamed of writing anything less than 1,000 pages, but every time, I can’t help be feel disappointed with how you choose to end these things. <em>Quicksilver</em> is no exception to the “Stephenson Rule” as I call it. The premise of the book shows such promise, chronicling a young Isaac Newton throughout his early and formative years (complete with appearances by a young Leibniz), but it fails to deliver much more to the reader other than a thousand pages of dead tree corpses marked by the smear of (often) indecipherable ink.</p><p><strong>Pattern Recognition (Blue Ant) | </strong>William Gibson</p><p><a href="https://www.amazon.com/Pattern-Recognition-Blue-William-Gibson/dp/0425198685">Pattern Recognition (Blue Ant)</a></p><p><em>Cliff’s Notes: </em>Being a huge fan of <em>Neuromancer, </em>I think I was expecting more from this book than I should have. It’s still expertly written in Gibson’s signature style, but its substance and material fell below the water mark of what I’ve come to expect from him as an author. It’s still an enjoyable diversion, but don’t expect to have your ice broken.</p><p><strong>The Lost World: A Novel (Jurassic Park) | </strong>Michael Crichton</p><p><a href="https://www.amazon.com/Lost-World-Novel-Jurassic-Park/dp/0345538994">https://www.amazon.com/Lost-World-Novel-Jurassic-Park/dp/0345538994</a></p><p><em>Cliff’s Notes: </em>It made me weep to read this book, knowing that there was an abomination of a movie that bore its name that existed in the real world. If you loved <em>Jurassic Park </em>but hated “the second of its name” as a movie, don’t hesitate to read this book. In fact, <em>Jurassic World</em> borrowed elements from this book, including camouflage dinosaurs (see, Crichton had that shit thought out <em>years</em> ago).</p><p><strong>The Lost City of Z: A Tale of Deadly Obsession in the Amazon | </strong>David Grann</p><p><a href="https://www.amazon.com/Lost-City-Deadly-Obsession-Amazon/dp/1400078458">The Lost City of Z: A Tale of Deadly Obsession in the Amazon</a></p><p><em>Cliff’s Notes</em>: If ever there was a book that would make you question your own sanity as a startup founder, this would be it (even though it has nothing to do with computers or software). <em>The Lost City of Z</em> follows British explorer Percy Fawcett in his unrelenting and maddening quest for the Lost City of “Zed”, a city which he <em>believed</em> was the Amazonian mashup of El Dorado meets Ancient Egypt — despite any physical proof that such a thing could even exist in the Amazon. If you’ve ever “believed” something without proof, this book might show you just how right — yet deadly wrong — you are at the same time.</p><p><strong>The Arabian Nights (Vol 1–3)| </strong>Anonymous</p><p><a href="https://www.amazon.com/Arabian-Nights-Tales-Penguin-Classics/dp/0140449388">The Arabian Nights: Tales of 1,001 Nights: Volume 1 (Penguin Classics)</a></p><p><em>Cliff’s Notes: </em>I decided to read <em>The Arabian Nights</em> after having read numerous references to it in <em>The Count of Monte Cristo</em> (which I read in 2016, and which I would *highly* recommend). Apparently, it was quite in fashion at the time, having recently been translated into French, and all the cultured elite were abuzz with its stories. Although insightful and “magical”, the stories are surprisingly rough in nature — not something I was quite expecting. But once you move past that, it’s actually quite fascinating. Although written in a different tone and style than you might be accustomed to (it’s a translation of stories hundreds and hundreds of years old), the stories are actually quite clever, and give you a different perspective.</p><p><strong>Snow Crash | </strong>Neal Stephenson</p><p><a href="https://www.amazon.com/Snow-Crash-Neal-Stephenson/dp/0553380958">https://www.amazon.com/Snow-Crash-Neal-Stephenson/dp/0553380958</a></p><p><em>Cliff’s Notes: </em>I actually liked <em>Snow Crash </em>as a novel, despite the 100 or so pages dedicated purely to Sumarian theology and philosophy. Another early 90s exploration of “cyberpunk” culture and values, it delivered masterfully on that front — while simultaneously diverging down a weird street of ancient and modern religion and philosophy. If you “did computers” in the early 90s and you liked <em>Ready Player One </em>(which I also *highly highly* recommend), then this book might be for you. It’s uncannily weird — in a good way (despite still finding a way to adhere to the “Stephenson Rule”).</p><p><strong>King Solomon’s Mines | </strong>H. Rider Haggard</p><p><a href="https://www.amazon.com/King-Solomons-Mines-Penguin-Classics/dp/0141439521">https://www.amazon.com/King-Solomons-Mines-Penguin-Classics/dp/0141439521</a></p><p><em>Cliff’s Notes: </em>Like I said before, Haggard is the Victorian Shit™. His novel, <em>King Solomon’s Mines, </em>actually originated as a bet with his brother about whether or not he could write a better adventure story than <em>Treasure Island</em> (coming up soon). In my esteemed opinion, he did just that — and then some. Introducing Allan Quartermain (forget <em>The League of Extraordinary Gentlemen</em>) — while setting the stage for Crichton’s <em>Congo — King Solomon’s Mines</em> is an epic Victorian treasure hunt. [Caveat emptor: Contains some sensitive subject matter from the period it was written in.]</p><p><strong>Treasure Island | </strong>Robert Louis Stevenson</p><p><a href="https://www.amazon.com/Treasure-Island-Robert-Louis-Stevenson/dp/1505297400">https://www.amazon.com/Treasure-Island-Robert-Louis-Stevenson/dp/1505297400</a></p><p><em>Cliff’s Notes: </em>Stevenson’s <em>Treasure Island</em> is an undisputedly classic adventure story that introduced much of the world to “pirates”, including buried treasure, “X” marks the spot, and their (sadly mostly fictional) language and colloquialisms (savvy, me hearties?). Despite these “pirate stereotypes”, <em>Treasure Island</em> is an enjoyably good read, and one that won’t leave you looking at Long John Silver’s the same way when you’re done.</p><p><strong>Seveneves | </strong>Neal Stephenson</p><p><a href="https://www.amazon.com/Seveneves-Neal-Stephenson/dp/0062334514">https://www.amazon.com/Seveneves-Neal-Stephenson/dp/0062334514</a></p><p><em>Cliff’s Notes: </em>Neal knocked this one out of the park, in all honesty. Although it still follows the “Stephenson Rule”, it does so in a less sophomoric manner, and showcases a much richer storyline than his other works. In <em>Seveneves</em>, Earth is about to be destroyed by an asteroid. But rather than try to destroy the asteroid, the race is on to get humans and other species in to space — so that a fragment of the population can “wait out” the impending destruction of Earth — and have an opportunity recolonize it thousands of years later. In the process, the characters have to solve and overcome a slew of obstacles and problems. Think of it like <em>Armageddon</em> meets <em>The Martian</em> meets <em>Star Trek</em>.</p><p><strong>Demian: The Story of Emil Sinclair’s Youth | </strong>Hermann Hesse</p><p><a href="https://www.amazon.com/Demian-Story-Sinclair%C2%92s-Penguin-Classics/dp/0143106783">https://www.amazon.com/Demian-Story-Sinclair%C2%92s-Penguin-Classics/dp/0143106783</a></p><p><em>Cliff’s Notes: </em>Hesse is one of those rare voices in literature, who, when he opens his mouth, forever changes the world. In <em>Demian</em>, Hesse explores the nuances of good, evil, morality, and the freedom of choice as they play out in the life of a coming-of-age youth. Both darkly disturbing and beautiful at times, Hesse walks the fine line of what it means to be human with skillful ease.</p><p><strong>The Picture of Dorian Gray | </strong>Oscar Wilde</p><p><a href="https://www.amazon.com/Picture-Dorian-Dover-Thrift-Editions/dp/0486278077">The Picture of Dorian Gray (Dover Thrift Editions)</a></p><p><em>Cliff’s Notes: </em>A dark descent into madness juxtaposed against the backdrop of eternal beauty, <em>The Picture of Dorian Gray</em> was considered an “evil book” by many people in its day. In it, Oscar Wilde brazenly (yet deftly) pushed the boundaries of what society at his time was willing to embrace (or even tolerate for that matter). Ever the aesthetic antagonist, Wilde’s wit and humor shine, all the while making profound statements about art, beauty, and morality. More than just a gothic horror novel, it is simultaneously a statement about society and the people who occupy it.</p><p><strong>Siddhartha | </strong>Hermann Hesse</p><p><a href="https://www.amazon.com/Siddhartha-Penguin-Classics-Deluxe-Hermann/dp/0142437182">https://www.amazon.com/Siddhartha-Penguin-Classics-Deluxe-Hermann/dp/0142437182</a></p><p><em>Cliff’s Notes: </em>In <em>Siddhartha,</em> Hesse explores the multi-faceted nature of humanity in a way that only he can do, following the rise and fall (and rise again) of a man seeking spiritual enlightenment. Hesse’s rich writing style brings the story of Siddhartha to life, written as if it were a thousand year old myth or legend being retold to the reader. Weaving powerful imagery with a direct writing style, <em>Siddhartha</em> is a book that has something to teach to everyone who is willing to read it.</p><p><strong>A Knight of the Seven Kingdoms | </strong>George R. R. Martin</p><p><a href="https://www.amazon.com/Knight-Seven-Kingdoms-Song-Fire/dp/0345533488">A Knight of the Seven Kingdoms (A Song of Ice and Fire)</a></p><p><em>Cliff’s Notes: A Knight of the Seven Kingdoms</em> is a prequel of sorts to <em>A Game of Thrones. </em>It’s a collection of three novellas that occur roughly a hundred years before the events that take place in <em>A Game of Thrones</em>, chronicling the early adventures of “Dunc and Egg”. The stories are astoundingly well written (as is pretty much anything George R. R. Martin does), but what’s unique about these stories when compared to those in the series of <em>A Song of Ice and Fire (</em>starting with <em>A Game of Thrones) </em>is that the tone of the storytelling (and the tone of the stories themselves) is much lighter and more in the voice of a set of chivalrous stories being retold from long ago. <em>A Knight of the Seven Kingdoms</em> welcomingly adds to the lore of <em>A Song of Ice and Fire</em> while simultaneously filling in some backstories in an interesting and entertaining way.</p><p><strong>A Game of Thrones, A Clash of Kings, A Storm of Swords, A Feast for Crows, and A Dance with Dragons (A Song of Ice and Fire) | </strong>George R. R. Martin</p><p><a href="https://www.amazon.com/Thrones-Clash-Kings-Swords-Dragons/dp/0345535529">A Game of Thrones / A Clash of Kings / A Storm of Swords / A Feast of Crows / A Dance with Dragons</a></p><p><em>Cliff’s Notes: </em>Do yourself a favor and read the books if you love the show. Or if you’ve never seen the show — just read the books. George R. R. Martin’s magnum opus is probably the most addictive series of books I’ve ever read (and I read <em>a lot</em>, if you couldn’t tell). I’m not going to go on and on about it, I’m just going to say “read it”. And do yourself a favor — don’t judge the series by the first book. The first book, although it’s good, is nowhere near as good as the the other books as the series progresses. If you’ve seen the show, you might think you’re just reading the show with the first two books, and in a way, you are. But if you keep going, you’ll be richly rewarded.</p><p><strong>Honorable Mention</strong></p><p><strong>Mistborn | </strong>Brandon Sanderson</p><p><a href="https://www.amazon.com/Mistborn-Final-Empire-Brandon-Sanderson/dp/0765377136">Mistborn: The Final Empire</a></p><p><em>Cliff’s Notes: </em>I’m including <em>Mistborn</em> in here as an honorable mention, since I haven’t finished reading it yet (and so can’t <em>technically</em> include it in my end of year tally). <em>Mistborn</em> was recommended to me by someone working the counter at a Barnes and Noble, and I wish I knew her name so that I could thank her personally. So far, I am <em>absolutely</em> in love with this book and am really looking forward to the rest of the series (there’s five books in it so far). <em>Mistborn</em> has it all — a fluid, fast-paced storyline set in a creatively dystopian alternative world, chalk full of action, adventure, and intrigue. “Mistborns” possess the ability to turn the use of ten different metals into ten different powers, from influencing the emotions of others to pushing and pulling metal objects. What’s most impressive is the application of physics as it pertains to these different powers. For example, a Mistborn can push a coin, using it like a weapon — or they can “anchor” that coin on the ground and push off from it (while simultaneously pushing and pulling on other sources of metal) to basically simulate flight. Out of all of the books I’ve read this year, I would put this one as one of my top favorites.</p><p><strong>Have a Recommendation?</strong></p><p>I’m always looking for great books to read — if you’ve got a favorite, leave it in the comments below for me and others to discover!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f5a6c7bbc87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How 2017 Completely Kicked My SaaS]]></title>
            <link>https://medium.com/@cliffordoravec/how-2017-completely-kicked-my-saas-c42540fb4ba2?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/c42540fb4ba2</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[year-in-review]]></category>
            <category><![CDATA[entrepreneur]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Sat, 23 Dec 2017 22:52:16 GMT</pubDate>
            <atom:updated>2017-12-28T03:52:15.203Z</atom:updated>
            <content:encoded><![CDATA[<p>An unconventionally epic bootstrapped startup year in review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*Cq3R--r0XJfWX_jYXqGaxQ.jpeg" /><figcaption>Just another year in the life of a wild-eyed, do-it-all-yourself bootstrapper…</figcaption></figure><p>For most of us, 2017 was a year better left in the dumpster fire from which it was born (aka, “ 2016”).</p><p>For me, 2017 was something truly remarkable and special that I’ll soon not forget — just like how I’d imagine contracting a mild case of necrotizing fasciitis might be.</p><p>If “growth is painful”, then 2017 left me feeling a bit like a bootstrapped startup remake of House.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*cwDfRMI5vNNgooHcEql-kQ.gif" /></figure><p>Between running a growing portfolio of bootstrapped startups (including <a href="https://gettamboo.com/">Tamboo, an all-in-one session recording and replay tool</a>), writing <a href="http://cliffordoravec.com/the-epic-guide-to-bootstrapping-a-startup">a book about bootstrapping startups</a> (while still adding to <a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1">my growing Medium epic</a>, which has now been read by over 180,000 people!!!), building a <a href="https://bootslacking.slack.com/">Slack community for bootstrappers</a>, entertaining all the awesome people following me on <a href="https://twitter.com/cliffordoravec">Twitter</a> (and adding over 500 new followers organically), getting ready to launch <a href="https://saasingear.com/">a new podcast</a>, starting <a href="https://github.com/cliffordoravec/saasyback">an open source SaaS-in-a-box</a>, training for an <a href="https://www.westernreserveracing.com/events/burning-river-endurance-runs-relay/">upcoming 100 mile ultramarathon</a>, reading <a href="https://medium.com/@cliffordoravec/the-38-books-that-i-devoured-and-destroyed-this-year-6f5a6c7bbc87">38 non-business books totaling 19,627 pages</a>, and answering over 766 emails from fellow bootstrappers the world over (all while still having “a life”), you might be thinking that I “crushed it” in 2017.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*cZq2NsGMdunPw_Abvq9QgA.gif" /></figure><p>Put that way, yeah, I guess I kicked some serious ass.</p><p>But in the process, I also got my ass seriously kicked.</p><p>But maybe I’m getting ahead of myself here. Maybe we should rewind things a bit and start at the beginning…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*hUJLABCqX7zOJIJiK9Mu-g.jpeg" /></figure><p><strong>December, 2016</strong></p><p>It all started on December 19th, 2016, a day that will go down in infamy.</p><p>That was the day that I <a href="https://medium.com/@cliffordoravec/the-morning-after-startup-famous-for-24-hours-dab9d6b2c036">inadvertently broke the internet</a> and set off this whole sick cycle carousel I’ve been riding ever since.</p><p>On that day, the stars, constellations, git branches, and quantum bits all somehow aligned (in what I can only describe as some kind of weird prank I’m still convinced the universe is playing on me) and plucked me from my comfy and cozy “lurking in the shadows” bootstrapped existence and unceremoniously plopped me down on the Mount of Startup Olympus (otherwise known as “Hacker News”).</p><p>Now, for most people, getting to the top of Hacker News (and all of the accompanying attention that ensues) is a wet startup dream come true.</p><p>(And I’m not going to lie— that whole experience definitely creamed my Twinkie a little.)</p><p>But truth be told, it’s been both one of the best things and one of the worst things that’s ever happened to me.</p><p>Before we dig into that though, I think it helps to share a little bit about what 2016 was like for me up until that point, which is something I haven’t shared with anyone to date (see, you’re special!)</p><p>Simply put, 2016 was <strong>rough </strong>— both personally and professionally for me.</p><p>I had a handful of projects flame out pretty much simultaneously, including one that was my oldest source of revenue, as well as another that was my (at the time) largest source of revenue.</p><p>I threw everything I could at them to try to bring them back from the startup graveyard, but try as I might to rescue and resuscitate them, I just couldn’t make their shit beep like it used to.</p><p>Admitting that they were “done” and that it was most likely time to kill them off was one of the hardest things I had to come to grips with.</p><p>That, and realizing that all of this represented a 45% hit to my income.</p><p>I’ll admit — I was not the funnest person to be around at that point in time.</p><p>In fact, I pretty much just shut down.</p><p>I couldn’t really deal with much of <em>anything.</em></p><p>Just trying to figure out what to eat for dinner would send me into an hour-long cycle of analysis paralysis (I kid you not).</p><p>To offset all of this lovely stress, I started running my ass off even more than I normally did. That is, of course, until I broke three of my toes and wound up with a crippling instance of achilles tendinitis that put me out of commission for <em>months.</em></p><p>After taking some (well deserved?) time to hit rock bottom and feel sorry for myself, I decided to pick myself back up and stare into the abyss looming back at me.</p><p>If I gave up, I knew that I could never forgive myself.</p><p>And I knew that if I didn’t stare down this existential beast staring back at me, that it would tear me apart limb from limb.</p><p>So I dug in and got myself right again.</p><p>I couldn’t run, so I started meditating regularly (which was brutal at first). I stopped listening to <a href="https://en.wikipedia.org/wiki/List_of_post-hardcore_bands">post-hardcore music</a> (quite arguably my drug of choice) and switched full over to <a href="https://en.wikipedia.org/wiki/Tropical_house">tropical house</a>. I started reading fiction and literature at night (sometimes going well into the morning). I started eating lighter (and cheaper). I forced myself to be brutally honest about my feelings — and sought to destroy them before they could destroy me.</p><p>And most of all, I forced myself to go “back to basics”.</p><p>After I had calmed myself down, I realized that I had probably prematurely torched a couple of the projects that I had taken behind the woodshed and that some of them could have probably been saved.</p><p>Of course, it was a little bit late for that now.</p><p>So rather than cry over spilled milk (or slain startups), I forced myself to shore up what I had left and to grow out what I could.</p><p>Once I had gotten myself back on solid ground, I had a renewed sense of clarity from the whole experience.</p><p>It was from this “back to basics renaissance” that I penned <a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1">the first part of The Epic Guide</a> in order to start the fulfillment of a vow that I had made to myself.</p><p>Two months later, it took off. And the rest is history.</p><p>That was 2016.</p><p><strong>Enter 2017.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*j7TOG1MTGKg65P7DlGKTpw.jpeg" /><figcaption>We *were* warned…</figcaption></figure><p><strong>January</strong></p><p>So I ended 2016 on a high note that appeared to be the harbinger of awesome for what 2017 would bring — or so I thought.</p><p>Looking back, January was actually rather foreboding in a way — I just completely missed the signal from the noise.</p><p>Much of January was spent trying to dig myself out of the fall out from having gone interstellar in December.</p><p>My inbox was flooded with emails.</p><p>I had more Tamboo signups in trial than I could keep up with.</p><p>And of course, this crazy idea for turning The Epic Guide into a full-length book was getting traction and picking up steam.</p><p>I remember January as “inbox month”.</p><p>Whether it was responding to people writing me about the articles, going back and forth with people interested in the book, or sending gazillions of emails to all of the people who were trialing Tamboo to see how I could help them, if I could get feedback from them, or if they were at all ready to convert to a paid plan, I just remember lots and lots (and <em>lots</em>)… of emails.</p><p>January ultimately ended on a disappointing note: Despite the massive influx of new trials, and despite all of the emails that I sent, people just weren’t converting like they should have. Part of me knew this would happen. I knew that these were just “tire kickers” checking out Tamboo from the Medium articles and that they were never serious about paying — they were just curious and wanted to play. And since it was free to try out and play with, they did just that. (Much to my chagrin.)</p><p>But that still didn’t stop me from <em>hoping</em> that that wasn’t the case and it most certainly didn’t stop me from <em>trying</em> to turn those trials into paying customers. In my exuberance, I even broke the cardinal rule of product management and added features requested by customers who said “It needs to do this before I’m willing to pay”. And of course, despite spending weeks building those features out, <em>none of them </em>converted or paid once they were in place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*wpbXkL47L7B2VE_9LCgoXA.gif" /><figcaption>And so it begins…</figcaption></figure><p><strong>February</strong></p><p>I wish I could say that I stopped foolishly chasing the influx of new trial users in February that I secretly knew where just bad for business, but then I wouldn’t be sitting here kicking my own ass for your amusement, now would I?</p><p>Instead, I spent a ridiculous amount of time fucking with Tamboo’s UI and UX to see if <em>that</em> would somehow convince them to stay.</p><p>Fucking amateur hour, right?</p><p>(Stay tuned kids, it gets better.)</p><p>It’s about this time that demand for <a href="https://cliffordoravec.com/the-epic-guide">The Epic Guide: The Book</a> reached critical mass. I had to make a decision — it was time to shit or get off the pot with this book “idea” I had.</p><p>Part of me really, really, <em>really</em> didn’t want to do this book.</p><p>Part of me knew that this would probably turn into a “bad idea” that I would regret.</p><p>Part of me was like “Are you nuts?! This is going to be a <em>huge </em>time sink and distraction!”</p><p>And yet there was that nagging voice in the back of my head that said “If you <em>don’t</em> take this opportunity you’ve been given and run with it, you’re going to regret it.”</p><p>I hemmed and hawed about it for weeks on end.</p><p>Eventually, I literally flipped a coin to decide if I was going to do it or not (I kid you not).</p><p>Fucking heads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*xfts1iBXFZI-x_pY8MHXbg.jpeg" /><figcaption>And no, it wasn’t a trick coin.</figcaption></figure><p>So I spent the better part of the end of February coming up with copy and building out the presale site for the book, hooking up payment processing, and getting <a href="https://medium.com/@cliffordoravec/ewww-your-startup-funnel-is-leaking-all-over-me-part-4-of-the-epic-guide-to-bootstrapping-d08e0db6b167">Part 4 of The Epic Guide</a> ready for launch, where I would announce the launch of the presale.</p><p>And of course, the damned thing had to take off.</p><p><strong>March</strong></p><p>March was kind of all over the board.</p><p>I did a lot of work on Tamboo, from adding features to updating the marketing site to tweaking the backend. I think this was around the time that I did the first major rewrite or update of the heatmap engine, as well (more on that fun later).</p><p>In addition to the book presales continuing to pile up, March is also when Courtland and I recorded <a href="https://www.indiehackers.com/podcast/009-clifford-oravec-of-tamboo">my Indie Hackers podcast episode</a>.</p><p>I don’t know if you can tell or not from listening to it, but I was <strong><em>super the fuck freaked out.</em></strong></p><p>The IH podcast was newer at the time (I was episode #9), but I knew it still had massive reach even then — and that that reach was growing every day.</p><p>I had never done a podcast episode or even a recorded interview for that matter before — and here I was doing my <em>first</em> podcast interview ever on Indie Hackers?!</p><p>March was also when I started Bootslacking, an invite-only Slack group for people running or starting bootstrapped startups. This was mainly born out of a frustration of not having any good place to “talk shop” with other bootstrappers, and since I was getting emails from so many of them, I thought it made sense to bring them together in a forum where the focus could be on sharing and learning knowledge and experiences about startups and business — and where anyone who turned out to be a random fly-by-night startup promoter would be immediately booted.</p><p>Meanwhile, The Epic Guide continued to grow and and spread its tendrils across the internet, creating an obscene number of “tire kicker” free trials that I (of course!) was still running around trying to turn into magical unicorn poop conversions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*kcDZYWhFmyzNWRXopLxENQ.jpeg" /><figcaption>These fucking tire kicker trials…</figcaption></figure><p><strong>April</strong></p><p>I remember April vividly, despite the complete lack of sleep.</p><p>April is when things <em>really </em>started to heat up.</p><p>It all began with the build-out of a “live demo” for Tamboo.</p><p>The idea for the live demo was simple enough: It would let people try out Tamboo on their own website in a quick interactive demo that wouldn’t require them to install anything so that they could see how it would work. Basically, they’d enter their website URL, I’d show them their website in an iframe, I’d record what they did, and then I’d let them watch a recording of that session.</p><p>On my end, this would hopefully:</p><ol><li>Discourage tire kickers from signing up for a trial — they’d be able to see what Tamboo did in the live demo and hopefully have their curiosity squashed if they weren’t serious.</li><li>Encourage signups from people who saw Tamboo in action and wanted to use it on their website — essentially giving people “a taste” in order to help incentivize them to create a trial.</li><li>Give me inbound leads to make my sales efforts a little easier (via the website entered). Rather than having to rely almost solely on outbound prospecting, I could add some interested inbound leads to my pipeline and close some more sales.</li><li>Give me data about what kinds of websites were using the demo and converting or not converting. I was hoping to find some kind of trend in the type of websites which were more likely to convert vs. not convert to help out with future targeting.</li></ol><p>Simple enough, right?</p><p>From a technical perspective, building out the demo was much more difficult than I had anticipated. It turns out browsers don’t really like it when you try to inject JavaScript into an iframe whose source URL isn’t one that you own (who’d of thought, right? 😐).</p><p>So I basically had to build a proxy that would retrieve the website requested and serve up the content from my own domain that I could then inject the Tamboo agent into to do its capture and recording magic. But even <em>that</em> wasn’t as straight-forward as you’d think, given all the websites using CORS to block requests to things like stylesheets, etc. And not to mention all the rewrite rules that you had to apply to things like stylesheets, image URLs, links, etc., etc., etc. to make it all work.</p><p>It took me about two weeks of (literally) around the clock hacking to get something that I thought would work together.</p><p>Once it was live, people started using it en masse.</p><p>And that’s when I realized just how far I was from “getting it right”.</p><p>There were so many random ass edge cases that pretty much every site that tried it out wound up having massive rendering and recording issues.</p><p>In short, I spent <em>a lot</em> of time sending emails to people to apologize for the shitty demo experience they had while trying to salvage what I could. And all that time, I was madly plugging away around the clock fixes for things that I saw people running into.</p><p>Oh, and did I mention that all those beautiful leads and data that I thought I would get were basically total trash?</p><p>Yeah.</p><p>It turns out a lot of people just liked to stick sites like cnn.com and whatnot in there to see what would happen (plus there were more than a few cheeky bastards who loved to put URLs in to my competitor’s websites…)</p><p>And the sites that did use their actual website address?</p><p>Most of them were things like doggy boutiques, hair salons, psychologists, a Hungarian foodie site, florists, and a bunch of (obviously) very early stage “startups”, just to name a few.</p><p>There was absolutely no rhyme or reason to any of it. None of them demonstrated any kind of target market pattern like I was hoping to uncover. There was pretty much nothing actionable that could be gained.</p><p>And to make things even more fun and interesting? The people who did sign up to view their recordings from the demo hardly ever converted to an actual trial. It was one and done, in and out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*xVypfcvlxuMg5ghQvHL1Pg.gif" /></figure><p>Also in April (oh, we’re not done yet here), I started to hit some massive performance issues and had to completely refactor my backend.</p><p>This was something that was slowly growing and coming to a head, but was put over the top by a super large website coming on that singlehandedly threw more traffic at me than I have literally ever seen in my life before.</p><p>So with all of this live demo fun going on, I was simultaneously doing everything I could just to keep the lights on while getting buried from more traffic than a Hacker News tsunami — on an hourly basis.</p><p>I eventually split out the new customer onto their own dedicated set of servers just to get their load off of everyone else (who were starting to complain about performance) and used the experience to completely revamp the backend.</p><p>That refactoring effort required me to do a <em>massive </em>data migration effort that I spent days planning and testing for in my staging environment to make sure it would go off without a hitch.</p><p>And of course, nothing went off without a hitch when I ran it in production.</p><p>In fact, there were hitches lying all over the floor of my office, broken and shattered as I frantically tried to make things work. Everything was locking up, freezing up, timing out, and taking <em>way</em> more time than my test runs would have indicated.</p><p>I thought I had done everything right to avoid this — I had even used a <em>complete</em> <em>copy</em> of my production data to run my tests against.</p><p>So what the fuck happened?</p><p>Production load.</p><p>The live load on the system wasn’t something I had accounted for and basically caused everything to violently thrash in an endless cycle of pain.</p><p>After three sleepless nights, I <em>finally</em> was able to pull the system out of its downward death spiral and get the migration to complete.</p><p>Three fucking days.</p><p>It took six hours in staging.</p><p>Oh, and then a few weeks later that massive new customer that I was really excited to have on board that kind of pushed everything to the tipping point of catching on fire and burying me in startup ashes unceremoniously cancelled without reason and went dark. This is of course after having had numerous back and forth emails and phone calls with them to get them properly onboarded, and after they had gleefully declared that everything was working “great” and that it was “awesome” and that the PO was being cut.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*czfs6UxTqyxWsb3V_o_TFA.jpeg" /></figure><p>As if that weren’t enough, I also wrote the first 100 pages or so of The Epic Guide Book in April, as well as started a major refactoring of Tamboo’s UI and UX, codenamed “Project Cayman”.</p><p><strong>May</strong></p><p>May saw the release of Project Cayman, (another) complete refactoring of Tamboo’s heatmap engine, and support for capturing and recording YouTube video interactions (yet another one of those customer requests I probably should have just passed on in hindsight).</p><p>I also completely updated the marketing site as well as modified the pricing structure to capture what I thought would have been a good opportunity to align pricing to how people were using Tamboo (which ultimately became yet another failed experiment).</p><p>At the time, there was no limit to how many websites you could use Tamboo on under a single account. I saw that a number of people were using Tamboo on multiple websites and thought “Huh! Maybe I should tier the pricing based on how many websites they want to use it on!” I had always hated the usage-based pricing of how many recordings people could have. Most people just don’t know how much traffic they get, or how many recordings they might need. I had done things to try and make this easier on the end user, such as leaving limits open during trials and then recommending a tier based on their trial usage, but I still felt that these “limits” were maybe preventing people from signing up for a trial. So in my mind, this was the best of both worlds — you know how many websites you have or want to use this with, and you don’t need to worry so much about limits then. Brilliant, right?</p><p>Yeah, not so much. (But it took over a month to figure that out.)</p><p>But honestly, what I remember most from May is how Project Cayman and its roll out just ruthlessly kicked my ass. All of this was a continued attempt to convert all of this “startup gold” traffic coming my way. I was getting people coming through, signing up, trialing, using it daily, and then never converting when it was time to pay (despite numerous outreach emails, many of which received favorable replies like “I love it!”, but then they’d go dark when it was time to pay). And so I continued to think that I had to fix something with the UI and UX to make it even more awesome to get all these people to convert. The conversion rates just weren’t where they should be, despite the large influx of trial users.</p><p>So I worked around the clock to “improve” the UI and UX to try and “make it work”. After all, the (small) number of people who responded to my emails about why they cancelled out of their trials all said stuff about the UI and the UX, so that <em>must</em> be what needed “fixed”, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*TdUKXNOobq2vM2Zp1RSajQ.jpeg" /></figure><p>Oh! And of course, live demos were still going at this time, causing me endless frustration and grief and somehow bringing <em>even more</em> tire kickers in through the gates. (More on that in a bit.)</p><p><strong>June</strong></p><p>At the start of June, I kind of lost my shit.</p><p>I think it helps to understand a few things in order to really understand why.</p><p>When I had originally written the first part of The Epic Guide, it was just a Medium article that I had written. It didn’t have any reference to Tamboo or anything else. It was just me writing as me.</p><p>A number of people were like “What’s your startup?! I want to check it out!”</p><p>I thought that was pretty cool and a completely valid request, but at the same time, I was like “which one”?</p><p>I had a number of “startups”, and I really didn’t want any undo attention on some of them that I thought could introduce some otherwise unnecessary competition in their space.</p><p>So I picked one of my newer ones that I thought was complicated enough that it would turn people off from trying to copy it and that I thought could benefit from some free eyeballs 🙃</p><p>Up until that point, I was slowly but steadily growing Tamboo with very specific market segments that worked well with it being a younger platform that still a lot of work ahead of it.</p><p>Tamboo was my first attempt at “leveling up” from more niche applications. It was an intentionally more ambitious, more mass market play. It was my “10x” endeavor. And it looked like it had the potential to do just that based on early engagement, feedback, and results.</p><p>Now, keep in mind, this is all before the Hacker News tsunami.</p><p>People who initially read the articles (again, <em>before</em> the HN kraken) checked out Tamboo (now that there was a “plug” for it), seemed to like it, signed up for it, and even became customers.</p><p>And I was like “Wow, this is pretty cool. Non-heavy handed content marketing about a topic that I’m completely passionate about for the win!”</p><p>And then the Hacker News tsunami hit (and spread) and all of that went to shit.</p><p>Sure, I started getting <em>way </em>more trials, but the conversions were total shit.</p><p>Because those people weren’t really my target market.</p><p>But there were just <em>so many </em>of them that I just couldn’t keep myself from <em>trying</em> to capture some of that “market”.</p><p>Now, the other thing to keep in mind is that prior to The Epic Guide gaining notoriety, I was pretty much a “shadow lurker”. Aside from playing around with answering startup questions on Quora at one point, I really hadn’t ever “put myself out there”.</p><p>In fact, I never wanted to be “out there”.</p><p>Some people <em>want</em> attention, recognition, notoriety, fame, and so on.</p><p>Me? I just want to make money running a business that I own. No muss, no fuss. I don’t care who knows who I am or what I do. I’m perfectly happy making bank and living my life without all of the accolades or vanity that come with running a “startup”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*R0Y42_VqeIRJTRG3OJMmhg.jpeg" /></figure><p>Okay, so where was I?</p><p>Oh yes, the losing my shit part.</p><p>Basically, I had spent the last six months chasing some sort of elusive “growth ghost” with Tamboo by trying to turn this “marketing channel” that startup notoriety had given me into something usable, and it just wasn’t working the way that I thought it should.</p><p>Combine that with the fact that I was experiencing high churn (about a 3 month average LTV) from these efforts with an app that I had planned on being low churn.</p><p>Part of the allure of Tamboo to me was that I felt that it would be something that people would buy and keep for a long time as a way to learn from changes they made to their website, as well as a kind of “insurance policy” they could use to troubleshoot issues that might creep up. I imagined it would be something more like an analytics program that people would use maybe a few times a month but would continue to keep around indefinitely because they couldn’t “go back” to running a business without the kind of visibility that it gave them.</p><p>So that was one part of the equation.</p><p>The other part was that at this same time, my profile as an “expert” in the bootstrapping space continued to grow.</p><p>The fact that my name became synonymous with Tamboo started to wear on me.</p><p>Here was this thing that I had started to grow in a very strategic way that all of a sudden is getting all of this attention, but none of that traffic or attention are “converting” properly.</p><p>And that was fucking with me.</p><p>Now, it wasn’t that Tamboo wasn’t growing or that it wasn’t “working”. It was just that it wasn’t growing or working the way that I thought it should now that it had all of this “free marketing” getting thrown at it.</p><p>And while all this is going on, preorders for the book keep pouring in, my followers keep growing, and more and more people keep discovering The Epic Guide and for some reason or another prop me up as some kind of a startup hero to be revered and looked up to.</p><p>This internal dichotomy started to mess with me.</p><p>Here I was, trying to figure out how to get this thing to convert all of this newfound traffic and attention into something meaningful, while at the same time everyone thinks that I’m some sort of magical startup hero who has all the answers.</p><p>But I’m not a hero.</p><p>I’m just a dude.</p><p>I do not have nor have I ever been imbued with any kind of startup superpowers.</p><p>But that didn’t seem to stop people from thinking otherwise.</p><p>My articles continued to get more and more popular. My inbox got more and more emails. And I continued to get more and more preorders for the book.</p><p>It’s around this point in time that I started to feel like I can’t fuck up for fear of some kind of a fallout.</p><p>The fucked up “growth” that Tamboo was experiencing and the fucked up live demo and free trial fiascos that were causing me to want to rip my hair out couldn’t ever be discussed because… <em>what would people think?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*ottvknvBCwdava0syQ4T5w.jpeg" /></figure><p>So the pressure got to me a bit and I kind of lost it.</p><p>I was spending an inordinate amount of time trying to figure out how to get my conversion and retention numbers from these people to work and I wasn’t getting much of anything else done.</p><p>Plus, I felt that maybe free trials, as standard as they are for other SaaS apps, might not be the way to go with Tamboo. You see, free trials mostly exist to 1) get people in the door and 2) give people time to get setup in a new app and to achieve some goal/get some outcome before being required to pay as a way to reduce early friction (and get them hooked).</p><p>With Tamboo, people got value out of the gate. And I had a sneaking suspicion that people were using the trial, getting that upfront value, and then just going their merry way.</p><p>So I killed the live demo and ripped out free trials and forced everyone to “pay to play” —aka credit card and payment up front.</p><p>That was probably a little hasty, <em>but it felt so fucking good.</em></p><p>The minute those changes went live, my inbox got quiet. Real quiet.</p><p>I wasn’t getting notifications about new “leads” I had to track down. I wasn’t getting error reports about shit breaking in a demo or getting support requests from people in a free trial complaining about something not working right (or at least not how they expected).</p><p>If you wanted my attention, you’d at least be a paying customer.</p><p>It was bliss.</p><p>It was at that time that I decided to switch gears and put some focus into this book, which was continuing to get steam and traction and weighing on me more and more each day.</p><p>I spent most of the rest of June focused on the book now that I could stop worrying about demos and trials and tire kickers.</p><p><strong>July</strong></p><p>Instead of stressing about Tamboo in July, I shifted most of my focus to the book (which I in turn wound up stressing about).</p><p>Writing the first pass of the first part of the book took much longer and required much more effort than I had anticipated.</p><p>It took me a little while to “find my groove”. Writing a book is very different from writing a bunch of blog posts. (Anyone who’s made an attempt at one will know what I’m talking about.)</p><p>I wound up writing something like 300 pages in a marathon multi-week writing session.</p><p>Then I threw it all away and started over from scratch.</p><p>The second round, I wrote something like 200 pages and wound up throwing 75 pages or so to the cutting room floor, leaving me with about 125 pages give or take.</p><p>Editing took far more time than I would have ever imagined.</p><p>I think that I went through three or four editing passes on the first part before I finally thought it was at a point where I felt comfortable releasing it.</p><p>I was a little nervous releasing such a monster (it was the first release, clocking in at over 100 pages), but at the same time I had reviewed and edited it enough that I was pretty confident in what I had put together.</p><p>Still, hitting “send” on that email list was honestly a little scary.</p><p>But it turns out people loved it and I got a lot of positive feedback and encouragement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*cAbhI2JezlMKjNttx3EpPQ.jpeg" /><figcaption>Kick-ass!</figcaption></figure><p><strong>August</strong></p><p>I really enjoyed working on writing the first part of the book. I had dreaded the effort that would be involved, but once I got into it, I really thoroughly enjoyed it. Shipping it felt even more awesome (I love shipping — there is no feeling quite like it).</p><p>But that whole time, I was stressing about Tamboo and all the things I <em>wasn’t</em> doing there.</p><p>Ever since I had killed off the live demo and the free trials, signups had plunged.</p><p>This was to be expected, but I knew that in order to maximize those pay-up-front conversions, that I would need to do a better job of showcasing and explaining Tamboo on the marketing site.</p><p>Up until then, I could afford to have less on the marketing site because the free trial kind of offset any kind of risk for people to try it out.</p><p>Not having any kind of trial anymore, I needed to really up the potency of my marketing site to convince people to fork over their credit card for something they couldn’t try out first.</p><p>So I did just that and completely overhauled the marketing site and pricing structure (again).</p><p>Like I had mentioned before, I thought that offering pricing around the number of websites that someone would want to use Tamboo on would be a logical way to segment tiers, but it just didn’t seem to be resonating the way that I thought it would. So I switched back to usage-based pricing, but I structured the plans around customer segments to make it scream “this is for me” to them. So I now had plans for “Personal”, “Startup”, “Business”, and “Agency” to target those different classes of users, which would hopefully help overcome any kind of confusion about recording limits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*gYYpbVn48WiGKFDviR0bSg.gif" /><figcaption>Daddy’s gotta go to work.</figcaption></figure><p>I also did some much needed marketing and promotion for Tamboo, but in hindsight, I was doing it in the wrong places again (more on that later).</p><p>At the end of August, I decided to bite the bullet and start the process of launching a podcast, which is something I’ve been wanting to do for a long time (sort of like writing the book). To gauge intereset, I created a landing page for <a href="https://saasingear.com/">SaaS In Gear</a> and started promoting it, following my tried and tested method with the goal of getting 100 signups.</p><p><strong>September</strong></p><p>Then September hit, and I had a serious meltdown.</p><p>Shit was starting to wear on me.</p><p>Bad.</p><p>It’s around this time that I started to feel like the market for Tamboo had somehow moved under me, and that I had missed a huge opportunity by having my focus and attention diverted by this whole “startup culture” thing I had somehow found myself wrapped up in.</p><p>Somehow, all of the effort that I had exerted to date caught up with me in one massive tidal wave of despair.</p><p>All of the late nights, all of the weekends, all of the emails, all of the seemingly endless refactoring and tweaking, all of the marketing site updates, all of the never ending support requests, all of the writing, all of the forums, all of the Slack groups, all of the shitty conversion rates, all of the atrocious retention numbers, all of the, all of the, all of the… <em>everything.</em></p><p>It just hit me.</p><p>Very much like a ton of bricks.</p><p>I shut down.</p><p>I became despondent.</p><p>I started to feel like I had back in 2016 when everything fell out from under me.</p><p>Sure, this was very different from then. After all, my revenue was going up instead of down, and I was still moving in the “right” direction — just not in the way that I wanted to, and not in the way that I thought that I should.</p><p>But I still had this feeling that what I was doing wasn’t somehow <em>right.</em></p><p>That I was screwing something up by not being as focused as I should on the things that I knew I should and that in the process, I was missing out on something much bigger.</p><p>And that I somehow might have “missed the boat” by the time I realized it.</p><p>It was at this time that I started to “feel” that things had somehow changed over the past few months.</p><p>I’d completely cut off trials, so I knew things would be much slower and less action-packed, but I felt that there was something <em>else</em> going on — something that was out of my control.</p><p>I didn’t have anything to support my suspicions, but I started to feel that session replay tools had become <em>commoditized</em> by my competitors — and that they had somehow turned this whole market into a race to the bottom.</p><p>This suspicion came from the observation that pretty much every one of my competitors were now engaged in a freemium play — offering completely free tiers for their products. And seeing a lot of people starting to tout that as a “benefit” — “You can use it for free!”</p><p>As a bootstrapper, you don’t want to get into a freemium fight if you can avoid it.</p><p>Freemium — especially in a resource intense business like session recordings — can be <em>very</em> expensive.</p><p>Based on what I knew, I’d come to the conclusion that the largest of my competitors had used their freemium play as a way to basically corner the market and juice their SEO.</p><p>In the process, they were forcing everyone else in the market to follow suite if they wanted to stay in the game.</p><p>The vast majority of their “customers” don’t pay for their service, but since they had a nice little war chest to burn, and since it helped them maintain their market dominance, they seemed to be fine with that. They were still making bank from the other side of the freemium play, and so it seemed to be working out masterfully for them.</p><p>They were able to keep low-cost competitors from “stealing away” at the lower end of their customer base by offering a free tier, and they were able to maintain their higher price point by being “number one”.</p><p>I didn’t know if this was a game that I wanted to play anymore.</p><p>I was beat down and worn out and I just didn’t know if I had it in me to fight this fight anymore.</p><p>I gave myself permission to crash.</p><p>And so I did.</p><p>A few days later, I picked myself back up.</p><p>I knew that feeling sorry for myself wasn’t going to fix anything.</p><p>The only thing that would fix anything would be to get back up and face these things head on.</p><p>So that’s what I did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*1s7hNXzwCPjMiQHaErXO8A.jpeg" /><figcaption>My name… is Neo.</figcaption></figure><p>I wrote down all of the shit that was getting to me.</p><p>And then I asked myself what I could do about each of the things I had written down.</p><p>If I couldn’t do anything about it, I told myself to suck it up and crossed it off the list.</p><p>If I <em>could</em> do something about it, I forced myself to figure out what I could do — even if it wasn’t a guaranteed “fix”. (Any action is better than no action.)</p><p>This exercise helped, but it didn’t take the emotional drain I was feeling away. It just gave me a course of action.</p><p>And so I went to work.</p><p>I continued to promote the podcast launch list.</p><p>I tackled some nasty support issues for some new customers that took a lot of time and effort.</p><p>I worked on Part 2 of The Epic Guide Book.</p><p>I made some performance and stability improvements.</p><p>I tweaked some UI and UX things.</p><p>I started working on adding a custom funnel feature to Tamboo.</p><p>All in all, I came back swinging in September, even though I still felt like shit the whole time.</p><p>It was around this time that I started feeling like I just wanted to shut down and do me and not worry about anyone else. So I pulled back on Twitter, email, Slack, forums, etc. This was the start of me going “inside” and just wanting to insulate myself from everything.</p><p><strong>October</strong></p><p>In October, I finished and rolled out the custom funnel feature for Tamboo, as well as completely gutted the heatmap engine again (this is the third time if you lost track) and added support for mouse movement heatmaps.</p><p>And of course, it’s pretty much useless to add new features and not tell anyone about them, so I made some marketing site updates and did some promoting to showcase the new funnels and heatmaps.</p><p>I even gave one more last-ditch effort to try to convert some of my Medium traffic by creating a special offer to get a copy of my book when people from Medium signed up for Tamboo (I still couldn’t let that go for some reason).</p><p>I spent (a lot) of time finishing up the second part of The Epic Guide Book, including spending what I would consider an obscene amount of time working on illustrations for it. Shipping the second part and getting some of that built-up pressure off my plate felt good, kind of like coming home and just crashing on your couch after a long day at work.</p><p>And if all of that wasn’t enough, I also wrote and published <a href="https://hackernoon.com/real-world-startup-sales-and-marketing-for-the-lost-and-the-clueless-part-5-of-the-epic-guide-to-87db07b436f5">Part 5 of The Epic Guide Medium series</a>, which was (embarrassingly) the first update to the series in <em>months</em>.</p><p>I was worn down, and not feeling very social, but I was at least still <em>moving.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*CV9UeeJzKfu8qUZK8ThsmA.jpeg" /></figure><p><strong>November</strong></p><p>All of that caught up with me in November.</p><p>I still did <em>stuff</em>, but it was getting harder and harder to get back up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/1*HYNGAHRL_wSpOSqDncvNUA.jpeg" /></figure><p>I got swamped pretty early on with some more intense support issues from new customers (this shit is hard, if you haven’t caught on yet).</p><p>I spent about a week fucking with heatmaps again (fourth rewrite in the year).</p><p>I marketed.</p><p>I started <a href="http://gettamboo.com/academy">Tamboo Academy</a>.</p><p>I started a prototype of a website chat feature.</p><p>I ran (keep in mind, I’m still training for an ultramarathon during all of this).</p><p>And I finally caved and brought back trials.</p><p>Signups were too low for my taste with the “pay up front” approach, so I compromised and decided to do credit card upfront trials (which have worked out better).</p><p>The whole time, I just felt down and didn’t really want to talk to anyone about anything.</p><p>I was really starting to feel this whole “split brain” life I was living.</p><p>On one hand, I have this great application that I spent a shit ton of time on that I feel has a lot of potential, but that I don’t feel I’m focusing on in the right way, and that could have more outsized results if I’d just go all-in on it. It isn’t easy to work with (there are days I absolutely <em>hate</em> working on this thing), and it seems to be getting harder to market it. There are things that I would love to do with it, but I just can’t bring myself to do those things unless I can get my conversion and retention rates where I want them to be. I’ve been half tempted to just put the thing on autopilot, be happy with the income it generates, and shift my focus to something else. It‘s not something that I necessarily <em>enjoy</em> anymore. There are times when I feel like I just can’t turn it into what I had originally wanted it to be anymore, and that I just haven’t been properly focused on putting my efforts towards the right markets for it.</p><p>On the other hand, I’ve built up this “startup personality” thing somehow, and I really enjoy writing and helping people get and see traction with their projects. (At least when I’m not emotionally burned out by everything.) I get honest enjoyment from helping people go from “I’m stuck and frustrated” to “I’m making $1,000 MRR!”. I feel honest pride and admiration for them, and it makes me feel like I have a purpose bigger than just eeking out another tenth of a conversion rate percent on my website.</p><p>But I was starting to see that the two are incompatible and are actually at odds with each other.</p><p>Like I’ve mentioned before, Tamboo had (and continues to get) a lot of attention from my Medium articles and all of the sites that link back to it because of my “startup status”.</p><p>But hardly <em>any </em>of that has resulted in any kind of actual, tangible business results for Tamboo.</p><p>The <em>vast</em> majority of the people who have paid for Tamboo did <em>not</em> come from any of those efforts or traffic.</p><p>By my calculations, roughly 3% of all paying Tamboo customers can be directly attributed to those sources.</p><p>(Surprised?)</p><p>And yet I’ve wound up spending <em>a shit ton of my time</em> contributing to that community since last year.</p><p>(And sure, I’m not going to lie — I’ve tried converting some of that traffic and attention, but it just doesn’t seem to want to be converted.)</p><p>But doing <em>both</em> when neither benefits the other, and when they both push and pull at me in very different ways that leave me exhausted, feeling like I’m failing at my goals for either, and make me feel like working on one over the other is causing me to choose which one I want to see fall behind even more?</p><p>I just don’t know.</p><p><strong>December</strong></p><p>By December, I’m feeling overwhelmed and ready to just curl into a ball and wait it out until January.</p><p>It started off okay enough.</p><p>I did some more marketing. I did some more customer onboarding.</p><p>But things kind of fell off the rails early on.</p><p>Maybe it was the <a href="https://blog.gettamboo.com/are-session-replay-tools-really-as-creepy-as-everyones-saying-5fdcbbe6f33e">fallout that hit the session replay market</a> from a widely publicized “study” that got covered in near every major tech publication. (A lot of us saw a major drop in subscribers as a result of that. I even had a few people start <a href="https://twitter.com/cliffordoravec/status/933875141259427840">leaving me “love notes”</a> on Tamboo’s website. Definitely “motivating” stuff.)</p><p>Or maybe it was the one customer that I had spent a few days helping to get onboarded (due to some issues with the way they had coded their website) that decided to just cancel on me that sort of pushed me over the edge.</p><p>Any one of these might have been the straw that broke the camel’s back, but it was a long time coming.</p><p>Despite all of the effort I put into my training this year, logging a shit ton of runs and miles, doing all kinds of interval and hill training exercises, including building up to half-marathons on the weekend, being super careful with everything I was eating and doing, and starting to get pretty damned ripped, I stopped running and put on a fair amount of “winter weight”.</p><p>I basically stalled on moving forward with my podcast, because I just couldn’t bring myself to talk into a microphone without sounding despondent and burned out.</p><p>I haven’t touched my book since releasing the last part in October, mostly because I just can’t bring myself to losing another month of progress on my business.</p><p>I haven’t been very “social” on the internet or otherwise. I just don’t have anything really positive to say right now, and I just kind of want to be left alone with my own thoughts.</p><p>And then throw in getting sick as a dog this past week, and that’s pretty much a recipe to just step back and want to admit defeat.</p><p>A lot of people have told me that they like me and my writing because I don’t bullshit.</p><p>Well, here you go.</p><p>No bullshit.</p><p>I’m burned out. I’m torn. And I don’t know how to go forward.</p><p>Just to get away from some of this, I started working on an open source project just to have something “exciting” to play with. So when you might think “Wow, he’s even doing an open source SaaS-in-a-box!”, it’s really just a distraction for me from this other shit.</p><p>Despite all of my experience building software-based businesses, I’ve never built a startup with ambitions like Tamboo before, and I’ve never had an audience or a following either.</p><p>So I’m not sure how to go about “this”.</p><p>Because I’ve never done “this” before.</p><p>Contrary to what you might think, I don’t have all the answers.</p><p>And I’m tired of feeling like I have to.</p><p>So I guess I have some decisions I have to make this upcoming year.</p><p>Don’t worry — I’m not going to leave anyone high and dry.</p><p>I’m still going to finish this book, and I’m still going to keep Tamboo chugging along.</p><p>But do I continue to live this split-brain existence?</p><p>Do I choose one over the other?</p><p>Or do I somehow make them “align”?</p><p>Right now, I don’t know.</p><p>But I do know that whatever choice I make will shape where I go this coming year, just like the choices I made earlier last year led me to where I am today.</p><p>Do I lick my wounds and walk away, choosing one over the other?</p><p>Or do I find a way to swing back at both?</p><p>Happy Holidays.</p><p>And Happy New Year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*F42cfbk_4Lt3MnBduIgKVA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c42540fb4ba2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are Session Replay Tools Really As Creepy As Everyone’s Saying?]]></title>
            <link>https://medium.com/tamboo/are-session-replay-tools-really-as-creepy-as-everyones-saying-5fdcbbe6f33e?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fdcbbe6f33e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 12:01:01 GMT</pubDate>
            <atom:updated>2017-12-05T12:01:01.492Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WbH-Q1duJ0pfgFNdmDXPrw.png" /></figure><p>A recent <a href="https://freedom-to-tinker.com/2017/11/15/no-boundaries-exfiltration-of-personal-data-by-session-replay-scripts/">Princeton study about how 400 of the top websites in the world use session replay tools</a> seems to have caught the internet off guard. It turns out, pretty much nobody knew that businesses could (or do) record what their visitors and users do on their websites.</p><p>And that makes me sad.</p><p>Mainly because I wouldn’t think this type of thing should come as such a huge surprise to everyone when we live in a world where we teach robots how to do parkour:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FfRj34o4hN4I%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DfRj34o4hN4I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FfRj34o4hN4I%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/0a323a4ea65ff52c1ae5aba5ad150fe8/href">https://medium.com/media/0a323a4ea65ff52c1ae5aba5ad150fe8/href</a></iframe><p>But also because that means that businesses like mine need to do a better job of marketing our <a href="https://gettamboo.com/">session replay tools</a>.</p><p>Yes, I’m “one of them”.</p><p>Because I run one of those “evil” companies that’s running around “spying” on everyone using the internet.</p><p>(At least, that’s what some of these sensationalist fear-mongering articles would lead you to believe.)</p><p>Now, I’ll be honest. I was kind of amused by the recent flurry of copy-cat articles and misinformed outrage this Princeton study triggered. The articles and the headlines are A+ clickbait, designed to stoke fear and encourage <em>can-you-believe-this</em> link sharing.</p><p>As an example, some of the stories published have headlines that read “<a href="https://motherboard.vice.com/en_us/article/59yexk/princeton-study-session-replay-scripts-tracking-you">Over 400 of the World’s Most Popular Websites Record Your Every Keystroke, Princeton Researchers Find</a>”, “<a href="http://technewsdir.com/risky-scripts-pose-threat-to-web-surfers-say-researchers">Risky Scripts Pose Threat to Web Surfers, Say Researchers</a>”, “<a href="https://www.digitalmunition.me/2017/12/20579/">World’s top websites record all your browsing movements</a>”, and even “<a href="https://www.fastcodesign.com/90152433/the-popular-web-design-tool-thats-actually-a-massive-privacy-nightmare">The Popular Design Tool That’s Actually A Privacy Nightmare</a>”.</p><p>My personal favorite is Wired’s take on this, entitled “<a href="https://www.wired.com/story/the-dark-side-of-replay-sessions-that-record-your-every-move-online/">The Dark Side of Replay Sessions That Record Your Every Move Online</a>”.</p><p>(Yeah, definitely no fear mongering going on there, right?)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*Io84oe713clkC-Sw9B6GBg.jpeg" /><figcaption>People tend to overreact when it comes to things they don’t understand…</figcaption></figure><p>After having read a few of these articles, I noticed that they were all missing the same thing — namely any kind of input, quote, or even explanation from any of the session recording vendors or marketers who use them that they so gallantly trash.</p><p>So I thought it was only appropriate to shed some light on the subject based on my own first-hand experience running one of these companies.</p><p>(Spoiler alert: It’s not nearly as exciting or as scandalous as they’ve lead you to believe.)</p><p><strong>Let’s pull back the curtain.</strong></p><p>Rather than just <em>tell</em> you what session recordings are, how about I <em>show</em> you one instead?</p><p>And how about I show you one from my own company’s website — and not just that — how about I show you one of someone who’s thinking of entering in their payment information?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fw6dwGUI5Hbg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dw6dwGUI5Hbg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fw6dwGUI5Hbg%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/ebe0d4b4d133176e933fdfdc491ff2ed/href">https://medium.com/media/ebe0d4b4d133176e933fdfdc491ff2ed/href</a></iframe><p>Huh.</p><p>Well that wasn’t as exciting as everyone made it out to be, now was it?</p><p>Sure, it did everything everyone said it would — it recorded the user using the website, it tracked their mouse as it moved around, it showed where they clicked, it showed where they scrolled, and (if they had decided to enter their payment information instead of walking away!) it would have recorded their keystrokes as well.</p><p>But it’s really not that <em>scandalous</em>, is it?</p><p>In fact, it might not have even been that interesting to you.</p><p>And it shouldn’t be.</p><p>Because it’s not your website!</p><p>Believe me, this one is <em>very</em> interesting to me — but that’s only because it’s <em>my site — </em>and I want to know why they got that far and didn’t enter their payment information. Was it something they saw that they didn’t like? Was it something they <em>didn’t </em>see but needed to? At this point, they already signed up for an account knowing that they’d have to enter their credit card information — so what happened that they didn’t?</p><p>But that’s exactly what this kind of tool is used for — to understand <em>why</em>.</p><p>And if this <em>were</em> your website, you’d probably be very interested in understanding these things as well.</p><p>This is exactly the use case for why people use session replay tools (as well as other tools that are usually employed in tandem, such as heat maps, surveys, website chat, and funnels) to get a more holistic view of “what’s going on”.</p><p>Using these tools, people are better able to see what parts of their website people engage with the most (or the least) — and how.</p><p>They help ecommerce store owners do what brick-and-mortar retail store owners have done for years — watch and see what seems to interest their customers so that they can make adjustments to their store based on that information.</p><p>They help startups learn how to best communicate to visitors what their product does and how it can help them (not to mention help them find parts of their site that might have broken since their last late-night deployment, like their signup process).</p><p>They help product managers see if there are friction points in a web application that keep people from being able to carry out the tasks that that application is designed to help them perform.</p><p>It’s important to point out that companies that use these tools <em>already</em> have access to all of this information and data. Most of it’s already sitting in their databases — and if it’s not — it wouldn’t be that hard for them to get it in there.</p><p>Session replay tools simply help you <em>visualize</em> all of this information instead of having to write and run some (very obtuse) reports.</p><p>And no, random people can’t just watch what you do on any website. Companies need to install and enable session replay tools on their websites, which requires special rights and permissions. Just like you can’t go and update Google’s homepage on your own, you can’t just drop one of these on Google and sit back and watch what happens.</p><p><strong>But! But! Privacy!</strong></p><p><em>But what if they </em><strong><em>did </em></strong><em>enter their credit card! That’s a total invasion of privacy!</em></p><p>Is it?</p><p>Let’s take a look at what it looks like when someone <em>does</em> decide to enter their credit card information:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*YGYvSyB65_A3ex2xgc3bHA.png" /></figure><p>Well now, that’s not very exciting either, is it?</p><p>Where’s all the juicy credit card details and other personal information?!</p><p>Nowhere.</p><p>In fact, that information never leaves the user’s browser.</p><p>That’s because Tamboo (and other session recording tools) allow you to mask information you don’t want to have captured. In the case of Tamboo, sensitive information like credit cards, passwords, etc. are <em>automatically</em> masked while still in the user’s browser— and are never transmitted to or stored on Tamboo’s servers. If you have other information you don’t want captured, you can mask that too, and none of it will ever leave the user’s browser. And that’s not just limited to form fields. You can mask information displayed anywhere on a page, and even control which pages you want to enable recordings for.</p><p>(Most of) us session replay companies aren’t recklessly irresponsible when it comes to protecting sensitive user information. That’s <em>why</em> we have these features in place — to keep information that isn’t useful or relevant to helping businesses understand their user experience from getting captured or showing up in a recording in the first place.</p><p>And that’s also why we encourage companies to <em>thoroughly</em> <em>test</em> using our products on their development, test, or staging environments before they go live with it — to make sure that all of their bases are covered and there are no surprises.</p><p>Now, that being said, I will say that there <em>were</em> some irresponsible parties in some of these articles — on both sides of the aisle.</p><p><strong>You shouldn’t use session recording tools when you deal with highly personal or sensitive information.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*-CtuENNKCm_SgQMGoqVicA.jpeg" /><figcaption>There’s that whole “think before you act” thing…</figcaption></figure><p>Being the founder of a company, I care deeply about how that company is run and how its customers are served.</p><p>That’s why I make sure that <em>every</em> site that signs up with Tamboo is audited and reviewed to make sure that it’s a good fit for Tamboo.</p><p>Because of the nature of session recording tools, there are certain types of websites where using them is <strong>not a good idea.</strong></p><p>Yes, I’m telling you that — depending on the type of website you have — I don’t want your business.</p><p>In fact, I’ve turned away business from companies whose websites I didn’t want to have on the platform because I felt it was too much of a risk for everyone involved — namely healthcare-based businesses, businesses in finance, and even schools and educational institutions.</p><p>While I do this “sanity check”, it doesn’t appear that any of the companies mentioned in the articles did or do.</p><p>And that’s a problem.</p><p>Anyone in the healthcare industry in the US is familiar with HIPPA. It’s a set of laws that dictate how personal and medical information in the healthcare industry is stored as well as who can have access to that information.</p><p>The session replay companies mentioned in these articles — as well as the companies using these tools — should have <strong>both</strong> had some kind of internal review and approval process before any of these tools were implemented for these purposes. If they did, they would have caught the issue before it became one.</p><p>Because keep in mind, session recordings are just like any tool — they’re neither good nor bad.</p><p>It’s how they’re <em>used</em> that matters.</p><p>And in some of these cases, these tools just simply <em>shouldn’t </em>been used.</p><p>But let’s step back here for a minute and be honest with ourselves.</p><p>The <em>real</em> reason that these articles have caught everyone’s attention and have drawn so much negative press is because of the <em>frightening</em> revelation that (gasp!) companies are watching what we do on their websites.</p><p>But honestly, this is nothing new.</p><p>Amazon’s been (famously) doing this for <em>decades.</em></p><p>Recording what people do on a website is not a “new” thing — it’s just something that’s historically been incredibly cost prohibitive to do, meaning that only very big companies with very deep pockets could ever employ these types of tools. It’s only until recently that we’ve been able to commoditize this technology and make it more accessible (and affordable) for everyone else.</p><p>But really, the only reason that session replay companies are in the hot seat right now is because <strong>we</strong> <strong>advertise what we do. </strong>We <em>tell</em> people that we record user visits, that we track mouse movements, that we capture clicks, that we measure scrolling, that we record keystrokes. We’re open about what we do, because there are people who are looking to use those things to help their businesses.</p><p>But the truth is that <strong>any </strong>third party JavaScript or plugin that you install on your website can do <strong>these same exact things </strong>and just not tell you.</p><p>And not just that, there are actually <strong>many </strong>internet companies (that don’t “do” session replay) that as part of their businesses capture and store more information than session replay tools do— they’re just not hitting the headlines (yet).</p><p><strong>It’s not just us you need to be worried about.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*u0K4tg7DUPOuMaMCASXjdg.jpeg" /></figure><p>If you’ve been in digital marketing for any amount of time, you’re probably more than familiar with the “standard” tools at your disposal, such as email marketing automation, social media tools, retargeting, analytics, SEO tools, A/B testing tools, landing page builders, video analytics, marketing funnels, PPC targeting, etc. (the list goes on and on...)</p><p>[And just so you can play along at home, if you’re not in marketing, but are more in the operational side of the house, systems such as order fulfillment, HRMS, customer service/support, and ERPs might be something you’re more familiar with.]</p><p>One of the things that you might have noticed over the past few years is that more and more of these systems have gone “to the cloud”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*gbjMeNTU3jJdArGrh9hrMA.jpeg" /><figcaption>Ugh, these commercials made me visibly cringe…</figcaption></figure><p>Regardless of whether or not we’re talking email marketing automation, customer loyalty, payment processing, CRM, ERP, ecommerce, customer service, or any other kind of system that you use to help run your business, <strong>a lot </strong>of your customer information isn’t necessarily stored “on premise” anymore.</p><p>It’s in the cloud (yay, cloud!)</p><p>And that means that your customer information is “out there” and is potentially visible by non-employees of your company.</p><p>But in this day and age, that practice is pretty much accepted and doesn’t cause people to unnecessarly freak out anymore.</p><p>But when it comes to session replay, people seem to think:</p><ol><li>You’re spying on me and recording all of my personal information!</li><li>It feels “creepy” (Why are you watching me?! It can’t be for anything good!)</li></ol><p>And like I’ve pointed out, these concerns are mostly around the visual nature of session replay — they can literally <strong>see</strong> what’s been captured.</p><p>But what about all of the <strong>other</strong> cloud companies out there recording and storing your information when you visit or buy from an online business?</p><p>It might surprise you to learn that session replay tools are not used nearly as much as these other types of <em>very common </em>tools — and that these other tools often capture, store, structure, and associate <strong>much more</strong> personal information than what session replay tools do.</p><p>Let’s take email marketing automation for example.</p><p>Email marketing automation systems work by associating an email address with information about the person behind that email address (and can often perform reverse lookups to get actual names and other personal information from other data sources). They track what topics you’re interested in, what offers you’ve responded to, how much and how frequently you buy something, what you buy, <strong>and even track your behavior on websites to “lead score” you.</strong></p><p>They know what pages on a website you’ve visited, how much time you spent on those pages, what keywords they should tag you with based on the pages you visited, how much of a page you viewed, what answers you provided to form fields on a page, and much, much more, including your complete purchase history with that site.</p><p>All of that information gets captured and stored in the email marketing software company’s servers and databases.</p><p>So if you’ve ever given your email address to “get more information” about fixing your credit card debt, about how to lower your blood pressure, about how to make your marriage or relationship work, about how to quit a bad habit or a chemical dependency — <strong>all of that</strong> information is captured and stored and associated with your email address, your purchasing history, your website usage, and even your email habits — so that they can find ways to sell more of what they they sell to you. (And sell they will!)</p><p>A healthcare company that uses an email marketing automation tool that tracks a person’s interest in specific medical conditions so they can send special email offers or newsletters to them is just as “in the wrong” as if they were using a session recording tool to track users ordering a prescription for that medical condition. (And so they <strong>shouldn’t</strong> be using <strong>any</strong> of them!)</p><p>So I think we can agree that using these types of tools on a site with any kind of sensitive or highly personal information is <strong>generally</strong> <strong>a bad idea, especially if those tools are cloud-based.</strong></p><p>But let me ask just how bad any of this is to you if were to buy some dog treats from an online pet store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*trOIRZlXQdn_jQoVDqVIXw.jpeg" /></figure><p>So long as nobody’s looking at your credit card information, do you really care if they have your email address in their database associated with the fact that you like to buy chewy dog treats for a small breed dog? Does it creep you out if they know that you used one of their coupons? Does it scare you if you get an email from them encouraging you to buy another bag of dog treats with a 20% off coupon?</p><p>For 99% of people, none of this is creepy.</p><p>Because it’s normal.</p><p>They know that’s how online businesses work.</p><p>They’ve seen it, they’ve experienced it, and it’s expected.</p><p>Session replay tools are no different — it’s just that you can <strong>see</strong> what’s going on that tends to freak people out.</p><p>Does it really bug you if someone <strong>saw</strong> that you were looking at one doggy treat versus another?</p><p>Maybe it does. (Again, that whole <em>visual</em> aspect is where people tend to get hung up.)</p><p>But email marketing automation tools know the same thing — as do many other kinds of analytics tools. They know that you viewed that one doggy treat but chose to buy the other. Session replay tools simply help you <em>visualize </em>that information. But other tools actually <em>use</em> that information to try to get you to buy from them again through personalized email marketing campaigns designed to push all the right buying buttons.</p><p>When it comes down to it, session replay tools are “watching” the same things that email marketing automation tools are.</p><p>But instead of obsessively tracking every bit and detail and associating it with your email address so we can sell more stuff to you, we’re just grabbing what you <strong>saw</strong> and showing that to people who <strong>care what you did </strong>so that they can learn how to make their site better.</p><p>Nobody’s spying or using that information to try to directly sell anyone more of anything.</p><p>They’re trying to understand what worked well and what didn’t, so that they can make a better experience for everybody who uses their website or web application.</p><p>Aside from marketers, it’s mostly designers, user experience professionals, and developers who use session replay tools — to understand the user experience and find ways to make things easier and more enjoyable to use.</p><p>To make it less confusing. To make it less frustrating. To make it work more like the way that you <em>want</em> it to.</p><p>They’re not trying to sell to you. They’re trying to make it easier for you to figure out if you want to buy something — and to make it as easy as possible for you to make that purchase if that’s what you decide you want to do.</p><p>It truly is a win-win.</p><p>The websites and applications you use get easier to use, get you what you need faster, and become a more enjoyable experience altogether. (Remember — Amazon didn’t get as good as they got <em>without</em> using these kinds of tools.)</p><p>The businesses running websites don’t lose customers due to unknown user experience issues. As a result, they’re able to help more potential customers get what they want, which helps them reduce their marketing costs and become more efficient.</p><p>At least, I hope that’s the point of view that I’ve been able to show you with this article.</p><p>If you agree with me, please <strong>share</strong> this article with people who might have misconceptions or who might not fully understand what session replay is really about. And please don’t hesitate to <strong>reference</strong> this post if you come across an article that only gives a one-sided view of session replay. As marketers, as business owners, as product people, as UX professionals, and even as developers, it’s important that we help <strong>educate and inform</strong> people about these tools so that they understand how businesses use them to help improve their users’ day-to-day experiences.</p><p>🙏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fdcbbe6f33e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tamboo/are-session-replay-tools-really-as-creepy-as-everyones-saying-5fdcbbe6f33e">Are Session Replay Tools Really As Creepy As Everyone’s Saying?</a> was originally published in <a href="https://medium.com/tamboo">Tamboo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unconventional Startup Architecture — For The Win!]]></title>
            <link>https://ehandbook.com/unconventional-startup-architecture-for-the-win-89bc2571eea4?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/89bc2571eea4</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Thu, 16 Nov 2017 14:16:00 GMT</pubDate>
            <atom:updated>2017-11-16T14:16:00.768Z</atom:updated>
            <content:encoded><![CDATA[<p>If you didn’t know, we do things a bit differently here in Startup Land, including the way we sling code. Here’s where you’ve probably been going wrong (and what to do about it).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4F-ei533DUyeX7T4TjRpNQ.jpeg" /><figcaption>Fun fact: The shiny lights help me crush it that much harder.</figcaption></figure><p><strong>A word of warning:</strong> What follows may not be for you.</p><p>If you find completeness, clarity, and a sense of purpose in designing elegant applications featuring domain-driven design, layers of abstraction, IoC containers, dependency injection, RESTful APIs, mock objects, and automated build tools with CI and comprehensive automated test coverage, you may want to just turn around and slowly close this door behind you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Na8jUhscRY-HdmbeHnf6Iw.gif" /><figcaption>Go ahead, it’s okay. I understand.</figcaption></figure><p>But if you want to learn why you’ve never been able to ship any of the “startup” projects you’ve worked on tirelessly for months or even years at a time (and which are still sitting sad and alone in some random Git repo you created for them, never seeing the beautiful light of day), then come on in and grab a chair.</p><p>Because I’m going to share some of the unconventional startup architecture tips and tricks I’ve learned building (and shipping!) bootstrapped startups all by my lonesome, including the things I’ve learned building and growing Tamboo — <a href="https://gettamboo.com/">a session recording and heat map tool for websites</a> — my most technically ambitious business venture to date.</p><p><strong>I Used To Be A Solutions Architect. Then I Started A Software Business.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LTg3z8DXEuzawa8LzVzd_A.jpeg" /><figcaption>I used to be that random stock photo startup hipster whiteboarding away just like you!</figcaption></figure><p>Ahhh. Memories.</p><p>The smell of dry erase markers on a whiteboard as I stand in front of a crowd of my colleagues and teammates, piecing together the techncial puzzles that have eluded them for years.</p><p>The feel of the Starbucks coffee cup in my hand as I take caffeine-laced swigs in between fielding questions from those gathered here.</p><p>The beautiful projection of my Visio masterpieces illuminating the wall beside me for all to see.</p><p>The smug feeling of knowing that I’ve found every conceivable fault, exception, bottleneck, timing issue, race condition, gotcha, hiccup — even gremlin — in the system that we’re now discussing — and that I’ve planned for <em>all</em> of them in my design.</p><p>And not just that — but my design is <em>beautiful</em>. Dead sexy even. And I know it.</p><p>Elegant yet unintuitive. Deceivingly simple yet tough as nails. The kind of thing that makes perfect sense when you <em>see it</em> — but something you never would have thought to have put together yourself given the pieces in front of you.</p><p>I was at the top of my game, and I loved everything about it.</p><p>I was a certified <em>whiteboard connoisseur —</em> I obsessed over the tactile feel and visual aesthetic of the brands and styles of the available dry erase markers on the market. I knew which color and tip size combinations worked most effectively together to best capture my game-changing insights and ideas — while still dazzling the people seated far across the room.</p><p>I had built out a (very expensive) private library of the very best technology and architecture books on the market — and had read every one of them. More than once in most cases. <a href="https://www.amazon.com/Patterns-Enterprise-Application-Architecture-Martin/dp/0321127420/">The tomes</a> with <a href="https://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612/">the fancy ribbons in them</a> were <a href="https://www.amazon.com/Software-Architecture-Practice-3rd-Engineering/dp/0321815734/">my personal favorites to showcase</a>. The more esoteric (and expensive), the better.</p><p>The <a href="https://en.wikipedia.org/wiki/ISO/IEC_9126">glorious “ilities”</a> were my philosophy and religion.</p><p>I ruthlessly chased down and consumed every shiny red ball that crossed my voracious path (including some of those devilishly slippery tricksters — Scala, Haskell, Eiffel, Clojure, and friends).</p><p>All in all, I was what you might call “a developer’s developer”.</p><p>So in my mind, it made “perfect sense” that I should fully leverage my impressive skillset and start a software-based business. After all, I should be able to make <em>way more</em> running my own company than working for someone else, right?</p><p><strong>This Was Supposed To Be Easy.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*31lTAMmeMaWveOIKiV2mBw.jpeg" /><figcaption>It’s almost done! I swear it! I just need to refactor the database *one more time* to better handle scale under load and then I need to finish rewriting the frontend to use Vue instead of React— and then I think it’ll be ready to do a closed beta with that one guy that signed up for my launch list two years ago!</figcaption></figure><p>Things didn’t go exactly as planned, to say the least.</p><p>And they didn’t go as quickly as I expected, either.</p><p>(But what’s a lost decade give or take a few years between good friends, right?)</p><p>Although <a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1">I learned a lot about building startups</a> during that time, one of the biggest traps that I kept falling into (and one that I see fellow developers languishing in <em>all the time</em>) is <strong>treating a startup’s codebase and architecture like it’s a doctoral thesis.</strong></p><p>Meaning, there is this tendency and this desire to make your startup’s technology <strong>awesome </strong>and<strong> ridiculously impressive</strong>, using only the latest and greatest techniques, approaches, tools, languages, and frameworks.</p><p>For some of us, our <em>startup</em> somehow becomes a reflection of <em>ourselves.</em></p><p>It becomes in our mind the <em>realization</em> of all of our acquired knowledge and skills.</p><p>It becomes the <em>culmination </em>of our life’s work.</p><p>We want it to be <em>perfect — </em>to be our <em>pièce de résistance.</em></p><p>Because for most of us, that’s why we wanted to build a startup in the first place — to build, work on, and live off of something that embodies the ellusive technical purity we’ve chased the majority of our careers but never found (but that we <em>know</em> must exist!)</p><p>And because we somehow entangle our own identities with the bits and bytes and function calls of our codebases — we are almost always dissatisfied with the end result — and do everything in our power to avoid “shipping it” into the world, where all can see our faults.</p><p>Of course, this is in stark contrast to our ability to ship things at our jobs.</p><p>If we didn’t have the working history to believe that we could code and ship something (often in just a weekend!) we probably would never have entertained this idea in the first place.</p><p>So why is that?</p><p>Why can we ship it like it’s nobody’s business at work, but when it comes time to ship our own “life’s work” as it were — the thing that should buy us <em>freedom</em> and make us <em>proud</em> of ourselves— <strong>we freeze up and find every reason to tinker, prod, poke (and even shelve) our projects instead of shipping them and going live?</strong></p><p><strong>Stop Being So Stupidly Serious. (Or Seriously Stupid.)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QdkV8Fx04aq4UxeAN29G0w.jpeg" /><figcaption>You’re not a business yet. So stop trying to act like one. And even then, just don’t.</figcaption></figure><p>Before we delve into the technical details about how you should probably being going about architecting and designing your startup, we first need to talk about your attitude.</p><p>You see, us developers tend to be pretty <em>serious</em> about, well, development.</p><p>Not to mention opinionated.</p><p>(You don’t say, right?)</p><p>But here’s the thing you need to realize — all of those opinions, preferences, and “best practices” you’ve committed to memory and tattooed on your soul like a set of holy mantras handed down from on high (Don’t Repeat Yourself! Single Points of Authority! Separation of Concerns! SOLID!) were likely developed and employed (religiously at that) in a <em>professional setting.</em></p><p>And the first thing that you’ll find in building a startup is that <strong>professionalism is for amateurs.</strong></p><p>When you write code <em>professionally</em> for an <em>employer </em>for <em>a paycheck</em>, you follow one set of rules (the ones you already know and love).</p><p>When you write code for <em>a speculative venture </em>on <em>your own time </em>with <em>no immediate path to revenue</em>, you <strong>need</strong> to follow a completely different set of rules (or you’ll never cross the finish line).</p><p>That’s not to say that you <em>shouldn’t </em>do those things at your day job — you very well should! Because that’s what your employer is <em>paying </em>you for. To write clean, maintainable code. To write documentation. To create unit and integration tests. To use version control and build automation. Because they’re paying for you to <em>contribute</em> to a system that <strong>must work reliably for their users and must be able to run after you quit or get fired.</strong></p><p>But here’s the thing.</p><p><strong>Your employer has stable revenue, an established position in the market, and most of all — actual users using their applications— and you don’t.</strong></p><p>All of these “concerns” that us software developers obsess over only matter when you have code that is actually used by end users and that is worth the time and investment of making it more stable, more reliable, more maintainable, and more fault tolerant.</p><p>No users? No reason to do those things.</p><p>Those are strategies used to help manage an application with a growing codebase, a growing footprint, a growing user base, a growing everything. Those are <strong>not</strong> strategies that will help get you off the ground. <strong>Because they’re not meant to.</strong></p><p>It’s <strong>asinine</strong><em> </em>to be concerned about growth when you have zero traction.</p><p>That’s like spending years trying to figure out the gory mundane details about how and where you’ll manage all the millions of dollars you have yet to ever earn (and trying to learn all of the tax implications of those moves as well!)</p><p>That’s the first part.</p><p>The second part is this odd emotional attachment people have about their “personal projects”.</p><p>I get it, you’re proud of the work you do.</p><p>And there’s nothing wrong with that.</p><p>But what <em>is</em> wrong is when you treat “your” code any differently than you would code that you would write for someone else.</p><p>Just because it’s “your” code does not mean that it should be any better than the code you get paid to write for a living.</p><p>If the code you write for <em>them</em> is good enough and “just works” — then why can’t you just do the same thing for yourself and stop over engineering everything?</p><p>It’s <em>because</em> you view it as “your” code that you expect <em>perfection.</em></p><p>Because hey, you’re going to be making a living off of this thing, right? So it better rock!</p><p>And that’s the issue.</p><p>When you think of a problem, goal, or situation a certain way, chances are that’s how you’re going to go about tackling it (rather than being open to alternate views and options).</p><p>In order to think <em>clearly</em> about your code — and to make sure you do things that make <em>business sense — </em>you need to create some <strong>emotional distance.</strong></p><p>So how do you do that?</p><p>Simple.</p><p>You <strong>reframe</strong> how you look at it.</p><p>Rather than thinking that you’re going to be building something “for yourself”, <em>convince</em> yourself that you’re going to be building something “for a client” or “for your boss”.</p><p>And your client/boss has a <strong>real tight</strong> deadline — and <strong>an even smaller </strong>budget.</p><p>But they <strong>have to have something for their users</strong> — and they expect you to deliver it within those parameters.</p><p>Changes the way you look at things, doesn’t it?</p><p>But that’s exactly what you have to do.</p><p>You have to treat yourself like a cheap-ass client/boss who wants something functional ASAP.</p><p>And then you have to go and do it.</p><p><strong>I’m Not Talking This.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDyvk2dPK2n319OmGSQ-7A.jpeg" /><figcaption>Your desk might look like this. But your app better not.</figcaption></figure><p>Now, let me be clear that we’re not going to be throwing shit against the wall just to see what sticks. (It turns out shit does not in fact stick very well on walls. At all. Just trust me on this.)</p><p>What I <strong>am</strong> talking about is designing and working <em>within constraints</em>.</p><p>Constraints force you to focus on what’s most important for the task at hand.</p><p>When you can do anything and everything — chances are you’ll probably try to (or be paralyzed by all the options available).</p><p>When you’re limited to doing one — and only one thing — then you can devote your entire focus to doing that one thing, and doing it well.</p><p>It’s more like taking a zen aesthetics approach to your architecture and design: It’s not just what’s <em>there</em> — it’s also what’s <em>not there</em> that makes it beautiful and elegant.</p><p>Using this approach, your goal is to distill all of the crazy ideas and “what-ifs” you have running around in your head down to the simplest possible solution (yet no simpler!) that puts the most emphasis on the most important aspects of your application.</p><p>Your focus should be on executing your application’s <strong>critical path</strong> ridiculously well while balancing the constraints you’ve been tasked with in order to extract the most ROI (Return On Investment) possible from the effort you’ve put in on behalf of your overbearing “client/boss”.</p><p><strong>Let’s Break Some Bogus Misconceptions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*gt8yz2FJyqZyVIqyJarnIw.jpeg" /><figcaption>Yes way, dude. Yes way.</figcaption></figure><p>Okay, so if you’re still with me, it’s time we let the dogs out and got this party started.</p><p>I’m going to start by reminding you what <strong>architecture</strong> and <strong>design</strong> really are, because it’s critical we be on the same page for the sake of this discussion:</p><blockquote><strong>Architecture</strong> is concerned with the creation, identification, classification, description, and documentation of the structures which constitute a system — be it software, hardware, or otherwise.</blockquote><blockquote><strong>Design </strong>is concerned with the development of a specification for a solution which achieves some specific goal while adhering to certain criteria and constraints.</blockquote><p>Yep, that’s it kids.</p><p>It really is that simple.</p><p>Now, the thing we need to pay attention to here are some keywords from each of these definitions — namely “structures”, “goals”, and “criteria and constraints”.</p><p>Because these are the parts that you’ve been screwing up.</p><p>The sad sorry truth is that most startups are just glorified CRUD (Create, Read, Update, Delete) apps — much like you probably build at your day job. Sure, we sprinkle a healthy pinch of unicorn droppings on them for good effect, but it doesn’t change the fact that it’s just CRUD under the hood.</p><p>The structures that constitute and support a CRUD application are well-known to just about anyone working as a professional software developer nowadays. At least until they try to build a startup. Then they just get cray with whatever hot new technology or technique they can get their hands on.</p><p>So the first thing you need to admit to yourself is that you’re not doing anything earth-shattering with your codebase. It’s a CRUD app in some way. Treat it as such. Stop trying to be fancy about it.</p><p>If you know how to MVC and ORM in some language and framework, just do it “the standard way” you’d do it at work and be done with it.</p><p>Now is <strong>not</strong> the time to play with new technology.</p><p>I know everyone thinks “Oh, I’ll build my new startup in this new framework because it’s so damned cool and at least I’ll get to learn that framework if my startup doesn’t work out.”</p><p>Yeah, and that’s <strong>exactly why </strong>your startup will not work out.</p><p>Because you put technology before business, when <strong>it must</strong> be the other way around.</p><p>You should <strong>know</strong> the technology stack you use to build your startup. In and out. You should use it every day. It should come as — and have no — surprises for you. It should be as boring and as familiar as that ragged college t-shirt you wear to bed every night.</p><p>Wear it. Own it. And move on.</p><p>Because if you don’t understand a language or a framework fully, <strong>there is no way you can design or architect for it efficiently or effectively. </strong>You put your startup’s entire future at risk when you violate this principle.</p><p>And now is <strong>not </strong>the time to learn a <em>new </em>language or framework. Do that on your boss’s time — not on your own.</p><p>Okay, so where was I?</p><p>Oh, yeah.</p><p>You want to pick whatever technology stack you already know.</p><blockquote><strong>Clifford’s Rule</strong> states: Only build your startup using a technology that you can code in without having to Google for answers or copy and paste from StackOverflow to make work.</blockquote><p>Yes, relational databases are boring. Use them anyways.</p><p>Yes, MVC is so 2008. Suck it up and use it.</p><p>Of course REST APIs are hot. Why do you need one?</p><p>SPAs are sexy, sure. But do you have experience building one?</p><p>React/Vue/Meteor are all everyone is talking about. Let them talk.</p><p>Been wanting to try out Sass? Use CSS.</p><p>That’s the first part.</p><p>The second part has to do with <strong>which</strong> <strong>structures </strong>you implement — based on <strong>known</strong> criteria and constraints.</p><p>Since you’re a startup, <strong>you have no operational history </strong>from which to make any kind of predictions or judgments. Very much unlike your employer, who <strong>does.</strong></p><p>When they say that they’re going to build a portal for their customers — <strong>they know how many customers they have that will potentially be using that thing.</strong></p><p><strong>You don’t.</strong></p><p>All of the design decisions that you make, all of the architectural considerations that you make in that scenario are <strong>based on probabilistic knowledge.</strong></p><p>You <strong>know</strong> that if your employer has 1,000 customers, that you’re (probably) going to have to build a system that can <strong>support </strong>1,000 users — and that you’re going to need all of the things that go into being able to do just that.</p><p>(Rocket surgery, I know.)</p><p>You’re probably going to need an administrative interface for your CSR team to help with support customer inquiries.</p><p>You’re probably going to need to have some kind of HA in place to handle the load of 1,000 concurrents, not to mention needing to be able to do updates to the system without affecting any of your active end users.</p><p>Because you’re going to have all of those concurrent reads, you’re going to need to have some read-only slave replicas — if not some cache stores — to speed things up most likely.</p><p>You’re probably going to need to have a DR in place in case anything goes wrong, as well as a comprehensive on-site and off-site backup plan.</p><p>Oh! And of <em>course</em> you’re going to have to have all of these layers of abstraction so that you and your team can mock anything and everything for your comprehensive suite of unit and integration tests, all while allowing you to swap out database backends (I’m sorry — <em>persistence providers</em>) at will!</p><p>And since it’s not just <strong>you</strong> coding the whole system, you’re going to need to have version control in place hooked into a continuous integration build platform that does automated deployments based on red/green test results so that you can do hands-off rolling deployments to this thing on a continual basis.</p><p>And let’s not forget the user management, email alerts, security, CMS, and information architecture while we’re at it!</p><p>Yes, all of that <strong>might</strong> make sense if your employer were to throw such a tasty task on your cubicle desktop.</p><p>But in Startup Land, ain’t nobody got time for that shit.</p><p><strong>Because you don’t have any users to worry about yet!</strong></p><p><strong>Always Be Overachieving?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*RRfGfewh3vKISPSz7fRAiw.jpeg" /><figcaption>Anything you do for a user you don’t have yet makes you an overachiever.</figcaption></figure><p>This is where <strong>everyone</strong><em> </em>goes wrong.</p><p>They forget about the <strong>goals</strong> and the <strong>criteria and constraints</strong> they need to be concerned about (and working within) when building their startup.</p><p>Goals?</p><p>The goals are easy enough to describe:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*712OnCLhKUpN2dG5wwSClg.png" /><figcaption>Easy enough. Let’s move on.</figcaption></figure><p>Because everyone gets so focused on their <em>personal</em> goals — and not the goals of the system — they very often completely forget the criteria and the constraints they should be thinking of.</p><p>Just a refresher: You architect, design, and build systems <strong>based on who your users are, what they need to achieve with your system, and how many of them you’re going to have.</strong></p><p>You don’t know who your users are.</p><p>You have no idea what they need to achieve.</p><p>And you have none of them.</p><p>So why spend <strong>all this time</strong> architecting, designing, and building all of these gory gears and springs and boxes for something that <strong>no one will probably ever use?! </strong>(Not being a cynic, just applying probabilisitic reasoning here.)</p><p>The bottom line is that you <strong>shouldn’t.</strong></p><p>And that you <strong>don’t need to.</strong></p><p>And here’s why.</p><p>How many users do you think you’ll get in your first month of going live?</p><p>Have you ever even <em>thought</em> about that?</p><p>And if so, have you ever come up with an <em>actual</em> number?</p><p>(Hint, hint: This is one of those “criteria and constraints” I’ve been talking about…)</p><p>If you have, kudos to you!</p><p>But it’s probably still too high.</p><p>I’m going to take whatever number you’ve come up with in your head and I’m going to suggest you make it “100” instead.</p><p>Yep, 100 <em>trial </em>users in your first month (if you’re <strong><em>super</em></strong><em> </em>lucky at that, too).</p><p>50% or more of those users will sign up (for free, of course), use your app maybe once, and then never sign in again.</p><p>Of those remaining 50 users, about 25–35 of them are going to stay active for a week or so, and, after throwing a number of ludicrous support and feature requests at you, will go dark and you’ll never hear from them again. The other 15–25 users will probably stick around long enough to (conveniently) churn out right around the time their free trial runs out.</p><p>Maybe you’ll get lucky and you’ll keep 1 or 2 of them for another month or so and pick up a tidy $29 or $49 in MRR.</p><p>But that’s reality (and one you better be prepared for).</p><p>And <em>how much time</em> are each of those users going to be spending in your app — <em>actively</em>?</p><p>(Hint, hint: That’s another one of those tricky “criteria and constraints” I mentioned…)</p><p>What? Maybe 10 minutes a week — <em>each?</em></p><p>So let’s use that “sticky” 15–25 user watermark (since those freeloaders are up and gone before the morning comes anyways), and assume each of them is going to spend 10 minute a week in your app.</p><p>What <em>exactly </em>would you need to have in place to support them?</p><p>Not much, right?</p><p>A pretty basic CRUD app running on a boringly predictible framework like Ruby on Rails with a relational backend like MySQL all hosted on a box with a couple gigs of RAM and a core or two of modest size should pretty much do the trick, no?</p><p>You’re not going to really have to worry much about concurrency issues with 15–25 users spreading load out over your app at 10 minutes a week a piece.</p><p>Chances are your average concurrent load will be <strong>zero.</strong></p><p>So our proposed system architecture is actually probably <strong>oversized</strong> for your current (and near future) load requirements.</p><p>You’re welcome.</p><p>You see, us developers — given the <em>expectations </em>that we’ve developed while working for <em>established</em> companies — often (ridiculously) overestimate how many users we’re going to get. And so we (ridiculously) overestimate the importance and scale of everything else.</p><p>You don’t need to start “big”.</p><p>Because you probably won’t.</p><p>Start small.</p><p>And then grow it organically.</p><p>And <strong>never</strong> build more than you have to for what you hope to accomplish in the next month or two.</p><p><strong>Tips and Tricks…</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*KNNFpaMIeuTxqIDvD92IGQ.jpeg" /><figcaption>Oh, we’re not done here yet.</figcaption></figure><p>Okay, so you came all this way. The least I can do is let you leave with a lollipop or two. So here are some additional startup build-out tips and tricks you might want to take to heart as you consider <em>your</em> startup’s architecture and design:</p><ul><li>Focus on building a business — not a “startup”.</li><li>Design the most basic app you can think of. Then find ways to make it even simpler. Remember to keep the enterprise out of the startup.</li><li>Stick with technologies you know and understand. This is not “experimentation time”. The more boring, the better.</li><li>Don’t plan for 100 users — plan for 10. When you get 10 users, plan for 20. When you get 20, plan for 40. And so on.</li><li>Avoid excessive “layers” in your code. Layers take time to write, and they add more moving parts to your codebase — with no value to your end users. Keep it simple, stupid. Stupidly simple.</li><li>Avoid unit tests until absolutely necessary. Test your critical paths if it makes you feel any better, but know you’re testing code for users that don’t exist yet for a business that hasn’t made a dollar yet.</li><li>Documentation is for teams that don’t know how to talk to each other. There’s no sense in writing any at this stage.</li><li>Comments are meant to help you understand what the hell you were thinking when you were either too drunk or too tired to know what you were doing. Use them if you need them. Or just learn how to read code like the rest of us.</li><li>Add logging for things that matter. Ignore things that don’t.</li><li>Yes, you should use version control. Use whatever you know. There is no shame in Subversion if that’s what you’re familiar with. (Besides, nobody really understands how to use Git anyways.)</li><li>Use global exception handlers to catch and report exceptions that occur in your code. Just email them to yourself for now. Once you have actual users than can produce actual errors, then worry about what comes next.</li><li>You don’t need an administrative interface to start out. Hack records in the database by hand until it’s too painful to do otherwise.</li><li>If you’re going to offer a free trial for new users, you don’t need to have payment processing in place until their trial runs out and they’re ready to convert. Either process your first payments manually or wait until then to build out your payment processing integration.</li><li>You don’t need to implement payment processing webhooks out the gate. Just manage events by hand in both systems until you can’t take it anymore.</li><li>Even after that, you don’t need to have self-service account mangement for your users. Just have them email you if they want to change their account or cancel their plan and then just do it manually behind the scenes. Do this until the support burden breaks you.</li><li>Plan for scaling vertically — and then do that until you can’t do it anymore. Avoid premature horizontal scaling. (Vertical scaling = adding resources (memory, processor, disk, etc.) to a machine to handle load. Horizontal scaling = adding additional machines to handle load.)</li><li>Start with a monolith. Deploy your DB and your app server on the same box. Worry about splitting them out when your DB becomes an unwieldy bottleneck that needs its own space.</li><li>Make it as easy as possible to deploy changes to your code and your database without going overboard. CI and build automation is probably overkill if you’re not already an expert in it. Don’t waste your time, just deploy like you would at work. Most MVC/ORM frameworks come with database migrations. Use them. Make it as painless as possible to Always Be Shipping.</li><li>Again — we’re not talking about writing shitty code here. We’re talking about being <em>realistic</em> about what we need to be focused on. You still need to bring the best user experience you can, and it needs to work ridiculously well for your users. Don’t confuse what I’m advocating with “hacking” stuff together (although admittedly you might have to do that from time to time).</li><li>Remember — writing code that never gets used by an end user is the saddest thing you can do as a developer. Don’t be a sad developer. Embrace your criteria and constraints and ship something. Anything.</li><li>And don’t forget — your users will never see your code. Only you will. So stop trying to impress yourself.</li></ul><p><strong>When can I see you again?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*6eVhPX6Xkxzl9hW6IaTayQ.jpeg" /></figure><p>If you enjoyed our special time together as much as I did, you should give me a follow on <a href="https://medium.com/@cliffordoravec">Medium</a> or <a href="https://twitter.com/cliffordoravec">Twitter</a> at @cliffordoravec. (I promise I’ll call!)</p><p>And if you’re hungry for more startup truth sandwiches like the one you just finished, you might want to check out my epic Medium series about bootstrapping a SaaS startup from scratch on your own:</p><p><a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1">The Epic Guide to Bootstrapping a SaaS Startup from Scratch — By Yourself (Part 1)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89bc2571eea4" width="1" height="1" alt=""><hr><p><a href="https://ehandbook.com/unconventional-startup-architecture-for-the-win-89bc2571eea4">Unconventional Startup Architecture — For The Win!</a> was originally published in <a href="https://ehandbook.com/">Entrepreneurship Handbook</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dark Times At Tamboo]]></title>
            <link>https://medium.com/tamboo/dark-times-at-tamboo-7c25c9644e44?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c25c9644e44</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Wed, 15 Nov 2017 14:37:23 GMT</pubDate>
            <atom:updated>2017-11-15T14:37:23.933Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M6XDzf6iuQ8oWdXciKxGyA.jpeg" /></figure><p>I’ll be honest — It’s been a dark couple of months at Tamboo.</p><p>And I’m afraid things just got even darker.</p><p>I’m sure I’m not alone in this.</p><p>After all, this time of year is always rather “dark”.</p><p>The skeletal fingers of trees once adorned with lush summer leaves tear the fabric of the cold grey sky as Halloween marks the death of summer and the beginning of days where darkness falls before dinner time.</p><p>But once your eyes learn to adjust to the dying of the light, there is often hidden beauty revealed.</p><p>It’s through this seasonal transformation, through this shift to darkness, that I found inspiration…</p><p>For a really bad piece of click bait.</p><p>(Yeah. I just did that. Sorry/not sorry 😜)</p><p>I just wanted to show you the hot new Tamboo dark theme — and I couldn’t help myself from passing on a good play on words 🙃</p><p>(I know, I know…)</p><p>But since you’re here!</p><p>You might be interested in checking out Tamboo’s hot new threads, just in time for the autumn season:</p><p><strong>Funnels</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*47AjGXT9g-tBIskgLfHp4g.png" /></figure><p>The new theme gives funnels more “pop” with a higher color contrast. Mini-funnels (which show how specific traffic sources perform) stand out more and are easier to visually scan for telling shapes and patterns. 👀</p><p><strong>Session Recordings</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cT7o9xvtkiUs34ExTTrGsg.png" /></figure><p>Tamboo’s <a href="https://gettamboo.com/">session recordings</a> are surprisingly much easier on the eyes with the new theme. Many professional video editing tools use a dark color scheme for this very reason — to help reduce eye strain. It makes the whole visitor recording experience feel more like you’re watching movies in a dark room or a home movie theatre. A word of caution — when you sit down to watch recordings of your website visitors with the new dark theme, you might be tempted to grab some popcorn (at least I was!) 🍿</p><p><strong>Heat Maps</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SfzxPEsxRHT-msYnNXro-g.png" /></figure><p>Just like their session recording counterparts, Tamboo’s heat maps feel much easier on the eyes with the new dark theme as well. Not only that, but the higher contrast between the dark theme and the highlighted activities regions makes it even easier to see who clicked (or moved their mouse) where. 🕶</p><p><strong>Analytics</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MJQZG25q7nssmH4qR6Pm-Q.png" /></figure><p>Even Tamboo’s analytics look better dressed in black! 📈</p><p><strong>Plus a Hot New Logo!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*262bvLt-uiTRu7TaDbRlBg.png" /></figure><p>And if that wasn’t enough, Tamboo is now sporting a hot new logo! After all, if you’re going to “embrace the dark side”, you might as well go full-out, right?</p><p><strong>You Asked For It — Trials Are Back!</strong></p><p>What good is it to get dressed to the 9’s for a night out on the town and <em>not </em>want to show it off to everyone you meet?</p><p>That’s why, after much popular demand, trials are back at Tamboo!</p><p>You can now <a href="https://gettamboo.com/">try Tamboo out on your website</a> — free for 14 days!</p><p>If you’ve been wanting to see what Tamboo’s session recordings, heatmaps, or funnels can do for you and your website (and I don’t know, maybe experience the new dark theme too? 😉), now’s the perfect time to find out.</p><p>See you there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c25c9644e44" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tamboo/dark-times-at-tamboo-7c25c9644e44">Dark Times At Tamboo</a> was originally published in <a href="https://medium.com/tamboo">Tamboo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real-World Startup Sales and Marketing for the Lost and the Clueless (Part 5 of The Epic Guide to…]]></title>
            <link>https://medium.com/tamboo/real-world-startup-sales-and-marketing-for-the-lost-and-the-clueless-part-5-of-the-epic-guide-to-87db07b436f5?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/87db07b436f5</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Tue, 24 Oct 2017 05:55:59 GMT</pubDate>
            <atom:updated>2017-10-24T13:57:09.576Z</atom:updated>
            <content:encoded><![CDATA[<h3>Real-World Startup Sales and Marketing for the Lost and the Clueless (Part 5 of The Epic Guide to Bootstrapping)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*2UPKxpkL2jWHGTna5RAfuw.jpeg" /><figcaption>The customers are *on* the internet? It’s so simple!</figcaption></figure><p>Or — “How to Get Real Traffic and Real Customers in Just 1 Hour a Day!”</p><p>Wow, it’s been a while!</p><p>I know, I know!</p><p>In fact, it’s been <em>months</em> since the last installation of <em>The Epic Guide.</em></p><p>All I can say is that I certainly hope that you’re all happy with yourselves.</p><p>It’s because of all of you super fans of <em>The Epic Guide</em> that I’ve had to basically go into hiding all summer long to focus on <a href="https://cliffordoravec.com/the-epic-guide-to-bootstrapping-a-startup"><strong>writing this damned book</strong></a> — while still <a href="https://gettamboo.com/"><strong>running and growing Tamboo</strong></a> on top of it.</p><p>In the process of being around-the-clock heads down, I’ve grown out a mean Thor-inspired hair style and aesthetic (not to mention a growing case of agoraphobia) that I think would make even Howard Hughes himself envious and proud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*QLaREjXuVGduVnvdwryCnQ.jpeg" /><figcaption>Write a book they said! It’ll be “good for you” and “fun” they said!</figcaption></figure><p>One thing of note that was actually pretty super fun is that <a href="https://www.indiehackers.com/podcast/009-clifford-oravec-of-tamboo">I had a chat with the super awesome Courtland Allen<strong> on the kick-ass IndieHackers podcast.</strong></a><strong> </strong>If you’re not familiar with <a href="https://www.indiehackers.com/">Indie Hackers</a> or <a href="https://medium.com/u/35d2978e0b2f">Courtland Allen</a>, you <strong>need</strong> to check them both out (and follow them!).</p><p>But enough about me!</p><p>Let’s have some <em>more</em> “fun” and pick up where we left off in <a href="https://medium.com/@cliffordoravec/ewww-your-startup-funnel-is-leaking-all-over-me-part-4-of-the-epic-guide-to-bootstrapping-d08e0db6b167">Part 4 of The Epic Guide</a> [If this is your first foray with <em>The Epic Guide</em>, you may want to start with <a href="https://medium.com/@cliffordoravec/the-epic-guide-to-bootstrapping-a-saas-startup-from-scratch-by-yourself-part-1-4d834e1df8c1#.uut3kmbyv">Part 1</a> and work your way back here — after all, it’s an ongoing <em>epic</em>…]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*6HcEDTfiMzvbul-j2EfB0Q.jpeg" /><figcaption>Look, see this? That’s quit your job money. $10k MRR. Might wanna hang onto that one.</figcaption></figure><p><strong>Stop pretending that whatever you’re doing is somehow going to “make you money”.</strong></p><p>If you haven’t been making mini-fuck you money off of your MVP yet, it might be time to step back and <em>think</em> about what it is that you <em>have</em> been doing. Because one thing’s for certain — if you keep doing whatever it is you <em>are</em> doing — you’re just going to get more of the same “results”.</p><p>Let me see if I can guess what’s been going on here.</p><p>You’re probably in one of two camps at this point:</p><ol><li><strong>You’ve done absolutely nothing of any real or substantial value when it comes to marketing or selling your startup.</strong> Maybe you tried “marketing” your startup on Reddit once or twice, sure. But since then? Not so much. And cold emails? Maybe you <em>thought</em> of sending that one that one time, but you kinda just never hit send and fucked around reading up on blockchain and cryptocurrencies instead (which gave you this <strong>great idea</strong> for a brand new startup, by the way!)</li><li><strong>You’ve been going “transparent” with your startup and writing blog posts about all of the geeky things you’ve been wasting your time on.</strong> People seem to <em>love</em> your posts about how you’re still at $0 MRR and how “hard it is” to actually build a startup. You’ve been getting some pretty good “traction” on Twitter and Hacker Noon with your content, but you’re not really reaching anyone in your target market (or on the off chance that you are, they’re not forking over their credit card, so it’s more or less the same). But hey! You’re “building an audience”, right?!</li></ol><p>What’s <strong>downright dangerous</strong> about finding yourself bunked up in either of these two camps is that — even though it <em>feels</em> like you’re doing something — <strong>you’re just busying yourself with bullshit.</strong></p><p>If there’s one thing you take away from this, make sure it’s this:</p><blockquote>If you aren’t reaching and resonating with actual people in your actual target market, you’re just “playing startup”.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/1*GxJIAqhCXev0UMrYQjzg3g.jpeg" /><figcaption>What the hell are we doing here? We gotta get out of this town!</figcaption></figure><p><strong>To a place where the beer flows like wine.</strong></p><p>I’m going to let you in on a little secret here.</p><p>You want to know the <em>real</em> reason you’re not getting anywhere?</p><p>It’s because your <em>goals</em> are all wrong.</p><p>No, that John Denver was not full of shit. You’ve just been looking in the wrong places.</p><p>You see, if you’re like most first-time founders, you’ve probably set some (“reasonably” sounding) goals for yourself like this:</p><ol><li>Get 100 visitors a day to my website.</li><li>Add 10 new people to my newsletter weekly.</li><li>Get 1 new trial signup a day.</li></ol><p>(and so on)</p><p>The problem with these “goals” — and the reason that you’re getting your ass kicked — is that they are not, in fact, <em>goals</em>.</p><p><strong>You</strong> <strong>cannot</strong> get 100 visitors a day to your website.</p><p><strong>You cannot</strong> get 10 new people to sign up to your newsletter a day.</p><p><strong>You cannot </strong>get 1 new trial signup a day.</p><p>Because <strong>those are not goals.</strong></p><p>Those are <strong>events</strong> that are based on <strong>what other people <em>choose</em> to do</strong>.</p><p>And you have <strong>zero</strong> control over them.</p><p>So for you “set a goal” of getting 100 visitors a day — you might as well “set a goal” of winning the lottery (or finding a briefcase full of money).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*2kylvvfoXilA-KqTsKv3lA.jpeg" /><figcaption>But I have “traffic goals” and “MRR targets” to hit!!!</figcaption></figure><p>The first step on your way out of this is to realize that <strong>you can only set goals for things you have direct control over.</strong></p><p>So let’s fix this up a bit. Let’s say that we have goals like the following:</p><ol><li>Find 10 potential customers a day and send cold emails to each of them.</li><li>Write at least 1 piece of content a day and promote it in at least 3 places.</li><li>Promote my startup in at least 5 different places a day.</li><li>Create and run a new ad for 1 week every week.</li><li>Find at least 4 people talking about or asking questions about topics related to my startup a day and write them a detailed, personal answer.</li></ol><p>Well, now.</p><p>These <strong>we can control</strong>, can’t we?</p><p><strong>You can control</strong> whether or not you choose to screw around watching the price of Ethereum bounce around or instead find yourself 10 people who might be interested in your product that you could then send 10 emails to.</p><p><strong>You can control </strong>whether or not you decide to slack off on Slack all day or instead find yourself 4 people asking questions about something related to your startup and write them some useful and helpful responses.</p><p>Now sure, you still have <strong>no control</strong> over the <em>outcomes</em> of those activities. Just because you send 10 cold emails does not mean you’ll get 10 happy customers — or even a single response. Just because you wrote an article does not mean you’ll get 100 visitors — or even one.</p><p><strong>But that’s not the point.</strong></p><p>The point is that rather than get hung up on things you have no control over and to expect any kind of “goals” you’ve set around such things to “magically happen” — that you’re instead focusing your energy and your efforts on things you can shape and influence — and you’re <strong><em>holding yourself accountable for doing actual, real work.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*s1B_GwxKP2qDVuLAb6h8rQ.png" /><figcaption>The good news? You can work on whatever you want to during the second 40.</figcaption></figure><p><strong>It’s time to do work, son.</strong></p><p>Okay, so let’s say you’re bought into this whole “measure activities instead of goals” business.</p><p>How exactly do we make money with that approach?</p><p>First thing’s first, you’re going to have to do some <strong>work </strong>(I hear you Millennials hate that word, so sorry if I just shocked some of you off of your parents’ couch while you were reading this).</p><p>When you start out doing this, it’s going to take some time to get the hang and feel of it all. Expect to put in some hours until things start to “click”.</p><p>But once they click?</p><p>You could probably do most of this in an hour or less a day.</p><p>For reals.</p><p>Okay, so let’s get to it.</p><p>For this to work for you, you have to know what you want to get out of it.</p><p>You have to know if you want to build traffic to your website to drive trials or opt-ins or if you want to close some cash-in-hand sales.</p><p>These things are your <strong>expected outcomes.</strong></p><p>You <em>expect</em> that if you do these activities <em>right</em>, that you will have (at least some of) these <em>outcomes</em> as a result.</p><p>Now, you don’t set goals on your outcomes at this stage (that comes later).</p><p>At this stage, you just need to identify the thing you want at the end of the day.</p><p>From there, you work your way <strong>backwards</strong> to determine <strong>what kind</strong> of activities you should be doing to <em>realize</em> those outcomes.</p><p>If you want to <strong>close some sales</strong>, you’re going to be focused on hand-to-hand sales combat activities, typically starting from scratch in the “lead generation” and “prospecting” stages, doing things such as:</p><ul><li>Using search engines and social networks to find businesses — and the individuals in them — who seem to be “a good fit” for what you offer and adding them to your CRM</li><li>Building opt-in offers and lead magnets to capture leads</li><li>Doing cold outreach (aka cold emailing or cold calling)</li><li>Performing educational outreach (webinars, etc.)</li><li>Generating referrals through partnerships and networking</li></ul><p>Your expected outcomes at this stage with these activities would be:</p><ul><li>Get responses from people you’ve contacted</li><li>Set appointments/meetings to talk with the people who responded</li></ul><p>If you want <strong>to build traffic traffic</strong> or <strong>get trial signups</strong>, you’re going to be focused on marketing activities, such as:</p><ul><li>Using search engines and social networks to find websites, forums, Slack groups, and even other social networks where people who would use your product go for information or entertainment</li><li>Promoting your startup on <em>relevant </em>websites your target market visits through educational (and entertaining!) content marketing, guest posts, recommendations, participating in forums, and even taking out ads</li><li>Finding “related” products or services that your target market uses that you can “tie in” your offering to through techniques such as integration marketing</li><li>Getting your product listed on <em>relevant</em> “lists” — such as “The top 10 best tools for X” as well as on <em>relevant</em> directories — such as Capterra and Product Hunt.</li><li>Creating (and promoting!) <em>relevant </em>content that you can use to get backlinks and list for specific keywords to improve your site’s SEO <em>for those keywords</em></li><li>Taking out <em>relevant</em> ads on Google or anywhere else your target market is likely to search for what you have to offer</li><li>Taking out <em>relevant </em>ads on Facebook, Twitter, or anywhere else your target market is likely to <em>be</em> and <em>be interested in</em> what you have to offer</li><li>Answering questions on Q&amp;A sites such as Quora, Product Hunt Ask, and (especially!) on “niche” forums specific to your target market.</li><li>Finding <em>relevant</em> publications (old-school industry-specific ones or even just simply Medium ones) and submitting <em>relevant</em> content to them that educates and informs their readers about a topic they give a shit about (and which you’re <em>perfectly</em> situated to help them with!)</li><li>Sponsoring <em>relevant</em> newsletters that your target market subscribes to</li><li>Doing interviews on <em>relevant</em> podcasts that your target market listens to about topics that your target market would find useful, interesting, and helpful</li><li>Engaging in <em>relevant</em> social media channels where your target market participates and consumes information and where you can <em>naturally</em> promote your articles, content, interviews, posts, answers, etc. to an audience that would actually <em>want to see and read those things</em></li></ul><p>Your expected outcome at this stage of the game with these activities would simply be <strong>traffic — but not just <em>any</em> traffic as you’ll soon see.</strong> (You can worry about optimizing for conversions after you actually <em>have</em> traffic you can optimize.)</p><p>And these are just ideas to get you started.</p><p>There is <em>so much more</em> that you can do.</p><p>But start somewhere you must!</p><p>So now you need to <strong>pick 2–3 things that you will do daily for a month </strong>(to start; once you get better at this, add more to your plate as you wish 😜).</p><p>[Ideally you’ll want to pick activities that you <em>think</em> (<em>read: </em><strong><em>wild ass guess</em></strong>) will have the biggest potential payoff. It shouldn’t be completely random.]</p><p>Let’s say that your list looks like this:</p><ol><li>Find 5 businesses a day that are a fit for my offering and send each of them an email to qualify their interest in getting/solving (this specific benefit/pain point).</li><li>Find 3 people asking questions on a forum or Q&amp;A site specifically related to my product offering and give them the <em>best</em> answer they have ever seen to their question.</li><li>Write 1 piece of “quick” content that talks about one <em>very </em>specific topic my target market is interested in in under 30 minutes and promote it in at least 3 different places (relevant Facebook Groups, Reddit, Medium, “link” sites, forums, Slack groups, Twitter, etc.)</li></ol><p>Do you think you could find the time to do <em>that</em> in 1 to 2 hours a day, every day?</p><p>No?</p><p>Well, if you never <em>try</em>, then you’re right — you’ll never do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*Apeymah5H9HTX6Jzp87cuQ.jpeg" /><figcaption>Better learn how to turn left, bruh.</figcaption></figure><p><strong>Up and to the right (very slowly)</strong></p><p>With <em>everything you do</em> — ask yourself — “How many outcomes can I reasonably expect this to get me?”</p><p>(A little secret? No one knows.)</p><p>So you just guess.</p><p>And you write it down.</p><p>For example, if you write a piece of content, you might think you can get 10–50 people to read it if you post it to a specific link sharing site your target market frequents.</p><p>Great. Let’s write that down and build a spreadsheet (we’re all nerds here, right?).</p><p>On the far left, you write down the “category” of the activity — such as “Content Marketing”.</p><p>Then, a cell over, you write down the <em>specific </em>activity you’re planning on doing — “Write a blog post about how to simply purchase ordering (plugging Startup Awesome).”</p><p>Then, a cell over from that, write down the <em>specific place </em>you’re going to promote that thing (if applicable). (When dealing with promoting the same piece of content in different places, create rows for each place and separate estimates for each place.)</p><p>One more cell over, write down what type of outcome you’re expecting — in this case “Traffic”.</p><p>Then, one cell from that, write down how many expected outcomes you might get (your wild ass guess).</p><p>Use one “sheet” per month and record your daily activities for each month <em>religiously</em>.</p><p>Then, as you actually <strong>execute </strong>on those activities (aka, that nasty word you hate — “work”), write down how many outcomes <em>you actually got </em>in a cell at the end of each row.</p><p>So something like this:</p><p><strong>Category | Activity | Place Promoted | Type of Outcome | Expected Result | Actual Result</strong></p><p>Using something like Google Sheets (free!), it’s pretty simple to get sums and totals from this information based on “Category”, “Place Promoted”, or “Type of Outcome” so you can see what’s working (and what’s not).</p><p>[Pro tip: Look for patterns.]</p><p>You’ll start to “get a feel” for how much you should <em>actually</em> expect from different kinds of activities and promotional placements. This is critical, as it helps you to dial in your (sometimes ridiculous) expectations. Once you’re better “calibrated”, you’ll be able to make better judgment calls about where you should put your efforts and how much you should expect from them.</p><p>Do this for a month.</p><p>Don’t expect everything you do to work well — or even work at all.</p><p>But keep at it.</p><p>And at the end of the month, pick the winners.</p><p>If you have certain Categories that are really paying off, <strong>double down on them.</strong></p><p>If you have certain Categories that aren’t moving the needle, <strong>dump them and replace them with something else.</strong></p><p>The same thing with Placements — use what works and ditch the rest.</p><p>The next month, carry forward the winners and mix in the replacements.</p><p>Lather, rinse, and repeat until finished.</p><p>It’s slog, but the little numbers add up (especially when you start “dialing in” your “what works compass”).</p><p>To get the sales and the marketing impressions you need to build your startup, you need to either knock it out of the park in one fell swoop (you probably have a better chance of being struck by lightning) or gradually building up hundreds and thousands of cold outreaches and marketing impressions over time.</p><p>In our example above, if you did that <em>exact</em> routine <em>every day</em>, after just one month, you will have sent 150 cold emails, have written 90 targeted answers (and plugs for your startup!), and have written 30 content pieces that you promoted in 90 different places.</p><p>And that’s just in one month.</p><p>Imagine if you do this <em>every month.</em></p><p>It’s cause and effect.</p><p>If you don’t <strong>do</strong>, you don’t <strong>get.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*P05tVoNRoY5HCt4A8FDlLg.png" /><figcaption>How can we be expected to teach founders to learn how to sell or market if they can’t even fit their product inside their market?!</figcaption></figure><p><strong>But what if I don’t know how to sell good or market good (or do other stuff good too)?!</strong></p><p>Ahhh!</p><p>So here we are.</p><p>You don’t know how to sell or market good?</p><p>Guess what?</p><p>I don’t want to hear your excuses! Your sales and marketing must be at least… three times bigger than this!</p><p>(Okay, okay, I’ll back up.)</p><p>Here’s the thing that I’ll tell you that the startup gurus won’t: There is no “right” or “wrong” answer when it comes to sales and marketing — the only thing that matters is <em>what works.</em></p><p>And one more thing I’ll admit that they won’t: I can’t help you sell or market to your customer base — because I don’t know who they are.</p><p>There is no “standard” way to do this (even if there are “well understood” patterns and practices).</p><p>Because the truth is that all the “templates” and “case studies” in the world aren’t going to help you if you don’t understand your customer.</p><p>That’s because <em>everything you do</em> — in sales or in marketing — <em>must be based on, about, and specifically tailored for your buyer.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*d1Na0-jtHtoI1b0_eb5Qtg.jpeg" /><figcaption>Go for it, Slick. I double dog dare you.</figcaption></figure><p><strong>It’s about them — not about you, stupid.</strong></p><p>In order to craft <em>truly effective</em> sales or marketing strategies or tactics, <em>you must first know your buyer.</em></p><p>You must know where they “congregate”.</p><p>You must know <em>how they talk.</em></p><p>You must know what they’re <em>interested in.</em></p><p>You must know what they <em>give a shit about.</em></p><p>You must know <em>what kind of content they like to consume — and share with their peers.</em></p><p>You must know who they <em>look up to, respect, and trust.</em></p><p>You must know how they <em>like</em> to be “engaged”.</p><p>You must know <em>what they’re trying to accomplish.</em></p><p>And you must know <em>how they like to buy.</em></p><p>Then — and only then — can you <strong>hope</strong> to be able to “craft a message” that <strong>resonates</strong> with them.</p><p>Your goal — in any copy that you use — must be to establish rapport and to (subliminally) communicate with them that “I get you and I get what you’re trying to do and all the <em>shit</em> that you’ve been going through trying to get that done.”</p><p>You do that by <em>talking like they talk.</em></p><p>You do that by <em>referencing things that only an “insider” would “get”.</em></p><p>You do that by <em>reaching them where they’re open to suggestion and influence— the places where they’re asking questions or trying to learn.</em></p><p>Then — and only then — can you <strong>offer a suggestion</strong> that they will register and <em>consider</em>.</p><p>How do you “learn” how to do this effectively?</p><p><strong>You practice empathy.</strong></p><p>You practice “putting yourself in their shoes.”</p><p>You practice “feeling” how they feel about what they’re trying to accomplish.</p><p>You practice “feeling” how <em>they</em> “feel” when they see and read your cold email/content marketing/social media posts, etc.</p><p>Basically, you project your mind into theirs until you “get them”.</p><p>You do this by <em>immersing yourself</em> in their world until you “get a feel” for “how they think” by reading their comments, posts, frustrations, and insights.</p><p>Until you somehow vicariously “become one of them”.</p><p>And then you just <strong>give them what they want.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*PxqrGZHa_ga1B-d5E_Pt-g.jpeg" /><figcaption>Yes, it’s stupidly obvious. But sometimes you need to be.</figcaption></figure><p><strong>Be an idiot (when it’s smart to be one)</strong></p><p>Chances are, if you’re like most developers, you’re going to get <strong>bored</strong> with this.</p><p>After all, it’s basically saying <em>the same thing </em><strong>over and over again.</strong></p><p>In a hundred different places.</p><p>But that’s what you have to do.</p><p>I do it, and so should you.</p><p>Never assume people “get” or “understand” what you can do for them.</p><p>Spell it the fuck out.</p><p>And yes. You’re going to be repeating yourself. A lot.</p><p>Get used to it.</p><p>Every article, every post, every answer — they’re all meant to reach <strong>new people who never heard of you before.</strong></p><p>So you have to <strong>tell them who you are and what you do.</strong></p><p><strong>Every time.</strong></p><p>Here’s an example of <a href="https://www.quora.com/What-should-I-measure-to-get-user-behaviour-results-on-a-one-page-web-design">an answer I posted on Quora</a> for a question that I felt <a href="https://gettamboo.com/"><strong>Tamboo</strong></a> would be able to help with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JgU71pNivECdUrpyrLm29A.png" /></figure><p>Now, there’s a few things going on here that I think I should point out, as I think they’ll help you “grok” how to sell and market “better”:</p><ol><li>Use some form or varient of an <a href="https://en.wikipedia.org/wiki/AIDA_(marketing)">AIDA</a> construct with whatever you write.</li><li>Use visuals where you can and where it makes sense. Humans are inherently visual and their attention will go where they pretty pictures are. Make sure you have pretty pictures to show.</li><li>Show proof. Don’t just tell — <strong>show.</strong></li><li>Use a conversational tone as if you were talking to a friend — don’t be overly “professional”. <strong>Professionalism is for amateurs.</strong></li><li>Be yourself, but be unique — don’t “blend in”. You <strong>must</strong> have a different “voice” than everyone else. You must “stand out” in some way. <strong>Don’t be a robot.</strong></li><li>Be clear about what you’re saying — explain it like they’re 5 (without being patronizing). Don’t assume they know as much as you do, and don’t make it intimidating to follow along. Also, don’t assume they’re total morons at the same time.</li><li>Don’t be pushy — just be suggestive. Craft your CTAs using “recommendations” and “suggestions”. Don’t tell them what to do — simply suggest how they can take what you’ve said to the next logical step.</li><li>Don’t be skimpy —whatever you say must be something they care about and must be better than everything else they’ve been reading. You must <strong>one-up everyone else in some way — always.</strong></li><li>Don’t ever forget — <strong>IT’S ABOUT THEM. </strong>Answer their question. Give them the information they came for. And only after you’ve done that, go in for the soft “ask”.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/1*bQ_afrRwNJpvsXgO2MIjRg.jpeg" /><figcaption>And what’s the deal with lamp shades anyways?</figcaption></figure><p><strong>One more secret: You don’t want “traffic”.</strong></p><p><em>Are you crazy?!</em></p><p>Don’t get me wrong — traffic is important.</p><p>Without it, you’re not going to go very far.</p><p>But you can have <strong>a lot of bad traffic</strong> and it’s not going to get you anywhere.</p><p>Pop quiz: Would you rather have 1,000 visitors at a 1% conversion rate or 100 visitors at a 10% conversion rate?</p><p>On the surface, they’re same thing: You get 10 conversions at the end of both.</p><p>But the second one (100 visitors at 10%) is <strong>easier to grow</strong>.</p><p>To get to <em>20 customers</em>, it’s the difference between having to get 2,000 visitors as opposed to just 200.</p><p>Ahhh!</p><p>And that’s the dirty little secret — <strong>you need targeted traffic.</strong></p><p>You don’t want just <em>any</em> traffic —after all, visitors != conversions.</p><p>You want <em>traffic from people who give a shit about what you’re offering.</em></p><p>Not people who are just “curious” because they saw your latest startup blog post.</p><p>You want people who you <em>resonated</em> with — who think “you get me!” and are <em>genuinely interested in your offering.</em></p><p>So how do you do that?</p><p>You find ways to send <strong>warm traffic</strong> to your homepage (or if you’re super slick, to a custom built landing page specific for the type of traffic you’re sending it).</p><p>Basically, you don’t try to sell on your marketing site. <strong>You try to close.</strong></p><p>And you can only do that if you’ve <strong>already had a conversation with the people going there.</strong></p><p>Whatever article, blog post, forum discussion, podcast interview, or Q&amp;A answer you put out there needs to <strong>warm up your prospect for your offer.</strong></p><p>You need to “hook them” with that “external” content — and then — and only then — do you encourage them to go to your marketing site to take the next logical step.</p><p>This is <strong>warm traffic.</strong></p><p>They are primed. They are ready. Because you’ve done the work to get them to that state — and that’s why they’re <strong>more likely</strong> to take whatever action it is you want them to take.</p><p>A lot better than just “spraying and praying” with whatever traffic you can get your hands on, right?</p><p>And with that final thought for you to ponder on, I’m going bring this installment of <em>The Epic Guide </em>to a close.</p><p>In the next Part, we’re going to go in depth about why your website sucks and why it’s costing you customers (enjoy!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*qIIm9-0mDUALTDMqrBqVsw.jpeg" /><figcaption>My friend here is a little slow!</figcaption></figure><p><strong>I almost forgot!</strong></p><p>If you love <em>The Epic Guide</em> and want even more down-and-dirty, no-frills, battle-tested startup warfare strategy and tactics, <a href="http://cliffordoravec.com/the-epic-guide-to-bootstrapping-a-startup">be sure to check out <em>The Epic Guide: The Book!</em></a></p><p>Or, if you want to hear my voice inside of your head (I’m not judging!) in what could only be comporable to Samuel L. Jackson’s character in <em>Pulp Fiction</em> reading you startup bedtime stories, <a href="https://saasingear.com/">sign up for my upcoming podcast (aptly titled) SaaS In Gear!</a></p><p>And of course, if you’ve been working hard on building your startup or online business but need a little “help” to understand what your website visitors are <em>really </em>doing, <a href="https://gettamboo.com/">don’t hesitate to give Tamboo a try on your website</a>. You’ll get all the secret tools marketers like me use to increase conversions and create even more potent sales pages — including funnels, visitor recordings, and heatmaps.</p><p>And last but not least!</p><p>Be sure to follow me on <a href="https://medium.com/@cliffordoravec">Medium</a> and on <a href="https://twitter.com/cliffordoravec">Twitter</a> at @cliffordoravec and give me a shout out if you like what I’m doing here!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87db07b436f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tamboo/real-world-startup-sales-and-marketing-for-the-lost-and-the-clueless-part-5-of-the-epic-guide-to-87db07b436f5">Real-World Startup Sales and Marketing for the Lost and the Clueless (Part 5 of The Epic Guide to…</a> was originally published in <a href="https://medium.com/tamboo">Tamboo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s New In Tamboo Visitor Recordings (Oct 17)]]></title>
            <link>https://medium.com/tamboo/whats-new-in-tamboo-visitor-recordings-oct-17-ca5eb16f3d90?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca5eb16f3d90</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[conversion-optimization]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[heatmap]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Thu, 19 Oct 2017 01:42:46 GMT</pubDate>
            <atom:updated>2017-10-19T01:46:45.973Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uRq99TCiPX5uf_VGoinqnQ.png" /></figure><p>Summer may be over, but things have been <strong>heating up</strong> over here at Tamboo! Here’s what you might have missed:</p><p><strong>New This Month: Funnels!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oX38kkThBOYAMszj83_AUQ.png" /><figcaption>Everyone who uses Tamboo funnels gets a trophy!</figcaption></figure><p>This release was a big one — with numerous enhancements to Tamboo’s user experience and core functionality.</p><p>But perhaps the biggest of those changes has been the introduction of <strong>funnels</strong> in Tamboo.</p><p>Funnels help you model and measure the steps that your customers take as they navigate your website from landing page to purchase. With funnels, you can quickly and easily see where people are “dropping off” before they finish signing up for your service or before they complete a purchase.</p><p>If you’ve been looking to increase the number of signups or sales your website gets, funnels help you see where you need to focus your efforts. By fixing a “leaky funnel”, you can often see <em>dramatic</em> improvements in your website conversion rates.</p><p>To help make the whole process of optimizing your website and increasing your conversion rates even easier, Tamboo’s funnels are seamlessly integrated with best-in-class visitor recording functionality. This powerful combination lets you jump right to screen recordings of your visitors so you can literally <em>watch</em> what people are doing at the different steps in your funnel.</p><p>Pretty cool, huh?</p><p><strong>Even More Awesome Visitor Recordings</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I7SFnyyljutVGIe7l5fs7Q.png" /><figcaption>So fresh and so clean-clean!</figcaption></figure><p>Speaking of Tamboo’s <a href="https://gettamboo.com/">best-in-class visitor recordings</a>, this release gave them some fresh love as well!</p><p>Perhaps the most noticeable change is that <strong>they’re bigger than before!</strong></p><p>The design of the playback has been updated and improved to give <em>even more room</em> to those gorgeous recordings of yours.</p><p>The search and filter menu (now with a new “slim” look) is now located at the top of the page, making it “stand out” less than before, while still being easy to find and use when needed.</p><p>Updates were also made to the design of the “playing next” recording previews in the playback menu on the right. With these new improvements, it’s easier than ever to get quick information about a recording with just a glance at its preview pane.</p><p>And last but not least, Tamboo’s visitor recordings now include “mouse trails” and updated “click stickers”.</p><p><strong>Mouse trails</strong> show you the path your visitor’s mouse takes as they move through a page, represented as a red line that grows and follows the mouse wherever it goes. Using mouse trails, you can easily track where your visitor‘s attention is and more easily visualize user experience issues, such as when a user is having difficulty finding the information they’re looking for.</p><p><strong>Click stickers</strong> show you where your visitors click during a recording, and are represented by a hand in a red circle. This release introduces a new semi-transparent click sticker so that you can more easily see what’s underneath a click.</p><p><strong>Expanded and Improved Heat Maps</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkQhUB1oW_s1Cys3WSqSYg.png" /><figcaption>Is it getting hot in here?!</figcaption></figure><p>Also in this release, Tamboo’s heatmaps have been completely expanded, improved, and redesigned from the ground up.</p><p>Tamboo’s updated heatmaps are now <strong>even more accurate</strong> when it comes to tracking clicks and mouse movements across <strong>tricky responsive designs</strong>, thanks to a major update to the backend heatmap engine.</p><p>In addition to improved tracking, Tamboo’s click summaries and CTR metrics also got a fresh update, making it even easier to quickly see how many clicks each of your page elements have gotten, and what each of their click-through rates are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GwYyVnXqs9Vb3K-xejtEig.png" /></figure><p>And if that wasn’t enough, Tamboo now has <strong>mouse movement heat maps</strong>, which show you all the places where people move, place, or hover their mouse — which is a leading indicator of user interest:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bq2hgOulTvvHytxLxv15Fg.png" /><figcaption>It might look like a giant splatter of spaghetti, but it’s actually a giant splatter of conversion tracking *awesomeness*!</figcaption></figure><p><strong>So What’s Next?!</strong></p><p>It might be hard to believe, but there are <strong>even more</strong> awesome goodies being cooked up in the Tamboo test kitchen right now as we speak!</p><p>To see what tasty website conversion morsels are next, be sure to <a href="https://blog.gettamboo.com/"><strong>subscribe to the Tamboo blog</strong></a> and <strong>follow us on Twitter at </strong><a href="https://twitter.com/gettamboo"><strong>@gettamboo</strong></a><strong>!</strong></p><p>In the meantime, if you’ve been trying to <strong>increase signups, sales, or conversions </strong>on <em>your</em> website but have been struggling to figure out where to start, you might want to <strong>give Tamboo’s </strong><a href="https://gettamboo.com/"><strong>visitor recordings, heatmaps, (and now) funnels</strong></a><strong> a try yourself!</strong></p><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca5eb16f3d90" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tamboo/whats-new-in-tamboo-visitor-recordings-oct-17-ca5eb16f3d90">What’s New In Tamboo Visitor Recordings (Oct 17)</a> was originally published in <a href="https://medium.com/tamboo">Tamboo</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 a kick-ass landing page (for reals!)]]></title>
            <link>https://medium.com/tamboo/how-to-build-a-kick-ass-landing-page-for-reals-37a88d73587e?source=rss-55e9fd9a459------2</link>
            <guid isPermaLink="false">https://medium.com/p/37a88d73587e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[landing-pages]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Clifford Oravec]]></dc:creator>
            <pubDate>Tue, 19 Sep 2017 04:43:45 GMT</pubDate>
            <atom:updated>2017-09-19T05:04:07.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/319/1*hMSt-kxgha-qbX1WG7filg.jpeg" /><figcaption>Heck yes!</figcaption></figure><p>I recently received an email about how to go about building a kick-ass landing page. Here’s my response — verbatim:</p><p>Hey &lt;Startup Dude&gt;!</p><p>First of all, thank you for the awesome note! It’s super encouraging to hear that you’ve found what I’ve put out there useful and helpful. I’ve been cooking up some new <a href="https://cliffordoravec.com/the-epic-guide-to-bootstrapping-a-startup">Epic Guide</a> goodies over the past few weeks and am excited to get them out to you (and to hear what you think!)</p><p>Also, you may be encouraged/surprised to know that my background seems to be very similar to yours. I was a developer and then an architect (and then a manager and then an architect — long story) in an enterprise setting for *years*. So you and I can probably swap some very apropos Dilbert cartoons together 😉</p><p>But back to your question and some specifics.</p><p>The first thing I would recommend you do is not let the fact that you have built out an app cloud your judgment. A lot of developers (myself included) think that “building the app” is the pinnacle of the process and they lead with that — and that’s a mistake. I would say keep the fact that you have your app fully developed in the back of your pocket — don’t let on that it’s built out yet to your target market. If you lead with “here it is — sign up!” you’re going to miss out on all kinds of learnings and interactions with people that you can gain if you just slow it down a notch and lead with “here’s this thing I’m ‘working on’ — sign up to get a notification when it’s ready and tell me what you think!” Although the feedback they give you may not affect anything you’ve built, it will give you all the tools you need to know how they think and how you need to approach sales and marketing. This is seriously invaluable, and you don’t get it if you lead with a full “here’s my app — pay for it” approach. So definitely start with a launch list (even if your app is complete) and reach out to people to talk about what you’re working on and how it will help them. These are the keys to the castle.</p><p>Honestly, I’m humbled that you think that my landing pages are so awesome! I’m my own worst critic at times and always think that I can do things better (occupational hazard I guess, right?). That being said, let me at least explain my thought process when I go about creating said landing pages so you can maybe draw some inspiration (and steal the best parts!)</p><p>The first thing I do is decide what my call to action will be. What is it I’m trying to get people to do? Is it get them to sign up for a launch list? Is it get them to sign up for a newsletter? Sign up for a trial? It’s pretty simple, but it drives the whole process.</p><p>I take my desired “I want you to do X” and then I think “why would you want to do that?” Usually, you can use a simple formula like so:</p><p>“I want to &lt;insert call to action&gt; because &lt;underlying reason/driver&gt;”</p><p>So, for example:</p><p>“I want to sign up for your new podcast about building SaaS startups because I’m looking for a podcast that can help me *actually* build out my SaaS”</p><p>Perfect!</p><p>Then I think: “Okay, how do I make this whole thing *scream* ‘THIS IS FOR ME?!’ to someone looking at this?”</p><p>In the podcast example, I asked myself — how do I *position* my podcast against all the other podcasts out there? And I was like, well, a lot of podcasts are full of interviews and low-value chatter. So if I position my podcast as being no-fluff, no-interviews, that would be something different, right? I’m the *opposite* of those things. I’m all-action, anti-thought-leadership. And then I build my messaging around that *WHY*. It’s not *just a podcast* — it’s a podcast for people who are sick of listening to interviews and fluff and want to learn how to actually fucking build something! Perfect!</p><p>Once I have a general idea for what my “messaging” is going to be, that’s when the creative stuff starts.</p><p>I don’t like to build stuff unless I know people are going to want it. It helps me save my energy for things that matter. So when I do a landing page, I *force* myself to not put out any screen shots or any kind of “completed product” — because I don’t want to waste the time building it. Instead, I focus on visuals and messaging that convey what I’m looking to accomplish. If you nail those things, *you don’t need a screenshot to get signups*.</p><p>So what I do is I think of the *emotional* aspects behind the messaging.</p><p>I put myself in those shoes and think — what things *resonate* with being in that state of mind?</p><p>For <a href="https://gettamboo.com/">Tamboo</a>, “awe” and “discovery” are common themes. So I try to find images that I think evoke that emotion.</p><p>For <a href="https://cliffordoravec.com/the-epic-guide-to-bootstrapping-a-startup">The Epic Guide</a>, “going it alone in a land of wonder” is the theme I think of. So I look for images that evoke *that* emotion.</p><p>For <a href="https://saasingear.com/">SaaS In Gear</a>, “racing down a road in the middle of the night (since most of us work at night) by myself (since most of us work solo) in a fast car (since that evokes a feeling of “accomplishment” and “getting somewhere quick”)” is the theme I think of. So I look for images that evoke *that* emotion.</p><p>The images are key — because I don’t have any screenshots or anything else to “offer”. I need to rely on 1) visuals and 2) messaging. In that order. Visuals “grab” people’s attention. Messaging draws them to the conclusion I want them to have — that they *want* this thing.</p><p>When you have visuals and messaging that *resonate* with each other and *compliment* each other — that is a very powerful psychological driver. There are *emotions* involved — and that’s what you want.</p><p>So where do you get visuals? I use <a href="http://pexels.com/">http://pexels.com</a> for most of my images. They’re all Creative Commons so I can use them for commercial use without an issue — and they’re very high quality. I literally spend *hours* looking though Pexels for “the right image” that conveys and resonates with the emotion I’m looking to capture. It’s not happenstance — it’s very calculated. For SaaS In Gear (which has a +40% conversion rate for signup), I had 10 different images I was considering before I settled on the one I chose. I probably spent 4–6 hours trying to find the image that “moved me” the most.</p><p>But here’s the thing — I give myself *two days* to build any landing page. I don’t let “perfection” get in the way (and probably hence my “I suck” insecurity 😜). Two days = a weekend. That’s all you should give yourself, otherwise you won’t ship it.</p><p>Once I have my general “messaging” and my “visual”, I focus on layout.</p><p>The layout aspect is very subjective, I’m not going to lie. What I’m trying to do with this is to find a way to *keep the focus on the visual* and to *complement it* with the messaging that I have. I don’t want to “drown out” the visual — since that is a huge emotional driver. I want text that is going to be positioned in such a way that it “fits” with the visual. I settle on a few “points” that I want to make that reinforce my messaging and find the best way to present that information on top of the visual that I’ve selected. And then I play, play, and play, with the layout until I achieve the right “balance” between visual an messaging. I don’t want the messaging to “drown out” the visual, so I’m very aware of that aspect — and I don’t want the messaging to not “resonate” — because that is very important, too. It’s a balancing act, and playing around with basic geometry and positioning goes a long way. The ultimate goal is to build something that is aesthetically pleasing — and it takes practice and iteration. I went through 10 different layouts (modifying text as needed) with SaaS In Gear before I settled on the one I ran with.</p><p>Now, when structuring your page messaging, you typically want to follow an AIDA construct. (Wikipedia it if you’re not familiar with it.) So the top of the page contains the A, the middle contains the I (and sometimes D), and the “do what I say” contains the D and the A. Look at SaaS In Gear, and you’ll see what I mean. Structure your pages this way and you’ll see how they just logically “flow” to the conclusion that people “need this!”.</p><p>I also pay special attention to my CTA buttons. They should evoke a *benefit* or an *outcome* that doesn’t scream “skeeze!” They should feel *natural* — some *obvious* benefit that people actually *want*.</p><p>And that’s honestly it.</p><p>It takes practice, and it takes a good eye, which takes time to develop (after all, I didn’t just “nail” my first landing page — if it were that easy I never would have had reason to write The Epic Guide 😉). I recommend creating a “swipe file” of landing pages you like that you can draw inspiration from (read: steal the best parts from) to help you to get the gist of how to structure one. But it takes practice, so don’t get too down on yourself if it doesn’t just “fit” after your first go.</p><p>I hope this helps!</p><p>Best of luck and *do stay in touch!*</p><p>Clifford</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37a88d73587e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tamboo/how-to-build-a-kick-ass-landing-page-for-reals-37a88d73587e">How to build a kick-ass landing page (for reals!)</a> was originally published in <a href="https://medium.com/tamboo">Tamboo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>