Charging for things on the web
People are willing to pay for things. It’s amazing! People are willing to put their credit card number into a form to buy things, and while that seems stupidly obvious to anyone who has ever bought anything, it doesn’t really hit you as a product developer until you after start getting “new payment” emails. For some reason, the default assumption is that charging for things on the web will never work, but, once you try it, even for something stupid like a life timeline, you might realize that assumption is incorrect. Sure, you might not be able to support a whole industry (newspapers) or a even a salary, but there is definitely some uncaptured profit there.
I don’t think Stripe is just a payments API into a pre-existing market, I think there’s an opportunity for them find a new market of people who never even considered charging for things on the web. People like me, with little side projects or with simple services. I am obsessed with payments innovation, so I’ll probably be writing more about this later.
Anyway, here’s the final tally:
Throughout the process, I charged between $1 and $13 for each account, but after some testing discovered the sweet spot was $5.
Revenue through credit card payments (Stripe and Paypal):
Revenue from eBay sale:
Cost of operations (hosting, etc):
I spent about 400-500 hours (let’s say 450), for a net profit per hour of:
And total net profit:
For a side project that I had no intention of charging for, or of selling, I consider that a success. Experiment over.
You should follow me on Twitter here.