<?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[CoVenture - Medium]]></title>
        <description><![CDATA[CoVenture partners with and invests in early stage technology startups. - Medium]]></description>
        <link>https://medium.com/coventure?source=rss----bd5106bd7aac---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>CoVenture - Medium</title>
            <link>https://medium.com/coventure?source=rss----bd5106bd7aac---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:49:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/coventure" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[JS minus JS: The Future of the JavaScript Community is better through transpilation.]]></title>
            <link>https://medium.com/coventure/js-minus-js-the-future-of-the-javascript-community-is-better-through-transpilation-b980d59eaa93?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/b980d59eaa93</guid>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Adam Daw]]></dc:creator>
            <pubDate>Mon, 09 Apr 2018 14:30:03 GMT</pubDate>
            <atom:updated>2018-04-09T14:30:03.274Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week, I had the pleasure of representing CoVenture while speaking at the <a href="https://forwardjs.com/ottawa">Northern edition of ForwardJS</a> about a topic near and dear to my heart: transpilation in the JavaScript ecosystem. It’s my understanding that a recording of that will be coming out soon, but before that (and with a desire to expand my thoughts outside of the 20 minutes I had to talk on the matter at the event) I decided that I would write out a bit more on my thoughts here.</p><p>Let me preface this discussion with a bit of celebration: in 2017, and so far in 2018, no matter how you slice the data, JavaScript is one of if not the top language used by developers. Its position is visible in rankings from <a href="https://octoverse.github.com/">Github itself</a>, the fantastic team at <a href="https://redmonk.com/sogrady/2018/03/07/language-rankings-1-18/">RedMonk</a>, even the <a href="http://pypl.github.io/PYPL.html">PYPL index</a>. The <a href="https://spectrum.ieee.org/computing/software/the-2017-top-programming-languages">IEEE has it as #7 on its list</a>, which is one of the lowest rankings I could find in relevant sources.</p><p>Suffice it to say that the field of JavaScript development continues to grow, and shows no signs of stopping. With the advent of native mobile frameworks and the adoption of server-side JavaScript increasing, there are more ways to develop in the language than ever before. Furthermore, through the introduction of the <a href="http://2ality.com/2015/11/tc39-process.html">TC39 process</a>, JavaScript continues to advance at an even faster pace. These points make the landscape in 2018 very, very exciting.</p><p>At the same time, the world of JavaScript can be very intimidating to the outsider and uninitiated: Mobile, Hybrid, Native, Server-side, Client-side, Gulp, Grunt, Bower, Webpack, React, Angular, Vue, NPM, Yarn, Functional vs. Object-Oriented… the lists of terms, concepts, and processes extend forever, sparking debates around which is best or en vogue. The fallout from these internecine conflicts is that it is quite easy to alienate new developers, and I would propose that it is only momentum and critical mass — the gravitational pull and monopoly JS has on development for the web — that allows JS to continue to grow. However, lack of clarity and cohesion will persist if not checked, and <a href="http://webassembly.org/">other contenders are coming down the track </a>towards JS. If the community wishes to continue to flourish, it can’t afford to be complacent.</p><p>There are two solutions to this scenario, as I see it. The most obvious is to determine a winner in the myriad of debates currently underway: to establish a “right way” to develop JS on the web in 2018 and beyond. The primary issue with this approach is that we will likely lose many people in the process — the functional fans will go back to friendlier territory, or the object-oriented observers find greener pastures to inherit.</p><p>The better alternative, in my opinion, is to open the gates entirely; embrace the wildness that is the JavaScript arena! Let everyone develop how they are most comfortable, and then work on consolidating and normalizing that code after the fact. If JavaScript is to be the <em>lingua franca</em> of the web, let folks get there in their own way. As the title of this post would suggest, this means, of course, turning towards the transpiler.</p><p>Before we continue, let us define the terms “compilation” and “transpilation” for the purposes of this conversation. More complex and specific definitions will of course be available, but it is important that we come to terms within the scope of this discussion.</p><p>When referring to “compilation,” I mean the transformation of code from one language to another: typically, this means from a language or form of higher abstraction to a lower one.</p><p>“Transpilation,” on the other hand, is a variant or subset of compilation, where one transforms code between languages at a similar level of abstraction. When used in the context of this conversation, this will even more specifically refer to the transformation of code from a given source language to the target language of JavaScript. You also often see this referred to in other places as “targeting.”</p><p>You should note that while abstraction in the context of programming has implications on human readability or ease of conceptualization, the process of transpilation is usually an automated one, and may also include removing readability aids (such as whitespace). While this may mean that the act of transpilation changes the level of readability of the resultant code, the general level of abstraction will remain the same.</p><p>I believe that embracing transpilation is the best future for JavaScript development for several reasons, and you can summarize many of them in the following statement:</p><blockquote>Transpilation allows developers to write in whatever language or framework they prefer, and have the result still be JavaScript.</blockquote><p>This process is beneficial for many reasons: it allows developers to leverage the pieces of abstraction more useful to them, to write in languages that they are comfortable in, and exposes JavaScript to more concepts and innovation.</p><p>Every developer is unique, and conceives of or conceptualizes differently. The implication of this is that each developer will prefer to abstract a different aspect of their writing process. Some prefer not to have to think about the typing of their components, while others would rather avoid the explicit declaration of every aspect of each of their structures. When designing a language, different problem areas will always be addressed, depending on the personal opinions and philosophies of the language’s creator. Like-minded individuals will naturally gravitate towards the implementation that most closely adheres to their profile to become more efficient in their work, and this should be encouraged.</p><p>Forcing people to write in languages they aren’t comfortable in, while it can be an effective way to expand one’s mindset (a laudable desire, in my opinion), is not a very good way to satisfy developers, and is more likely to lead to poorly written or designed code. Most developers, given a choice, would choose not work on a project rather than be forced to use a language or framework they find incompatible with their approach or mindset.</p><p>Instead, if we encourage various mindsets to contribute to a project in their unique way, we introduce new concepts to what might otherwise be an incredibly homogeneous conversation. <strong>More diversity is always better.</strong></p><p>Transpilation is not a new concept and has been around in the JavaScript space for a while. CoffeeScript first appeared at the tail end of 2009, TypeScript in 2012 (it’s interesting to note that TypeScript itself is now one of the most popular languages on GitHub), and even the Babel predecessors (6to5, Traceur) are four years old now. This field continues to grow — the <a href="https://github.com/jashkenas/coffeescript/wiki/list-of-languages-that-compile-to-js">list</a> on the CoffeeScript Github is extensive. For virtually every member of the top 10 or 15 programming languages, there is a method to get your code transpiled to JavaScript. Here are just a few, for some of the more popular options.</p><ul><li>Java: there are several options, but two of the most interesting are <a href="http://www.jsweet.org/">JSweet</a> and <a href="https://kotlinlang.org/">Kotlin </a>— a language in its own right that is remarkably similar to Java, is growing in popularity among the native Android developers and targets JS out of the box.</li><li>Functional Fan?: Clojure has <a href="https://clojurescript.org/">ClojureScript</a>, and <a href="http://elm-lang.org/">Elm </a>is a functional language (primarily for the graphical side of the web) that targets the modern web stack (HTML/CSS/JS).</li><li>The C School: <a href="http://kripken.github.io/emscripten-site/">Emscripten</a> can convert C/C++ projects to the asm.js JavaScript subset, and Dart (a C-style language) offers <a href="https://webdev.dartlang.org/tools/dart2js">dart2js</a>.</li><li>PHP and others: while not every language may have perfect interoperability with JavaScript, projects like <a href="https://haxe.org/">Haxe</a> can act as a Rosetta Stone of sorts, making PHP-&gt;Haxe-&gt;JS relatively effortless, but tremendously advantageous for testing out the impact of various approaches across systems.</li></ul><p>In summary, I would like to say the following two things:</p><ol><li>The future is a polyglot one.</li><li>The more ways there are to write JavaScript, the more people will write JavaScript, and the more people that write JavaScript, the better JavaScript will get.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b980d59eaa93" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/js-minus-js-the-future-of-the-javascript-community-is-better-through-transpilation-b980d59eaa93">JS minus JS: The Future of the JavaScript Community is better through transpilation.</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Build A “WOW” User Experience]]></title>
            <link>https://medium.com/coventure/how-to-build-a-wow-user-experience-816024caf333?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/816024caf333</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Jamil Goheer]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 17:41:48 GMT</pubDate>
            <atom:updated>2018-04-02T17:41:17.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*gc1r1bdlIxQqNcfTrAueUw.png" /></figure><p>And It Has Nothing To Do With Software Development</p><p>You must have thought that software development is the most complex part in rolling out a successful product. Sure, it’s a nightmare for many, but building a solid user experience is even challenging. And yes, user experience design is NOT software development. There is much more that goes into product thinking far before we even start writing a code. And many founders and product owners miss the beat here.</p><p>We typically follow the five step process to create the user experience that our founders wish to offer their customers.</p><h3><strong>I — Product Aspiration</strong></h3><p>A typical <strong>“user experience design”</strong> kickoff is to understand the product aspiration i.e. why the product really matter to a user. This requires understanding the user behavior, user psychology and doing some user research to understand why a user will ever use this product and what value it brings to the user. This is the beginning of a high level concept development.</p><blockquote><strong>Outcomes:</strong> This phase includes a high level concept development and builds a list of aspirations for the product to exist.</blockquote><h3><strong>II — User Story Boarding</strong></h3><p>This steps involves a detailed description of the requirements and functional specs. One needs to get into the minute details about the user flows, user personas, user behavior, user interactions, call to actions and outcomes. This is an important stage so <strong>DO NOT MISS OUT THE GRANULAR DETAILS!</strong></p><p>With our founders, we use the user story document that narrates the entire product inform of a story. It’ typical format includes a sequence of wording like,</p><blockquote><strong>“As a &lt;user&gt;, I want to &lt;click the facebook icon&gt; so that I can &lt;view the latest social updates&gt;”</strong>.</blockquote><p>These stories are often coupled with defining the acceptance criteria for the development team to know what will be accepted when the story is delivered. Yes, it’s a laborious task but its worth spending time now instead of reiterating the code later in the dev cycle.</p><blockquote><strong>Outcomes:</strong> This phase is completed once we have detailed user stories developed. This phase also triggers the need for building the necessary content required for some of the user stories. This content includes narrative, headings, text for prompts, pop ups, messages, emails etc.</blockquote><h3><strong>III — User Interaction Design</strong></h3><p>This phase includes a sequence of diagrams to help clarify a user interaction visually. We craft the user journey and start building the foundation for the user experience. As <a href="http://someslightlyirregular.com/"><strong>Steve Krug</strong></a> explains in his book, <a href="https://en.wikipedia.org/wiki/Don&#39;t_Make_Me_Think"><strong>“Don’t Make Me Think”</strong></a>, the real user experience one should aim for is <strong>“Seamless”</strong>.</p><blockquote>The user should NOT be thinking, instead they should just be following what you really want them to do.</blockquote><p>With our founders, we have a practice of building sequence diagrams or interaction flow diagrams that highlights a users flow of interaction. These interactions are defined through the “call to actions” leading to the desired outcomes. Since this also includes the data being used, passed or processed during the steps, we also create a detailed information architecture to ensure a timely availability of all the information used / required in the product.</p><blockquote><strong>Outcomes:</strong> Information flow diagrams and Information architecture.</blockquote><h3><strong>IV — Mockups</strong></h3><p>Mockups, often terms as wire frames represents how the product content and features look on the web or mobile. It’s the placement of content on the application screens and defining a visual application without too much consideration of look and feel.</p><blockquote><strong>Outcomes:</strong> LoFi — Low Fidelity Wireframes are produced and can be used to run a demo with early users, partners, investors to get feedback.</blockquote><h3><strong>V — User Interface Design</strong></h3><p>This is the final stage of user experience design that fills in the aesthetics to the entire experience. Aesthetics are driven by typography, color schemes, design elements, pictures, videos and placement of content. Once the designs are done, the entire user experience is defined for the app and its ready to go into development.</p><blockquote><strong>Outcomes:</strong> HiFi — High Fidelity Wireframes are produced as a final version of the app before they are sent to the software development team.</blockquote><p>Many founders keep pushing the dev teams, keep iterating through dev sprints and keep incurring costs and burn resources. They often do not realize that it’s the initial thinking and attention to details that actually translates into a killer user experience. Spend more time building up the mockups before you even start your software development.</p><p>Remember, more changes you do in the later stages of the development lifecycle, more cost you incur on your application development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=816024caf333" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/how-to-build-a-wow-user-experience-816024caf333">How To Build A “WOW” User Experience</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Speed vs. Scalability Dilemma, or: How I learned to stop worrying and love CI]]></title>
            <link>https://medium.com/coventure/the-speed-vs-scalability-dilemma-or-how-i-learned-to-stop-worrying-and-love-ci-c778cc9cf303?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/c778cc9cf303</guid>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Adam Daw]]></dc:creator>
            <pubDate>Thu, 15 Mar 2018 20:09:59 GMT</pubDate>
            <atom:updated>2018-03-15T20:43:08.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*wMYEdZkOpnSNmW0IGVlLhA.jpeg" /></figure><p>It’s inevitable that at a given stage in the growth of your development team — either in the nascent steps of a company that’s focused on building software or later on in organizations with smaller internal IT or engineering initiatives — that the topic of speed vs. scalability will arise.</p><p>The positions typically pitted against each other are presented as something along the lines of “It’s just a prototype, we won’t be keeping this code-base” versus “I don’t want to crash the first time we get more than 1000 simultaneous users.” Both of these statements come from an entirely reasonable place, as the need to deliver and iterate quickly can be crucial for early-stage startups, and quality of service is one of the factors that is going to determine whether your offering is mere curiosity or can become an essential part of your users’ day-to-day.</p><p>At some point, you must make the decision: do we push a given component now, understanding and accepting the technical debt we’re incurring, or do we delay the release to triple-check, solidify the code-base and make sure all parts are scalable from the get-go. On a team of more than one developer, you’re going to have more than one opinion on this to one degree or another. The approach taken can either be mandated or reached by consensus, but regardless of how you decide on it, you will make compromises on speed or scalability.</p><p>You have to expect these compromises. In a game of limited resources, the allocation is never ideal. What I want to talk about today isn’t which of these sides is more or less correct, or why a particular decision is right at a given stage. Instead, I’d like to discuss tools at our disposal to mitigate the downsides of either approach: applications and processes we can implement to speed up or scaling or make our rapid iteration more stable. These aren’t necessarily new concepts, nor are they controversial, but it seems that sometimes we forget why we adopt or implement these devices. So for those to whom this is old hat, consider the following as homage to some familiar friends. If any of these approaches or concepts are new to you, then I encourage you to explore them further and share your findings as you implement them with your team.</p><h3>Continuous Integration</h3><p>The concept of Continuous Integration (CI) was first introduced in the early 90s by Grady Booch at Rational Software. Over the course of the past quarter-century, it seems to have evolved into an inscrutable or monolithic topic that everyone seems to know they need, but no one is quite sure how to go about implementing. Put simply; the concept is that “we should probably not all be working on overlapping and potentially conflicting pieces of code without making sure that they will work together on a regular basis.” Today, this is usually exemplified by the merging of multiple git branches into a master or staging main branch, resolving conflicts and performing testing on a regular basis.</p><p>Continuous Integration is a practice, not a specific application, though many tools exist to automate this process. Many of them are available for free to open source or initial prototyping projects, and a quick search for “CI tools” will present you with some options.</p><h3>Testing &amp; Code Coverage</h3><p>One of the steps that you can in your automation is testing. Testing in this context typically takes the form of Unit or Integration Testing for the various components of your application. What the difference between those two approaches is and how or where you want to use each is not the topic of today’s post, as each of those could benefit from more than one post on its own. Suffice it to say that through a continuous integration implementation, you can simplify the process of testing the overall code-base, as well as maintain or guarantee a certain level of coverage and accountability for your developers. By automating this process, you can approach the situation more objectively, and have a degree of confidence that you have tested any given component of the application with some rigor.</p><h3>Automated Deployments</h3><p>Errors will happen — bugs will never completely go away. We can, however, make the deployment or recovery process from an issue as fast as possible through inclusion in our overall automated process. We can automate the propagation of various branches to different locations, allowing features to be tested in an environment that resembles our production systems as closely as possible. Moving beyond simple testing, this can identify issues that would be obvious to a human but difficult to describe to an automated suite.</p><p>We can also use this process to quickly re-deploy when our systems fail, spinning up new servers, replicating databases and alerting the right people when our applications start acting out of character.</p><h3>Conclusion</h3><p>These tools and steps allow us a certain degree of comfort that we can build well and quickly without sacrificing the overall rigor of our process. By automating the approach, we lighten the load on the team while making sure that we’re protecting our users from the inevitable conflict or oversight. We can be anywhere on the Speed/Scalability spectrum, and the automation of these tools can be beneficial. Furthermore, implementing them early on in the growth of our application and engineering team can prevent significant headaches in the long term.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c778cc9cf303" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/the-speed-vs-scalability-dilemma-or-how-i-learned-to-stop-worrying-and-love-ci-c778cc9cf303">The Speed vs. Scalability Dilemma, or: How I learned to stop worrying and love CI</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Features Don’t Make a Company]]></title>
            <link>https://medium.com/coventure/features-dont-make-a-company-bc8c58edbaa3?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/bc8c58edbaa3</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Saumil Patel]]></dc:creator>
            <pubDate>Tue, 06 Mar 2018 19:02:59 GMT</pubDate>
            <atom:updated>2018-03-15T20:11:14.652Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*SHtr8c-VaQIgWfTeNz9QYA.gif" /><figcaption>Source: <a href="https://giphy.com/siliconvalleyhbo">https://giphy.com/siliconvalleyhbo</a></figcaption></figure><p>I assume you’re expecting a pep talk about cutting down your feature list. Well, you are absolutely right. This is that kind of an article. This is an article about lean startups. It’s an article about being agile. This is an article about doing 80% and leaving the other 20% for later. This is an article about laser beam focus.</p><p>Two weeks ago, my colleague <a href="https://medium.com/@karlclement">Karl Clement</a> wrote an article about <a href="https://medium.com/coventure/knowing-when-to-scale-5279c99034e9">knowing when to scale</a> and our null to 0 concept.<em> </em>Following this trend, I wanted to take a brief moment to speak to you about our lord and savior <a href="https://medium.com/coventure/the-first-mile-of-product-dd05fbc92f2a"><strong>Product Market Fit</strong></a>.</p><p>At CoVenture, we work with many early-stage portfolio companies looking to test their thesis in the real world and we do this most effectively with the help of an alpha release.</p><h4><strong>What is an Alpha you ask?</strong></h4><p>During a software product’s lifecycle, it goes through many phases and an alpha is its first.</p><p>You’ve got the perfect idea with the perfect value proposition for the perfect customers and now all that’s left to do is to build a laundry list of features that’ll keep us occupied for the next two years.</p><h4>Is that really the correct Approach?</h4><p>I think not. While working with several companies for the past one year and half, I’ve seen many examples of founders getting lost in features and of those, the most extreme example has to be my own.</p><p>Over the span of 2 years, we rebuilt our product twice to meet the ever-growing requirements list established by my co-founding team and potential customers alike.</p><p>Now having been through the process numerous times, I would have done many of those things differently.</p><h4>Features (seriously) don’t make a Company</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*thWnCrzH3FESAvI8J52BFQ.gif" /><figcaption>Source: <a href="https://www.gifbay.com/gif/when_i_see_someone_hacking_a_computer_in_a_movie-127955/">https://www.gifbay.com/gif/when_i_see_someone_hacking_a_computer_in_a_movie-127955/</a></figcaption></figure><p>During the validation phase of your startup, the most important thing is to find your <a href="https://medium.com/coventure/the-first-mile-of-product-dd05fbc92f2a">product market fit</a> and in most cases that isn’t really affected much by slideshows on your front page.</p><p>I’m sure you knew that already but where I can maybe provide a unique point of view is on the technical implications of such decisions. Lets talk about my own startup for an example.</p><p>The alpha release of our product was beautifully designed by our in-house designer and accompanied by a full dashboard for both sides of the two-sided marketplace. This was the dream, it had everything our customers ever asked for.</p><p><strong>BUT.</strong> There was only one small problem, we forgot to find our <a href="https://medium.com/coventure/the-first-mile-of-product-dd05fbc92f2a">product market fit</a>. Two years and two full iterations later, we realized that the path we had been all working towards had led us down the rabbit hole of just one more feature.</p><p>Having learned this lesson the hard way, I am now a big believer in Reid Hoffman’s quote <strong>“If You’re Not Embarrassed By The First Version Of Your Product, You’ve Launched Too Late”</strong>.</p><h4>What CoVenture does Differently</h4><p>At CoVenture, we break down our development into two separate builds to first allow our founders to quickly validate their idea and find their <a href="https://medium.com/coventure/the-first-mile-of-product-dd05fbc92f2a">product market fit</a> before we move onto the next build that then allows them to further expand onto their product with input from their customers.</p><p>This helps to mitigate risk and more importantly, it helps to save time, money, and effort both for you and your engineering team.</p><h4>Lesson Learned (Focus)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*QBsXiTwcCIkqeqChW-HQUg.gif" /><figcaption>Source: <a href="https://cheezburger.com/8305839104">https://cheezburger.com/8305839104</a></figcaption></figure><p>As a founder, it’s easy to get lost in all the little features that enhance your value proposition, but you also must beaware of the fact that the 80/20 rule applies to your engineering team as well. It’s your responsibility to look past all the noise and help your team establish that laser beam focus on your unique value proposition and not the stupid slideshow.</p><p>Interested in <a href="http://eepurl.com/dkHE2T">hearing more from us</a>?</p><figure><a href="http://eepurl.com/dkHE2T"><img alt="" src="https://cdn-images-1.medium.com/max/560/1*H3dSlsRDdvGu3kz11987Wg.png" /></a><figcaption>Source: <a href="http://eepurl.com/dkHE2T">http://eepurl.com/dkHE2T</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc8c58edbaa3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/features-dont-make-a-company-bc8c58edbaa3">Features Don’t Make a Company</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Dream Product]]></title>
            <link>https://medium.com/coventure/building-a-dream-product-287412f39ffc?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/287412f39ffc</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[minimum-viable-product]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jamil Goheer]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 10:45:28 GMT</pubDate>
            <atom:updated>2018-03-15T20:10:08.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CnPP3K_QKobkQzERtTccNA.png" /><figcaption>Building A Dream Product</figcaption></figure><p>You Are Damaging The Success Of Your MVP</p><p>Are you a product founder? Oozing with ideas and dreaming big? Excited to kick off your product development? Planning a big release? Feature rich? You think your customers would love it? Your competitors will be left behind? Finding it hard to leave out any feature? Itched?</p><blockquote>Well, you are lowering down your chances of success, manifold. If you want to keep them higher, remember to <strong>Sell first, Build Later.</strong></blockquote><p>A common trend we have experienced during our engagements with founders is about founders preparing for a large build. They are excited by their ideation process and plan to build and launch almost everything they have thought of. When we say everything, it’s almost everything. That includes essentials, well mostly nonessentials. It’s hard for them to digest a thought of leaving out a feature in a product launch. Two common blunders, that founders must avoid:</p><h4>1. Delaying their product release due to engineering, well over engineering</h4><h4>2. Delaying the critical customer feedback due to delayed launch</h4><p>Both contributes to failure and kill your game. Building a heavy product roadmap without prioritization locks one into a <strong><em>vicious cycle of product development, defect management and quality enhancement</em></strong>. Founders struggle to manage too many moving pieces. They don’t have a clear prioritization of features to roll out. They lose focus towards their monetization model. They are often sucked by development challenges and divert away from their milestones and core focus, that should have been, <strong>validating customer hypothesis</strong>. This delays their launch, cost them resources (money, man hours and critical time) and decrease their precious energy required to push forward.</p><p>Secondly, the delay in product launch, holds them from getting important customer feedback early in the development cycle.</p><blockquote><strong>The cost of software development increases exponentially along the product development timeline.</strong></blockquote><p>The more changes and tweaks required later in the timeline, the costlier and resource consuming is the process and product. Many founders, who discover <strong>customer feedback</strong> late in the cycle are highly vulnerable to starve from lack of resources. They are left with no runway to continue and they often crash. Actually, they mostly crash and shut down.</p><p>I remember, the first venture I was part of back in 2003, building a “Language Identification System” through signal and speech processing. We were very engineering focused team and somehow kept building the perfect product. We ignored the valuable customer feedback and could not really test the system early in the cycle with our potential customers. By the time we launched, we discovered some valuable feedback that required heavy re-engineering and resources. Another competitor in the market had already introduced an easier product that had a better customer experience. We had exhausted our resources and were left with hardly any cash. Our investors lost interest considering changing market dynamics. And we had to eventually shut down the company with a heavy heart and a pricy lesson.</p><h4>Remember: There are NO dream products. The Best are the ones directed by your users / customers. So get the product in the hands of your customers as early as possible.</h4><p>In our engagements with founders, we have over emphasized the importance of prioritizing user stories. We help define the customer journey and identify the essentials required to demonstrate the most critical business processes. These user stories are clubbed according to release cycles. A complete product roadmap is crafted for founders to keep iterating and keeping track of their product evolution. Every release is a production ready output that can be used by the user. Once identified, developed and launched, we keep iterating the backlog until we make a transaction ready MVP. Aim is to help founder test their business model as early as possible. Enabling founders to collect valuable feedback from their customers early and help them to pivot rapidly and save resources. They do get a bigger runway and considerably improve their chances of success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=287412f39ffc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/building-a-dream-product-287412f39ffc">Building a Dream Product</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The first mile of product]]></title>
            <link>https://medium.com/coventure/the-first-mile-of-product-dd05fbc92f2a?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd05fbc92f2a</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Brandon Waselnuk]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 22:40:14 GMT</pubDate>
            <atom:updated>2018-02-14T17:04:56.646Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iYju9vUptKj0PtAd." /><figcaption>“A dilapidated boardwalk in a forest” by <a href="https://unsplash.com/@elijahhenderson?utm_source=medium&amp;utm_medium=referral">Elijah Henderson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Building technology products is an incredibly complex process no matter what industry you’re working in. Just look at the body of work on every stage of the product lifecycle: from <a href="https://www.goodreads.com/book/show/10127019-the-lean-startup">Lean Startup</a> (and it’s thousands of iterations), micro services architecture, to <a href="https://www.goodreads.com/book/show/22668729-hooked">Hooked: How to Build Habit Forming Products</a>. However; one part of the process I find is constantly overlooked by founders today is, well, the first part.</p><h3>Ok, so what comes first?</h3><p>Business validation.</p><p>That is, speaking to actual potential customers / users (if you don’t have revenue plans just yet, that’s cool) and seeing if they understand the problem you’ve identified. Then worrying about whether they even <em>want </em>a solution to that problem. Finally, checking if they’d pay money / use your solution.</p><p>This seems like a no-brainer but the number of entrepreneurs that have presented polished slide decks to pitch us new and interesting businesses but haven’t even done this basic form of validation for a market, let alone a product, is getting to be alarming. You can’t just build it and expect people to come and ‘marketing dollars’ is not a viable answer.</p><p>You simply shouldn’t expect to be able to raise outside capital to build out a product without first being able to clearly articulate the market problem, the potential solution you have in mind, and show that actual customers have validated the need for this problem to be solved.</p><h3>Alright I believe you, so how do I get started?</h3><p>Write your assumptions about the market problem you’ve seen and structure around 3–5 hypotheses that you can isolate and test for in conversation with <a href="https://en.wikipedia.org/wiki/Subject-matter_expert">domain experts</a>.</p><p>Eg. “The average person is poor at personal financial management.” — This statement can be proven true or false in conversations with ‘the average person’ (your market at this time) and very likely lead to interesting conversations and outcomes.</p><p>Here’s a handy google sheet template to get you started; with examples! If it is of enough interest I’ll write a post to help guide you in writing hypotheses. Just let me know in the comments if you’d like that.</p><p><a href="https://docs.google.com/spreadsheets/d/1j9Im9NK01r0cfRopqgq2GoG8V5HpsynDHEKfHWUOzWg/edit?usp=sharing">https://docs.google.com/spreadsheets/d/1j9Im9NK01r0cfRopqgq2GoG8V5HpsynDHEKfHWUOzWg/edit?usp=sharing</a></p><h3>How do you know if you validated / invalidated your hypothesis?</h3><p>If you’ve followed the template (google link above in case you missed that) you’ll have created a hypothesis that is binary, that is it’s either true or false. Once you’ve collected data and if you’ve written it correctly you’ll know if it is a valid or invalid assumption you’ve made and you can start to plan to build your company.</p><p>That’s it!</p><p>Now you should be better informed about your market and can draft new, more refined, and more nuanced hypotheses to test against until you have a confident direction for the market and therefore a strong narrative that shows business validation to any potential investor.</p><p>Interested in <a href="http://eepurl.com/dkHE2T">hearing more from us</a>?</p><figure><a href="http://eepurl.com/dkHE2T"><img alt="" src="https://cdn-images-1.medium.com/max/560/1*H3dSlsRDdvGu3kz11987Wg.png" /></a><figcaption><a href="http://eepurl.com/dkHE2T">http://eepurl.com/dkHE2T</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd05fbc92f2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/the-first-mile-of-product-dd05fbc92f2a">The first mile of product</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Knowing When To Scale]]></title>
            <link>https://medium.com/coventure/knowing-when-to-scale-5279c99034e9?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/5279c99034e9</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Karl Clement]]></dc:creator>
            <pubDate>Mon, 12 Feb 2018 21:20:40 GMT</pubDate>
            <atom:updated>2018-02-14T17:20:58.368Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1peJxmYT3uu-e8HF6u-QtA.jpeg" /></figure><p>Recently, I was working on an application that required multiple repetitive tasks to be activated all at once. These tasks would be fairly simple and would require a user to have logged in as well as access to a hosted database to store all the details. Without getting into too much technical detail, there are multiple tools available to help me scale this process to millions of users. That’s when things can sometimes spiral out of control.</p><p>As a curious engineer, my immediate thought was to explore the possibility of micro-services and hosted serverless functions to extract this process from my main application. In short, this means I would need to split up my application in multiple places to make things faster (much faster).</p><p>This would allow the application to process multiple simultaneous tasks all at once, without skipping a beat. In other words, thousands and thousands of users can press the big red button at the same time.</p><p>It was at that point that I started to question my decision. In theory, using all these tools might sound correct, but is it the right thing to do right now? Am I thinking too far ahead? Most likely.</p><p>To remain consistent, let’s assume we are <strong>building a web application</strong>.</p><h4>What stage are you at?</h4><p>Determining which stage you are currently at, is the first step to establishing which tools are required to move forward. Not only in terms of your application, but for the business as a whole. Many, many engineers will try to build their application to handle millions of users when they haven’t launched a product yet.</p><p>If you are currently in beta with 600 users testing the application, there is no need to handle 100 000 concurrent users. Take your development step by step, while following the needs of the business at that point in time.</p><p>Time is your most valuable asset in the early stages of building your application — you should always consider how much time you are spending towards its optimization. Simultaneously, you must evaluate how much time you will need in the future to come back and fix everything.</p><h4>What’s your North Star?</h4><p>Every startup has a North Star. What is your North Star, and towards what are you working? This question should help you identify what is more important to the business at the moment. It’s essential to keep your North Star in mind, and never lose track of why you are building this functionality.</p><p>It’s always easy for a founder to say “Our competitor uses ElasticSearch, we should start implementing it too.” If your time is better utilized on another feature for the application, it’s important you voice your concern with the team. Otherwise, you might end up over-engineering in areas that won’t benefit the business in the long run.</p><h4>Use the tools you already have in your toolbox</h4><p>It’s easy to read an article about machine learning and assume your application needs it to survive. If your application’s core functionality does not rely on machine learning to function, start looking into hosted tools and APIs to make your life easier. You can easily implement Google APIs to solve your problem.</p><p>That’s just an example, but the point is that you should always consider the tools already available to you before trying to reinvent the wheel. This can help you move quickly and build the functionality your users are really looking for. Hosted APIs and SAAS applications are extremely useful at any stage of building your application.</p><h4>Always be planning</h4><p>While you are building all these amazing, groundbreaking new features for your application, you must always consider the areas that might need future revision. Don’t intentionally add in problematic code you know is a problem unless you have no other option. You are just asking for problems later down the road. Sometimes, things can get scary…</p><pre>getData(function(x) {<br>    getMoreData(x, function(y) {<br>        getEvenMoreData(y, function(z) { <br>            getEvenMoreData(z, function(wow) {<br>                // I forget where I was going here...<br>            });<br>        });<br>    });<br>});</pre><p>If you do add something you aren’t exactly proud of, please document everything. Whether you add some @todo comments in your code or you add it to a public to-do list in your repository’s readme file. Just make sure your team knows this is a temporary solution and we need to keep an eye on it.</p><h4>Good problem to have</h4><p>At the earliest stages of your startup, traction is probably one of the most motivating factors for your team: more and more users keep coming in droves, and you’re starting to feel the burn. This is a very good problem to have!</p><p>Once you have both product-market fit and consistent growth, you can start planning the next steps for scaling your application. There are tons of tools out there to help you measure exactly what is slowing down your app, causing bottlenecks or even failing for some users.</p><h4>Where to begin?</h4><p>This is the first of many posts covering scaling and tooling for software startups. We hope to cover many topics, including MVP building, tools for scaling, planning for scale, and more. This is where we will get into the nitty-gritty details of building applications.</p><p>We’d love to hear from you. If you have any subject ideas, questions or comments, please feel free to “clap” and comment below!</p><figure><a href="https://coventure.us17.list-manage.com/subscribe?u=bae34a222d1b9c0dbae763134&amp;id=157a2f5442"><img alt="" src="https://cdn-images-1.medium.com/max/560/1*H3dSlsRDdvGu3kz11987Wg.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5279c99034e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/knowing-when-to-scale-5279c99034e9">Knowing When To Scale</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Much Capital Should You Raise?]]></title>
            <link>https://medium.com/coventure/how-much-capital-should-you-raise-75aac0c4f203?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/75aac0c4f203</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Thatcher Bell]]></dc:creator>
            <pubDate>Thu, 09 Feb 2017 16:45:56 GMT</pubDate>
            <atom:updated>2017-02-09T16:45:55.573Z</atom:updated>
            <content:encoded><![CDATA[<p>Entrepreneurs embarking on a fundraising process struggle with this question. Will you suffer too much dilution by raising too much? Do you need to raise at least a certain amount to get the attention of certain investors? What if you set your sights too high and fall short?</p><p>I suggest that the answer is fairly simple, and should be guided by the needs of the company, not so much by the vicissitudes of the funding market. You should try to <strong>raise enough capital to achieve your next important milestone(s), plus enough for an additional three to six months</strong> of runway to enable your next fundraising process and to account for inevitable error in estimating the time you need to hit your milestones.</p><p>Determining your next important milestones is a non-trivial task on its own, but the first and most important hurdle should be that of the founders/management team. What do you need to prove to yourself to continue to invest your own time?</p><p>Often, entrepreneurs try to raise enough capital to hit several additional milestones (launch a product, hit a certain level of sales, etc.). The logic here is that fundraising is painful and distracting, so better to raise more sooner. If you can raise more money on acceptable terms, that’s fantastic. But be clear about the amount you really need to hit your next milestone (and raise capital after that) — that should be your minimum, even if raising that amount may put you back in fundraising mode sooner than you’d like.</p><p>Of course, if you are asked “Why don’t you raise more?” by an investor who seems interested, you should (happily) engage that question. Explain that you need a certain amount to hit your next milestones, but can put additional capital to good work (again, on the right terms). And, if you like, you can create an “aggressive” growth plan based on a larger capital raise than you might pursue as a minimum.</p><p>The important thing to remember is that you are raising capital to accomplish certain things — your milestone(s) — and to give you time to raise more capital if needed. Any additional funding is helpful, but only under the right terms.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75aac0c4f203" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/how-much-capital-should-you-raise-75aac0c4f203">How Much Capital Should You Raise?</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Valuing Startup Common Stock]]></title>
            <link>https://medium.com/coventure/valuing-startup-common-stock-cc347ea343e9?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/cc347ea343e9</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <dc:creator><![CDATA[Thatcher Bell]]></dc:creator>
            <pubDate>Thu, 09 Feb 2017 16:45:21 GMT</pubDate>
            <atom:updated>2017-02-09T16:45:21.525Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the years, I have had many occasions to talk about company valuations with founders. Whether negotiating the terms of an investment or discussing option grants at board meetings, the topic is central to the relationship between a company and its closest stakeholders — its shareholders. But while much has been written about company valuations and the negotiations that determine them, I find that little has been written, and many founders are uneducated, about how to value the common stock and options in their companies.</p><p>First, a few reasons why you should care about this topic, peppered with some key information about common stock pricing:</p><ul><li>Generally speaking, for a company with both preferred and common stock, the value of the latter is less than that of the former. The values are different because preferred stock comes with rights that the common does not have. It’s not unusual for the preferred shares to be valued at three times the common price.</li><li>The price of the common stock is typically the strike price for employee options (which are generally options to purchase common shares).</li><li>Pricing your common shares incorrectly or at the wrong time (see below) can lead to overpriced (or underpriced) options, tax consequences for employees or the company, and disappointed employees.</li></ul><p>Second, given the points above, you should be thinking (a) how do I price my common shares, and (b) when do I price them?</p><p>There are three ways to price common shares:</p><ol><li>The board of a company agrees to a common share price according to an analysis of the company’s value, declaring that value in writing.</li><li>The company hires an accounting firm which conducts a valuation of the company and determines a corresponding common share price; this is called a 409A valuation. This service generally costs several thousand dollars or more.</li><li>The company sells common shares (or issues them in exchange for consulting or advisory services) to an arms-length third party at a negotiated price.</li></ol><p>Generally speaking, most companies reprice their common shares (and therefore options) when they raise a new financing round. Most experienced investors will prompt the company to undertake a 409A at that point to ensure the common shares and options are appropriately priced.</p><p>Entrepreneurs need to be careful, though, to consider (re-)pricing the common stock at other points when appropriate. For example, it can be a good idea to set a common share price after a company is founded and has begun operations, but before it has raised capital from professional investors in a seed financing. Doing so ensures that employees and advisers who work with the company at this risky stage receive options (or shares) with an appropriately low basis (initial price). If the founders wait until they raise capital to set the common price, they may be tempted to set a price that is influenced by the valuation of the recent financing, which price is almost certainly higher than is “fair” for employees who joined before the company raised the round. On the other hand, granting options at the price set for founder shares (the lowest price that the shares are ever likely to bear) is also inappropriate, as employees who come on after the founders are taking on less risk.</p><p>For new companies that have not raised capital, in spite of the logic above, it can be tempting to put off a common stock valuation exercise. You may not want to pay for a 409A valuation or even have a functioning board. But experienced founders will tell you that it’s worth it to find a way to set a price if you are granting options or shares to employees or advisers. Those early supporters deserve fair treatment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc347ea343e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/valuing-startup-common-stock-cc347ea343e9">Valuing Startup Common Stock</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Principles of Good Projections]]></title>
            <link>https://medium.com/coventure/principles-of-good-projections-ccf2a35a63db?source=rss----bd5106bd7aac---4</link>
            <guid isPermaLink="false">https://medium.com/p/ccf2a35a63db</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Thatcher Bell]]></dc:creator>
            <pubDate>Thu, 09 Feb 2017 16:44:13 GMT</pubDate>
            <atom:updated>2017-02-09T16:44:12.664Z</atom:updated>
            <content:encoded><![CDATA[<p>This post was written for founders of relatively new businesses… it started as an e-mail to one such founder about how to build an early financial model and, in particular, how to project revenue.</p><p>I suggest you not try too hard (if at all) to make revenue projections until you start selling, or at least until you talk to many potential customers. You should have a reasonably good idea of what your customers might pay — based on numerous conversations if not actual paying customers — before you construct projections. Perhaps you’ve made a lot of progress and are already there. If that’s true, some things to consider when you create revenue projections are below. Most of these build on a key premise: as much as you can, you should <em>build the projections keeping in mind the way the business will actually work</em>. Here’s what I mean:</p><ol><li>In reality, you will control certain inputs that influence revenue: salespeople (note you are the first salesperson), marketing spend across various channels, etc. A simple subset of these <strong>inputs</strong> should be inputs to the model — numbers you can change that automatically change the projections.</li><li>Some measures of effectiveness (e.g. leads generated per $ spent on AdWords, $ sales per salesperson per time period, etc.) will be observable, and will be items you’ll try to optimize, but are not so easy to control as the inputs described in #1. You should also call out these measures as discrete <strong>assumptions</strong> the model. That way, you can easily change these assumptions to see what impact an increase in salesperson productivity might have, for example. You will also modify these assumptions as you get more data in the real world about your effectiveness.</li><li>For your first sales, you may input the revenue and support costs manually if you can guess at them. The same manual input process might be appropriate for various line items — if you know the cost of something, don’t create a formula to calculate it, just input it. But you should also layer in the ability to modify assumptions for revenue on top of what you know and/or further into the future (e.g. 6–12 months out and longer).</li></ol><p>These are fundamental principles of good projections. If followed, they should give you a model that can “live” with you as you grow the business. You can change the inputs and assumptions as you learn more about them to get better projections over time. You can easily change those inputs to see different scenarios for growth, and share the model with investors who can then easily review additional scenarios.</p><p>Much has been written about financial modeling for startups. Some of the best and most practical content can be found on <a href="http://foresight.is/">foresight</a> and was created by <a href="http://taylordavidson.com/">Taylor Davidson</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccf2a35a63db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coventure/principles-of-good-projections-ccf2a35a63db">Principles of Good Projections</a> was originally published in <a href="https://medium.com/coventure">CoVenture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>