|
|
|
Ask HN: Ethics of selling using HTML prototypes?
|
|
10 points
by ethicalornot
4088 days ago
|
|
I work at a small startup with some angel funding. We have a launched product and are working on new products that will probably be built and launch in 6 months if the founder closes a funding round he says is almost finalized. We don't have the money to start building them until the funding comes in. In the meantime we built some HTML prototypes (not functional) for the new products and the founder is showing these to potential customers on sales calls. I am involved in bizdev so I am on these sales calls but I feel really uncomfortable that the prototypes are not explicitly presented as "prototypes" to the potential customers. They are basically presented as being real and most of the customers respond like they are real. It's really difficult for me to answer customer questions about what our products can do when I know the products don't even exist yet. I also worry about what will happen if somebody wants to buy the product before we build it, which seems very possible since it it will take at least 6 months to build. Even if I don't have to come up with the excuse/delay I don't like the thought of it. A few of my friends say that I'm worrying for nothing. This is how startups work they say. But I still feel that if you're showing a product that is only a HTML mockup and you haven't even started building the real thing you should be honest about what they are looking at. Am I wrong and not cut out for early startups? Or is what our founder doing unethical? Any opinions and experiences would really help me make a decision about what I should do next (get over it, tell the founder my concerns, resign). |
|
The entire Lean startup movement and concept of the MVP is to test your product idea in the market, in front of real customers, before investing too much time trying to build something no one wants.
I thinks its OK to focus the discussion on features, benefits, etc if you can get in front of potential customers. It should not be long before they ask about pricing and availability. That's when you simply say you think it will be ready by date X.
Take for example the email assistant AI startup X.ai. They say in their FAQ that "Amy" is human assisted. For all we know Amy is 100% humans booking your appointments and the algorithm is total vapor. It's not unethical to do this, as long as customers are not expecting some guarantee of no human intervention (e.g I sell you an instance of Amy I claim lives on your desktop, but requests are actually sent over the network for humans to do the work)
If you have a black box in your demo where data goes in and magic comes out, and you say "This is actually taking the input and generating the output in realtime right now" you are sticking your neck out and it's likely to get chopped. Building a new customer relationship on a lie like that would be a mistake. But depending on the specifics it's a calculated risk; if the black box is completely do-able but just not yet quite done, then I think hard coding results in a mockup is time-honored, wide spread and perfectly ethical. But when they ask about availability you've A) confirmed market interest, and B) you state not all of the features are ready but you are expecting to ship on Date X.