<?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 Brandon Dixon on Medium]]></title>
        <description><![CDATA[Stories by Brandon Dixon on Medium]]></description>
        <link>https://medium.com/@9bplus?source=rss-4ed29fb827a7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*0zJzj8c-dcAE4wtWEllwmw.jpeg</url>
            <title>Stories by Brandon Dixon on Medium</title>
            <link>https://medium.com/@9bplus?source=rss-4ed29fb827a7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:15:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@9bplus/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[The Coffee Business That Wasn’t]]></title>
            <link>https://9bplus.medium.com/the-coffee-business-that-wasnt-ba67445df99e?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba67445df99e</guid>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[lessons-learned]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Fri, 03 Dec 2021 15:56:06 GMT</pubDate>
            <atom:updated>2021-12-04T14:29:55.716Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwdU0rMhn_TVVVZeYAjUow.png" /><figcaption>Landing page for Split Key Coffee</figcaption></figure><p>4 years ago, I thought I was going to leave the cybersecurity industry and pursue creating a business in speciality coffee. That obviously didn’t pan out, but I am often asked how the coffee work is going and why I choose to not start my own business. This post outlines the process I took, mistakes I avoided and why I didn’t see a lot of promise in going into coffee full time.</p><h3>From Passion to Business Planning</h3><p>My interest, and later obsession, with coffee started from a place of curiosity––tasting quality coffee triggered a desire to know more about the process. I spent years exploring coffee, learning about the beans and regions, understanding the growth process, refining my brewing methods and of course, speaking with others already in the industry.</p><p>By 2017, I started to see opportunities to apply my technology skills to solve some interesting coffee problems. More specifically, when speaking with shop owners and Q graders, there was value in refining inventory management and the quality assurance (cupping) process from farm to production. When my ideas get to this stage, I often form an LLC to track my investments, account for expenses and consider what branding could look like. Split Key Coffee was born quickly and served as a way to gather interest from the general public.</p><p>As a small scale experiment, I purchased a home coffee roaster that I could interface with code, several pounds of green beans and began writing a web-based software platform I dubbed <a href="https://github.com/splitkeycoffee/split-key-roast">Split Key Roast</a>. Fun fact, I may be one of the first people to have created a roaster that <a href="https://twitter.com/splitkeyroast">live-tweeted its roasts</a>. As I made progress on these ideas and continued speaking with others in the industry, I began to consider what it would be like to open a roasting business locally in my area.</p><h4>Scaling to Create a Roaster Business</h4><p>By this point in my journey, I had spent several thousand dollars on supplies and countless hours in development. This wasn’t a concern for two reasons: 1) I was passionate about the idea and enjoyed the work and 2) much of my purchases (e.g. Espresso machine) were items I’d continue to use for many years even if I decided against the business idea.</p><p>After months of research and home roasting on my own tools, I reserved a <a href="https://millcityroasters.com/shop/coffee-roasters/1kg-gas-coffee-roaster/">1KG roaster from Mill City Roasters</a> for roughly $10K and enrolled in one of their local classes in order to meet like-minded coffee lovers and pick their brains on the business end. This was a large leap for me and spending that much money on a side business left me unsettled––keep in mind, I had <a href="https://www.riskiq.com/press-release/riskiq-acquires-passivetotal-expand-portfolio-threat-infrastructure-analysis-capabilities/">successfully built and sold PassiveTotal</a> with a partner for less than $15K investment.</p><blockquote>Doubt is not a reason to give up on your ideas, but suggestive that more research is needed to validate them.</blockquote><p>While I waited for the in-person class, I spoke with more businesses, found others who left cybersecurity to pursue coffee or other passions, and continued to educate myself on requirements for creating a local roasting business. I maintained a spreadsheet of all the perceived costs to enter the roasting space and it became obvious that while coffee itself has great margins, running the broader business eats heavily into those profits.</p><h4>Learning from Others</h4><p>I arrived in Minneapolis in 2018 for the Mill City Roasters training class extremely excited, and feeling well prepared. I met hobby roasters, direct-trade distributors, those within the farming side of coffee and full-scale roasting operators. Determined to make the most informed decision on whether to start a proper business, I spent the days in class asking questions and speaking with others.</p><p>What I found most interesting, and a bit frightening, were those getting into the space with little business experience, simply fueled on their love for coffee and desire to give back to their community. Those individuals had staked real money to open a coffee shop/roastery, yet they weren’t exactly sure how to go about running it. I truly wondered whether they’d succeed long-term and used their uncertainty to further validate my decision process.</p><p>As I reviewed my own numbers on the plane ride home, I began to realize that my passion for coffee wasn’t necessarily a good enough excuse to start a business. Not only that, we were poised to have our first child and it didn’t feel responsible to pursue a business that required an incredible amount of work for it to even have the chance of succeeding.</p><p>After several weeks of final contemplation, I phoned Mill City Roasters and asked if I could cancel my order. I relayed my story to the owner and he was incredibly understanding, noting that he wouldn’t impose any costs to me as my roaster would be given to someone else on their long list of clients waiting for orders. My passion would remain just that.</p><h3>Why I Passed on the Business</h3><p>“Follow your passion” is a phrase commonly suggested to someone who’s shown interest in a field and is considering pursuing it in some capacity. I am not going to debate the advice, but will state that passion is <em>not</em> enough to build a business. I am thankful for the research I performed, those at Mill City and the roasting class I attended. Below are the more specific reasons why I decided opening up a coffee shop/roaster was not in my best interest.</p><p><strong>Scaling coffee roasting requires a larger upfront investment</strong>. If you want to roast coffee and sell it to others, you need to ensure you have a roaster capable of roasting enough coffee at once. Home roasters can service a small amount of coffee, but do not scale. You will not only need to invest in a larger roasting setup, but also a kitchen from which to operate as coffee is considered a food.</p><p><strong>Taxes exist everywhere. </strong>Purchasing and roasting beans is a fairly cheap process. Getting them to customers in a timely manner means you need to coordinate your roasting and ship the beans quickly. Bags, boxes, and shipping all cut into your profits and mean you’re eating them or passing it to the customer. In the early stages of business, this is going to be very chaotic until you have a consistent base of customers.</p><p><strong>Brick and Mortar is Not SaaS. </strong>If you have a store, there’s a ton of obvious costs associated with that. Leases, materials, labor, licenses and of course your time to run it. Coming from a SaaS background where you write once, sell many, it was tough to conceive running an actual store and managing the day-to-day workings.</p><p><strong>My Passion Wasn’t Reflected in the Market. </strong>I love coffee, specifically specialty coffee. When conducting surveys and speaking with shop owners, it became obvious to me that coffee is largely a caffeine vehicle for most people. The source, nuanced taste and quality of the beans is rarely considered. I wasn’t confident I’d be able to maintain my drive in an environment like this. Educating others is exciting, but for many, they just want their cup and they want it fast.</p><p><strong>Coffee is a Commodity. </strong>Go to any major city and you’ll see no less than 5 coffee shops within a couple blocks. What differentiates the shops from one another? In most cases, it’s the experience and less the quality of the coffee. In order to rise above the rest, you need to invest in marketing, educate the consumer and partner with adjacent businesses (bakers, artists, etc.) to deliver a rich customer experience. This is not impossible, but not something I was less passionate about at the time.</p><h3>How is Coffee These Days?</h3><p>It’s great and still a passion of mine. Since foregoing the broader business idea, I’ve visited several farms in different parts of the world, created <a href="https://medium.com/split-key-coffee/homemade-nitro-cold-brew-8c59639aa6ad">my own at-home nitro setup</a> and continue to <a href="https://medium.com/split-key-coffee/brandons-coffee-journey-guide-c79c4d524e9">share my knowledge of coffee</a> with others. I have zero regrets in not pursuing coffee as a business and in fact, later learned that at least one roaster I spent a lot of time with unfortunately went out of business. This multi-year journey was, and continues to be, one I very much enjoy.</p><p>If I had to summarize all I learned down to one simple fact, it’s this: Not every idea or passion <em>needs</em> to become a business.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba67445df99e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GCCCT 42-mile Ultra]]></title>
            <link>https://9bplus.medium.com/gccct-42-mile-ultra-69945306f376?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/69945306f376</guid>
            <category><![CDATA[ultramarathon]]></category>
            <category><![CDATA[running]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[fitness]]></category>
            <category><![CDATA[endurance]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Sat, 05 Dec 2020 21:40:42 GMT</pubDate>
            <atom:updated>2020-12-05T21:40:42.727Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sbV2c1lacnqWrZGJh_Q0ig.png" /></figure><h4>Background</h4><p>2020 has been a mess of a year and with nearly every race being cancelled, I turned to creating my own events to stay focused. The first half of the year was 70.3 training and when that ended in June, I narrowed my focus to the marathon I had planned in October. This was my first marathon and I wanted to avoid injury, so I decided to slowly build up speed and endurance by alternating larger workouts on the weekends where one set was focused on Z3 and the other closer to Z1.</p><p>Through a combination of excitement and nearing burnout, I tackled my first marathon in September and finished in 3 hours and 50 minutes, 20 minutes off my primary goal. I ran into a few physical issues during the run, but mentally, I never hit the wall that most people speak about. My training program of normalizing longer runs paid off!</p><p>Despite reaching my goal, I wasn’t as pleased with the outcome. Missing the goal wasn’t the core issue as much as I had just lost sight of the journey. In retrospect, I didn’t put in enough recovery over the summer, didn’t taper and as a result, didn’t enjoy the training and rushed to be done. Knowing I had at least one more larger event in me, I opted to go after an ultramarathon.</p><h4>The Course</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*s4-2d29O3pDvTmrNKAm8NA.jpeg" /></figure><p>Much of my training and the marathon itself was done on paved segments of the <a href="https://www.fairfaxcounty.gov/parks/trails/cross-county-trail/maps">Gerry Connolly Cross County Trail</a> here in Northern Virginia. Originally, I wanted to tackle the GCCCT in 3–4 segments, but with my newfound understanding of my body, I opted to use this as my ultra course. The trail is 42 miles and is a nice combination of single-track dirt and paved segments. Having been on numerous parts of the trail through biking or running, I knew that it was well-maintained and had plenty of opportunities to see others and get any support if needed.</p><h4>Pre-Race Training</h4><p>Post-marathon, I took 2 weeks recovery still doing about 4–6 hours of training, but far less intensity. I wanted to avoid full-on winter conditions, but also give myself enough time to get acclimated to trail running and build a good base of weekly miles. 45 days put my target date around November 14th and I built a training plan from there.</p><p>Unlike the marathon training, I spent far less time doing cross workouts and slowed my pace down to Z1 runs. Having not really spent anytime on trails, I began running exclusively on softer gravel paths and single-track dirt paths through the woods to prepare. Being on a softer surface means you don’t get the same spring you do on asphalt and as a result, you work different muscles and aren’t able to maintain the same speeds. What I lost in speed, I gained in comfort though––being out in the middle of the woods is such a different vibe than racing on the road. You’re forced to slow down, pay attention to your footing and just focus on running.</p><p>During peak training, I ended up at 72 miles over a 7-day period and was feeling great. A few weeks before the race, I did a 20/16 long run weekend to assess how my legs would feel and there were no issues at all. I put a 2 week taper in place and moved the event up a week to November 7th given the weather was great and I was worried about the coronavirus around our area.</p><h4>Gear and Nutrition</h4><p>Knowing my ultra would be at least 7 hours, I used the 45 days to try out new foods and supplements in order to see which ones worked best for my body. In the end, I really found myself enjoying a liquid combination of endurance Gatorade and Perpetuem from Hammer Nutrition. For the hourly fueling, I had mini Clif and Kind bars, peanut butter packets, Hammer gels and Clif shot blocks––I tried to give myself a lot of options knowing I don’t enjoy eating much during any of my runs.</p><p>As a final component of my training, I introduced gear to be as self-sufficient as I could. My wife was going to provide support along the run, but I wanted to ensure I could easily hold most of what I needed. For that, I used the Nathan VaporKrar vest with a Camelbak 1.5L bladder for water and 4 hydroflasks (2 for carry, 2 for replace) for my liquids. I made sure to train with all my gear on every run in order to get used to the vest.</p><p>The night before the race, I packaged up all my gear into crates and created 4 baggies with a combination of fueling options, so I could just grab and go when seeing my wife.</p><h4>Goals</h4><p>I am never a fan of the “finish the race” style goal, but considering this was my first ultra, I truly just wanted to avoid blowing up. During training, I had locked into a pace between 10:30 and 12 that felt good. Knowing that range was sustainable, I put a rough goal in place to try and run 11–11:30s or just get under 8 hours for the entire distance.</p><h3>Race Day</h3><p>I woke at 4:50AM and immediately mixed my drinks for the day and made some oatmeal. I prefer to give myself a good hour to really wake up, digest food and handle any business prior to getting out the door. At 6AM, we made the drive over to the start location (25 mins) which is about a mile off a parking lot. My wife dropped me off and I trekked to the starting position, getting there at about 6:45AM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sbV2c1lacnqWrZGJh_Q0ig.png" /></figure><h4>Miles 0–19</h4><p>No real issues apart from an elevated heart rate to start which mentally through me off and caused some concern. I suspect this was from a combination of being up early, it being cold outside and just excitement for the event. To keep warm, I used windproof jacket, pants and gloves.</p><p>Recognizing nutrition was the most important element of the day, I kept a regiment of trying to take in food and electrolytes every half hour even though I wasn’t hungry. This worked out to about 100 food calories per hour with another 50–75 via liquid.</p><p>The first 10–12 miles were trail segments I did not get a chance to train on and as a result, got turned around twice, adding in some extra distance. This wasn’t a big deal and once I got to areas I recognized, I fell into a flow. At mile 18, I met my wife where I swapped my hydroflasks, took off my windproof items and swapped to a fresh pair of shoes as mine were pretty muddy.</p><h4>Miles 19–31</h4><p>Again, no major issues. At mile 28, I accidentally ended the workout on my watch, then immediately had to start a new one. This was annoying as I had programmed specific pace and alerting into the actual workout and lost it when I started a new run file. I pushed on and just tried to run on feeling, but would check against the averages as often as possible to ensure I could keep close to my under 8 hour goal. At mile 31, I met up with my buddy Dan and grabbed nutrition from my wife.</p><h4>Miles 31–40</h4><p>The last bits of this course had a whole bunch of hills and harder efforts. Heat had kicked in by this point (70s), but it didn’t impact me too much. My right knee was getting annoyed earlier on, but it wasn’t so bad that I needed to stop. This continued until the end and was eased by slowing the pace down a bit as we had crept up to running 11s. Around 38–39, I had my first feeling of a wall due to nausea. I had a tough time getting any food to stay, but ultimately had success with peanut butter packets mixed with water. I was able to blast through the mental barrier quickly and rally around the idea of finishing.</p><h4>Miles 40–42</h4><p>The trail ultimately ends in a park by the water. As we made our way into the park along the long entrance, we continued to see trail signs. I had hoped to see a final “end” post or mile marker, but none ever showed up. The paved section of road we were on just merged with a 5K trail which looped at the bottom of the park. I wanted to be sure I didn’t miss any signs, so we ran to the bottom of the park and looped back up to the final parking lot, making it a full 42 miles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1CnI07vEeribxAfA9k8lyA.png" /></figure><h3>Post-Race</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LwK4AOAUgSGNswHs3fAGyA.png" /></figure><p>According to my Stryd footpod, I was just a few seconds under the 8 hours moving time for the event. The last 2 miles were mixed with a lot of stop and go due to a lack of course markers or details, but ultimately, I hit my goal. Moving pace was right around 11:20s for the day and despite all that distance, I felt very good. Upon getting home, I took a 20 minute ice bath and spent the rest of the day relaxing.</p><p>The next day, I was sore, but not to a point where I couldn’t get around the house. Within 24 hours, my resting heart rate went back to normal and a few days after that, I was back to doing basic workouts. I made sure to give my body a rest and took 2 weeks to properly recover, but I was amazed how well I was able to adapt to the event and it immediately had me seeking out my next race.</p><h4>Reflections on the Event</h4><p>I am so glad I decided to commit the time and energy in running this ultramarathon––10 months of heavy training, wrapped up into a single day. It makes you appreciate the effort and of course, those in your life that make these sorts of things possible. It was a great way to end the year and has given me a new outlook on running, specifically on the trail. What I love about endurance events/races is that it forces you to confront your limits both mentally and physically. Completing your goals and pushing yourself not only gives you a feeling of success, but extends deep into your life from family to your career. With enough practice, anything is possible!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BX2CZohHmWXWLHwetkOWKw.png" /><figcaption>60 mile course from Harpers Ferry to Washington DC.</figcaption></figure><p>Pending I am in good health next year, my intention is to take on a 60 miler on the C&amp;O Canal trail into Washington DC. I’ve worked out my plan, setup my training and now it’s just time to execute. But first, a little winter break. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69945306f376" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Series: Accounting]]></title>
            <link>https://9bplus.medium.com/experience-series-accounting-339e30bb177a?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/339e30bb177a</guid>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Sat, 09 May 2020 21:05:26 GMT</pubDate>
            <atom:updated>2020-05-09T21:05:26.042Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*5IYKUp74mvYnx6uU2z_aTg.gif" /><figcaption><a href="https://dilbert.com/strip/2011-02-03">https://dilbert.com/strip/2011-02-03</a></figcaption></figure><p>This post is part of my <a href="https://medium.com/@9bplus/on-building-companies-and-products-612e9d2f4652?postPublishedType=repub">Experience Series</a> where I share opinions I have formed from building companies and running product. Each posting is a break down of a company function. This post focuses on accounting specifically.</p><p>Unless you enjoy wasting money, you are going to want to track your expenses. Do that with a spreadsheet or free service. Even if you don’t make any profits, you still need to file taxes.</p><ul><li><em>This seems obvious, but some people just throw expenses on their credit card and pay the bill each month. When you are running a small business, you should constantly be evaluating your spend and justifying the services you pay for each month.</em></li></ul><p>When it’s time to file taxes, work with an accountant to maximize your losses and handle your write-offs. Do not file your own taxes.</p><ul><li><em>Apart from time saved, having someone else do your taxes moves the liability over to them. It’s easy to make a mistake and just not worth the time.</em></li></ul><p>Setup a separate bank account for your business and get a debit card or some way to pay for services. This makes tracking expenses much easier.</p><ul><li><em>Setting up a new account takes less than an hour and once it’s done, there’s no need to do it again.</em></li></ul><p>Project your burn rate for the company and know how long you can be alive based on your spend. Models are free, so build them out. Worst case, best case, whatever case you want. Don’t let your accounts go to zero.</p><ul><li><em>Another easy step that a lot of people don’t do. Just because your business is doing well this quarter, doesn’t mean it will the next. Ensure you do not overspend and that you can actually project your revenue for the year and beyond.</em></li></ul><p>Learn to be thrifty and take pride in getting the best price. If you are paying for services, see if there is a discount for small businesses. If you want a discount, consider offering up a testimonial or some well-formed product feedback. If you can hack a small solution together instead of paying, do that.</p><ul><li><em>Notice I state discount, not “free”. Asking for free services can offend some people, especially if they are trying to build a business just like you. Value does not always need to be in the form of money and it’s clever ideas like that which can get you discounts.</em></li></ul><p>Taxes can be complicated. If selling in other countries outside the United States, make an attempt to understand what’s required of your business or consult an accountant.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=339e30bb177a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brandon’s Coffee Journey Guide]]></title>
            <link>https://medium.com/split-key-coffee/brandons-coffee-journey-guide-c79c4d524e9?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c79c4d524e9</guid>
            <category><![CDATA[coffee-roasters]]></category>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[coffee-culture]]></category>
            <category><![CDATA[specialty-coffee]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Sat, 04 Apr 2020 17:24:59 GMT</pubDate>
            <atom:updated>2020-04-04T17:31:24.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnvuPktQdJJC4NETf1I-2w.jpeg" /><figcaption><a href="http://bipartisancafe.com/wp-content/uploads/2016/01/journey-game-color-1024x512.jpg">http://bipartisancafe.com/wp-content/uploads/2016/01/journey-game-color-1024x512.jpg</a></figcaption></figure><p>Coffee plays a large role in my life and has for quite some time. My first real exposure to coffee happened to be that of the specialty grade––I know, lucky me. My quest evolved into learning about different brewing methods to the importance of water and then transitioned into the bean itself with roasting and speaking with those involved in the trade.</p><p>I’ve put this guide together as a resource to help others who want to delve more into coffee. I am commonly asked by friends and others in my network where to start and it always depends where they are on their journey. Below, I outline the different stages of coffee from my view and what it means to be at that stage. No matter where you are in your journey, there’s always an opportunity to learn more!</p><h3>Who are you?</h3><p>In speaking with friends, family and those on the Internet, I have identified 5 different types of coffee people. Naturally, there’s some overlap and not everyone falls cleanly within a single category, but this is a good summary. I view coffee as a journey, so don’t worry, you have time to work your way up the ranks, pending you care, but hey, that’s why you’re here!</p><ol><li><a href="#128d">The On-the-Go Drinker: Starbucks is my choice, can I do better?</a></li><li><a href="#de6e">The Dabbler: I am willing to invest a bit in coffee.</a></li><li><a href="#0b2e">The Half-Way Hipster: Living life on the coffee edge.</a></li><li><a href="#1cf5">The Artisan: I’ve seen the light, now what?</a></li><li><a href="#480c">The Addict: Take me all the way down the rabbit hole!</a></li></ol><h4>The On-the-Go Drinker: Starbucks is my choice, can I do better?</h4><p>If you fall within this category, coffee is more of a caffeine vehicle to you and less about the “experience”. In fact, your taste is tainted, as Starbucks––and most other commercial companies––burn their beans, giving it a charred flavor. Any nuance or unique qualities within the bean are lost as you move more towards producing charcoal.</p><p>It goes without saying, you can totally do better. Next time you’re out and about, consider visiting a speciality coffee shop. These used to be tough to find, but almost every major city has at least 2–3 good shops within walking distance of a major chain. Search for “specialty coffee” or “coffee roaster” to help you identify a location.</p><p>When you get there, regardless of your typical drink order, go for a black coffee––it can be drip, a pour-over, french press or whatever other fancy method. Aim for a single origin, ignore the price and take a seat. Enjoy the coffee. Savor the flavors and if the cashier hasn’t already told you what to expect, ask them about the profile of the cup.</p><p>My work here is done, you’re welcome.</p><h4>The Dabbler: I am willing to invest a bit in coffee.</h4><p>The journey has begun. Maybe you experienced great coffee out in the wild, or you’re finally ready to up your game at home. Whatever the reason, welcome. I tend to find most of my friends and family land within this category.</p><p>Coffee drinkers here recognize their home setup could be better, but it’s not clear where to make investments. The dabbler range could best be described as the “tipping point” in which you’ll go deeper into the journey, or you will settle into “good enough”. Either is fine, but this is the defining stage––time and money dictate your next move.</p><p>When you get coffee to go at your local shop or roaster, you want freshly roasted, whole bean coffee. Regardless of your machine setup and brewing method, the first step to better coffee at home is getting yourself a burr grinder––I’d explain the value here, but a quick Google search will yield tons of results. Trust me, go with burrs. Entry level items like the <a href="https://baratza.com/grinder/encore/">Baratza Encore</a>, <a href="https://www.capresso.com/coffee-grinders/conical-burr/infinity-plus-conical-burr-grinder-black-1-1.html">Capresso Infinity Plus</a> or <a href="https://www.kitchenaid.com/countertop-appliances/coffee-products/coffee-grinders/p.burr-grinder.kcg0702er.html">Kitchen Aid Grinder</a> are all fine choices.</p><p>Using fresh (2–3 weeks past roast date) beans and grinding just before brewing is going to change your coffee experience. If you’re not measuring your coffee, consider doing that too. A good ratio would be 15 parts water to 1 part coffee (e.g. 20 grams of grounds should yield 300 grams of coffee).</p><h4>The Half-Way Hipster: Living life on the coffee edge.</h4><p>You’re drinking speciality on the go and at home. Hell, you may be actively converting your latte-loving friends. At this stage, you’re taking note of the fancy coffee shop gear and wondering how the hell you ever drank from a Keurig machine––don’t worry, we’ve all done it. It’s now time to select your brewing method of choice.</p><p><strong>Standard Drip</strong>––If you’re needing multiple cups of coffee per day or servicing a small army, you may want to stick with the standard drip method. I’ve heard good things about <a href="https://us.moccamaster.com/">Moccamaster</a> products and experienced them at a few shops. This should be my knee-jerk go-to option for batch coffee.</p><p><strong>French Pres</strong>s––Easy, versatile and convenient. Add some grounds, pour in some water, wait a few minutes and plunge. Pretty hard to mess up this method and it’s a cheap way to make 1–3 cups without having to devote too much time to the coffee gods. You can find a French Press anywhere.</p><p><strong>Pour-over</strong>––Those looking to introduce a bit more theater into their brewing or simply want to filter out the coffee oils will want the pour-over. <a href="https://www.chemexcoffeemaker.com/">Chemex</a> or <a href="https://www.amazon.com/Hario-Ceramic-Coffee-Dripper-White/dp/B000P4D5HG">V60</a> are good options here. I personally prefer a manual approach, but <a href="https://www.chemexcoffeemaker.com/ottomatic-2-0-coffeemaker.html">automation</a> has crept onto the scene and I’ve heard good things.</p><p><strong>Aeropress</strong>––Initially intimidating, but beautifully simple. This is a cheap way to brew coffee and it doubles as a good travel device. The nature of the <a href="https://aeropress.com/">press</a> forces you to experiment with ratios, but that’s part of the fun.</p><p><strong>Espresso</strong>––The ultimate. Be weary of diving deep in espresso as all options lead to thousands of dollars. Sure, you can find plenty of options under $2,000, but to do the coffee justice, you need to spend a lot more. If you’re hell-bent on milk drinks, go for it. Otherwise, grab espressos at the local shop and brew larger cups at home.</p><p>There’s a few other methods to brew coffee out there, but the above are the most popular. Find the one––or many––that best suite your schedule and tastebuds you rebel, you.</p><h4>The Artisan: I’ve seen the light, now what?</h4><p>You’re buying beans from the local shops and not even ordering a cup of coffee as your home setup is just as good. You’ve experimented with a few brewing methods and have started to understand the tasting notes printed on the designer coffee bags. Coffee is to be respected.</p><p>If you’ve reached this stage in the journey, congratulations. Prior to this point, changes you’ve made to your process would net big gains in quality––those days are mostly over. From now on, you will spend cash on gear that refine your process, but don’t always translate into easily identified gains in the cup. None of that matters though because you’re an artisan. You will perfect all the things.</p><p><strong>Scales</strong>––If you aren’t in double-digit weight precision, it’s time to fix that. <a href="https://acaia.co/">Acaia</a> is the Apple of coffee scales––they look good, function well and are expensive. You should be weighing your beans and your output every single time you brew, no excuses.</p><p><strong>Boilers</strong>––Maybe you used a pot of water or you’re already leveraging an electric kettle. Chances are you haven’t thought about pour-rates and flow. Don’t worry though, there’s products for that. In the past, I’ve used the <a href="https://www.amazon.com/Bonavita-BV382510V-Variable-Temperature-Gooseneck/dp/B005YR0F40">Bonavita Gooseneck Kettle</a>, but after 3 of them dying on me, I went with the <a href="https://fellowproducts.com/collections/heat/products/staggekg">Stagg EKG</a>.</p><p><strong>Grinders</strong>––Whatever grinder you had before this was “okay”, but it’s time to consider an upgrade. Consistency and expense go hand-in-hand when it comes to coffee, so expect to shell out some more coin here. I use a <a href="https://www.seattlecoffeegear.com/nuova-simonelli-grinta">Nuova Simonelli Grinta Grinder</a> for my daily brews and a <a href="https://clivecoffee.com/products/compak-e5-espresso-grinder">Compak E5 OD</a> for espresso. What you ultimately choose will depend on whether or not you plan to go full addict or you stay artisan. If espresso is important, consider a price tag of $600 and up. If it’s not, under $400 will get you a great daily grinder.</p><p><strong>Vessels</strong>––You put all this cash into your brewing, why stop there? In all seriousness, getting nice glasses or ceramic cups add to the coffee experience. No specific recommendations here, but it’s one of the few areas where you can inject some style and some of your own personality. Have fun with it.</p><p><strong>Miscellaneous</strong>––There are tons of other items you can buy. A few items I own that do not fit easily within a category would be storage (where you keep your coffee), brushes (for cleaning), travel grinder, dosing vessels (for distributing grounds), tampers, ground distributors, and tasting charts.</p><p>And you thought you had it all figured out! Like I said, none of the above––sans the grinder––are going to make an extreme difference in coffee output, but it does add to the experience.</p><h4>The Addict: Take me all the way down the rabbit hole!</h4><p>If I’ve brought you this far, sorry, not sorry. I assume at this point you are doing all of the above and are contemplating one of the three options.</p><ol><li><strong>Espresso. How the hell do I produce the god shot?</strong></li></ol><p>To answer directly, consistency. Espresso is an extremely violent process and a lot needs to be done correctly to produce a great shot. You need to be thinking about every single stage of the coffee.</p><p><strong>Beans</strong>. Where are they from? When were they roasted? What stage of roasting did they get to? How fresh are they? <strong>Water</strong>. Is the water the right temperature? Does the group head stay hot? Is the pressure correct? Is the water balanced? <strong>Grind</strong>. Is the grind consistent? Is it too fine or too coarse? Is the coffee stale? How many grams were weighed? When was the grinder last cleaned? <strong>Tamping</strong>. How much pressure was applied? Were the grounds evenly distributed? Is the tamp even and level? <strong>Brew</strong>. Is the machine able to produce enough pressure? Is the machine too hot? How long has the machine been on? Is the filter obstructed?</p><p>To find answers, you need to experiment, do your research and spend some cash, that’s it. Good luck!</p><p>2. <strong>Roasting. This appears key, how do I control it?</strong></p><p>You are correct in noting that roasting is a critical step in the coffee process. Roasting is where the true characteristics of the coffee are created or killed––under-roasted beans lead to a grassy, bitter cup and over-roasted beans kill any nuance and tastes like charcoal.</p><p>Bringing this process to your home is possible through a number of small home roasters, but the return is not quite what you’d expect. If you like to learn, have some cash to spend and enjoy coffee as a hobby, then home roasting is for you. I would not encourage someone to do home roasting as a means to save on spend or because you think your quality will be better than a local shop.</p><p>If you fall into the home roasting camp, I’d say to check out a <a href="https://www.hottopusa.com/">Hottop Roaster</a>. It’s cheap enough that you can eventually net even on the expense, has built-in controls for roasting without the need for a computer, and has a USB-interface which lets you read/control the roaster through other software. If you’re like me, you may even opt to <a href="https://github.com/splitkeycoffee/split-key-roast">write your own roasting software</a>.</p><p>For green beans, <a href="https://www.sweetmarias.com/">Sweet Marias</a> is a great resource and offers a wide range of coffees from multiple origins. The prices are reasonable and the service is great.</p><p>As mentioned above, home roasting quality may not be better than your local shop. Much like espresso, roasting is heavily reliant on consistency––airflow, heat, time. Smaller home solutions have all these elements, but because of their size and lower price, you will not get the same tools that you would in a commercial grade roaster. As a result, coffee from a home roaster is more likely to be less consistent and thus may hide or bury some of the unique elements of the coffee you purchase. All that said, it’s still possible to produce great coffee.</p><p>3. <strong>Farming: Can I grow my own coffee?</strong></p><p>No. Go visit a farm and support those who’ve made coffee their life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c79c4d524e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/split-key-coffee/brandons-coffee-journey-guide-c79c4d524e9">Brandon’s Coffee Journey Guide</a> was originally published in <a href="https://medium.com/split-key-coffee">Split Key Coffee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Series: Legal]]></title>
            <link>https://9bplus.medium.com/experience-series-legal-3229ccd92c4e?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3229ccd92c4e</guid>
            <category><![CDATA[legal]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[advice]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 17:48:01 GMT</pubDate>
            <atom:updated>2019-12-31T19:57:27.743Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*S8ryuViG3F5-JLE9qX1z2g.gif" /><figcaption><a href="https://dilbert.com/strip/2011-02-25">https://dilbert.com/strip/2011-02-25</a></figcaption></figure><p>This post is part of my <a href="https://medium.com/@9bplus/on-building-companies-and-products-612e9d2f4652?postPublishedType=repub">Experience Series</a> where I share opinions I have formed from building companies and running product. Each posting is a break down of a company function. This post focuses on legal specifically.</p><p><strong>Standard disclaimer––These points are just my personal experience and the way I operate. It’s not intended to be a replacement for actual legal advice, nor does it represent any views but my own. I am not liable for the decisions you make.</strong></p><p>If you are building out a company, register it and make it official. Having an entity afford you some small protections, gives a more professional look and allows you to begin splitting up your expenses.</p><ul><li><em>For PassiveTotal and most of my companies, I register in Delaware and use Legalzoom. It costs about $300 and I handle nothing. When it comes to getting your EIN, do it yourself and save the cash; it’s free to get that on the IRS website. One slight change I would make today would be to register locally so that I don’t need to have Legalzoom be my representative agent in the state.</em></li><li>P<em>assiveTotal, NinjaJobs and Split Key Coffee are all LLCs, nothing special. I like having an LLC because it makes taxes simple and there’s no structures to work out. Despite what some may think, you can take seed funding with an LLC too. It’s worth exploring the different types of companies that exist to find the best fit for you.</em></li></ul><p>Make sure you have an NDA drafted and definitely have NDAs and IP assignment agreements with employees and all contractors who could possibly touch your technology (no exceptions).</p><ul><li><em>More importantly, make sure you can trust the person or organization you’re working with. Contractual paperwork is not going to bridge the trust gap between two entities. If trust isn’t there, just consider revisiting the relationship later on or not at all.</em></li></ul><p>Preferably, have people sign your paper, but if you are forced to use someone else’s, spend the time to read it and note any weird clauses.</p><ul><li><em>Early in the days of PassiveTotal, we were passed an agreement that would allow us to use another companies data within our product. The agreement itself was structured more around a joint sales go-to-market where we were beholden to selling the other data set whenever we sold our own product. Our intention was to be a lead generation source for the other company, not a forced sales staff. In the end, we passed on the agreement and found other data partners to work with.</em></li><li><em>As a further reason to read contracts no matter what––a lawyer friend shared one of his techniques with me of planting typos and grammar mistakes across paperwork. If they went unnoticed, he would know the agreements weren’t reviewed carefully. The goal here wasn’t to introduce anything malicious, but simply assess the emotional effort on the deal and diligence in review.</em></li></ul><p>Always have a paper trail when working with partners, vendors, advisors or anyone else who could potentially bring you issues later on.</p><ul><li><em>Assuming your company gets purchased, that business is going to want any loose-ends closed out. Better to have the paper work up front than to go have go back and get it later.</em></li><li><em>Whatever paperwork you put in place, also make sure that it has the business in mind and plans for worst case scenarios.</em></li></ul><p>Lawyers are expensive, use them strategically. Try your best to read any paperwork you get yourself and highlight the areas where you think there is risk or have questions. Have the lawyers focus there. If it’s serious business, have them review the whole thing.</p><ul><li><em>Whenever I hear someone complain about lawyers and the cost, I have to wonder what their relationship looks like with their counsel. If you choose to use a lawyer as an extension of your full time staff––giving them a feed of work, not checking in as often, not limiting your requests––then expect to pay a lot. On the flip side, if you use them more as a consultant or advisor, you’ll see lower costs and likely have a better relationship.</em></li></ul><p>A good set of terms and conditions and privacy policy can go a long way on your application. If fleshed out well, you can drastically reduce the language in your master services agreement (MSA).</p><ul><li><em>This insight was the result of working strategically with good lawyers who functioned like partners, not staff. When we first created PassiveTotal Enterprise services, we knew we would need a master services agreement to close any deal. After speaking with our lawyers, they took a step back, understood what we were trying to achieve and suggested the route of heavier terms of service and privacy policies over bloating the MSA. Reason being, a heavy MSA would likely get redlined during procurement whereas one with generic, straight-forward language would likely go through without issue.</em></li></ul><p>Keep your intellectual property clean. If you are going to moonlight, declare your work with your employer and have it exempt from your agreements. If you are leaving a position to create your product, make sure you aren’t risk of getting sued from your current employer. Hint, don’t be a jerk on the way out and wait a month.</p><ul><li><em>This is one point never to ignore, especially these days when working at technology companies. Most friends I talk to who are considering creating a company aren’t aware of what their current employment agreement says. Unfortunately for many, their agreements are liable to be sweeping in that any derivative or related work created at the company is the companies property. Read your agreements before you sign them and always declare your work. It’s extremely rare that a company would ever sign paperwork allowing you to declare a work later on.</em></li><li><em>I’ve had numerous ideas that could have been companies die within the walls of a private organization. It was frustrating to know the company didn’t want to make money from the idea, but also didn’t want to let it go. Here’s the harsh reality––that company is covering your salary and gave you the opportunity and space to create that idea, it’s their prerogative to do what they want with the idea. If you feel strongly otherwise, quit and make the dream into a reality.</em></li></ul><p>A lawyer’s job is to point out risk, not tell you what to do. They should enable you to make intelligent, informed decisions. Learn to think like they do and play out every scenario you can. Expect the best, prepare for the worst. And by prepare, I mean have yourself covered via contract or something else.</p><ul><li><em>Building a business requires you to think like this already, but you especially need to do it when protecting your ideas and intellectual property.</em></li></ul><p>Risk profiles increases once you start accepting money. Most people are reasonable, but if you breach your terms, expect that someone may want their money back. Don’t fight them, learn from your mistake.</p><ul><li><em>More common is that a business will ask for a discount or more services if you breach your contract. Same rules apply, learn from your mistakes and take some solace knowing that the customer is now getting even more of your service than before.</em></li></ul><p>Extending the risk profile into the current market––if you’re collecting personal data, understand what that means in the event of a breach. Could you be fined? Do you need to take certain steps to protect the data? Can you avoid the liability altogether? Data privacy laws are rapidly evolving in the technology world and if you intend to collect sensitive data, it’s on you to understand the risks and what you need to be doing.</p><p>Threats should be rare, but recognize they could occur. Like IR, a legal threat is extremely stressful and you may not be thinking straight during the process. Have details for a lawyer beforehand just in case. No need to retain, just have someone you can call.</p><ul><li><em>Been here, suffered through it. For me, documenting and detailing helped keep me grounded during the process. Beyond a lawyer, also have a friend you can talk to as it’s helpful to get another perspective on the situation.</em></li><li><em>Keep in mind, an inbound threat may not be based on any real foundation, but that doesn’t mean a court won’t hear the argument. If you choose to fight, be prepared to spend a decent amount of money, time and most importantly, sanity in going through the process. Sometimes it’s better to concede, even if you believe you’re right.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3229ccd92c4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Series: Operations]]></title>
            <link>https://9bplus.medium.com/experience-series-operations-7b1852c8ed4b?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b1852c8ed4b</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Fri, 27 Dec 2019 16:40:16 GMT</pubDate>
            <atom:updated>2019-12-27T16:40:16.568Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*SAxWrRn1Rpe9v9ka5aDqAg.gif" /><figcaption><a href="https://dilbert.com/strip/2001-03-27">https://dilbert.com/strip/2001-03-27</a></figcaption></figure><p>This post is part of my <a href="https://medium.com/@9bplus/on-building-companies-and-products-612e9d2f4652?postPublishedType=repub">Experience Series</a> where I share opinions I have formed from building companies and running product. Each posting is a break down of a company function. This post focuses on operations specifically.</p><p>No one ever plans for systems to stop working, ensure you have back-ups and that they are tested on a regular basis.</p><ul><li><em>About a month after launching PassiveTotal, our primary database node ran out of disk space, causing everything to halt. In a panic, I was on the command line trying to free up space only to accidentally typo and remove a portion of our journal file. Database, corrupted. Backups, none. Complete failure that could have been avoided in so many ways. Fortunately, we were barely off the ground and most people were understanding.</em></li></ul><p>Back-up locally and to some cloud-based service that supports strong, multi-factor authentication.</p><ul><li><em>After the database deletion with PassiveTotal, I went above and beyond on backups, so that we’d never have an issue like that again. Cron jobs were set to backup key portions of the database on every hour, every day and every week. Each of these remained encrypted locally on the machine and were then securely posted to a cloud service with 2FA enabled.</em></li><li><em>With PassiveTotal, we never ran into a major issue like we did the first time, but we did encounter cases where database nodes would become out of sync, causing data inconsistency. Having snapshots at multiple times from multiple databases was helpful in piecing together the proper database.</em></li></ul><p>General operations rule of thumb––bad things happen at the worst possible times, just get used to it. Always have a means to fix a problem, no matter how remote you are––or better yet, train someone else.</p><ul><li><em>I was flying to Memphis in order to see Steve when one of the PassiveTotal application front-ends failed. I had just landed in Chicago and needed to make my connection, but also try and fix the problem. I managed to SSH into the serve from my phone, work some magic to get the service back up until I could properly troubleshoot.</em></li><li><em>Attending a conference on the beach, I ran into one of my NinjaJobs customers who jokingly said I should fix my service if I am going to be out on the beach. Turns out I had introduced a bug in my last commit, and it was impacting their job posting. I ran back to my room, identified the issue and pushed the fix to production.</em></li></ul><p>Use local or 3rd-party services to track the health of your product and company resources. If your customer is your way of finding out something is wrong, you are in a bad position.</p><ul><li><em>Even with numerous services monitoring your application, this can still be tough to get right. To this day, I will still occasionally find a customer or friendly-user letting me know something is off with one of my products, only to find a monitor had a gap or alert was routed to the wrong location. It’s rare, but it still happens. Keeping your services healthy 24/7 is a tough business, especially when you continue to grow.</em></li><li><em>For PassiveTotal and NinjaJobs, I liked using Datadog to track the health of our services. The agent would look at general host performance––network, disk, IO, memory––and application performance––key services running, processes in place, etc. All alerts were set to trigger on Slack, email and via text message.</em></li><li><em>For Backscatter.io, I wanted to take a more manual approach in order to save money, so I went with Nagios. It’s a lot more work to manage your own local monitoring, but if you intend to spin up hundreds of servers, it ends up being worth it for cost savings.</em></li></ul><p>Testing your application is a pain. Consider using 3rd-party services to automate integration and functional tests in order to save time and catch bugs before your customers do.</p><ul><li><em>To this day, I am poor at writing great test harnesses. In fact, if I am not making money on a project, I will seldom write them. For the 95% of the time when no issues are caused, I feel great, but it’s that 5% introduction of bugs that breaks the application that really make me wish I had those tests.</em></li><li><em>With PassiveTotal, we didn’t introduce much in the form of tests until after RiskIQ purchased the company. Immediately, we put integration test coverage in place with GhostInspector. This was helpful for ensuring key processes like login, registration, running a search, and getting to settings, all functioned properly.</em></li><li><em>At RiskIQ, we eventually rewrote PassiveTotal and can now happily say that the platform has great test coverage––no thanks to me, but still a big win.</em></li><li><em>Once I saw the magic of integration testing within RiskIQ, I ported that same logic over to NinjaJobs and automated the same key process analysis. This suite of tests has saved me over and over from introducing a breaking bug into the platform.</em></li></ul><p>Assuming you are working with more than one person, have a means to communicate amongst each other. Ideally, send your first-pass alerts there and fall back to email.</p><ul><li><em>At the smaller end (less than 10 people), I think Slack is the best fit for these communications. The cross-platform nature is great and they integrate with nearly every service. Slack was invaluable when Steve and I ran PassiveTotal.</em></li><li><em>As a company grows and more people are added, it’s easy to ignore a Slack alert or filter out email. Phone calls can be ignored too, but are more effective alerts when an outage takes place. When I worked at Facebook, they had a system that would escalate calls from you (the committer) all the way to the CEO pending no one answered their phone––someone always answered before that.</em></li></ul><p>Being able to teardown and stand-up your services at will with no business impact is as glorious as it sounds. It takes a lot of work, but it’s worth it when you run into issues later on. Notice I said “when” and not “if”.</p><ul><li><em>When I first wrote PassiveTotal, I had no idea all the ways you could automate system deployments. We started with a single node that ran the whole company and slowly branched out to have multiple web frontends, multiple backend database nodes and tons of services that were called by the primary application. Anytime we had issues, I was rebuilding by hand with a checklist, hoping I got everything right. Fortunately, we never hit any major snags due to this, but man, it was a lot of time wasted.</em></li><li><em>In building Blockade.io, I wanted to try out building an application that existing completely in the cloud with no true server presence. Completing that project was magical––the setup eventually became completely automated using AWS APIs. There’s nothing cooler than pressing a button and watching an application manifest itself from nothing but a configuration file.</em></li><li><em>For Backscatter.io, I went one step further in my configuration building. Aside from automating the provisioning of machines, I also automated the installation of the service and logging components using OS packages. Install steps normally done by hand were all automated with tests inside of a Debian package. Automating the provisioning process is one of the most satisfying feelings.</em></li></ul><p>Logging should be baked into your application, but ensure those logs flow to a central location that you can query.</p><ul><li><em>When I initially wrote PassiveTotal, logging was baked into the application through simple statements. This was better than nothing, but not highly effectively for measuring application performance or troubleshooting at scale. Over time, we migrated from internal logging over to using a combination of open source performance monitors and paid services.</em></li><li><em>As a general security tip, be sure to avoid leaking sensitive information within your logging––think passwords, usernames, tokens, etc. In a development environment, you may want to have these, but they should never go full production.</em></li></ul><p>Split your corporate website and status pages from your application. If you product needs to go down for updates, it should not knock your business offline.</p><ul><li><em>All of my older applications used to bake the corporate website within the application itself. While convenient, it was annoying to manage and made it difficult to communicate to users during maintenance periods. These days, I favor hosting the primary website in something like S3, using an “app” subdomain for the core application and outsourcing the status page to a paid service.</em></li></ul><p>Patch your machines, apply updates, do all the normal work we all love to heap onto everyone else. You start to get a sense for how annoying this is when you update and break your production build.</p><ul><li><em>Managing PassiveTotal brought on a good dose of security medicine. I can’t count how many times I just decided to update our server without checking versions, only to find the application broke or specific logic no longer functioned like it did before. After breaking production several times during patch cycles, we instituted a process to stand-up development machines, perform patching tests and then roll-out during planned maintenance periods.</em></li><li><em>Container technology has come a long way since some of my early projects. If I were to build anything today, I would implement the use of containers just to maintain consistency in my deployment process.</em></li></ul><p>If people are paying you for a service, chances are high you agreed to some SLAs. Don’t breach your contracts, keep your systems up and running.</p><ul><li><em>As indicated by blurbs mentioned above, PassiveTotal went down a number of times in our early days. Most of our customers were understanding and didn’t bother to use this against us. As the product has grown within RiskIQ, it’s a different story. There’s an expectation of maturity and service levels being met. When they aren’t, you can expect a customer to request a discount, or credit to their account for the lapse in delivery. It’s annoying as no system is ever perfect, but a reality you need to live with.</em></li></ul><p>Implement measuring tools inside of your application stack to identify hot spots or areas that could be further optimized. Establish a baseline and chip away at the performance updates when you are waiting on idea feedback.</p><ul><li><em>In the early days of PassiveTotal and NinjaJobs, we didn’t have any great application performance monitoring. As the services grew over time––both in data and users––these monitoring services became invaluable. Bad code that worked for a handful of users would eventually fall apart at scale, resulting in a degradation of performance or an outright failure despite no code changes. Using application performance monitoring allowed us to not only gain insight into why a failure took place, but let us become more proactive by addressing hotspots before they become failures.</em></li></ul><p>If you’re constantly pushing out new features or changes to your product, invest in a fully replicated development environment.</p><ul><li><em>PassiveTotal has grown in complexity since RiskIQ purchased the company. These days, changes are being made to PassiveTotal every day, with pushes sometimes happening several times a week. Testing in production isn’t an option. In order to ensure builds are being tested beyond what’s been automated, a separate development environment has been stood up. This staging environment lets internal users “dogfood” the application prior to a production release and also offers up a good test bed for our provisioning processes.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b1852c8ed4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Series: Sales]]></title>
            <link>https://9bplus.medium.com/experience-series-sales-1e3f2090ead1?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e3f2090ead1</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Fri, 01 Nov 2019 18:57:48 GMT</pubDate>
            <atom:updated>2019-11-01T18:57:48.825Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aiZiEdSFf_yXqQR_gViw-g.gif" /><figcaption><a href="https://dilbert.com/strip/1992-12-15">https://dilbert.com/strip/1992-12-15</a></figcaption></figure><p>This post is part of my <a href="https://medium.com/@9bplus/on-building-companies-and-products-612e9d2f4652?postPublishedType=repub">Experience Series</a> where I share opinions I have formed from building companies and running product. Each posting is a break down of a company function. This post focuses on sales specifically.</p><h3>General Opinions</h3><p>It’s easy to “show up and throw up” on a demo. That’s not doing sales, that’s you talking the entire time. Do prep work prior to meetings, have a plan and spend as much time as you can doing discovery with the prospect.</p><ul><li><em>During the early days of PassiveTotal, we were proud when we managed to get our product pitch down to 45 minutes. These days, I won’t even open a deck unless proper discovery has been performed and there’s a clear need for the product. Respect your time, and the time of the prospect.</em></li><li><em>Looking back, we spent so much time speaking and not enough time listening. Prospective customers will happily tell you all the ways their existing solutions don’t work or the challenges they face or what their boss has asked them to do. They can’t do all that though if you are spewing your pitch. Ask good questions and align the answers to your solution’s value.</em></li><li><em>In terms of prep work, you should know who you’re talking to––their work history, how they fit into the business, who their manager is and who their peers are. You should have a set of discovery questions you can ask to uncover pain points, understand the team and direct the conversation towards your product. Finally, you should have a way of taking notes and being clear on action items.</em></li></ul><p>Define a set of sales stages as best as you can. There’s resources out there to help here, but you want to ensure you are able to track progression of deals. Not every lead is an opportunity.</p><ul><li><em>Sales is a nuanced process and is not simply “sold” or “not sold”. As you enter an account, it naturally works through stages like “first meeting”, “product pitch”, “budget identified”, “price shared”, “trial started/completed”, “procurement approval”, “purchased”. Reflecting these stages lets you better track where you are in the purchase cycle and likelihood the deal will close. If too much time passes, it’s best to make the hard decision and remove the deal from your pipeline.</em></li><li><em>When we first started out with PassiveTotal, we had no clue that sales cycles would last anywhere between 3 months all the way to 9 months. There’s a whole lot that happens between your technical champion saying they want to buy your product and the organization actually signing off to purchase it. And even then, you still need to wait for your money.</em></li></ul><p>If at all possible, use metrics and happy paths as a means to score leads or help auto-progress deals through stages. This will save you time and help you focus on which accounts to target.</p><ul><li><em>PassiveTotal was a freemium platform and so we were seeing new users register every day. If we tried to pitch every single user who registered, we would have never gotten anything done. To help separate the signal from the noise, product metrics and user data (company size, industry, etc.) were factored into our lead sorting. Active user part of an established organization targeted by threats? Engage.</em></li></ul><p>If your product allows for prospecting, go for it. A great way to start a conversation is to show the prospect something about them that may peak their interests.</p><ul><li><em>You should really know your audience before going down this route. In PassiveTotal, our users tend to value their privacy more than a normal user and do not take kindly to random contact from a vendor. This is the opposite case in NinjaJobs though where someone is always willing to engage with someone interested in helping them find a new job.</em></li><li><em>If you decide to engage, show up with something worthwhile––again, respect the time of your users. If someone just downloaded a recent whitepaper from your website, ask them what they thought of it or what had them interested in that sort of topic? Reaching out and immediately going into pitch-mode is unlikely to be successful.</em></li></ul><p>Respect your buyer and their time. Don’t be late, come prepared and follow-up once you have had the meeting. This goes for post-sales too.</p><ul><li><em>Follow-up can’t be stressed more. If you say you are going to do something, do it. Unless you have a product that’s absolutely needed by everyone, it will always be up to you to prove your value in order to move the deal forward.</em></li><li><em>I recall being on a tropical island for a conference and speaking with one of my clients from NinjaJobs. They made a side jab that I was here having fun while their job post was having issues being displayed. It was so embarrassing to hear this. I immediately left, went to my room, identified the issue, fixed it and pushed it live to production. If someone is paying you money, you owe it to them to ensure the product works.</em></li><li><em>When’s the last time you attended a meeting and thought to yourself, “I wish that person spoke longer”? Chances are high that’s never crossed your mind and those you pitch are likely the same way. Be crisp, get to the point and avoid a bunch of fluff.</em></li></ul><p>Opportunities open more than 90 number of days without progression should be closed and considered stalled.</p><ul><li><em>Never aging out opportunities just leads to a messy sales pipeline where you can’t reliably predict what is likely to close. 3 months with no interactions or progress is the sign you are dealing with the wrong person inside of the account, you have not shown value or what you are aiming to solve is not a priority. Add these leads to your marketing nurture tracks and move on.</em></li></ul><p>Use a CRM (Salesforce isn’t the only solution) that has a good API, flexible data model and ideally auto-populates details about contacts.</p><ul><li><em>Before PassiveTotal released an enterprise product, we had decided to wire in the HubSpot’s CRM into our platform. Registrations, logins, activities and marketing were all tracked and associated with leads in the system. This simple concept allowed Steve and myself to really scale the business with only two people. Each day, we each reviewed our queues of activity––me on the product usage side and Steve on leads and opportunities. Another benefit to HubSpot was their email tracking plugin that would associate actions or follow-up activities directly to the lead in the platform.</em></li><li><em>With NinjaJobs, we had a slightly different set of requirements for our sales process in that we needed to support a team of recruiters and the ability to search across resumes. After doing research, I identified CATSOne and wired that into our platform. CATS operated as the NinjaJobs recruitment database, but also generated job orders and tracked platform activities so our recruiters could find the best people for the open jobs.</em></li><li><em>HubSpot has since changed their license model. If I were to do another project today, I’d likely use something like FreshSales, Prosperworks or HubSpot––essentially any platform with an API and way to automate the mundane portions of sales.</em></li></ul><p>At least once a week, analyze the new users inside of your product and figure out who they are. Do they meet your expected audience? Where are they coming from? Are there any patterns in users?</p><ul><li>O<em>nce a day makes more sense, especially when the company is smaller. If you don’t find yourself addicted to the running list of new users entering your product, you may want to reconsider if a startup is the right place for you.</em></li><li><em>Each day, PassiveTotal brought new users into the system from all different parts of the world and from all different types of companies. Using Google Analytics and social media tracking, we were able to identify key channels for getting new users and then formed marketing plans to invest more into those channels. Sometimes these efforts failed to get the traction we wanted, but we always learned from the process.</em></li></ul><p>Word of mouth is the best way to enter an account. Make it easy for your product champions to invite their peers or share elements of your product.</p><p>Procurement is tough no matter who you are. Expect the process to take a long time, especially if you are a nice-to-have product. Keep in mind, you will need to support the user during this process and can’t easily just nuke their accounts.</p><ul><li><em>In the early days of PassiveTotal, procurement wasn’t really a known term to me. As our first deal neared closing, I got a big dose of reality in dealing with the procurement department. More discounts were needed and more justification had to be provided––something we did not plan to for at all. I now know that it’s okay to ask about procurement with your prospect. If they want the product, they may have an idea of the internal sales process or what to expect as paperwork moves through the organization. Take any advantage you in the account.</em></li></ul><p>Know your audience and have clear goals. If you are speaking to technical users, chances are high that they do not have the budget. Your goal is to get them to help you convince their manager to buy your product.</p><ul><li><em>Even when you build strong technical champions, it can be tough to get them to make the case to purchase your product. Align yourself to their goals and even go as far as getting an introduction to their boss or decision maker or helping them craft a message to those individuals. The less work they need to do, the more likely they will help you out.</em></li><li><em>There’s been a few times with PassiveTotal where I have generated a “canned” email highlighting all the benefits of our platform and how it was superior to other solutions in the market. Attached to the email was a data sheet describing the solution for more detail. When I get the sense that we need to prove ourselves in an account, I will pass this email along as fodder that can be used to convince upper management. Sometimes it works, other times it doesn’t.</em></li></ul><p>Influence is not budget. People who say they have massive influence or a silly budget figure probably don’t.</p><ul><li><em>People like this are in their own class of “interesting”. Without elaborating too much, you will know when you come across one and it will be pretty clear they are going to be a waste of time. Be nice, move along or more importantly, get introductions to other team members or departments.</em></li></ul><p>Once you land in an account, let the product do the heavy lifting, but keep the relationship alive. Provide timely support, follow-up with status checks and keep an eye on your users to see if and when they change roles or companies.</p><ul><li><em>At RiskIQ, we call this Customer Success and no matter what you name it, this function is difficult. Getting through the sales process can be a slog, but that’s just the beginning of the customer journey. Once sold, you need to ensure your product is being used and that your users are seeing value. When I say “heavy lifting”, I mean making use of metrics that indicate usage––login, activity, happy-paths, growth, etc. If you notice a decline in any of these values, it’s worth having a meeting to engage the account and ensure it’s healthy.</em></li><li><em>There were times in PassiveTotal where a bug would be surfaced by a client and I would fix it within minutes. To the customer, this was as close to magic as you could get and it created life-long product champions. Naturally, this cowboy-style coding does not scale as you get larger, but when you can, it’s awesome.</em></li></ul><p>Taking money for your product changes your relationship immediately. It doesn’t matter if the buyer is a friend or not. Be professional and deliver their service.</p><ul><li><em>Your early buyers are likely to recognize you are a startup and may run into delivery issues, but minimize this as much as possible. Throwing a price tag on your product implies you’ve went and done the necessary testing to know it will scale to demand or function properly 100% of the time. If that’s not the case, consider delaying your launch.</em></li><li><em>Some of the harshest product feedback I have gotten to this day comes from friends or peers in the industry. While it hurts sometimes to hear, those are some of the same people I call up when I want to test a new idea or get an honest answer to a question. Develop thick skin and expect to get an ear full if you don’t deliver.</em></li></ul><p>Let your friends or peers off the hook when you see them if they claimed they would buy and didn’t. It’s an awkward situation and one they likely have little control over. Best to not hold a grudge and preempt their apologies.</p><ul><li><em>I’ve mentioned this in other points in the series, but this behavior ties into people largely being nice and wanting you to succeed. Try not to get sucked into the hype generated by peers and use metrics to evaluate your sales/marketing/product progress.</em></li></ul><p>People love to talk, so let them. Learn from your prospects and customers — their problems, their organization structure, how their funding works, which competitors they use, what they think of other products, etc.</p><ul><li><em>The more information you have about an account, the market, or your competition, the better. All of this helps you in your sales process and allows you to start building a repeatable process to counter objections, pitch efficiently and get introduced to the budget holders faster.</em></li></ul><p>Use a CRM or integration that allows you to associate email correspondence to your contacts. As a bonus, integrate your calendar as well, so you can see when you had a meeting.</p><ul><li><em>When we started PassiveTotal, HubSpot was our tool of choice. After being acquired by RiskIQ, we switched over to Salesforce and their plugin tools.</em></li><li><em>For meetings and conferences, I’ve had the best luck with Zoom so far.</em></li></ul><p>Your email send-to-recieve ration is going to look something like 90% out and 1% in. Every week, sit down and identify previously sent messages that got no response and try again.</p><ul><li><em>This goes back to following-up and it’s tough. Your days will easily turn into a blur where the email you sent two weeks prior feels like it was only two days ago. Reviewing your sent messages or leveraging plug-ins/email clients that can remind you of one-sided conversations go a long way in ensuring you are always keeping the conversation going.</em></li><li><em>With PassiveTotal and NinjaJobs, we were able to automate some of the first few emails to an account. This saved us a ton of time and helped filter out anyone who may not be as serious about upgrading. By no means did we give up on anyone who didn’t respond, but we did factor it into their likelihood of progressing in the sales cycle.</em></li></ul><p>Order of prospect outreach communications by preference. Call. Call again. Email. Call next day. Email a few days later. Get creative.</p><ul><li><em>If you don’t like being on the phone or giving the same pitch over and over, don’t go into sales. You need to get used to being rejected, ignored, yelled at, misdirected, strung along, and chastised. It’s a tough job and it takes real persistence. With that said, next time a sales person calls you, consider being direct with them and treating them with respect––they are human just like you!</em></li></ul><p>If you’re going to do a demo, make sure there are no bugs and have a video back-up. For the materials, try to personalize the content, but at the very least, ensure it’s not older than 6 months.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e3f2090ead1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Series: Marketing]]></title>
            <link>https://9bplus.medium.com/experience-series-marketing-943f22792313?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/943f22792313</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 14:44:48 GMT</pubDate>
            <atom:updated>2019-09-10T14:44:48.952Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugUsrW4oX6PMN8-dbn_REg.gif" /><figcaption><a href="https://dilbert.com/strip/1994-10-07">https://dilbert.com/strip/1994-10-07</a></figcaption></figure><p>This post is part of my <a href="https://medium.com/@9bplus/on-building-companies-and-products-612e9d2f4652?postPublishedType=repub">Experience Series</a> where I share opinions I have formed from building companies and running product. Each posting is a break down of a company function. This post focuses on marketing specifically.</p><h3>General Opinions</h3><p>Your messaging should be clear and focused on outcomes. What value will a customer get for using your service? Why are you the best solution for them to use? Be concise and to the point.</p><ul><li><em>It’s easy to fall into the trap of describing features of your product instead of how you’ll make your customer’s life better. Keep this in mind when you are generating copy and recognize that even something simple like a registration is an exchange of goods––your customer is giving you their information in exchange to learn more or use a portion of your product.</em></li><li><em>Within cybersecurity today, it feels like everyone is touting the same outcomes, which almost renders the copy useless. Focus on understanding your audience and let your product do the talking.</em></li></ul><p>Respect the “fold”. Use services like Hotjar to measure how users engage on your website and pages in order to optimize what users see first.</p><ul><li><em>When I first developed PassiveTotal, “above-the-fold” was a foreign concept for me. Fortunately, modern frameworks like Twitter Bootstrap protect you and help to fill in the gaps or provide responsive viewing, so we never suffered too much.</em></li><li><em>With NinjaJobs, I had exposure to a lot more tools and ways to optimize a website. I leveraged Hotjar in order to build heatmaps and observe user interactions within our product in order to optimize specific elements. Our first landing page concept lacking any major calls to action (CTA) and buried our recent job postings below-the-fold. Hotjar was able to show me that job postings received the most interaction and helped drive an alternative––and more effective––conversion path.</em></li><li><em>For Backscatter, I again leveraged Hotjar to optimize my landing page, though this time around instead of 5–10 iterations, I easily did over 100, tweaking pixel-by-pixel until I felt every element lined up perfectly. The website needed to load fast, tell a good story and encourage registration.</em></li></ul><p>Much like your product, measure as much as you can on the website. Do users download materials prior to registering? Do those who read your blog progress faster within your sales pipeline? Traffic patterns can be very important.</p><ul><li><em>For PassiveTotal and NinjaJobs, we originally used Google Analytics to track major events from the website to our applications. It’s a great free product and if instrumented properly, you can easily track specific events and maps those to goals.</em></li><li><em>Pre RiskIQ, PassiveTotal leveraged home-grown measurement tools and Hubspot CRM in order to map interactions back to users. This information later fed into Mandrill for transaction emails and Mailchimp for standard marketing campaigns.</em></li><li><em>Post RiskIQ, PassiveTotal was moved over to Marketo for marketing capture. I personally find the platform to be clunky and a bit too expensive for the value we get from it, though it does integrate with a number of other solutions and scales quite well.</em></li><li><em>For NinjaJobs, we track behaviors and interactions using a combination of Intercom, Datadog, Google Analytics, Hotjar and Mailchimp. Ideally, these would be all within one platform, but outbound marketing for the platform is lower and so a manual approach is okay.</em></li></ul><p>The best way to tighten up your messaging is to employ constraints. Describe what you do in 500, 250, 100, 50, 25, 15 words. Be consistent with your copy and use this on your website, presentations and data sheets.</p><ul><li><em>At RiskIQ, it feels like I have produced endless streams of copy and messaging for the work we do within product. I don’t always follow this exercise for every effort I take on, but tend to do it on the larger features or product launches. It’s such a fun and effective way to really hone your messaging.</em></li><li><em>NinjaJobs employed this approach and apart from keeping consistency, it’s also made running the platform easier. New inbound asking about services, copy/paste. Question about what we offer, copy/paste. Filling in sponsorship details, copy/paste. You get the idea.</em></li></ul><p>Make sure you have a data sheet that clearly describes your product and it’s value. If your presentation is successful, someone is bound to ask for it. They plan to send it to their peers or boss in order to begin the purchase process.</p><ul><li><em>When we first started PassiveTotal, we managed to work up a decent presentation––though way too long–– that was received well. Our first stumble was realizing that the presentation was just one step of many in order to further the purchase. Without a data sheet, we were forcing interested users into describing the who, what, and why to their internal team; unless you are 100% required, no one will spend much time justifying the purchase of your product, so make it easy. Data sheets, copy describing your services and price listings are all needed.</em></li><li><em>Assuming you go more of the direct self-services route, you can likely ditch the notion of a data sheet. Your website materials and pricing should be easy enough to follow that you shouldn’t have to bother with mailing information around. This has been our approach with NinjaJobs, but in time, we decided to generate a data sheet just for the rare occasions when a recruitment department needed to get us into their systems.</em></li></ul><p>You don’t need to be a designer to have a good looking website. Pay for a template and modify it to meet your needs. Same thing for a presentation or data sheet. There are plenty of generic templates out there. Truthfully, the design is less important.</p><ul><li><em>Nearly every project I have worked on has started from a generic Twitter Bootstrap template, or was purchased from </em><a href="https://wrapbootstrap.com/"><em>Wrapbootstrap</em></a><em>. I can’t overstate how much time this process has saved me and how it’s made my final output not only cross-platform, but good looking too. The best part with the paid templates is that you continue to get updates year-after-year, meaning you can easily refresh your design.</em></li><li><em>For PassiveTotal, I purchased and used the </em><a href="https://wrapbootstrap.com/theme/unify-responsive-website-template-WB0412697"><em>Unify template</em></a><em>.</em></li><li><em>For NinjaJobs, I purchased and used the </em><a href="https://wrapbootstrap.com/theme/boomerang-multipurpose-bootstrap-theme-WB021609D"><em>Boomerang template</em></a><em>.</em></li></ul><p>Marketing is easy to spend money on and hard to get right. Pay for services to automate your communication processes.</p><ul><li><em>When I say “automate your communication process”, what I mean is paying for services that can speed up your outbound marketing and help manage the data. Services I’ve used in the past with a lot of success have been Mailchimp, Mandrill, Hubspot, Marketo, Google Analytics, Intercom, and Sendgrid.</em></li><li><em>As an example of automation success, take NinjaJobs and one of our many uses of Intercom. When one of our customers posts a job on the platform, we track views, bookmarks and applications. From historic data, we have been able to identify the sweet spot for a job to perform well. If we observe limited engagement on a post, we have a system that can analyze the details of it in order to make suggestions. Jobs not doing well that could benefit from changes are flagged for follow-up using Intercom where job posters are sent an automated email from one of us suggesting specific changes for the job. If the user replies asking for more help, we can immediately engage, otherwise, no additional effort is taken part on our end. This may sound a bit removed or cold, but this style of automation has created countless engagements we would have otherwise never had.</em></li></ul><p>Know your audience and how they want to be engaged. There’s no one-size-fits-all approach here. Let your metrics guide how you outreach to your users.</p><ul><li><em>Within the cybersecurity industry, this is tough to get right. Security end-users tend to be sensitive about their privacy (rightfully so) and do not want to be bugged, especially by sales. I continue to see the industry evolve on the marketing/tracking/privacy front and it’s tough to know how to best engage an end-user. Beyond the different segments, I suspect the future of outbound marketing will be a less-is-more approach.</em></li><li><em>On the no one-size-fits-all approach, take Intercom. Many end-users have reported hating the pop-up dialog, and find limited utility in the in-app notifications. However, when they have an issue, engaging with a human directly is nice. With NinjaJobs, it’s the exact opposite (as illustrated in my above example), where users want to be engaged and interacted with––after all, finding a job is stressful and it helps to know someone has your interests in mind. For each company, we take different approaches to engagement and it results in completely different, yet successful, outcomes.</em></li></ul><p>Generate a few different marketing tracks, so you can make your communications specific. Consider marketing, product updates, operational, nurture for users slipping away, nurture for users who may be stuck.</p><ul><li><em>This is driven from my company experience, but also my own personal habits. Splitting up your outbound marketing by type ensures that if someone unsubscribes from one type of update, that they continue to get some form of notification from you. Of course, they could unsubscribe from all notifications, but the point here is to diversify your outbound channels around themes, so that you aren’t unnecessarily bugging your customers.</em></li></ul><p>Social media is not a set it and forget it tool. If you want to look relevant, you have to maintain your accounts and keep them fresh with content. Find strategic ways to automate some of this.</p><ul><li><em>I personally struggle with social media these days and the value it brings to a business. It feels like a necessary evil in which you need to participate, but it feels like 24-hour technical support.</em></li><li><em>With PassiveTotal, we made some attempts to automate postings and create chat bots on Twitter and Facebook, but those never really took off. All our social media channels became just ways for users to reach us directly for support or question answering, and disseminating platform updates or research posts.</em></li><li><em>With NinjaJobs, we get more benefit out of social media through automating the socialization of jobs posted within the platform. This effectively turns our social media presence into a running feed of jobs, but it’s a convenient way for our customers to interact with the platform and they seem to get value from it. Unfortunately, given the high-degree of phishing and spam, we find ourselves constantly appealing a ban in order to keep this functionality intact.</em></li></ul><p>Build out a media plan every quarter that gives you enough content or fodder to keep going on a weekly or bi-weekly release basis. It could be a blog, feature announcement, podcast, webinar, whatever. Better to have a schedule of ideas than scramble after 3 weeks of silence.</p><ul><li><em>The notion of content creation sounds easy, but it’s hard to sustain, especially for years on end. Doing the prep-work before-hand ensures you always have something ready to post, promote or slot-in to keep your product in the spotlight.</em></li><li><em>In the early days of PassiveTotal, we employed an “earned media” technique of tacking value or additional information onto existing public media posts. If a research company posted about a new threat, we would use our product to add more to the narrative and then turn that into a blog posting, webinar or email we could send out. This technique was and continues to be highly successful not only in getting attention, but also keeping our materials up-to-date with relevant examples.</em></li><li><em>For several months, we attempted to build a marketing engine within NinjaJobs, but struggled to keep up with the content. Beyond analyzing job information, we would ideally be interviewing professionals, capturing their experiences and sharing that with others. Doing all of that takes an immense amount of work and could easily be a full-time position on its own. As a result, we ended up stopping our content creation for NinjaJobs in favor of focusing on platform automation.</em></li></ul><p>Organic marketing has been the most successful method in all my companies. Paid traffic helped, but it typically brought an audience who was not my ideal buyer. If you can find a way to speak the language of your buyer in content, you win.</p><ul><li><em>PassiveTotal and NinjaJobs largely grew organically from local peer networks and word-of-mouth. In the early days, we experimented with paid ads on social media and SEO-experiments in order to increase our audience. Those efforts were successful in getting us new conversions, but often resulted in the wrong “type” of user — their service, price and usage expectations didn’t match our organic community. As a result, we ditched the paid ads and focused on tooling.</em></li></ul><p>Don’t bother trying to go viral, it happens or it doesn’t. There’s ways to hack at it, but your time is better served making your product better.</p><ul><li><em>I fell into this trap several times with PassiveTotal. I’d come up with ideas or blog posts that I thought would take off and really change how we did threat analysis only to be underwhelmed with the response. Other times I would randomly quip on social media and have the post completely blow-up with interactions and feedback. After a few situations like that, I stopped trying to game the system and focused on generating good content that followed a regular schedule, and ensured my delivery of it respected my audience’s prime consumption periods.</em></li></ul><p>Attend events, always have swag (stickers, shirts, whatever) and if ever given the chance to pitch, go for it.</p><ul><li><em>Don’t bother in trying to find the next new shiny object to give away at a conference. Focus on good design or materials you know your customers will appreciate and deliver those. My all-time favorite swag was a PassiveTotal shirt that was just an image of our iconic heatmap that tied back to infrastructure for a Chinese threat group. The back of the shirt had a small “PassiveTotal by RiskIQ”, but aside from that, we kept a clean design. The shirts were well-liked and every now and then, I still see a few of them at events.</em></li><li><em>For stickers, I use </em><a href="https://www.stickermule.com/"><em>StickerMule</em></a><em>. For shirts, I use </em><a href="https://www.customink.com/"><em>Custom Ink</em></a><em>. For business cards, I use </em><a href="https://www.moo.com/us/"><em>Moo</em></a><em>.</em></li></ul><p>If you have good marketing or appear to be gaining traction, expect for your competition to steal your materials or find creative ways to leverage them against you.</p><ul><li><em>RiskIQ has been focused on external intelligence and monitoring the attack surface of an organization for 10 years now. Our messaging has not really changed, but in the past 1–2 years, we have noticed terms, phrases and other copy we have been using, showing up within our competitor’s websites or materials. I personally find this as helpful as it provides validation to what we are doing and ensures others are helping to educate the market.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=943f22792313" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Series: Engineering]]></title>
            <link>https://9bplus.medium.com/experience-series-engineering-5a8d40ec8124?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a8d40ec8124</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Mon, 29 Jul 2019 15:14:51 GMT</pubDate>
            <atom:updated>2019-07-30T02:31:39.532Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eG8NBe36WnmULhPm_D-Y0Q.gif" /><figcaption><a href="https://dilbert.com/strip/1995-01-20">https://dilbert.com/strip/1995-01-20</a></figcaption></figure><p>This post is part of my <a href="https://medium.com/@9bplus/on-building-companies-and-products-612e9d2f4652?postPublishedType=repub&amp;source=post_page---------------------------">Experience Series</a> where I share opinions I have formed from building companies and running product. Each posting is a break down of a company function. This post focuses on engineering specifically.</p><h3>General Opinions</h3><p>The language you write your product in doesn’t really matter, as long as it solves the problem you are trying to market.</p><ul><li><em>PassiveTotal and NinjaJobs were originally written in Python. Is it a highly scalable language for dealing with web-based problems? No, but it got the job done and continue(s/ed) to do so while making money.</em></li><li><em>Be mindful that you may not be the only person to eventually support your product, and so whatever language you do choose, make sure it’s at least known to others.</em></li></ul><p>First-pass code — even with the best intentions — will have issues and likely need a major refactor or rewrite. Focus on delivery, not scaling (can’t scale something not delivered).</p><ul><li><em>For me, engineering is a never-ending discipline. As I learn more and read better code, naturally, my code starts to improve. Even when I felt like I had successfully designed the perfect system, I’d view the code 6-months later and find glaring issues.</em></li><li><em>With PassiveTotal, we undertook several rewrites to bring the system front-end and back-end to match the technology stack of RiskIQ. Ideally, we’d avoid such rewrites, but as part of scaling, we needed our core staff to be experts in the system.</em></li><li><em>Specific components of PassiveTotal eventually failed to scale as we grew the business. While this was stressful to deal with, it was also a validation that what we had put together was getting used by our customers.</em></li><li><em>In initially designing NinjaJobs, technology was chosen that best suited the job. There was no intense discussions around scale or longevity, yet 4 years later, the original system continues to thrive and work as intended.</em></li></ul><p>Stay focused and avoid the engineering pitfall of “building all the things”. As a startup, it’s okay to be cheap, but your time is money. If you need to manage contacts and sales pipeline, don’t build your own CRM, go and pay for the service.</p><ul><li><em>Most of the systems we paid for in PassiveTotal and NinjaJobs were ones tangentially related to the business––customer support, marketing, contact management, sales operations, accounting, devops, etc. Paying the small fee––or sometimes none at all––let us focus on what was most important, building the product.</em></li><li><em>Many existing packaged solutions are not going to meet 100% of your needs and that’s okay. That’s not a reason to go build your own. Identify the gaps in the outsourced services you use and if it’s important enough, get creative.</em></li></ul><p>If given an MVP to implement, don’t go hog wild on the implementation. The key to an MVP is the metrics used for measuring. Get as much coverage as you can and move on.</p><ul><li><em>As a developer and someone who enjoys writing code, this is easy advice to say and the hardest to put in practice. When you think about it, most MVPs could be a button, that when clicked, logs a message-of-interest and kindly thanks the user for their input. Seldom do you need to engineer much of anything for an MVP. Always validate before you build!</em></li><li><em>So many of the early PassiveTotal features were driven from my personal experience doing analyst work. While they were great ideas, they often failed to get the level of engagement expected when delivered. Had I validated the ideas properly, I would have saved myself a lot of time.</em></li><li><em>Prior to my involvement in NinjaJobs, the product was literally an email digest and a single PHP file––talk about an MVP. Not only was the company placing hundreds of people in jobs, but it was also making a hefty profit. Moving it over to a platform later quadrupled the traffic, but doing so came at a risk-free cost since so much validation was done using the MVP.</em></li></ul><p>As best as possible, build feature-flagging or gating into your product. You can roll your own or use a service. It’s a great way to deploy rapidly and release selectively.</p><ul><li><em>Working at Facebook and RiskIQ exposed me to the power of flagging within the product lines. There’s a beauty in being able to release constantly to production, yet never break the experience for your users as the functionality exists behind a flag. Depending on your instrumentation, you can selectively release to certain users and truly control your roll-out.</em></li><li><em>Products I build today contain some element of flagging, though it’s not usually as granular as a company like Facebook. For my projects, “groups” tend to serve a good balance for who should see a certain feature and when. Unlike your traditional RBAC groups, my groups are typically organized around a feature or beta functionality. It’s far from perfect, but it works and is not terribly difficult to implement.</em></li></ul><p>If you plan to deliver an API, put some serious effort into the documentation and language-specific abstracts. My general approach is that a non-developer should be able to use one of my APIs and be successful without writing a single line of code.</p><ul><li><em>There are plenty of systems to take code written and output an API client. While these tools save you time, they often deliver a poor experience to the end user. APIs should be written for humans, by humans and not for humans, by machines.</em></li><li><em>As the PassiveTotal API evolved, we found ourselves working with an audience who could cobble together scripts, but were far from developers. Giving those users a copy/paste example gave those scripters confidence to use our tools.</em></li><li><em>With Backscatter (RIP), I went a next step in making the tool approachable by providing multiple (curl, bash, python, library) code samples for each call. No matter how the user wished to engage with the product, they could find a copy/paste example.</em></li></ul><p>Don’t release experimental APIs to the world unless they are clearly marked alpha and subject to change. Once someone implements your API, it’s nearly impossible to get them to change to something new, even when there is new content. It’s best to plan your design, test it, actually have someone implement it and then release.</p><ul><li><em>To this day, decisions we made early on within the PassiveTotal API continue to haunt us. Could we deprecate the functionality and move on? Sure, but we have to be mindful of our audience. Releasing a new API with little new functionality or changes is not a good way to get users to upgrade.</em></li><li><em>As a test case for your API, have a developer (customer) build a few tools or scripts with your alpha release and listen to their feedback. What may look good in documentation, could pose annoying in the real-world.</em></li><li><em>Libraries are great ways to abstract away from your users directly calling your API. These are also helpful when integrating with other products. If done correctly, even if you need to change the API later, you can just update the client to reflect the changes, leaving the end-user none the wiser.</em></li></ul><p>The goal early on is to build a product, not an engineering masterpiece. Your implementations do not need to be perfect. If the code works, handles under the load you have and meets customer expectations, you are doing it right. That said, don’t build a house of cards.</p><ul><li><em>PassiveTotal was largely a successful proof-of-concept when sold to RiskIQ. NinjaJobs was making healthy profits as a single PHP script and email digest. Blockade.io was formed using all free services from AWS and supports hundreds of users. Focus on the product, not the technology.</em></li></ul><p>Use technology you know and are comfortable with. Save the new tech or experimental ideas for side projects. Test them there, find the issues and then implement if you think it’s worth it.</p><ul><li><em>Running PassiveTotal and NinjaJobs at the same time afforded me the ability to run experiments between each company. I often used NinjaJobs as a testing ground where I would roll-out new features or technology in order to see how customers interacted with them. If I saw a lot of success, I would understand why and identify if that same success could be brought to PassiveTotal.</em></li><li><em>Today, I write code on my own time and poke around at different services in the market today. It’s a fun way to keep my skills fresh and allows me to gain exposure to technology I may want to use in my future products.</em></li></ul><p>As you begin to scale, consider technology that a greater audience knows. If you need to hire someone later on, it’s best to have a large talent pool to choose from. Mature/widely used technologies also tend to have better support overall.</p><p>If you have a team writing code and you’re in product, remove your write-access if you can’t follow process. Your code slinging days are not done, but you need to respect your team and not undermine their efforts.</p><ul><li><em>This assumes you are moving into more of a product role. I struggled for a long time to let go of writing code when I joined RiskIQ. It’s not that my contributions weren’t valuable, but I was not following process. There was a number of times that my code would introduce a bug, cause a distraction or simply fail to show success. If you’re going to write code, make sure you are willing to do all that comes along with it, including support and maintenance.</em></li></ul><p>Leverage frameworks to speed up development, but don’t forget it’s possible to manually instrument. Sure, you can push a full MVC pattern into your user’s browsers, but do you really need it? Would HTML and a few JS calls be sufficient? Think of the fragility and support over time.</p><ul><li><em>Take this point with a grain of salt, as my bias for tried and true methods is showing here. I’ve personally had poor experiences with modern Javascript frameworks that aim to handle immense amount of application logic on the front-end. Arguments I often here in favor of these frameworks don’t usually account for the long-tail support of a product overtime.</em></li><li><em>All of my projects have been developed largely using good old fashion HTML and Javascript when I felt it was useful to improving the user experience.</em></li></ul><p>Fast-track your application look and feel with a paid template. Buy it and extend it to make it your own. You’ll save a lot of time focusing on real product development, not the bones of your application.</p><ul><li><em>Most engineers are not designers. I myself am not a designer, but can produce decent looking products. For every single application I build, I start with a template––typically from wrapbootstrap––and adjust it to meet my needs. I can’t stress how much time this process saves me. Plus, as that template is updated, you can incorporate those into your project.</em></li></ul><p>If you write several applications, consider making your own bootstrap framework in the language of your choice. This would include the basics like user login, registration, session management, administrator controls, logging, etc. These save you time in the future and creates a consistent codebase to operate from.</p><ul><li><em>I am most comfortable using Python, and so my boilerplate code is written in that language. When I want to start a new project, I copy a generic base that covers 80% of my needs and then build custom logic within it. Using this approach, there are times when I can go from idea to deployed application within less than 24 hours.</em></li><li><em>This same approach can extend to the MVP phase of a project too. For “coming soon” pages that collect email addresses, I use a number of free-tier AWS services (Route53, SES, S3, CloudFront, API Gateway) and LetsEncrypt in order to stand-up a professional page that I can use for promotional materials.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a8d40ec8124" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Homemade Nitro Cold Brew]]></title>
            <link>https://medium.com/split-key-coffee/homemade-nitro-cold-brew-8c59639aa6ad?source=rss-4ed29fb827a7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c59639aa6ad</guid>
            <category><![CDATA[specialty-coffee]]></category>
            <category><![CDATA[summer]]></category>
            <category><![CDATA[home]]></category>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[cold-brew]]></category>
            <dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
            <pubDate>Fri, 28 Jun 2019 13:14:14 GMT</pubDate>
            <atom:updated>2019-06-28T13:14:14.790Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s summer time here on the east coast and that means it’s time for cold-brew coffee! In the past, I’ve made a few small batches from my personal roasts, but I thought it could be fun this year to dive into something new…nitro! Nitro cold-brew is one of my favorite ways to enjoy coffee, but I’ve always been too intimidated to try it at home. Turns out, making my own batch wasn’t difficult at all! In this post, I am going to walk through my process in making nitro cold-brew at home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WTrbWeidw0NVvWkwzusrrQ.jpeg" /></figure><p>This is the 3rd batch of nitro cold-brew I’ve made at home with my last batch being a naturally processed Brazilian bean––one having more chocolate and nutty flavors. For this batch, I roasted 400 grams of naturally processed Burundi Agahore Station which tends to have more wine and jam-based flavor notes. With this batch, I tried to keep the roast levels the same (medium), so I could compare the overall taste between each bean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J_jae0MvYk-wx2yacwrBzw.png" /></figure><p>Post-roasting, 400 grams turned into 347 grams due to moisture loss. For this coffee, I’ve found that it benefits from resting for 4 days prior to brewing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*56vyKpswDBFr8Vu8jLg1Qg.png" /></figure><p>For drip coffee (pour-over, french press or cold-brew), I use a <a href="https://www.seattlecoffeegear.com/nuova-simonelli-grinta">Nuova Simonelli Grinta</a> grinder and grind directly into a <a href="https://www.amazon.com/Pro-Quality-Nut-Milk-Bag/dp/B00KLT6X9W">nylon bag</a>. I’ve found the bag to be extremely helpful once the grounds are introduced to the water. It saves me one less filtration step for when I move the coffee to the keg later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kdxKXtb4eXGdAHNfAwkp6Q.png" /></figure><p>One of the biggest benefits to grinding so much coffee at once is that the whole basement takes on a fresh coffee smell. This Burundi puts off a beautiful sweet scent that reminds me of Trix cereal and fresh-baked shortbread cookies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rbAKdiB7iqC21u6nEk9JDg.png" /></figure><p>I use a 5 gallon bucket for steeping and fill it will Poland Springs water. I use Poland Springs in my espresso machine to reduce internal mineral build-up and now also enjoy it for all my other brewing. For this batch, I am using a 13:1 ratio which yields 1.25 gallons of cold-brew. Unlike other recipes, I prefer to avoid the concentrate approach as it can get complicated mixing ratios post brew.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IMYWchPBeCXDyv9T817MPg.png" /></figure><p>The nylon bag filled with coffee grounds is added to the bucket and covered for 18 hours. I haven’t played around with overall steep times too much, though generally find the 16–18 hour steep to work well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jMhjVeT1AdLgycujYxYYw.jpeg" /></figure><p>After the long steep, there’s a noticeable change in the overall color as the coffee has made it’s way into the water. Just on smell alone, I could tell this roast came out as I wanted––there was a strong jammy sweetness to the coffee that was very-much what I am used to when brewing hot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73MBZDgZMDVC1JzfQbm00Q.jpeg" /></figure><p>With the grounds removed from the coffee, it’s time to transfer over to the keg. I ended up going with a <a href="https://www.kegoutlet.com/kombucha-keg-2-5-gallon-aeb-metal-strap-keg.html">smaller keg (2.5g)</a> since it’s rare, if ever, that I will brew more than that at any given time. From past experiments, I’ve found the cold-brew coffee to have a 2–3 week shelf-life before it starts to degrade in quality. I use a mesh filter when pouring the coffee into the keg just to be safe, it doesn’t really filter the coffee itself (nylon bag for the win).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNLr7X0NcqJBS_n-9al3ag.png" /></figure><p>Pro-tip if you ever decide to follow along and make your own nitro cold-brew––there’s always a very fine sludge of coffee at the end of your pour that <em>should not</em> make it’s way into the keg. If the sludge gets into the keg, it’s likely to run through your output lines and clog your taps when serving.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zu4j74vf3OopecLcvhQCIA.jpeg" /></figure><p>With the coffee in the keg, I move onto the last stage of the process, infusing the nitrogen. I ended up going with a <a href="https://www.kegoutlet.com/carbonating-keg-lid.html">Quick Cascade Lid</a> for my keg which includes an input feed line that filters using a diffusion stone. Having this lid just helps speed up the infusion process, though it’s not a requirement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PhV2Q-WIG1yMRYvQ4TpX1A.jpeg" /></figure><p>This is where I always felt intimidated––something about highly pressurized gas freaks me out. My fears were misplaced as hooking up the nitrogen was super easy, I just had to follow a few steps. I start with a cold canister (left in my fridge) and hook the hose line into the “in” feed for the keg. Before unscrewing the nitrogen, I check my flow valve to ensure it’s closed and that my regulator screw is all the way out (no pressure).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lwOQLOc-4X9xXTzDw9h8TQ.jpeg" /></figure><p>Once unscrewed, the left gauge will give me a read out of the remaining gas I have left in the canister. From there, I open the flow value to the keg.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibOt9jdcxpEe_DKmWOYjWQ.jpeg" /></figure><p>Using a screwdriver, I slowly bring the keg to pressure by turning the pressure screw until I get to 45%. I will pause at each 10% increment and wait a minute before increasing. During the process, I will pull the release on the keg lid a few times just to purge any oxygen in the keg (since I don’t do full batches).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CflR1_zhgNzIeV-Ghm1p2Q.jpeg" /></figure><p>And that’s all there is to it! After several hours have passed, the cold-brew is ready to enjoy. While it can be enjoyed almost immediately, I find that it is best to wait 24–48 hours for good results and 3–4 days for the best results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4U1_pD1-qiRjE4u1ewOrKg.jpeg" /></figure><p>You know you have a good result when you see a lot of cascading in the coffee. As it settles, you should see a nice billowing effect take place as a foam head appears at the top of the cup. Cold-brew coffee alone is extremely smooth and shouldn’t have much acidity. Adding nitrogen to that output only increases the creaminess of the coffee and gives it much more body. For hot summer days, there’s no better way to enjoy coffee in my opinion.</p><p>I linked to the materials I used throughout the post, but here’s a quick reference just in case you want to replicate elements of this at home.</p><ul><li><a href="https://www.kegoutlet.com/draft-coffee-starter-kit-nitro-coffee.html">Keg Outlet Nitro Starter Kit</a></li><li><a href="https://www.amazon.com/Pro-Quality-Nut-Milk-Bag/dp/B00KLT6X9W/ref=sr_1_3?keywords=nylon+nut+bag&amp;qid=1561727384&amp;s=gateway&amp;sr=8-3">Nylon Nut Bag</a></li><li><a href="https://www.amazon.com/gp/product/B0088HVTUM/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&amp;psc=1">5 Gallon Bucket</a></li><li><a href="https://www.sweetmarias.com/hottop-roaster-kn-8828b-2k.html">Hottop Roaster KN-8828b-2k+</a></li><li><a href="https://www.seattlecoffeegear.com/nuova-simonelli-grinta">Nuova Simonelli Grinta</a></li><li><a href="https://acaia.co/products/pearl">Acaia Pearl Scale</a></li><li><a href="https://www.amazon.com/gp/product/B00PIT4HVG/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&amp;psc=1">Poland Springs Water</a></li></ul><p>For the nitrogen canister, you can go to a local oxygen store to get one of these. Tanks run about $90–100 and are exchanged each time you need a full one. A fill ends up running around $40–50 dollars.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c59639aa6ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/split-key-coffee/homemade-nitro-cold-brew-8c59639aa6ad">Homemade Nitro Cold Brew</a> was originally published in <a href="https://medium.com/split-key-coffee">Split Key Coffee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>