Re:Ask HN: Should we demo a half-baked product?
by Breakfast on Friday November 19, 2010 @01:33AM
(#1920652)
I have to agree with this. The customer/buyer is going to be looking at it from the perspective of their own users experience and will be mostly interested in how it will enhance their workflow. I'm in a similar position. I want some early feedback but don't have the whole backend settled yet. So I'm just going to dummy up some backend data and processes and present them onscreen to get the concept across. Once they've got the concept, they can be instrumental in designing what the processes and presentation will actually be. I mean hell, if I can't even explain/sell the concept, I've got the wrong idea or the wrong audience. Invaluable knowledge at this stage.
'this is x' is more powerful than 'this will be x', because 'will' really means 'might' and introduces doubt, whereas 'is' is concrete and undeniable.
You know that adding pretty logos is simple stuff, and that the real challenge is in integrating the data feed quickly enough, but your customer very often just assumes that the functionality will be there, and only worries about the flashy cruft. Get the flashy cruft right! I think it's easier to sell a product that looks great but does nothing than a product which does loads but looks terrible.