If I, as the prospective designer, were in your shoes I would do everything outlined above and then pause. Not for effect or some grand gesture of importance but to give the other guy a chance to interject, to impose their own thoughts and ideas.
Take a project I recently worked on. I've worked with the client before so they already knew I could code the bejesus out of anything they wanted and they also knew that I do not use the word "no". I might ask them to re-evaluate the element we're discussing, I might put a hefty price tag on the concept being developed but I'll hardly ever use "no" as a reason not to design. So, we chatted over a Hangout about the concept in broad terms and what they'd like to do and I kid you not, I "got it" within 30 seconds. I got it so much I wanted to be a part of the project immediately.
At this point I reserved my Pavlovic response and started talking about other elements of their project that they may have looked at but not realised or developed, how wide a geographic spread the application might have, the audience, the facilities and functions and more importantly the conversion of prospects to customers through the website itself (as it was only ever intended to be a tool).
This is what I mean when I refer to "got it". I wanted to be involved but more than that I could see the potential the product had and desperately wanted to be a part of it. I didn't want any other designer's name to be associated with this. Call it ego, call it pride, call it what you like I simply wanted to be a part of the development of this application.
So, that pregnant pause... Use it, don't be the first to speak, see what he/she comes back with and you might be surprised or even astounded at what comes back. At the very least you can take their ideas and develop them internally as no developer should be frightened of opening up the potential of your project to a wider audience.
Putting it Into Practice...
Next time you have a web project you're thinking of pitching to a web designer (and yes, it is a pitch whether you like it or not) why not draft a brief, much in the same way you might if you were contracting someone through Elance or an agency and then present that to 2 or 3 designers/developers and guage responses. Then sit back, evaluate what each brought to the discussion and make a decision on which direction to go in.
Share This Post !