dqdo
1. Olin gives free tuition or reduced tuition leading to almost no debt. There is probably a positive correlation with not having school debt and starting companies.
2. Olin has a very small population size. The best and the worst cases can always be found in small sample sizes.
3. Schools such as Stanford, Berkeley, MIT, etc. have a wide range of students with wide range of interests. Most people do not go to these schools with the sole purpose of being an entrepreneur. There are many people that become doctors, writers, researchers, etc. and benefit society in other ways. Measuring just one narrow dimension may be understating contribution in other places.
4. Olin seems like a great place. It's small enough and independent enough to take chances in how it educates its students. Most older and more prestigious are more conservative in their teaching methods. Since Olin is fully endowed by one person with an open vision, they are able to do things that other institutions cannot.
Just a side note, most mediators are former lawyers. After many years of practice, they seek a better way to resolve conflicts. The pay isn't bad either.
One more thing. Randy is actually one of the best mediators in the world. After the 9/11 attacks in New York, Randy was called in to mediate and arbitrate the case with the insurance companies and tenants. After 2 years, they were able to come to an agreement and the resulting funds allowed for the area to be rebuilt.
http://www.wqsadr.com/randallwwulfffeescheduleandpolicies.ht...
You generally don't need a payment processor when starting out. The first ~200k in revenue can be done manually. Payment processing is something that takes time to do and most likely you will need to tweak it a few time as you figure out your business model.
>Paying for dev/design work by hour for a new startup is an insane concept to me now. There are always gonna be bugs, something that doesn’t work, something that needs to be added, etc.
Tech products are very complex. There are thousands of bugs and edge cases that needs to be resolved for a high quality product.
>And ideally, especially if you’re a non-tech founder like me, PARTNER.
One of the worst idea is to have non-technical people try to create a tech business without a strong technical co-founder. Imagine starting a dentistry office without any prior knowledge or a partner who is a dentist. Imagine trying to start a restaurant without a chef, etc. Creating a tech business is not a get rich plan. It takes a lot of skill, knowledge, and luck to get a business off the ground. Unfortunately, the media stories that we read make creating a great product or fundraising millions of dollars super easy. The reality is that running a start-up is probably one of the hardest things that one can do.
If you want to build for the web then I would recommend learning Javascript. You really can't avoid Javascript on the web so it is a good thing to learn it well. You can even learn Node in order to make it easier to set up a backend for your web app. The quickest way to get started with the web these days is to learn Javascript and use it with a Node server on the backend. There is a lot of noise in the Javascript community with tools such as React, Angular, Webpack, Typescripts, etc. that are very good for advanced production code. For a beginner, I recommend that you just stick with Jquery until you have to write a large codebase (>50,000 unique lines of code).
Python is just a pleasure to work with. I personally use Python to write code that solves math problems and to build small personal projects. Some people say that there is a problem with Python version 2 to 3 transition. As a new programmer this should not be a problem for you. Just start with Python 3. If there is a package that you want to use, it will probably be ported over soon. If you start with Python 2 then you will need to update your codebase for the transition which is neither fun nor worth your time as a beginner.
Ruby is a great scripting language. I think that many of the things that you can do with Python you can do just as well with Ruby. If you are already good at Ruby or know some people who can help you then you should go with Ruby. If you are new to both Ruby and Python, I would recommend learning Python since there are way more applications for Python (i.e., data science and machine learning).
German Car Makers Preparing Formal Bid for Nokia’s Here Map Service
From an economic perspective, you can imagine that a lawyer can typically bill 2000 hours per year. If the lawyer's salary + benefits + retirement contribution is 150k per year, they would need $75 per hour to cover this cost. Since the lawyer is working for a big firm which has high overhead costs and a goal of returning profit to their partners, the amount that they bill typically 3X their hourly salary (3X $75 = $225). This is why it is so expensive to hire an attorney. For large corporations, this fee is reasonable since they have millions of dollars at stake in an M&A transaction, IPO deal, or patent litigation. For regular working folks, this is often unaffordable. Due to the bifurcation of the potential clients (big business vs. everyone else), there is also a bifurcation on attorney salaries.
Firstly, what you are suggestion is very doable. You might want to look at Jquery UI draggable elements https://jqueryui.com/draggable/#scroll. There is nothing technically challenging about this concept.
Secondly, your specification is too vague for anyone to actually build. Programming is an exact art since the computer is the most unforgiving thing to work with (computer = fast + stupid). I would suggest that you work with a UI/UX (user interface/ user experience) person to refine your specifications. It would be helpful if the UI/UX person has some experience with programming to validate your concept and turn the idea into build-able specs.
Usually programmers work with UI/UX designers (and sometimes visual designers and marketers) to vet out the concept before starting to work on the code. The reason for this is that coding is a big investment in time and just the slightest change can have profound effects on the underlying code because fairly simple things can turn out to be very complex when you factor in everything.
The way that you have your description right now, most competent programmer would not be interested in this project because there seems to be a big gap between what you want and what you know from the technical perspective. My advice is to narrow this gap by enlisting the help of a UI/UX designer first.
Analysizing Your Business Through Supply and Demand Sides
Given how fast we are moving in the world in terms of technology and business, there are new break throughs and developments everyday that can change the landscape of entire industries. As a CEO, your main role is to understand this landscape and have a vision for the next 2 to 5 years in the case of technology companies. For older and less turbulent industries this could be 5 to 10 years.
Keep in mind that what I am saying applies to companies with +100 employees. For early stage start-ups, the CEO will have to wear multiple hats and have to take a hands-on role otherwise the company will not have enough revenues to survive. Once you have pass the threshold of survival (~100 employees), you need to reorganize your company for growth. This is a difficult transition for most start-up CEOs and the dirty little secret that VCs keep from founders is that few founder CEOs make it through this transition.
One of the best way to ensure growth in your organization is to learn about the ever changing world outside of it so that you can help the rest of the organization continuously grow and thrive. One way of doing this is to look beyond your own industry and explore how other industries are dealing with their problems. Different industries are more advanced in different area so use this to your advantage. You can "steal" the best ideas and use them to improve internal operations. Remember that at this stage in your company, you are not really building anything new. Instead you job (which is just as difficult) is to improve on whatever already exists.
One reason why you should use your spare time to learn is that some companies actually march towards a wall because they are too busy pursuing immediate profits. This is the argument behind Clayten Christensen's book the Innovator's Dilemma. It is a great book and I would highly recommend it to all CEOs whether in start-ups or in large organizations.
Your conversion rate depends on the marketing channels that you use to bring your users to your landing page and how relevant your product offering is for the customers. You should track the conversion rate of your different marketing channels to optimize your marketing spending mix (e.g., spending on X brings Y number of leads per month with Z percentage of them converting). Different marketing channels and marketing campaigns can bring in radically different results so you should focus your spending on the ones that bring the most bang for your buck.
The more money you spend on marketing, the lower your conversion becomes. This is due to the fact that over time, you start getting lower quality leads to your website. This is analogous to mining in less resource rich areas. As a company, your goal is not to maximize your conversion rate (the effectiveness of your spending) but rather to maximize your profits. If you think carefully, it may make sense that the conversion rate (effectiveness of your spending) can decrease while your profit increases. You can find more about this argument in the economic concept of marginal vs. average cost.
For SAAS products, the most important metrics are: Life Time Value, Acquisition Cost, and Churn Rate. You just need to make sure that your (LTV - Acquistion Cost) > Profit + Costs and that your churn rate is not unreasonably too high. A high churn rate (>5% annually) limits the potential growth of your company in the long term.
The first strategy (Freemium) is only appropriate for a very very small segment of saas applications. This model relies on huge network effects (aka your product becomes more valueable as more people use it -- think Dropbox) and often times 1% of the paid users cover the cost of the product. Most companies that follow the Freemium model often burn cash very quickly and rely on VC money to stay alive in the first 5 years of operations. This is not a recommended strategy for most Saas products and should be avoided unless there is clear evidence that your product benefits from the network effect and that it is more valuable to monetize later on. The other situation where this strategy might be appropriate is if you think that there is a high probability that your users will convert to paid customers in the near future.
The second strategy (Paid subscription with a short trial) is the most common strategy of Saas products. The reasoning behind this strategy is that it gives the users a way to evaluate the software at a very low risk for a limited amount of time. If the user finds value in the software, then they would convert to purchasing it. For most Saas applications, there is almost no difference between 14 days, 21 days, or 30 days of free trial. So optimizing for the time period of the short subscription is usually not the best use of your time.
The third strategy is the paid subscription with a long trial period. This strategy is applicable for big business applications where it may take a very long time to train and get everyone onboard the software. This strategy should be used in the case where the number of users for the software within an organization is very large (100s to 1000s). The risk of using this strategy over the paid subscription with short trial is that you give the users too long consider the purchasing decision. By giving them 2 months, some users might forget about the software and why they were looking for it in the first place. A situation where this strategy is ideal is when there is a very high cost of switching to alternatives. For example, AWS offers 1 year of free tier EC2 because they know that once you start using their product, it would be relatively difficult (time consuming) to move your web product to App Engine or Rackspace.
The fourth strategy is the money back guarantee. This is effective in separating the people who truly want your software from the people who are just shopping around and it makes the buying decision very close to the beginning of the experience. The risk of this strategy is that some people may be reluctant to give you their credit card information at the beginning unless your product is very known.
TLDR: there are four different types of strategies that you can use in this situation. For more established companies who have well known brand recognition, I would recommend using the money back guarantee. For most saas companies, a subscription with a short trial period is the recommended strategy unless there is evidence to suggest that a longer trial period would be more suitable for your software.
And finally there is one last thing to consider. Certain markets have existing expectations for pricing and pricing strategies which you really have no choice but to follow. The example that comes to mind is the database as a service market. Both Parse and Firebase (as well as any other saas company in this segment) offer users an unlimited time free trial. They expect to make their money after the user's data usage increases which would naturally convert them to paid users.
One last comment before I go. Remember that "strategy is choosing what not to do". Out of these four strategies, you will need to determine which bucket your product fits in and use the appropriate strategy.