But the Big Ideas don't happen here. That comes by doing customer discovery, reaching out, and engaging in live conversation.

For just one of your ideas-- can you identify and talk to 100 potential end-users and buyers? It takes a long time to actually connect with these people. You'll get blown-off or simplistic good luck platitudes. But every now and then, you'll find someone generous with their time, and thoughtful feedback. Those people are golden and will make all the difference. Incidentally, here's good read on Give & Take > http://www.goodreads.com/book/show/16158498-give-and-take

So true. Go out and talk to people. You'll be amazed by how better your brainstorming gets.

In the end, there are usually two main routes for ideas. Enterprise products are easy to profit from, you just need to know the space, talk to potential customers ahead of time and do it. Boring but profitable. Consumer ideas are much harder. Everyone can get ideas for consumer products (do we really need another dating app?).

So choose wisely. Is your real goal to build a small but sustainable stream of income? Choose enterprise. Are you dreaming big? Maybe try consumer.

Reaching out to potential customer isn't what I'd consider one of my strong points. I think I'll be taking some time to think about, and read up on, how best to go about this.

I would then attempt to workout exactly what the business model and your value proposition to your consumer would be. I've read the Business Model Generation book and I found it to be helpful and thorough in coming up with ways to generate potentially profitable businesses. Their second book, on Value Proposition, looks fascinating as well. http://businessmodelgeneration.com/

They also provide downloads for blank canvas' to print out and use during your brainstorming sessions. https://strategyzer.com/canvas?_ga=1.134434994.233324054.141...

Edit #1

I would also look into reading Lean Startup (http://smile.amazon.com/Lean-Startup-Innovation-Successful-B...) if you aren't already familiar with developing MVP's, especially landing pages for gauging consumer interest in your idea.

Edit #2

I would also read 'Goodbye Minimum Viable Product, Hello Maximum Value Proposition' (http://torgronsund.com/2014/12/04/minimum-value-proposition/), which includes the video i posted earlier, as well as an intro to Simon Sinek's work on Why How What.

It's not so much the problem of finding a business model I'm struggling with – it's not knowing when to run with an idea as opposed to sitting on it and looking at other avenues. I think it might be something you learn through experience (and failure). I was just hoping to see other peoples view on it.

I have a friend who wants me to work with him on a project. The problem he is trying to solve doesn't scratch an itch for me though. I have noticed, for me personally, that I am more motivated to work on something if the solution solves a problem I am currently experiencing.

First stop for you is to watch @DHH's startup school talk . . . most ideas that are successful are simple . . . it really is all in the execution.

Link to DHH at Startup School: http://www.youtube.com/watch?v=0CDXJ6bMkMY It's from 2008 but still inspiring and relevant.

Ok . . . so you're inspired . . .

Don't just build the software . . . you'll fall in to the trap of spending too much time building something your customers don't want or doesn't provide enough value.

Read Dan Norris's book the 7 day startup and listen to his podcast.

And listen to StartupsForTheRestOfUs.com.

Lots of good info on proving an idea, talking to customers, building an email list.

The key is launching fast with minimal development time. Once you have paying customers you can automate and improve your app/software to provide even more value with less effort on your part.

I would pick something you like thinking about/would enjoy working on and would enjoy dealing with the potential users.

There are infinite ideas/opportunity out there in apps/saas so don't worry about that . . .

@DHH "Zappos is selling F'n Shoes . . . "

Execute, do it right and provide value to your signups and you'll be revolutionary.

Remember you don't need an office, an LLC or anything else in the beginning . . . just start getting to know potential paying customers and build out the simplest version of your app that clients can sign up for. Once you have revenue you can think about office space (if needed) an LLC, etc.

Services/Ideas to help you get off the ground for low/upfront costs:

Rails/Laravel (frameworks) Digital Ocean (hosting) Stripe.com (payments) Mandrill.com (App emails) MailChimp.com or Drip.com (building an email list)

Also start blogging now about your product/niche right away.

Feel free to email I love talking SaaS/apps, startups and bootstrapping.

I've been running this same playbook and will be launching my second SaaS in early 2015.

Good luck in 2015!

I'd like to avoid the cost of office space but I would literally not do an iota of work from home. Home is for home stuff, work is for work stuff; that is how my brain works. I'm in Europe and my desk is costing me €160/month so it's not exactly an especially taxing expense.

I keep my ear to the ground with regards start-up news but I think I'm going to spend some time listening and reading to some of the resources you and others have posted. Hopefully it will help me narrow down what I'll ultimately set out to create.

And thanks for the offer. The best of luck to you as well.

y, the podcasts and Dan's book are great resources . . . be careful about listening and reading though . . . get the good gems of information and then take action . . . you can spend months/years listening to other people and how they executed.

http://yourstory.com/2012/11/my-name-is-porn-entreporn/

So listen, learn and take action . . . otherwise time will pass you by . . .

BootStrappedWithKids.com has some gems as well . . .

And of course read/listen to everything by paito11.

One of these days I'll take my own advice...

http://www.paulgraham.com/startupideas.html

There is a level of insecurity to going it on your own that you need to embrace, to put it bluntly. Obviously if you quit your job and found office space then you have started down this path of embracing insecurity, but you haven't embraced it enough. You have thought of a few ideas and then knocked them all down because you are a sensible guy. You can see how they will fail, why your dream (which seems to be just "entrepreneurship", maybe) won't come to fruition, and how you will have to start over again, or whatnot. That's a tough spot, I have always started new ventures with my product idea in mind beforehand. But whether you come up with the product idea beforehand or in the middle of the process, you have to embrace the idea that you are likely going to hit hundreds of roadblocks and issues, and you will most likely fail. That's no big deal! That's part of the fun.

Another problem you seem to have is, despite the few ideas and potential revenue models, you aren't solving a problem you actually have. If you were, you wouldn't be worried about the potential problems with hypothetical development paths. You would be fixing a problem, a problem you have and understand, and one you need a solution to right now. Solving a problem you have also answers the question of how revolutionary your solution is. If you hate how the rest of the world distributes widgets, and you need widgets, and you come up with a better way to distribute widgets, is this not revolutionary? Maybe "widgets" in this case are men's shaving razor blades. I don't think that razor blades are all that interesting, and certainly aren't that revolutionary. But Michael Dubin had a problem, thought up a solution that was better than what everyone else was doing, and "revolutionized" the men's razor blade industry. In reality he made it easier to buy blades online; his model can be described on a cocktail napkin with room to spare. But he did something revolutionary. He seems pretty happy.

What problem do you have, regularly, that you hate? If you have no problems, what problem does your significant other have? Your best friend? Your dog? Your local municipality? Stop thinking about development paths and revenue models; those will come in time. Find something you can get behind and care about. Something where, when it doesn't work out, you won't care about how much money you didn't make, you'll only care that the problem isn't solved! The voice in your head that says "just take one of the ideas and execute on it, don't worry about the outcome" is totally right! But first, find an idea you care enough about that the outcome doesn't really matter.

On an unrelated tangent, think long and hard whether you want to learn an entirely new development ecosystem while you are trying to solve your problem. C# and .Net are good. So is Python. Do you want to build the solution to your problem, or do you want to learn a new language?

My current list of ideas has slowly formed from people (family and friends) asking me "can you build an app for this thing because I hate doing xyz". Other ideas have come from things that annoy me personally. So I'm pretty happy with my thought process in regards to where I'm getting potential product ideas. Currently where I'm at is trying to decide which of these potential projects am I going to settle on. I've had ideas piling up over the last few years and now I have to strike out all but one.

So now I'm in the frame of mind where I'm thinking if I do idea A it's probably not going to be the next big thing but it's quite possible I'll make a good go of it. Or for idea B I'm thinking it's a long shot but if I pulled it off it might really go somewhere. I think I'm looking for a reason to pick one idea over another. Is it just a case of doing whatever seems like the most fun (after filtering ideas based on merit)? That doesn't sound like a bad plan. Or is a small but manageable first step the right approach and leave any grand ideas for a later time when my experience in developing a product has matured?

As to switching stacks. I thought about that long and hard. I've dabbled in Linux over the last two years and have picked up a little Python. I know it's not ideal adding the extra overhead of learning a new language and environment but sometimes you just have to do what your gut says. And I've been hankering to leave the MS world behind for a while now. I think once you're running Cygwin as you CLI, using a Vim emulator in Visual Studio, and drooling at the thought of using PostgreSQL as your DB of choice it's probably time to change stack.

I appreciate the time you took to write out that reply.