Ask HN: I have a great idea, but nobody likes it. So here it is.
So, I've decided to run the idea by you guys to see what you think. Of course anyone who likes it could just implement the concept themselves, but I'd be happy to try and work with someone on it (I'm not a programmer, but am willing to contribute where possible). The concept I've simply called "ChanceMail", and is outlined below. Any advice/criticism is appreciated.
"Chance Mail is a powerful concept in terms of monetization specifically- users benefit based on how much they pay for the same task.
Users are allowed to send a free message to someone, but the message only has a certain percent chance of actually being delivered. This percentage is determined by the sender, and is displayed in the message, if delivered. The sender is not told whether the message is delivered or not. To promote use of the app, when you send a message and it "fails" to go through, the receiver gets a message saying "someone sent you a message and it failed to go through".
Psychologically, when you send a message with say, a 10% success rate, you obviously don't know if they received it. But if they did receive it, when they see it has a 10% success rate, they know you're pretty sure they didn't get it. Ideally, this will work for things that you don't want to admit in person, because the first level understanding is unbearable.
In other words, if there's a piece of information you want someone to know, but you don't want them to realize that you know that they know, this is the best way to achieve such an understanding. But so far, the system is ineffective- the chance your intentions were actually carried out are slim.
Here's where it gets interesting, and where gaming the system for a few bucks can give the sender a psychological advantage:
You charge the sender for each additional "send" of the same message. Someone who wants to ensure that 10% message goes through buys 20 messages, and after one goes through, no more are sent, but we can't tell him nor not charge him for those extras. The great thing about the charging for additional messages is that people will actually want to pay more.
The reason for this is simple- if the receiver knows it's free or even cheap to send a ton of messages with a given small percentage, they will expect the sender to be sure the message goes through, even though on the surface it says 10% (or whatever percent). If the prices are high, they won't expect the sender to part with that kind of cash, so the sender can gain psychological footing by proving the receiver wrong and paying more.
I imagine this being useful for people who are too proud to directly say things to their family and close friends, or things that would embarrass or humiliate someone if you just told them. What's great about it is that the recipient can't directly respond, because that would imply that they received the message. If they don't respond, supposedly there's a chance they haven't even received it. When they change their actions slightly later on, much to the satisfaction of the sender, it could be because they received the chancemail, or it could be for another reason.
I envision this as simply an email website. You can send regular email, as well as chancemail messages which you specify a certain percent. It would probably be best if we limited the options to a few specific percentages, for simplicity's sake."
51 comments
[ 1.8 ms ] story [ 114 ms ] threadThe application for this chancemail thing is narrow but definitely exists.
Furthermore, doesn't buying 20 messages at 10% so you're sure it will go through defeat the purpose of sending a message that you don't really want to send?
I also don't see how you come to the conclusion that the recipient can't respond.
Perhaps I am used to startups having some sort freemium service that becomes difficult to monetize, while this is unique in the sense that users often would like to pay more for the same service. I would call this powerful. I understand the bottom line is how much the average user pays for the service, and on that note I'd say that the types of people that would like this service would definitely use it multiple times.
>Furthermore, doesn't buying 20 messages at 10% so you're sure it will go through defeat the purpose of sending a message that you don't really want to send?
No. If you do this, you know (or are 95%+ sure) that they have read your message. What you avoid is the knowledge that they know you know. This is what people go to great lengths to avoid for basic human traits such as pride and embarrassment.
>I also don't see how you come to the conclusion that the recipient can't respond.
If they respond, it implies they read the message. Before they respond, it's their own secret, since the sender supposedly doesn't know if the message went through. So they can choose to act as if they didn't get the message.
So run with it and learn how to program. You'll learn how to think through the problem and implement it.
You have no idea what it will become.
You didn't write that there are opportunity costs here - that is, I'm assuming you're not quitting your day job and letting your kids go hungry. If there's nothing to lose, go for it, because you do have the experience to gain. If it works, great; if it doesn't, you'll be better prepared to evaluate an idea's success next time (and better prepared to implement the next idea too).
I have a similar issue with your chancemail idea. I can just about see the 'let fate decide' value, and also the bit where the receiver gets to pretend it never happened if they wish. But the bit about paying to remove all of this, and add in the receiver's mind the suspicion that you probably did so really muddies the waters.
In this case I'm questioning whether there is one for something foreign and new.
Your core idea is that, "there's a piece of information you want someone to know, but you don't want them to realize that you know that they know."
This builds uncertainty. Can't say I would ever use it, but that's fine -- I'll hold my disbelief.
Then your monetization model is to pay money to reduce that uncertainty. Said uncertainty is the only reason you used this site to begin. So you're looking for people who want uncertainty, but want to be able to reduce uncertainty within that specific instance? Seems like your target customer has split personalities, which is going to make your idea really hard to sell to them.
The other problem that I see is your explanation isn't very clear or concise. The best I can figure out is this:
"there's a piece of information you want someone to know, but you don't want them to realize that you know that they know... for things where the first level understanding is unbearable... but then you fool yourself into thinking the other person doesn't know if you know that they know."
Can you come up with a good elevator pitch for this? I'm still not quite sure what the core idea is. Examples would be greatly beneficial here, too.
The recipient's perception of the sender's certainty is what's important here. If the recipient knows you sent 25 messages in a row, it's as if you sent a regular email. It logically follows that the recipient must respond, which won't happen if the recipient thinks the sender doesn't know if the message went through.
This is as explicit as I can articulate it, I think. But moving on to a few examples makes it more intuitive.
Say your boss has meetings that take up too much time and he needlessly covers off-topic things that reduce efficiency in the workplace. He's a proud guy and if you told him about this he would defend his position, as adjusting because a subordinate suggests it might make him seem weak. Of course this isn't ideal and many of you would claim to never work in such an environment, but this would be a perfect opportunity to shoot off a chancemail message with some constructive criticism. Now he doesn't have to worry about how he's perceived, because he can tell himself he just as easily could've not received the message and decided to change the meeting structure on his own.
Another example would be a father telling his son or daughter that he's sorry for mistakes made in the past, or that he is simply proud of them. This is hard to do because a response to an explicit message is necessary. With chancemail, the recipient can not respond to let the sender save face, (again, since he could have not gotten the message) while being able to appreciate that the communication took place.
As for an elevator pitch, I'm notoriously bad at them and have been meaning to improve. Often I'm so caught up in the theory behind my ideas that I lose sight of the fact that I usually only have a few seconds to sell someone on the concept. Any help would be great.
pain: sometimes telling someone necessary causes an interpersonal friction because the recipient of the feedback is aware that the sender is observing / judging him on certain qualities. solution: give a margin for error so the feedback can be sent/received, but both parties can pretend as if the message was never sent.
So again, what does your idea offer versus an anonymous service like http://www.sendanonymousemail.net/ (or any of the others; that was just the first google result).
While I would encourage you to continue to develop this, the fact that you're unable to easily and clearly describe your idea tells me that it's a little vague to you, as well. At least that's how it comes across.
Maybe you could try to explain by analogy? E.g., "ever wish you could send someone an email they could pretend to forget? well, try [blah blah blah]"
And you're expecting someone who hasn't decided they're really going to make a go at understanding your product (i.e., the average, time-starved consumer) to not only understand but hand over money to use your product?
What hurt does your product soothe?
Right now you're describing a (very complicated) mechanism. It's what you use that mechanism for that counts.
As an exercise I'd come up with three customer stories and write a pretend press release for your product, because right now it's f^%$ing confusing.
My advice? Build it. Forget about monetization and just build it as a fun website. Then iterate, iterate, iterate.
You may end up with a website which you can monetize, or not. Either way you will have learnt something and you would be more ready for your next challenge.
i.e. so you can tell someone that they smell, or their partner is cheating on them, without having to have the awkward conversation that both the sender and recipient would like to avoid.
Do you think this would also help manage the 'drunken email' syndrome many of us get?
Subject: You Smell
Body: Sorry mate, but I wanted to tell you that you really stink, it's really offputting and I feel pretty sick when I have to stand near you. This message was sent through chancemail, there was a 1 in 10 chance this message was delivered, so the sender probably thinks you never got this message, allowing you to act on it without having to feel awkward about it.
Reaction: wtf dude, why did you email me telling me I smell?
Or in other words: Once you've sold the sender on the concept, you have also to sell the recipient on the concept. That task is even harder, because typically the recipient will just have been told something hurtful or awkward.
Question: Why is this better than anonymous email?
If it's NOT anonymous, is the value to be able to send someone an email with you identified as the sender but with ambiguity about whether the email was delivered? - so that changes in behavior aren't assumed to be linked to the message?
Yes, that's it.
It seems like a lot of use cases of this product are what people use the anonymous feature of formspring for.
As the old dude that I am, I ask myself: Would I pay any amount to get an anonymous message to anyone and the answer is no. Maybe I'm missing the real value of your proposition - and if so, then you need to bring more clarity to the value.
Also, one problem I notice is that the receiver might simply have no clue what's going on, either failing to read or misinterpreting the "you were to receive this email with 10% probability" message in the footer.
What you're talking about here adds another dimension on top of this basic anonymous scenario that doesn't make any sense to me. If I receive an email from an anonymous source that only had a 10% chance of delivery, how is this any different than if the email went through an anonymous mail system that had a 100% chance of being delivered?
License it out to game theory/behavioral economics programs.
Let them access other users analytics just as other users will be able to access their analytics.
That could be a really fun and informative unit... or even the subject of an entire class. Actually using real world data and how users interact with the uncertainty of having their message sent balanced against the necessity of having their message read.
Your users aren't going to want to crunch probabilities in their heads and finely adjust a dial there. Rather, what they're really after is probably conveying information in an anonymous manner. Unless I'm misunderstanding you?
That is, making electronic plausible deniability more feasible is the kernel of an interesting idea but your implementation doesn't tap into human psychological hooks. Instead of "25%", if you showed pictures of four Facebook accounts and said "one of these sent you this message", that would get the effect you seem to desire. Might be an interesting viral dating site.
Another interesting variation could be for performance reviews or political/government statements. Anytime someone wants to send a message, has an identifiable group from which that message would be seen as legitimate, yet also wants to preserve a degree of plausible deniability...this could be interesting. Suppose someone wants to float a trial balloon to find out what "coming out" as a conservative on Facebook would do. Imagine the wheels turning when it just says "one of the following frienda posted this". It's kind of like the Crushlink scam...humans are fundamentally motivated to try to put a return address on certain kinds of sensitive communication.
You can't simply bring an idea to the table. Ideas are a dime a dozen. You better bring some real research, funds, or programming skills for developers to take you seriously. Other than that you could just try to fund the development yourself and keep all the IP rights.
I can see this being an example use for your service. If you take out the "someone sent you a message and it failed to go through" part, then it might actually work. People can ask someone out, and just write it off to a failed message if they don't get a response.
That said, go for it. Who knows what people would do with something so strange?
But the other person doesn't know that you know that they know, while you simply know that they know. This is as explicitly as I can articulate it.
What you're avoiding is them knowing you know they know. Make sense?
Actually, as I sit here overthinking things, I think your target audience is not people trying to avoid awkward social interactions, but people trying to avoid awkward social interactions because they overthink them, and what's to say they won't overthink past becoming a customer?
If I send one of these things to my grandmother, I'm fairly certain she's going to not understand whatever explanation you provide in the email and try to ask me about it. Then, once I've explained that I tried to tell her something I don't want to say in person, we're already having a conversation about it, and I would have to say it directly to her, which is what I was trying to avoid. That's the kind of overthinking you don't want, because it takes away customers.
Edit: having said that, I think it's a pretty neat idea and worth developing if you're still interested in it. Not sure I would pay money for something that could just as easily put me into the awkward situations I'd be trying to avoid.
In technical terms, there is in a certain branch of science the concept of "common knowledge". Something is common knowledge between us if I know it, you know it, I know you know, you know I know, I know you know I know, and so on to infinity. It's a powerful concept with many surprising implications.
Basically you aim to sell a service to let some knowledge be shared without it becoming common knowledge. The main problem I see is that it doesn't work - it doesn't achieve that goal. The problem is that the most likely outcome of your low-probability email is that nothing happens. No mail is delivered, no knowledge is shared. This is not providing any value.
I don't see how even in theory to provide knowledge transfer without that becoming common knowledge. If you could come up with a way, it might well be worth paying for.