Founder of Innovation Workshop on Internet/Mobile Internet Small Team Entrepreneurship

This article aims at the Internet/Mobile Internet Small team entrepreneurship


find a big enough, fast growth, still in the relatively early general direction, entrepreneurial to homeopathy, too small too narrow, too early too late are not appropriate.


Find someone you really know and trust, board the LDTX team. Entrepreneurship is a difficult process, only to know 1 2 days of people even talk about it, it is best to spend long enough time to deepen understanding, build trust. A person entrepreneurship is a lonely process, 2 people in the spirit, skills, division of labor often have better results





Find a good product entry point: 1 Your product is for who services, can be a clear description of a clear user group (all Internet users are not the answer, for an early product, it is best to find a group of the most needed core users, trying to meet the more users, often your product will be more complex, The more not to let everyone satisfaction) 2 can be a word clearly, product core requirements and core functions if these two points can not be clear in two words, it is not a good point of entry. In addition, do not regard your own assumptions and requirements as the needs of the user


Choose the pointcut when not over fancy, do not have to do what no one has done, learn from the existing applications and models to do incremental innovation or integrated innovation is also a good way, at least the validated user needs and business model, as long as you make good partition points. To make a new demand, it's best to make sure that the demand is clear within a year, and then it's best to find an intermediate transition demand point for one year.


before you start, you need to be aware of how to promote and access your defined core users, there are no low-cost users and traffic access channels, according to different products, may be good user communication mechanism, SEO,SNS website, API cooperation, user database mass, forum, download station, Internet cafes, web site, bundle, preset, Network Alliance, the App store friend help and so on. Make full use of open platforms. If you don't have early, low-cost user access or promotion channels, don't do it unless your product can make money early.


early methods of earning money were unequal to the final business model of the product. The importance of making money early: 1 You never can predict how long it will take to get the next amount of money, the income to keep the team alive, and to get the initiative in front of the investors 2 any promotion is cost, even if it is "free", such as the acquisition of each user can bring income, That can increase the speed of development several times early ways to make money to be simple, can be the network alliance, selling traffic, selling users, selling props, specific service charges, E-commerce, to do not require complex business operations should be


You can start without considering your income: 1 products have very cheap user access cost 2 products have very cheap user operating costs 3 products have a huge number of potential users


If a project does not have an early way to make money and does not meet the above conditions, then this project is not suitable for small teams to start from scratch,


start the basic principles of product development: the fastest speed to develop the core functions, as soon as possible to obtain user test feedback, as soon as possible to improve (or give up)


like Microsoft, using 12 months to make a boutique or behemoth is not suitable for the internet, especially for small teams. The first stage of the team is to explore the direction, emphasizing the low cost, fast. All the projects you start with are just assumptions about the user and the market, and the small team's money and resources are limited, and you have to quickly find a way to verify the direction


so the first version of the product is designed to validate user needs and feedback, rather than doing a full-featured version. The first edition should focus on developing core functions and core requirements, and users spend 70% of their time to give up non-core requirements. For example, download speed is the core needs, antivirus, login, social may be the external needs.

The first version of
is defined as 2-4 people can be developed in 2-4 months, can be used for hundreds of thousands of users. If you expect to exceed this time and resources, cut the perimeter and simplify the design to ensure that you can do several explorations before money and resources are spent, even if the first exploration direction is wrong. No matter how complex the Internet products are, I have not yet seen an initial version that cannot be reduced to this development cycle.


1 Use the ready-made code framework as much as possible, templates, open source projects, APIs, the use of off-the-shelf tools, even if not 100% to meet the needs, engineering background entrepreneurs tend to like to develop their own architecture and technology, in the long term this is a competitive advantage, but this can verify the user needs, with user volume in the refactoring


2. As long as the user needs, the first version can be used as simple as possible solutions, such as part of the background and algorithms, can be static page, manual intervention methods to resolve


3. The first edition does not seriously affect the progress of the situation, as far as possible for the future to consider upgradeable architecture, if contradictions, refer to the first article


4 finds all similar, related, upstream and downstream products, Full research study


5 figure out what you want to verify the user behavior and data, do a good job of data tracking analysis module. Blind data collection does not make sense, should have a clear release target and validation objectives before release


6 interface Concise, to ensure that the core function in the first interface of the main position, users can immediately find, a key access without ambiguity. It's more important than aesthetic style


7 focus on 80% of the focus on the core functions, one time to do only one direction, a core requirements of the exploration, the core to achieve more perfect, unless the failure, and then do the next direction to explore, not at the same time to do two directions.


8 Fast, stable is always the first requirement, whether the website or software, basically do these two points is the premise of the release, function can be reduced, the function of the problem can not be opened first


9 products to have a clear, user-friendly user feedback interface, pay attention to user feedback


10 peripheral functions, especially the website, to do once proposed, can be implemented within a few days of validation, if more than, you can consider not to do in the first edition, to ensure that the core needs


11 Strict progress, day after day, if the bottleneck of serious problems, do not delay or excessive entanglement, as soon as possible to resolve or adjust the plan, or quickly give up the source address: http://blog.sina.com.cn/s ... 0100ld1f.html