Live data from Hacker News

Introducing Backer: crowd funding for features

backer.app.net

1–10 of 28 posts

Re: Introducing Backer: crowd funding for features

#3
We just had great success trying this idea out. It was via CrowdTilt, not Backer, but our customers pre-paid over $50k for push-to-cards: http://blog.balancedpayments.com/push-to-cards/

I'm also really excited about open source projects self-funding via this. Or at least, paying for someone to do design, write documentation, or all the other non-development expenses. Think NPM raising that money to keep the service going.

Re: Introducing Backer: crowd funding for features

#4
This looks excellent.

We've been crowdfunding an open feature roadmap on WikiHouse.cc and, internally, have been very concerned to build credibility by shipping the funded features before asking for more funds - especially because, with a simple paypal setup, we've been getting paid in advance.

I can see the payment on delivery and project curation being very valuable trust builders, if administered soundly / well governed.

Re: Introducing Backer: crowd funding for features

#6
I understand the appeal of a single page "corresponds to a single feature" but is there a way to display the status of a full project?

Let's say I have UmbrellaApp, a website which offers a service. I create a Backer page for a mobile app, and 4 more Backer pages for optional features which I'd be interested in building into both the website and the mobile app but I'd want to gauge interest individually before committing to development.

Can there be an UmbrellaApp page, not a Backer page, but which lists all the possible configurations which Backer would enable (if successful) and their real-time status?

Re: Introducing Backer: crowd funding for features

#7
post #5

Great idea! Is this connected to App.net at all, or just built by the company?

Thanks

We are using it (and plan to continue using it) for our own market validation tests, and so yes it is connected. We are also making use of a few App.net API features to power it.

Re: Introducing Backer: crowd funding for features

#9
post #6

I understand the appeal of a single page "corresponds to a single feature" but is there a way to display the status of a full project? Let's say I have UmbrellaApp, a website which offers a service. I create a Backer page for a mobile app, and 4 more Backer pages for optional features which I'd be interested in building into both the website and the mobile app but I'd want to gauge interest individually before commit…

My instinct is that trying to run multiple Backers at the same time might make it harder for any one of them to succeed, and thus it might make sense to run them serially.

We are certainly open to trying things like this out, and sharing the best practices of what works best with the public.

Re: Introducing Backer: crowd funding for features

#10
I think this is really cool! I can see these campaigns dropping into one of two buckets. 1. Funding to pay for development time and 2. Validating the idea. I think it's up to the campaign runner to determine how much to ask for for bucket 1 type campaigns, but it could be immensely helpful for Backer to offer clear guidance for the second.

For example, lets say I have an existing user base of 100,000 people, and I normally charge $15 / m for my service, of which 5% of my users actually pay. What is a sufficient contribution to validate the idea of a new feature for the paid version? For the free version? Over time, finding the proper heuristics/weightings for Backer users could be very very helpful.

Post reply on HN