How to start developing a startup?

Question

Startups

Hello!
The idea of ​​a startup has been hatched for a long time, and now everything is at the investment stage. The total investment is $30,000. Requires terms of reference and the start of a seeding round.
The service is completely mobile, the web version is planned to be launched only as a last resort. I am a web and UI/UX designer myself.
Faced with the following questions:
1) How to correctly draw up a technical task?
2) How to find a programmer for backend development?
3) At what stage to hire an iOS developer?
4) What is the best way to set up this process for the best performance measured in quality and time?

Answer 1

All imho:
1) The terms of reference of a startup should describe the functionality + detail the implicit points in detail.
Writing according to GOST on 40+ sheets is a sure way to nowhere.
I categorically do not advise hiring anyone to write technical specifications - you, as the bearer of the idea, should do this.
If you are responsible for the design in the project, in principle, the finished design + frontend scripts + implicit backend scripts is a completely normal TOR.
* frontend scripts - a set of application screens with arrows "what happens when you click here"
** backend scripts - all the logic that is not obvious from the design.
Degenerate examples:
"When registering, the user enters the email and password fields, they are saved in the database" - not the right scenario, this is obvious from the design.
"After registration, the user receives a letter, here is a link to the layout" - the desired scenario
*** In general, it is strange to take investments without having a technical specification and, accordingly, a development assessment.
In my experience, $30k is more of an MVP than a full-fledged product.
2) hantim.ru , hh.ru , verified outsourcers, etc.
3) The correct order is: TK > Design > Backend Design > Backend Development > Mobile Development.
* If the deadlines are burning, you can collect mocks in a day before developing the backend and develop on them.
** If there are things in the backend that are not related to design, you can start doing backend in parallel with the design
4) В общем случае ответ на вопрос - нанять грамотного человека который будет рулить процессом разработки, но Вы тогда не влезете в бюджет. Книжек по менеджменту море, читайте )

Answer 2

С чего начать разработку стартапа?

С подтверждения того, что вас сервис кому-нибудь нужен и что пользователи будут готовы за него платить. Без этого все остальное может оказаться бесполезно.

Answer 3

Все перечисленные пункты действительно важны, но это только идейная и техническая сторона вопроса.
Начать надо с того, чтобы посмотреть на то, как экономически и управленчески развиваются стартапы. Желательно послушать питч-сессии - очень полезно. Был на таких недавно на прошедшей Startup Village 2016. Действительно много интересного. И кстати некоторые уже работающие стартапы говорят о том, что не правильно оценили потребность в своем продукте и после исследования рынка изменили свои проекты и теперь просят новых денег у инвесторов.
Иными словами важно правильно понять своего потребителя и свой бизнес в целом. Вопросы монетизации тоже не на последнем месте. А по указанным четырем пунктам, уверен вы справитесь.

Answer 4

1. In no case do not write TK. TK - this is only for custom development. Compiling a TOR is comparable in time to creating a minimum product version (MVP) and just reflects your hallucinations about your startup. Its value is zero.
2. You need to start by studying the theoretical material on the topic of startups. Watch the IIDF reports on youtube. They have a very good startup school, all reports are available in the public domain.
3. Find a partner to fill in your skill gaps. In your case, it makes sense to take, for example, an experienced full-stack developer, and for you to level up in the business part. Or involve a marketer-salesperson in the team, and you will master the development. Well, or a team to collect from more than 2 people, but it's more difficult. An additional plus of a partner in increasing mutual responsibility: you will kick each other in cases where, under other circumstances, you would relax and postpone the matter for later.
4. Be sure to discuss the working conditions with your partner in detail, including possible conflicts, ways for one of you to exit the business, and the procedure for closing the project. At some point, a detailed corporate agreement should appear. Believe me, this is very necessary, so that you don’t sue for years later.
5. Work systematically on the traction map ( firrma.ru/data/articles/3482/?sphrase_id=15453). Especially you need to learn problem interviewing and selling. Ideally, you should have some preparations so that you can make an MVP within 2 months after a problematic interview.
6. Never raise outside funds until demand is confirmed. If you needed 30 k$, then this means that your project is not worth a damn. External money can be attracted ONLY to expand an existing business.
7. Shrink your project to the minimum that can be sold at all (MVP). Instead of Android and iOS, make one web at the first stage (well, or try learning Flutter).

Answer 5

How to correctly write a technical task?

Make up as best you can, and if you don’t know how well, then it’s better to minimize and coordinate everything with the developer, a good technical task is part of the developer’s work, it will be easier with this, you can more accurately voice the amount, and it will be less, but bad is part of the work "with a minus sign".
Freelancing.
Immediately, and for Android too.
You won’t even have enough of the entire startup amount for better performance, so be specific.

Answer 6

1 describe everything you know and then ask the programmer if he understands after reading this that he needs to create
2 just like any other programmer on job sites
3 well, you must have a launch plan and launch date for the iOS application
4 agile scrum in your case will be probably the best

Answer 7

1) How to correctly draw up a technical task?

In simple human language, without abstruse formulations.
But take into account all the nuances.
What will not be agreed immediately - can be interpreted in any way. Or will require additional money. There can be no self-evident or "everyone does it, it's obvious" thing.
As usual:
Acquaintances, freelance exchanges, headhunter/recruitment firms.
When everything is ready, so that he can start work even yesterday.
No way.
Not all pros can do this.
Therefore, you don't.
I recommend watching the results of the work at least 2-3 times a week.