How to tell the story of your planned path from MVP to big growth when pitching to investors.

I started a large SaaS Company for B2B where perfection in code is as importante as it gets. So here is my advice, DON'T CODE until you know what the Saas Really is. First start understanding what the problem REALLY is. Interview people and actually spend 100% of your time doing Customer Discovery. (This sounds easy but it is a skill you'll have to develop far more important than coding). Once you understand what the problem is, come up with a value proposition. Still no code. Then make a sell. If you can actually find things already existing that you can Hack and put it together then use that. Then make another sell. If you can sell it to at least 50 people if you are B2C, or if you are B2B you should have at least 1 customer. Once you do that then start automating some parts of the solution that you have hacked and so on. But THE most important thing is to be in constant conversations with your customers and hot leads. Remember you are a customer making machine not a coding machine, the first one is where the money is. Hope this helped you, if you want to talk more about customer discovery and customer development, just give me a call.

I'm answering your question assuming that you hope to be able to replicate it's own success in your own mobile app. There are a couple of factors responsible for it's growth that are instructive to anyone building a mobile app. "Leveraging the intimacy and privacy of the mobile phone." We now have an *intimate* relationship with our phone like no other device in the history of technology. Every internet company that started before around 2010 has built their core interactions around "the old web" one which was accessed primarily via a browser on a computer. Companies that start with a clean slate, should be building their interactions around how to do whatever the app is supposed to do while leveraging what is unique to people's relationship to their mobile devices. Photo-sharing has become a core part of the way we communicate now. Snapchat built something that provided an experience that leveraged the feeling of privacy and intimacy that is unique to mobile. "Provided an escape from the "maturity" of other online services." Too many parents, aunts, uncles and other "old people" have encroached into the social networks of teens and young people. As a result, they've had a desire to find places to express themselves in places inaccessible by older generations. An important distinction is that it's not just parents and relatives that young people are trying to avoid, but also employers & colleges who are increasingly using "mature" social networks to review applicants. "Leveraged PR even bad PR" The fact that the app got so much press about it being used to sext was perfect PR for the company, as it essentially reinforced the brand experience that it has today. Essentially, "if it's safe enough to send a sext, it's safe for any kind of communication I want to have." And although the safety and security of Snapchat is actually not as advertised, it still enjoys the reputation of having less impact than any primarily web-based service. Building a successful mobile application is one of the hardest challenges to face designers, programmers and entrepreneurs in the history of writing software. Happy to talk to you if you're considering building a mobile app, about what I've learned about the "table stakes" for success.

Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.

There is quite a bit of information available online about eCommerce conversions rates. According to a ton of sources, average visitor-to-sale conversion rates vary from 1-3%. This does not mean the Furniture conversions will be the same. The bigger problem is that visitor-to-sale conversions are not a good data point to use to measure or tune your eCommerce business. All business have some unique friction factors that will affect your final conversion rate. It's very important to understand each of these factors and how to overcome them. The best way to measure and optimize is to take a conversion funnel approach. Once you have defined your funnel you can optimize each conversion rate to better the total effect. For example: Top of the funnel: - All web site visitors, 100,000 / month First conversion: View a product page, 50% of all visitors Second Conversion: Add to Cart, 10% of people who view products Final Conversion: Complete Checkout, 80% of people who put items in a cart In this example we see that only 10% of people who actually view products put them in to a cart, but 80% of those people purchase. If you can figure out why visitors are not adding items to their cart and fix the issue to increase the conversion rate, revenue should increase significantly because of the high checkout rate. You can use free tools like Google Analytics to give you a wealth of information about your site visitor and their behavior or there are some great paid tools as well.

Here is a link to a basic model - http://monetizepros.com/tools/template-library/subscription-revenue-model-spreadsheet/ Depending on the purpose of the model you could get much much more elaborate or simpler. This base model will help you to understand size of the prize. But if you want to develop an end to end profitability model (Revenue, Gross Margin, Selling & General Administrative Costs, Taxes) I would suggest working with financial analyst. You biggest drivers (inputs) on a SaaS model will be CAC (Customer Acquisition Cost, Average Selling Price / Monthly Plan Cost, Customer Churn(How many people cancel their plans month to month), & Cost to serve If you can nail down them with solid backup data on your assumption that will make thing a lot simpler. Let me know if you need any help. I spent 7 years at a Fortune 100 company as a Sr. Financial Analyst.