ShreyaChaurasia

10 ms·

1. 1.▲
   Show HN: Credit-to-currency conversion controls for wallet-based billing

   7 points by ShreyaChaurasia 8mo ago|2 comments
2. 2.▲
   by ShreyaChaurasia 8mo ago

   Pricing changes are easy in slides. Expensive in production.
3. 3.▲
   Show HN: Custom Pricing Units in Flexprice (price in credits, bill in USD)(flexprice.io)

   5 points by ShreyaChaurasia 8mo ago|0 comments
4. 4.▲
   by ShreyaChaurasia 8mo ago

   Interesting pricing contrast. How are you thinking about sustainability as usage scales compared to X’s per-tweet pricing?
5. 5.▲
   by ShreyaChaurasia 8mo ago

   Credit-based pricing makes sense when costs swing this much per request. Otherwise you end up subsidizing heavy users. If anyone’s looking to avoid reinventing this logic, worth checking out Flexprice.
6. 6.▲
   Show HN: A customer billing portal built to reduce "can you resend the invoice?(flexprice.io)

   6 points by ShreyaChaurasia 8mo ago|1 comments
7. 7.▲
   Show HN: Nomod payment integrated into usage-based billing stack

   9 points by ShreyaChaurasia 8mo ago|5 comments
8. 8.▲
   Show HN: Checkout Flow for credit-based billing(flexprice.io)

   4 points by ShreyaChaurasia 9mo ago|0 comments
9. 9.▲
   by ShreyaChaurasia 9mo ago

   This breaks the principle of value alignment. Developers value API credits and rate limits, not storage or web UIs. When pricing ignores that, it creates double pay and churn.