A hundred different engineers would answer that question a hundred different ways. Software engineers have styles and preferences, just like musicians. One swears by Ruby on Rails. Another works exclusively with a MEAN stack. Here's the elephant in the room: if you're a non-technical founder, you can't answer your question for yourself, and you likely won't understand the answer that a technologist gives you. You're not an architect, so what can you do with a blueprint? A better question might be, "What is the best way for a non-technical founder to develop software?" To that question, I would respond, hire a CTO-type to consult with you, architect your app, and hire a junior developer to build the thing. Here's a blog post that has more details on this approach: http://blog.closeup.fm/2014/01/24/how-to-hire-a-php-developer/.