<?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 D Keith Casey Jr on Medium]]></title>
        <description><![CDATA[Stories by D Keith Casey Jr on Medium]]></description>
        <link>https://medium.com/@CaseySoftware?source=rss-eb33efba22fc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eaFZT8f02jNc6Pkb.jpeg</url>
            <title>Stories by D Keith Casey Jr on Medium</title>
            <link>https://medium.com/@CaseySoftware?source=rss-eb33efba22fc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:22:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@CaseySoftware/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[How Unprofitable Companies IPO]]></title>
            <link>https://medium.com/@CaseySoftware/how-unprofitable-companies-ipo-ed082e1f9194?source=rss-eb33efba22fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed082e1f9194</guid>
            <category><![CDATA[financial-modeling]]></category>
            <category><![CDATA[saas-sales]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[ipo]]></category>
            <dc:creator><![CDATA[D Keith Casey Jr]]></dc:creator>
            <pubDate>Mon, 10 Jun 2019 14:53:33 GMT</pubDate>
            <atom:updated>2019-06-10T14:53:58.384Z</atom:updated>
            <content:encoded><![CDATA[<p>In the last few years, we’ve seen a flock of tech IPOs and — with only one exception: Zoom — none of which have been profitable on IPO day. In this post, I walk through basic SaaS economics and how they stack up to make the case for an (eventually) wildly profitable company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*CKZRXWSIaHrD4Ffd6asb0g.png" /><figcaption>The Simplest Financial Model</figcaption></figure><p><em>Read the full post of “</em><a href="https://caseysoftware.com/blog/how-unprofitable-companies-ipo"><em>How Unprofitable Companies IPO</em></a><em>” on CaseySoftware.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed082e1f9194" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech IPOs — An Inside Out View]]></title>
            <link>https://medium.com/@CaseySoftware/tech-ipos-an-inside-out-view-a3b468efdbdf?source=rss-eb33efba22fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3b468efdbdf</guid>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ipo]]></category>
            <category><![CDATA[stock-options]]></category>
            <dc:creator><![CDATA[D Keith Casey Jr]]></dc:creator>
            <pubDate>Wed, 24 May 2017 15:52:39 GMT</pubDate>
            <atom:updated>2017-05-24T19:29:33.033Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Disclosure:</em></strong><em> I am a shareholder of both Twilio and Okta and currently employed by Okta. Nothing here reflects the internals of either company, forward looking statements, or guidance related to either. If you’re looking for financial or investment advice, talk to your financial advisor. Don’t go it alone or blindly follow internet advice.</em></p><p>Going through an IPO is a wild experience. Just having a piece of a company on the “Big Day” is exciting, scary, nerve wracking, and a truly unique experience. In the last twelve months, I’ve gone through it as both an insider (Okta) and as an outsider (Twilio) and wanted to share some perspective.</p><p><strong><em>First, understand that it’s a lottery ticket.</em></strong> A small number of companies get funding, an even smaller number will have a liquidity event, and even fewer will have an IPO. It’s the special combination of a huge number of things like product, execution, marketing, sales, state of the industry, competition, market, phase of the moon, tides, and your lucky socks. You can control some of those, influence others, and get blindsided or blessed by the rest. It’s a crapshoot.</p><p><strong><em>Second, you need liquidity.</em></strong> It takes liquidity to execute on your options. Post-IPO and post-lockup it’s easy because you can do a “cashless exercise” which is a short term loan you use to buy the shares and then immediately sell enough to pay it off. Pre-IPO it’s a whole other ballgame because your can’t sell your shares. As a result, you buy shares that — <em>in all likelihood </em>— will be worth zero. In the best case, you may get your money out years later. Remember: the earlier you join, the cheaper the shares will be but the risk is higher and the potential payout is further out.</p><p>To make things more exciting, there are tax implications when you buy shares at less than the current value. Post-IPO the value is the current stock price. Pre-IPO the value is whatever the Board says it is which will always change at each funding round, potentially more often.</p><p>For example, your exercise agreement says $1/share but your company has raised money and now shares are $10 each, you’ve “made” $9 upon purchase. So not only do you need the cash to execute but also enough to pay taxes on your entirely-paper “gain.” If you’re really unlucky, you might get hit by the AMT. Hire an accountant or financial planner to help you figure out the details.</p><p><em>For a better discussion of stocks and options check out David Weekly’s ebook “</em><a href="http://amzn.to/2q7zUgl"><em>An Introduction to Stock and Options</em></a><em>.” It is the best $3.99 I’ve ever spent.</em></p><p><strong><em>Next, you need to know your responsibilities.</em></strong> If you’ve been out of the company for years, you’re probably not an insider and have a lot of flexibility. You can tweet, blog, buy drinks, and generally celebrate. Double check before you do.</p><p>If you’re a recent or current employee, there’s the dreaded “<a href="https://infogalactic.com/info/Quiet_period">Quiet Period</a>” which is an archaic set of SEC rules saying you can’t promote the company’s stock. Depending on how strict your Legal and Comms/PR teams are, the specifics will vary but that’s because it’s so vague, it can mean tons of things. A good rule of thumb is to not engage with anything and if directly asked, stick to “Thanks for asking but due to SEC regulations, I can’t talk about that right now.”</p><p>Most likely your CEO and other senior staff will post things, make announcements, share job openings, and get quoted by the media. You’ll want to share and celebrate them. Unless your Legal and Comms/PR teams explicitly authorizes you, do not engage. If you f* this up, there can be major ramifications for your company, job, and career.</p><p><em>When in doubt, keep your mouth shut.</em></p><p><strong><em>Next, you need a plan.</em></strong> Work with a financial advisor to review your priorities, create a sell plan to diversify (if necessary), and document all of it long before you see the dollar signs. It’s much easier when everything is still hypothetical. If you are an insider, be careful. Do not share anything sensitive and if you don’t know what’s sensitive, ask your corporate counsel. When in doubt, keep your mouth shut.</p><p><em>And once you have a plan, stick to it.</em> The only actions I regret are when I didn’t follow my plan.</p><p><strong><em>Finally, don’t watch the stock price.</em></strong> Twilio shares opened in the low $20s, hit $70 during the lockup, bounced in the $30–35 range for a few months, and dropped to the mid $20s in early May. Unfortunately, I know this because I watched the stock rise rise rise and then fall fall fall. And yes, I did the math at every stage even when I could do absolutely nothing with my shares. The stress isn’t worth it.</p><p>Fundamentally, remember that all of this pain and annoyance is because of a good thing. If your company has made it this far, they’ve navigated major challenges and are one of the few still standing. You’ve helped accomplish something amazing. Stop and take a minute to appreciate that and to celebrate and congratulate your friends and colleagues.</p><p><em>And then get back to work. ;)</em></p><p><em>This originally appeared on my personal site </em><a href="https://caseysoftware.com/blog/tech-ipos-inside-view"><em>CaseySoftware.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3b468efdbdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mayor Steve Adler is Scamming the Austin Tech Community]]></title>
            <link>https://medium.com/@CaseySoftware/mayor-steve-adler-is-scamming-the-austin-tech-community-399d12b976e9?source=rss-eb33efba22fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/399d12b976e9</guid>
            <category><![CDATA[civic-innovation]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[austin]]></category>
            <dc:creator><![CDATA[D Keith Casey Jr]]></dc:creator>
            <pubDate>Tue, 24 May 2016 14:07:10 GMT</pubDate>
            <atom:updated>2016-05-24T14:07:10.309Z</atom:updated>
            <content:encoded><![CDATA[<p>As one of the founders &amp; organizers of <strong>ATX Hack for Change</strong>, I’m sorry to say:</p><blockquote><em>I have resigned my role in ATX Hack for Change and will not be attending. More importantly, you should not attend either.</em></blockquote><p>When we started ATX Hack for Change as part of the <strong><em>National Day of Civic Hacking</em></strong>, we started with the premise that there are smart people on both sides: people who know the tech but don’t know the problems and people who know the problems but don’t know the tech. If we put them together with some planning and structure, great things would result. So far we’ve been proven correct facilitating services to help feed the homeless, organize Girl Scouts’ merit badges, and help people understand their local government better.</p><p>In our 3rd year (May 2015), I served as MC for the weekend and introduced Mayor Adler for his welcome keynote. He gave a honest and sincere address about Austin being a great place but having problems that we need to solve together, one of the biggest being transportation. <em>I was excited and impressed.</em></p><p>Now we know that the City’s engagement in the tech community is for show and good PR, not because they actually want us involved:</p><blockquote><em>The City of Austin is the hot girl from high school who wanted you to do her homework and then just go away.</em></blockquote><p>Fast forward six months and <strong><em>Mayor Adler and the City Council knowingly work to make Austin less safe</em></strong>. Think I’m exaggerating? Here’s a quote from the hearings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/0*uYMF15Ww6YCwkmsk.png" /></figure><p>Fast forward another six months when Proposition 1 failed. I was frustrated but accepted it.</p><p><strong>This is where things get weird…</strong> here’s the timeline:</p><ul><li>May 7th — Proposition 1 vote fails.</li><li>May 9th — Uber and Lyft end service in Austin.</li><li>Immediately various “Gypsy car” services pop up. Some are just <a href="http://www.thedrive.com/tech/3572/what-its-like-to-live-in-a-city-without-uber">random guys posting to Craigslist</a>. Even the “official” services backed by the city are run by a guy parked behind a gas station and <a href="http://www.austinmonitor.com/stories/2016/05/council-scrambling-find-replacements-uber-lyft/"><strong><em>NONE</em></strong> of those comply with the law</a>.</li><li>May 16th — The City of Austin <a href="https://archive.is/Wn0xw">announces three job fairs in one week</a> for now-unemployed Uber &amp; Lyft drivers.</li><li>May 19th — The City Council passes a resolution to invest in Uber and Lyft’s competitors. Councilwoman Troxclair — <a href="http://www.mystatesman.com/news/news/opinion/ellen-troxclair-austin-is-chasing-its-tail-on-ride/nrQnW/"><em>one of the few who gets it</em></a> — tries to amend it to require compliance with the law. Mayor Adler rejects it.</li><li>May 20th — Mayor Adler points out that they <a href="https://archive.is/6lEjn">never expected these companies to comply with the law</a>.</li></ul><p>And late last week, Mayor Adler raised the stakes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*ZCe4uKh3pkbcKqB8.jpg" /><figcaption><a href="http://www.citylab.com/commute/2016/05/austins-post-uber-plan-break-up-the-taxi-cartel/483417/">CityLab.com, May 19th</a></figcaption></figure><p><em>So wait, the entire goal of this is to regulate online commerce?</em></p><p><em>No wait, Tinder isn’t commerce. So this is to regulate </em><strong><em>any</em></strong><em> online interactions?</em></p><p>Since I raised these issues, I was informed that I should have attended the <strong><em>secret off-the-record dinner with Mayor Adler</em></strong> last week. I declined because public policy feedback and debate shouldn’t be secret <em>unless you have something to hide</em>.</p><p><strong>This is no longer about Prop 1.</strong></p><blockquote>This is about a Mayor and Council that talks transparency and innovation… as long as they think we’re looking. But once we stop, they cut backroom deals and encourage people to break the laws they wrote.</blockquote><p><em>So as much as I have loved working on and attending ATX Hack for Change for the past four years, I’m done. I won’t be used as a prop in this scam.</em></p><p>I feel bad for the many people who work for the City and groups like <a href="http://www.open-austin.org/">Open Austin</a> who “get it” and want Austin to be a welcoming place for business, tech, and innovation.. <em>they’ve been lied to even worse than the rest of us.</em></p><p><em>If you want to understand more of the implications of Prop 1, read Courtney Powell’s “</em><a href="https://austinstartups.com/the-true-cost-of-prop-1-for-austinites-29m-jobs-funding-and-lives-805418e6712c#.48oacowoe"><em>The True Cost of Prop 1 for Austinites: $29M, Jobs, Funding and Lives</em></a><em>.”</em></p><p><em>This post is also on my normal blog at </em><a href="http://caseysoftware.com/blog/mayor-steve-adler-scamming-austin-tech-community"><em>CaseySoftware.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=399d12b976e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Hypermedia Makes Sense]]></title>
            <link>https://medium.com/@CaseySoftware/why-hypermedia-makes-sense-30633ac79e81?source=rss-eb33efba22fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/30633ac79e81</guid>
            <category><![CDATA[hypermedia]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[D Keith Casey Jr]]></dc:creator>
            <pubDate>Mon, 08 Feb 2016 17:10:34 GMT</pubDate>
            <atom:updated>2016-02-08T17:10:34.020Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Why Hypermedia Makes Sense</p><p>If you’ve worked in the API space in the last few years, you’ve probably come across the concept of hypermedia and the debate surrounding it. Some people believe it’s a silly idea that makes client applications more complex than necessary while others believe it’s a powerful concept that can be used to simplify applications for easier upgrades and greater flexibility.</p><p><em>At </em><a href="http://clarify.io/"><em>Clarify.io</em></a><em>, we believe that hypermedia makes sense as it makes our API explorable for clients, more flexible in design, and provides explicit descriptions for relationships between resources.</em></p><p>Before we get into the “why,” let’s make sure we’re talking about the same thing.</p><h4>What is Hypermedia (or HATEOAS)?</h4><p>First, hypermedia is the idea that the API itself tells you what is available based on your context. This is similar to when you visit Amazon.com. The first time you ever visited Amazon, you saw links like “create account” and “log in.” Once you logged in, those links were replaced with “log out” and “account history.” The site knows your current context and only gives you options relevant at that time. The alternative — and how most APIs are structured — would require you to dig through the documentation and find the specific URL for each step and figure out what to do next. Relatively simple multi-step processes that we take for granted — <em>like checking out</em> — become complicated and fragile to the point of being unusable for mere mortals.</p><h4>Hypermedia: Choose Your Own Adventure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/184/0*_i-Og947Lf73xTKZ.jpg" /></figure><p>In a Choose Your Own Adventure book, you don’t read the pages sequentially. Instead, as you progress through the story, you are presented with choices which send you to different pages. You go to that page, are presented with another choice, and then repeat. In an API, these choices are represented by URLs which are described by relationships or intents. As you use the API, the relationships we understand become options available to us. This understanding comes from a defined set of relationships called <strong>link relations</strong>. Some <a href="http://www.iana.org/assignments/link-relations/link-relations.xhtml">link relations are defined</a> — like next, previous, first, last — but you can also create more which are specific to your industry, application, or even use case.</p><h4>How is hypermedia used?</h4><p><em>The “how” is where things gets a little squishier.</em></p><p>Great APIs are designed around noun/verb combinations. Those are listed in the documentation, developers build things around them, and then embed that information in your client applications. This all works until the API changes. In the simplest case, new optional parameters are not a problem. On the other end of the spectrum is changing an existing URL. It’s a breaking change which implies a new version of the API. Somewhere between those extremes is when the API adds new resources.</p><p>A new resource gives you easier, faster, or more powerful functionality that you don’t currently have. Unfortunately, in most APIs, a new resource implies new/more documentation, helper library updates, new quickstart guides, more support emails, etc, etc. It’s a pain at best because we can’t take advantage of this resource unless we update our application to create the URLs and process the results. But if we shift our thinking from URLs to <strong><em>link relations</em></strong> (or an <strong><em>intent</em></strong>), things change in subtle but powerful ways.</p><p>If we have a payload that suddenly adds a URL with the “next” link relation, we know that following it will get another page of results. As long as we know how to process the payloads, our application is updated. We don’t have to do anything else. We can skip over concatenating strings or doing string replacements. Which brings us to the point…</p><h4>So why does Clarify use hypermedia?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*BgPmDX0iIhq_sZUc4e9Anw.png" /></figure><p>At Clarify, we’re building machine learning systems to process, understand, and transform audio and video from bits and bytes into data that’s actionable and understandable to mere mortals. The most important part is that those systems are constantly dissecting and analyzing media files — including both the audio and video — to extract what it contains, understand what it means, and turn it into something useful and actionable. As a result, sometimes our systems discover unexpected patterns, relationships, and attributes that someone finds useful.</p><p><em>Or to put it another way: </em><strong><em>we don’t always know what’s next.</em></strong></p><p>Therefore, we end up with an unpredictable collection of ever-expanding objects beneath each piece of media that we need to process and consider. In our opinion, hypermedia is the <strong><em>only</em></strong> way to support this growing web of related resources.</p><p>When we launched, we only supported search. Although we were processing and understanding quite a bit about the media, we weren’t exposing it via the API. As our automated transcripts improved, we applied basic Natural Language Processing to extract the spoken_keywords report to give you the important words. Taking this a level deeper, we analyzed the content to determine the spoken_topics to figure out what the media is about. As we explore and learn more, we simply add more link relations to represent each insight we discover about your media.</p><p>The resulting JSON payload looks something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e13f0a2243618fc7271837aefbe55a9f/href">https://medium.com/media/e13f0a2243618fc7271837aefbe55a9f/href</a></iframe><p>Now for someone to find the keywords, they find the <strong>insight:spoken_keywords</strong> key and retrieve the corresponding <strong>href</strong>. Or the client application can let the user explore related resources or even go back to the beginning with the parent link relation. Our <a href="http://docs.clarify.io/libraries/">helper libraries</a> further emphasize this by completely hiding the URLs and letting you request specific insights by name. In fact, when we launched the topics insight recently, none of our libraries needed updating because you simply request the insight by name and the resulting data is the same structure as keywords.</p><p>The point is that once you understand one part of the API, that understanding can be applied to other parts with almost no effort. As new parts of the API light up, developers — or their client applications — can explore quickly and simply. It speeds the initial development and encourages more and deeper integrations over time.</p><p><em>If you’d like to delve deeper into hypermedia, check out Luke Stokes’ post on “</em><a href="https://medium.com/@lukestokes/why-your-colleagues-still-don-t-understand-hypermedia-apis-1a5a2cf82540"><em>Why your Colleagues Still Don’t Understand Hypermedia APIs</em></a><em>.”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30633ac79e81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So You Want to Build An App]]></title>
            <link>https://medium.com/@CaseySoftware/i-m-contacted-a-few-times-a-month-by-people-who-want-to-build-usually-mobile-apps-7c72b236701e?source=rss-eb33efba22fc------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c72b236701e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[great-ideas]]></category>
            <dc:creator><![CDATA[D Keith Casey Jr]]></dc:creator>
            <pubDate>Mon, 28 Dec 2015 22:11:55 GMT</pubDate>
            <atom:updated>2017-06-26T17:52:21.804Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>So you want to build an App..</strong></h3><p><em>I’m contacted a few times a month by people who want to build (usually mobile) apps. Or more properly, want someone to build apps for them. While I don’t begrudge or criticize their hopes or goals, we need to look at things critically and honestly. Also, I’m tired of telling people the same thing over and over again.</em></p><p>Let’s start with some assumptions to calibrate who I <strong><em>think</em></strong> you are:</p><ul><li>First, you probably aren’t a developer. You <strong><em>might</em></strong> be a degreed/certified professional (actual engineer, doctor, lawyer, etc) with domain specific knowledge but you don’t cut code.</li><li>Next, you probably aren’t well-connected or active in the tech community.</li><li>Next, you aren’t a Kardashian. (More on that later.)</li><li>Next, you’ve seen others “make millions” with their ideas and your idea is “<em>way better</em>” than theirs.</li><li>Finally, your idea is <strong><em>so good</em></strong> that you don’t want to share it with others.</li></ul><p>Now, before we start dissecting this, understand that this isn’t criticism of you, your idea, or anything similar, this is generic advice and thought that applies all over.</p><p><strong><em>First, I think it’s awesome that you’re interested in technology.</em></strong> The problem is, I’m not sure you really are. After the Social Network showed how a bunch of hoodie-wearing bros made a pile of money overnight — <em>not true, but it’s the common takeaway</em> — people flocked to startups as the new gold rush. The same thing happened 1995–2000 before the crash. But I’ll give you the benefit of the doubt.</p><p><strong><em>Next, very few people make significant money with apps.</em></strong> It’s not impossible to make money with apps, but the vast majority won’t. In fact, many people don’t even earn back the $100 annual fee to release apps in Apple store. If you don’t believe me, check out the <a href="http://www.businessinsider.com/how-much-do-app-developers-make-2015-5">Forbes article from May 2015</a> where a top 10 paid app maker earned $302 the day it peaked. Remember, that’s the peak! If you’re Kim Kardashian, you might <a href="http://www.forbes.com/sites/maseenaziegler/2014/07/16/why-kim-kardashian-hollywood-is-a-200-million-hit-app/">make $200 million with your app</a>, but that is an outlier among outliers.</p><p><strong><em>Next, your idea probably isn’t that good.</em></strong> It’s not that all the good ideas are taken — <em>though there are already probably a half dozen variations of your app</em> — the problem is that you’re keeping your “great idea” to yourself. What you should be doing is telling <em>everyone who could be your customer</em> about your idea. Get feedback, listen to criticism and concerns, and refine and adjust your idea. Some feedback will be junk, but the useful parts will make your idea better. Also, skip talking to your BFFs. Instead, talk to people who should buy your app and learn from them.</p><p><strong><em>Next, writing code is the easiest part.</em></strong> Before I lose my <strong>Developer Card</strong>, note that I said “easiest” not “easy” and this is in the realm of Tiger Woods making something look easy. When I wiggle my fingers on a keyboard to write code that works, there are years that went into knowing how to structure things, how they fit, what not to do, etc. But no matter how well I do my job, you still need to get out there and sell it. And once you sell it to a couple people, you need to sell it to more and more. Once again, that part is easy if you’re a Kardashian but you’re not so you’ll need a website, advertising, referral codes, etc.</p><p><strong><em>Next, you need to maintain the app.</em></strong> Just like a car or a home, there is regular maintenance like software updates, security patches, new features, dozens of other things, and then re-testing all of it. Just because it is “done” for now, doesn’t mean it’s <strong><em>DONE</em></strong>. You need to budget for this. In fact, testing is so big and hard, there are companies like <a href="https://testlio.com/">Testlio</a> that focus entirely on that.</p><p><strong><em>Next, this isn’t a passive income stream.</em></strong> Beyond the technical maintenance, there are customers involved and they have problems, need refunds, complain, and write reviews. You need someone to provide support and respond to issues. You need to budget for this.</p><p><strong><em>Finally, there are lots of steps you can take before you hire a developer.</em></strong> You should take them. It will cost you less in discussion, debate, confusion, dead ends, and time. Here are six things I recommend that everyone with an idea should do:</p><ul><li>First, write a paragraph about what the app is. Until this is on a physical sheet of paper, it doesn’t count. Having it in your head is great, but that allows you to not think through implications, contradictions, etc. Putting it on paper exposes those things. And if you say “<em>Facebook but for X</em>” stop immediately. Facebook is the “Facebook for X.”</li><li>Next, write a paragraph on what that app is not. The same applies as above but this also helps you draw some boundaries and inform your developer, team, etc what <strong><em>not</em></strong> to do.</li><li>Next, do some serious research into your competitors. Don’t google it once and call it complete. Spend at least a few hours finding potential competitors and describe how you are different from each. Even better, find some competitors who have gone out of business and describe what you’re going to do differently.</li><li>Next, use a tool like <a href="https://balsamiq.com/">Balsamiq</a> to sketch out your user flows. This means you draw the opening screen, show what the user does next, what that looks like, what they do next, etc. It doesn’t have to be beautiful and your final app probably won’t look like this, but you’ll be forced to think through implications, contradictions, etc.</li><li>Next, start thinking about thinking about the bare minimum version that you can put in front of someone where they can still do something useful. This is called a <a href="https://en.wikipedia.org/wiki/Minimum_viable_product">Minimum Viable Product or MVP</a>. It’s not the final system but enough to validate people will pay for what you’re building. For example, if you want to build a game with 50 levels, figure out if you can launch it with 5 and then do it. You can always release version 2.</li><li>Finally — and throughout this entire process — start setting aside some money. Very few good developers will work for equity and <a href="http://caseysoftware.com/blog/startup-risks-for-developers">they shouldn’t</a> and even fewer will work to “build their portfolios” so don’t try that line. This amount will usually be five figures — <em>not my area of expertise, so I can’t be more specific</em> — but I’ve seen it go into six figures. Regardless, figuring out all the above will decrease this number a bit.</li></ul><p><strong><em>Isn’t this fun?</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*Dpt0Jl9renqEcyQ4.jpg" /></figure><p>If you’ve made it this far, you <strong><em>should</em></strong> feel overwhelmed. What you probably thought was “a weekend project for a good developer” has suddenly turned into something much more than you’d considered. If you decide to bail at this stage, no harm, no foul. At this point, you’ve spent some time (probably hours) and a little bit of money (less than $50) but you haven’t broken the bank or wasted months of your life.</p><p>But if you decide to go forward, you will have a much clearer understanding of what to build, what not to build, which competitors to emulate, which to distinguish yourself from, and realistic expectations of what will happen. In fact, you should check out “<a href="http://amzn.to/1NluCWW">Avoiding a Goat Rodeo</a>” from my good friend Cal Evans. While it’s about website development specifically, many of the same points apply.</p><p><strong><em>Good Luck.</em></strong></p><p><em>Keith Casey currently serves on the Platform Team at </em><a href="https://www.okta.com/"><em>Okta</em></a><em> working on Identity and Authentication APIs. Previously, he served as an early Developer Evangelist at Twilio and before that worked on the Ultimate Geek Question at the Library of Congress. His underlying goal is to get good technology into the hands of good people to do great things</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c72b236701e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>