That said -- raise your prices. You might try something that's more explicitly tied to revenue. But if not, I would try the 3 tiers at 39/99/199 (or 49/199/299). Maybe make a 0-10 customer tier that's lower cost. The bigger customers will demand more features to justify the price point, but many of those features will likely prove relatively easy to implement (SSO, 2FA, let them pay you via PO).
Edit: plus, since you’re not driving new revenue, and replacing you is a one-time-fee (maintenance for this feature is minimal), all you’re doing with pricing based on percentage of revenue is pushing your largest and most valuable customers to get rid of you as fast as possible.
- free until revenue hits $X/mo (versus # of customers, this better tracks ability to pay)
- buckets defined as revenue of $X-$Y pays $Z
- max revenue tier is $X/mo, BUT
- pricing can go higher with more value-added services. Really common examples: SSO, Salesforce integration, QuickBooks integration, we'll call customers to find out why they churned, we'll proactively handle renewals of your customers who pay by PO (this is a PITA), and other things your $$$$$ customers will ask for.
Also: no pricing model will work for every one of your potential customers. And it's easier to lower prices than raise them.
Quick question. Any recommendations for a "wallet library" for a web-app side project (either JS or Java backend) ?
Basically we want to take payments from users, charge the wallet for certain operations, and show history and balance.
I am not even sure what to google to find this.
Any pointers appreciated.
Heads up though. There's a bug on your sample page: https://www.pubilling.io/sample
When you click the "Edit" button for the CC, the UI shrinks into nothing...
Which made it hard for me to figure out if there were some possible requirements issue.
Small nitpick, but there's an extra l at the end of "renewal" in the mockup. The capitalization of "Next Subscription renewall" is also a bit off-- maybe consider "Renews on:" or "Next renewal"?
On the pricing side, I definitely agree with runako. Prices are much easier to lower than raise, and so you should experiment early on with the higher end.
<script src="https://app.pubilling.io/sdk.js" async></script>>It's PuBilling another payment...
Should be
>Is PuBilling another...
https://www.servicebot.io/pricing
https://www.chargebee.com/pricing
this one is free: https://www.chargebee.com/open-source-customer-portal/
I am kinda of looking for a library to manage each customer billings and balance