[Retric]

You can always reduce overhead after you gain some traction.

[listic]

The principle is good. But is it really painless to change payment API and hosting platform?

[MicahWedemeyer]

Hosting platform isn't too bad, but changing payment API is a real pain since it's basically impossible to move existing subscriptions to a new system without user interaction.

However, I think Chargify is probably the best route for anyone doing subscription based stuff. Managing billing for subscriptions is such a pain in the ass, and these guys seem to understand that at the core.

I'm on Amazon SimplePay right now and I'd switch to Chargify in a heartbeat...if I could move over my existing subscribers ;)

[aaronblohowiak]

That is a "good pain to have" as it were, and the reduced friction gets you iterating more quickly.

[MicahWedemeyer]

I call those "Maserati Problems", as in, "I'll think about how to deal with that as I drive around in my Maserati."

[zackattack]

Eric Ries calls it Technical Debt

[aaronblohowiak]

Technical Debt is different. Technical Debt slows future velocity for feature development / changing to fit customer needs. That you are "leaving money on the table" with these choices does not impede feature progress at all.

[zackattack]

Thanks. Can you please elaborate with an example? :)