If you have to be aggressive about user acquisition when you’re small, you’ll probably still be aggressive when you’re big. If you have to manufacture your own hardware, or use your software on users’s behalf, you’ll learn things you couldn’t have learned otherwise. And most importantly, if you have to work hard to delight users when you only have a handful of them, you’ll keep doing it when you have a lot.
- Recruit your user proactively
- go outside to find your users
- do not think that this a small number, gradually grow 10% users per week.
- Fragile
- Almost all startups are fragile initially
- Do not be arrogant
- Delight your users
Why should teach this thing, there are three reasons.- You’re supposed to build things that are robust and elegant, not be slavishly attentive to individual users like some kind of salesperson.
- Current larval state, funders have nothing to lose.
- But perhaps the biggest thing preventing founders from realizing how attentive they could be to their users is that they’ve never experienced such attention themselves. Their standards for customer service have been set by the companies they’ve been customers of, which are mostly big ones.
- Experience from your user
- The feedback you get from engaging directly with your earliest users will be the best you ever get
- Fire your market from a small group
- For B2B market, the best early adopters are usually other startups. They’re more open to new things both by nature and because, having just been started, they haven’t made all their choices yet.
- Meraki
- For hardware startups, fabricating things yourself turns out to be valuable for hardware startups.
- Consult
- In the beginning, building your software only for specific users, just like being a consultant for these users.
- Use your software yourselves on their behalf
- Manual
- When you only have a small number of users, you can sometimes get away with doing by hand things that you plan to automate later.
- Big
- the Big Launch usually doesn’t work
- Vector
- Try thinking of your startup ideas as pairs of what you’re going to build, plus the unscalable thing(s) you’re going to do initially to get the company going.

