> If I wanted to use a “pay as you go” pricing model for my own service - what problems should I be prepared to deal with? The big one is convincing people tha

> If I wanted to use a “pay as you go” pricing model for my own service - what problems should I be prepared to deal with? The big one is convincing people that the HTTP request they're about to make is going to be worth the price. That's friction that will lead to hesitation, and that hesitation may lead to users never using your product more than a few times. In the specific case of search, users don't and can't know whether pressing submit will be worth whatever number of pennies it costs. If that's the case with your SaaS I think pay as you go might be a bad choice.