5 ms·
>you're doing is not startuppy enough to count I have always had a problem with that. A start-up is a start-up if you decide it's a start-up and want to transf
by prayag 15y ago
>you're doing is not startuppy enough to count
I have always had a problem with that. A start-up is a start-up if you decide it's a start-up and want to transform it into a viable business. There is no magic line that you have to cross to transform your project into a start-up. I always advice people to call their projects a start-up from the beginning.
- riffraff 15y ago> I always advice people to call their projects a start-up from the beginning Could you expand on why you advice this, meaning, what is the advantage of it? According to your post simple message above it could be the other way around (always call your startup a project).
- prayag 15y agoFirst of all, it makes you take it seriously. It's not a side project that you are doing. You think of it as work as something that is going to pay your bills at some point. You work harder, you take smarter decisions and you start thinking about customers early. Secondly, other people take it more seriously. Everyone has some sort of a side project, very few people have a start-up. They give you more time and listen to your more intently. All anecdotal, no data to back any of the claims.
- gujk 15y agoIt boosts morale and makes you more excited to work on your project.
- sathishmanohar 15y agoI prefer not calling projects startups, Since, I try many projects, So, calling something startup, after "rails new project_name" sounds like a disgrace to a startup to me. (ofcourse, opinions differs)