Everybody can't code, but everyone can make mockups. Use a tool like mockingbird (gomockingbird.com) and literally sketch out every single page/screen. When you make the mockups, you should be sure to know where every link/button goes, otherwise there's a page missing in your mockups!
Just this task alone would stop 95% of people with vague ideas. It also shows the coder that you have taken it as far as you reasonably can without learning to program.
A prototype is halfway. :-) All the way would be learning to code well enough that you could launch the product yourself.
If you can communicate your product vision in static mockups, that's great. But for most products, there's a world of difference between seeing something working - even if it's held together with string and wires and only works for the inputs you're demoing - and seeing a bunch of pictures.
Comments
Why not meet half way?
Everybody can't code, but everyone can make mockups. Use a tool like mockingbird (gomockingbird.com) and literally sketch out every single page/screen. When you make the mockups, you should be sure to know where every link/button goes, otherwise there's a page missing in your mockups!
Just this task alone would stop 95% of people with vague ideas. It also shows the coder that you have taken it as far as you reasonably can without learning to program.
A prototype is halfway. :-) All the way would be learning to code well enough that you could launch the product yourself.
If you can communicate your product vision in static mockups, that's great. But for most products, there's a world of difference between seeing something working - even if it's held together with string and wires and only works for the inputs you're demoing - and seeing a bunch of pictures.