I think that having the other revenue sources transparent to the users would help both problems. People do want to know that a service that their business depends on (even a little bit) is going to stick around, and they don't want surprises when you ask for money from something other than subscriptions.
If the revenue is coming from transaction fees, present that as a feature. I could really see a transparent transaction-based model with free accounts working.
When you say "invoicing should be free", that sounds like a nice revolutionary pitch, but I wonder if BallinBige could clarify what features would be paid?
this is good/ well said!!! As we roll out new features, and identify possible revenue streams, (i.e. processing, additional delivery methods), we will clarify the paid features. we are evolving :]
If the revenue is coming from transaction fees, present that as a feature. I could really see a transparent transaction-based model with free accounts working.
When you say "invoicing should be free", that sounds like a nice revolutionary pitch, but I wonder if BallinBige could clarify what features would be paid?