Wang Hua, the first group of Internet/mobile Internet entrepreneurs

Reprinted note:Http://blog.sina.com.cn/s/blog_67e201370100ld1f.html

 

Find one that is large enough, fast-growing, and still in the relatively early direction. It is not appropriate to start a business that is too small, too narrow, or too early or too late.

Create a team with someone you really know and trust. Entrepreneurship is a difficult process. Even if people who have known each other for 12 days have a great time, it is best to spend enough time to deepen understanding and build trust. Entrepreneurship is a lonely process. Two people often have better results in spirit, skills, and division of labor.

 

Find a good starting point:

1. Who is your product serving? You can clearly describe the user group in one sentence (all online users are not the answer. For an early product, you 'd better find a group of core users that are most needed, the more users you try to satisfy, the more complicated your product will be, the less satisfied you will be)

2. The core requirements and functions of the product can be clearly stated in one sentence.

If the two points cannot be clearly stated, it is not a good start point. In addition, do not consider your own assumptions and requirements as user needs.

Do not over fancy when selecting a start point,

It is not something that nobody has done. It is also a good way to learn from existing applications and models for incremental innovation or integrated innovation. At least it is verified user needs and business models, as long as you make a good separation point. If you want to create a new demand, it is best to determine that there is a significant amount of demand within a year. If you are far away, you 'd better find an intermediate transitional demand point within a year.

 

Before you start, you need to be clear.

How to promote and access your defined core users, whether there are low-cost user and traffic acquisition channels, depending on different products, may be a good user communication mechanism, Seo,

SNS websites, API cooperation, Mass Sending of user databases, forums, download sites, Internet cafes, website sites, bundling, presets, network alliances, appstore friends help and so on. Make full use of various open platforms. If there is no early low-cost user acquisition or promotion channel, do not do it unless your product can make money early.

 

Early ways to make money

Early ways to make money are not equal to the final business model of products. The importance of making money earlier:

1You will never be able to predict how long it will take to get the next sum of money. revenue can keep the team alive and take the initiative in front of investors.

2Any promotion is cost-effective, even if it is "free". If every user can earn revenue, the development speed can be increased several times.

Early ways to make money can be simple. It can be Internet Alliance, selling traffic, selling users, selling items, charging specific services, and e-commerce. It is best to make money without complicated business operations.

 

You can start to ignore income in the following cases:

1. The product has very low user acquisition costs
2. The product has very low user operation costs
3. The product has a huge number of potential users

If a project has no way to make money in the early stage and does not meet the above conditions, it is not suitable for a small team to start a business from scratch.

 

Start Product Development

Basic principle: Use the fastest speed to develop core functions, release them as soon as possible, obtain user test feedback as soon as possible, and improve (or give up) as soon as possible)

Like Microsoft, it is not suitable for the Internet to make a boutique or giant thing in 12 months, especially for small teams. The first stage of the team is the exploration direction, which emphasizesLow Cost and fast. All your plans at the beginning are actually just assumptions about users and the market. The money and resources of small teams are also limited. You must quickly find a way to verify the direction.

Therefore, the purpose of the first version of the product is to verify user requirements and feedback, rather than making a perfect and functional version. The first version should focus on developing core functions and core requirements. users spend 70% of their time on features and discard non-core requirements. For example, the download speed of the downloader is the core requirement, anti-virus, login, and social networking.

The first version is defined as 2-4 users who can be developed within 2-4 months and can be used by hundreds of thousands of users. If the time and resources are expected to exceed this time, the peripheral functions will be reduced and the design will be simplified to ensure that, before the money and resources are used up, even if the direction of the first exploration is wrong, there will be several times of exploration. No matter how complicated the Internet products are, I have never seen them be able to make an initial version within this development cycle.

2. Try to use ready-madeCodeFrameworks, templates, open-source projects, APIs, and the use of ready-made tools, even if not 100% meet the requirements, entrepreneurs with engineering backgrounds often prefer to develop their own architectures and technologies. In the long term, this is a competitive advantage, however, this can be used to verify user needs, and the number of users is being reconstructed.
4. As long as the requirements of users are met, the first version can use as simple a solution as possible, such as some background andAlgorithm, Which can be solved by means of manual intervention on the first Static Page
6. When the first version does not seriously affect the progress, try to consider the architecture that can be upgraded in the future. If there are any conflicts, refer to article 1.
8. Find all similar, related, upstream and downstream products, and fully study and learn
10. Find out what user behavior and data you want to verify and complete the data tracking and analysis module. Blind Data Collection is meaningless. Clear release targets and verification targets must be established before release.
12. The interface is concise, ensuring that the core functions are at the beginning. You can find them immediately and access them with one click without ambiguity. This is more important than beautiful styles.
14. Focus on the core functions with 80% of the focus, and make only one direction and one core requirement at a time. The core should be perfect unless it fails, and then explore in the next direction, do not make two directions at the same time.
16. Fast and stable is always the first requirement. Whether it is a website or software, basically achieving these two points is the premise for release, the function can be reduced, and the problematic function can be disabled first.
18. The product must have obvious and convenient user feedback interfaces and pay attention to user feedback.
20. Peripheral functions, especially websites, should be verified within a few days once proposed. If they exceed, they can be considered not to be in the first version to ensure core requirements.
22. Strict progress, day-to-day cleaning, in case of serious problems and bottlenecks, do not delay or excessively tangle, solve or adjust the plan as soon as possible, or give up quickly

Today we have written so much. For small teams to start a business, we have set up a run-up plan for the Innovation workshop. You can go and see it.Http://www.chuangxin.com/project/jumpstart