This usually turns into multiple back-and-forths to flesh out what the client really needs, and usually requires a lot of thinking on the developer's part (me) to nail down an actionable solution that could potentially be estimated in terms of $$$.
I was hesitant reading Trevor's article thinking what he was suggesting was devaluing dev work, but when he emphasized the importance of specificity I was on board with him. If a client has fully thought out their idea to the point of step by step mockups, that takes a LOT of the pain, frustration, and effort out of the equation which translates to the required work not costing as much.
Developers are one step away from computers (literally) and require a lot of the same rigour when interacting with them. Know what you want and be able to explain what you want (in detail) before engaging them ;)
The more you can learn to help the client work through ambiguity, rather than expect the client to match your technical understanding and then be frustrated when they don't, the more successful you will be.
Great point. Most people are not used to the level of specificity required to be a developer.
Of course not everyone's that way, but you sure can make friends much faster by treating your contractors well.
We actually built some of these ideas into the core of matchist (http://matchist.com/talent). Specifically, milestones and paying your developer quickly. All projects on matchist are milestone based and the client can pay developers in 2 seconds by just clicking a button.