I don't! As mentioned in another comment, I had not heard of them before. I'll be trying them out. On first blush, it looks fairly close to what's in my head

I don't! As mentioned in another comment, I had not heard of them before. I'll be trying them out. On first blush, it looks fairly close to what's in my head - so perhaps this is not a thing to chase. The one critical difference I can spot early on is that their system appears to be closed-source. Were I to do it, it would for sure be open. I want to see a method of supporting yourself with code far more than I want to make money myself. For example, in this moment, I like what they're doing and would love to contribute to the work myself to empower the goal of having more indie software devs in the world, but I would have to quit job (not happening), apply (might not get hired), and then work on whatever features are in the business' best interests (which won't necessarily be in the user's best interests). All that said, they did it already and I didn't, so hats off to them. I hope bountysource gains more traction in the future. Edit: another reason to have <bountysource-clone> be open source, is to recurse the value add. The site would develop in the same way any open source project does (if / when they get popular): by people implementing what they consider the most critical features.