Many “CEOs” have a “great” idea and consider themselves “visionaries.” Over the years, after working with both successful and unsuccessful startups, I’ve learned that building the application is infinitely harder and more time-consuming than having the vision of the application. 99% of the time, the great idea feels like a smart idea without real research and analysis to back it up. Whenever someone approaches me to build an app or partner with them, I have a few entry-level questions for them to answer to determine if they are truly serious and have the correct discipline, training, and background to really work on an application. Much like a financial investor requires a pitch deck, I also require a deck to see if I want to invest my time and skills in the application. Here are some of the questions which I require in writing:
Regarding the idea:

1. What is the vision of the application?
2. What problem are you trying to solve?
3. What applications and/or businesses do you consider to be in the same market space as your vision?
4. What applications and/or businesses do you consider to be a direct competitor?
5. What is the differentiator of your vision; what is unique that the other businesses have not solved?
6. What is your research of tech blogs, news, etc, if the idea is a work in progress for some of these businesses? ( Many will announce future plans to their investors, which is public many times ).
7. What is your research on current patents that are near or similar to your idea?
8. What does an MVP look like, in your opinion?
9. What is your marketing strategy?
10. Do you already have test users available?
11. How much can you pivot from your original idea if you discover the market is not accepting your vision ( think Instagram from the original messaging app idea )?
12. How much money can you invest in the development costs – for example, GCP or AWS costs, hosting, domains, servers, test devices, development accounts, etc?
13. How much money is needed for marketing costs?
    Regarding building the APP:
14. What are your skills to properly test applications ( not just use it and say yes/no )?
15. How do you document issues?
16. What is your level of technical expertise? Can you follow instructions to install, use a test account, go through a user flow, etc?
17. Are you willing to learn these things until a team is available?
18. Can you give feedback in a timely manner? Within minutes/hours? I have to sacrifice this time for development. You should, too.
19. What is your availability on weekends, holidays, evenings, etc? I have to sacrifice this time for development. You should, too.
    If the CEO does not already have this information documented or is unwilling to work to create it, then they are not a good fit to build an application. These questions have weeded out 98% of the “I’m the visionary” people who are not dead serious about creating a business or a product.

If you are not technically proficient how do you accurately project how much development time will take? With previous technical expertise leaving, the issue is starting to make sense.