How can I go about building a website from scratch without the technical knowledge?

A generalized question can only get a generalized answer. The most significant accomplishment is validating that the product you have built is a fit with your target market. This is demonstrated primarily by engagement (the people who sign-up or who previously visited, continue to return) and secondarily by growth, ideally based on word-of-mouth or viral growth but effectively converting paid traffic is a great second prize. Other significant accomplishments include: Not running out of money Recruiting and retaining great talent who believe in the founders' vision. Your loved ones not thinking you're as crazy as they thought you were a year ago. I'm happy to talk to you in a call to give you more specifics about what you want to set as your goals more specific to your startup.

Dilip was very kind in his response. My answer might be a bit on the "tough love" side. But that's for you to decide. My intention, just for the record, is to help you (and those like you) on your path to success. And that starts with having a viable philosophy about entrepreneurial-ism and business. And I'm going to answer this because I get asked some form / version of this question very frequently from newcomers to entrepreneurial-ism. The scenario goes something like this: "I have a great idea. It's amazing, I love it, and I just KNOW it's gonna make me a ton of money. But I have no money right now so I can't afford to (fill in the blank with things like "to build it / create it / market it / etc" or "to hire the required staff needed to work in my business to sell it / develop it / etc"). And I don't want to tell anyone about my great idea because I'm worried someone will steal it and make MY million / billion dollars. But I can't afford to legally protect it either... So how do I launch without the skills to personally create the product AND no money to hire anyone else to do that either??" The answer is ... You don't. Look - let's be honest. All you have is an idea. Big deal. Really. I'm not saying it's not a good idea. I'm not saying that if properly executed it couldn't make you a million / billion dollars... But an idea is NOT a business. Nor is it an asset. Until you do some (very important) initial work - like creating a business model, doing customer development, creating a MVP, etc - all you really have is a dream. Right now your choices are: 1. Find someone with the skills or the money to develop your idea and sell them on WHY they should invest in you. And yes, this will mean giving up either a portion of the "ownership" or of future income or equity. And the more risk they have to take - the more equity they will want (and quite frankly be entitled to). 2. Learn how to code and build it yourself. MANY entrepreneurs without financial resources are still resourceful. They develop the skills needed to create what they don't have the money to pay someone else to do. 3. Get some cash so you can pay someone to do the coding. You'll probably have to have some knowledge of coding to direct the architecture of your idea. So you will likely still have to become knowledgeable even if its not you personally doing the coding. (This is not meant to be a comprehensive list of options... And I'm sure some of the other experts here on Clarity have others to add - and I hope they do) To wrap up - Here's my final tip to you that I hope you "get"... It's FAR more valuable to have an idea that a very specific hungry crowd is clamoring for right now - One that THEY would love and pay you for right now - Maybe even one they'd pre-order because they just have to have it - Versus YOU being in love with your own idea. [Notice I didn't say "an idea that some as-of-yet-undetermined market would probably love"] I wish you the best of luck moving forward.

Yes Wix supports a mulitude of APIs to used for various fetch calls for your web pages. If you already have to API's in mind you can venture off within you WIX code to integrate within your application's processes. There shouldn't be any complications getting this done. Please see the link below for more information https://www.wix.com/code/home/api

If you're not technical yourself, then you might not be able to gauge the efficiency of a candidate's algorithms or critique her code. But there are still some higher-level, more behavioral things that a non-technical interviewer should be looking for in a strong development candidate: 1. What are some tech blogs that you follow? Explain an interesting article to me that you read from one of them. The software development world changes all the time. Best practices are constantly evolving and new libraries are regularly released which make developers more productive. If a candidate doesn't keep up with the latest software news, that might be a red flag that they're not curious or trying to improve themselves. Also, having them explain a technical concept to someone who's non-technical is a great way to gauge their communication skills. Do they seem like someone you could work with and understand easily? Do they care about pausing to make sure you understand, or do they just drone on with jargon? If you feel overwhelmed while they're explaining this answer, imagine how you'll feel when they're telling you why the product has bugs or isn't going to be done on schedule. 2. Tell me about a time you ran into a big roadblock with something you were building. How did you get past it? It's inevitable that a software developer will get tripped up or have to solve some Gordian Knot. Everyone has to bang their head against the wall from time to time. Maybe an API didn't have the data they needed or some function was running too slow and they weren't sure how to speed it up. You're looking to see how they are as a problem solver. Did they come up with a clever but hacky solution? Were they methodical or did they fly by the seat of their pants? Did they go back to the stakeholders and see if the feature's requirements were flexible? Did they work on it for hours and hours trying new things? Did they ask for help from colleagues or on the internet? No right or wrong answers here, but you want to get the sense that this isn't someone who throws up their hands when they hit some friction. 3. Tell me about your favorite project that you worked on. What work are you most proud of? By asking them about the project they're most proud of, you'll get to see what it is that they value most. Maybe one candidate is most proud of a side project they built, even if it wasn't that technically complex, while another candidate is proud of their esoteric PhD project or some specific algorithm they improved. Again, no right or wrong answers, it really depends what type of candidate you're looking for. But it lets you see into their mind a bit, and get at some of the aspects that can make someone a strong development candidate. If you want to talk more specifically about hiring for your team, I'd be happy to do a call!

Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.