Hi Everyone, I just though I would add to this as I am a developer and see things from the other side of the coin so to speak.
A bit about myself, I have been coding for over 20 years. I am working to become a marketer and leave development behind, but it has been a slow transition. I have currently done two successful JV's with a marketer, where I build it and he gets them to come. We split the profits.
Ok, so taking an idea that a marketer has and turning it into a running application can be a but complicated and here is why. As a coder, I would prefer more details for several reasons. Number one, it helps me determine the time it will take to build something. It also allows us to spell out the contract between us better, ie) I will create this, this and this feature, by this date in exchange for $x.
The other reason it is better to have details, is that it stops what we coders call scope creep. That is the part of the project where you marketers (or customers) come to me and say, it would be so cool if we could do this or that when this happens. Can you make it happen? Well of course I can make it happen, but it takes more time and we are now out of the bounds of our original agreement. I may not be able to make the deadline now that we previously agreed upon and you will be upset.
A simple idea, does not always translate into a bit of simple coding
Now, I don't mind taking on a "rough idea" as the original poster remarked about is not that difficult, if it is a profit sharing JV. I don't mind putting in lots of hours to create a product that I get a recurring income from, but, taking a rough idea and turning that into a quote for X number of hours is pretty hard in many cases.
So contemplate this when you do your next outsourcing, the more details you have on how things are to work, will save you tons of grief in dealing with your coder. As for the project that never got completed, that was mentioned earlier in this thread, well, in that case I just think you got a bad coder. Or he/she dumped you for a more profitable deal. Either way it is poor behaviour on the part of the coder and it gives all coders a bad name,
Well, that's my 2 cents worth
Darren