Should I use ready made scripts or a custom solution?

The best way to build an MVP for any SaaS product is to create a landing page that looks like a real product. Here's an example of one I built. http://www.happiily.com In this case, it advertises the primary features of the product and invites people to sign-up. When they do, they are asked for information which qualifies the person and then sends me an email. I built this quickly and very inexpensively and started getting inbound leads from it shortly thereafter. I got on the phone with each person who signed-up and explained the features I wanted to build and was able to do a lot of customer learning based on that. Happy to talk to you in a call if you'd like to talk more about customer development with SaaS products.

Your skills would be most useful if you were starting your own startup and needed to make an early prototype to show to investors or potential cofounder developers. Your experience in debugging, testing, and agile, could help you get a job as a product manager, and the fact that you have a background in some sort of 'coding' will help too. It's very unlikely that it would help you get an actual dev job though, since you wouldn't be able to translate your programs into actual code that could be taken over/continued by other devs. Even if the programs you mentioned do allow you to export as code, it's unlikely that it would be exported in a way that's very usable by other devs.

Here are some options: ___Free Options___ 1) Make apps without needing to spend a lot of time learning to code. Look into "MIT App Inventor" (http://appinventor.mit.edu/explore/). It's a very _easy_ way to make pretty complex apps using drag and drop coding. You can find youtube tutorials that will show you how to make your first app within 5 minutes. I've used MIT App Inventor to make prototype apps for many of my ideas, saving me tens of thousands of dollars if I paid a dev to do it instead. Learn to do "real" coding yourself. The main investment will be your time. There are plenty of free resources for learning coding on the web. I'd suggest learning "React Native", it's a relatively new way to code apps, which allows you to make one app that will run on both Android and iOS. 2) Find a software engineer cofounder. Go to Meetups, conferences, local hackerspaces / makerspaces. Hang out on relevant online forums (e.g. https://www.reddit.com/r/startups/ make sure to read their rules for posting before posting though). It won't be easy to find a tech cofounder, your idea will need to be amazing, and you yourself will need to be very passionate and capable in order to convince someone to partner up with you for sweat equity. ___Paid options___ 1) Use developers with less established reputations / portfolios (lower cost, higher risk) Be very wary of freelancers on sites like Upwork, Fiverr, etc. Here are some basic hiring rules: In your hiring script, make sure to ask for all applicants to give their account name for github/bitbucket and Trello. Don't hire agencies, only hire individuals. To get hired, ask them to do a simple task via Trello and submit the code via github/bitbucket. This task should only take them maybe 1 hour. Check the quality of what the applicants and if they deliver it in a timely manner. Keep the 1 or 2 people that do a good job. If you don't do this vetting these "low cost" developers may end up costing a lot in the longer run. 2) Use developers with more established reputations / portfolios (higher cost, lower risk) With this option your app will probably cost > $20k to develop, but it can be worth it if you have a single idea that you know you want to move forward with. I can introduce you to a very high quality developer in NY if you're at this stage. Let me know if you'd like any additional help more tailored to your specific app ideas, best, Lee

Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!

I'm not sure if this is how you imagine this world to work, but at least according to the order you wrote it "raising funds" was first. In reality it should actually be one of your final steps of the stage you are at right now. It may even come after a year or two! So you have this great app idea, and you're looking for a place to start... Don't! Don't start yet before you decide whether you have what it takes to get into a roller coaster that can ruin your life and make you miserable! Not trying to scare you but I think most people only hear about these great success stories. They have this dream of maybe, possibly, becoming the next big thing... Because they have the best idea for an app... You don't hear about the failures so often. And even if you do, you don't hear about what the founders of these failing startups had to go through. Truth is you are most likely gonna fail. And I'm saying that without even knowing what your idea is. There are so many barriers on your way that even a great product with a great team is likely to fail. Some people would say "I'm not afraid of failing", "It's good to fail cause you learn", "Failing will make me stronger for the next startup". That's somewhat true but it doesn't mean that failing is easy. As oppose to what people sometimes say - you do not want to fail! It's very painful!!! You have to understand what failing in a startup means. You can work your a$s for 2-3 years, have little to no salary, waste other people's money (most likely your friends and family first), lose friends, fight with your partners, your family, your spouse, devote 20 hours a day for your startup all this time, forget about the little and big things you used to enjoy in life, and only then, after debating 100 times whether you should quit or not, you finally decide that it's not gonna work and you've failed. Disappointing your family, your investors, yourself. Trust me it is painful. Are you sure you wanna do this to yourself? If yes, give me a call. I have the experience you need! From idea stage, to proof of concept, to running beta tests, getting millions of millions of users in ways you can't even imagine, creating features and experience that will make these millions of users completely addicted and viral, raise money in a smart way, hire the right people, find a great co-founder, succeed, fail, be persistent, and enjoy the ride! Good luck, Roy