Users wouldn’t use my projects, because … there a lot of reasons. So let’s call it . because I don’t really understand that “startups vision-mission” thing. A Startup Anti-Vision First of all - don’t make this mistake: Don’t think, that anyone will use your product. That all-world population or the whole market will be your users. It’s your brain, trying to fool you. Ohh, thank you Brainie for this… Science behind this article calls it - “False consensus effect”. Read more at Wikipedia: https://en.wikipedia.org/wiki/False_consensus_effect I find this very interesting though. I’m proposing to other owners or wannabe-trepreneurs to play this mind game. You just need to list . Like I did it below. why nobody will use your product It’s a bit painful but important. An owner must be pessimistic. A lot of peoples cannot handle this, so… maybe… you will close this article? I’m building a few projects, so I’ll need to play in this game a few times. We’re trying to kill optimism for ChickenKyiv project(meal planning tool). Some information about this project you can find . here So, why a lot of users wouldn’t use project, that I’m working on 1) . They don’t know about my project. This problem is partly related to growth and marketing. (this is why I wrote an article at HackerNoon) They wouldn’t find us 2) . (Because I’m too lazy to build a complex project from start) My functionality is limited 3) . It works badly with mobile devices at this moment(we should make it better) Heavy-weighted project 4) (lazy, but right now I getting help from designers and frontend developers) Design with bad UI 5) . I set up SEO for my clients, but for now, I think this is not a necessity at current project stage SEO 6) — we should “play” with prices, then we’ll understand how much users want to pay for our services. High/low prices 7) I plan to have it low from the start because it’s an art — manipulate with this numbers. Right now it’s easy to increase user registrations, rather than make them pay > 12 months in a row Low customer retention rate. 8) Users can use and don’t want to make a transition similar projects 9) 80% of users, that will purchase our services, . will be gone after 1 year of using this service 10) Create a stunning support system is hard. Hope Intercom will help us, but we cannot use it in first stages. If project will grow — we should have at least 1–2 people that can cover 12 hours of ongoing support per day. It should be English native employee, maybe US citizen, because of timezone issues. Bad support. 11) and other problems, related to the development process Bugs 12) Hire (less than 10 years of experience) not experienced developers 13) Create a and raise a technical debt into the sky bad project architecture 15) Servers, hosting, uptime ( t stuff). environmen I’m just a developer, without a lot of knowledge about cooking (I can boil an egg, make a soup, or order pizza). But I cannot create a unique recipe-based content. And I’m not 100% clear about knowledge of cooking. So I can create a page, a block, but not a recipe. I don’t have “special feeling” about cooking. it’s bad. 16) Right now . So the functionality is really limited. I hope this will reduce the number of users too. People want to go to someplace -> see good products -> see a price tag and buy it -> like a standalone solution. This is not about my current project. parts of the project are separated 17) There are no innovations at this moment. A lot of projects with similar functionality are presented on the Web. This project cannot disrupt. 18) There can be a possibility to to work with have conflicts other programming languages or different platforms. 18) I don’t have a lot of connections with the US, where I plan to promote my project. I don’t have a mentor, that have an experience in the similar field 19) Let’s assume that this project will start to grow and will get first users. . And wouldn’t grow 10x of sales with next 6 months. It’ll grow slow Please tell me what do you think in comments below. Hope you’ll try this method with your product too.

2021 - Top Slogging Maestro

2022 - HackerNoon Contributor of the Year - Culture

2022 - HackerNoon Contributor of the Year - Elon Musk

2022 - HackerNoon Contributor of the Year - Email

2022 - HackerNoon Contributor of the Year - Futurism

2022 - HackerNoon Contributor of the Year - Life Lessons

2022 - HackerNoon Contributor of the Year - Npm

2022 - HackerNoon Contributor of the Year - Php

2022 - HackerNoon Contributor of the Year - Robotics

2022 - HackerNoon Contributor of the Year - Slogging

try my Email Marketing Course

Nominated for 2022 - HackerNoon Contributor of the Year - Robotics

Nominated for 2022 - HackerNoon Contributor of the Year - Life Lessons

Nominated for 2022 - HackerNoon Contributor of the Year - Npm

Nominated for 2022 - HackerNoon Contributor of the Year - Email

Nominated for 2022 - HackerNoon Contributor of the Year - Slogging

Nominated for 2022 - HackerNoon Contributor of the Year - Culture

Too Long; Didn't Read

Developers: Build Less. Deliver More. [Learn how]	

[Startup Anti-Vision] - Why I Think Nobody will Ever Use my Product 

[Startup Anti-Vision] - Why I Think Nobody will Ever Use my Product

Too Long; Didn't Read

Company Mentioned

Arthur

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

[Startup Anti-Vision] - Why I Think Nobody will Ever Use my Product

Too Long; Didn't Read

Company Mentioned

Arthur

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES