PredictBill: Transparent Pricing and Cost-Forecasting API for Technical SaaS

Roast, as requested. The $10 is the biggest issue, and not because it's cheap. This thing sits in the data path of someone's product. If it breaks or you disappear, their app breaks. Hobby-project pricing on a production dependency makes buyers nervous rather than excited. I'd sooner pay $49 and believe you'll still be around in two years. Second, nobody can predict their bill from your units. GB of egress, embedding requests, GB of file storage. A buyer thinks in "documents indexed" and "questions answered per month". Right now they have to guess the conversion themselves, and people who can't forecast a bill just don't buy. Put a worked example right on the page: a 5,000 page docs site with 20k questions a month costs roughly $X. Third, and this is the one that would actually stop me: the page never says what happens when I hit a free cap. Hard stop, or overage billing? For something in production that ambiguity is scarier than a higher price. "Embedding costs at provider rate" also means $10 is not the real price. Passing it through is fine and honest, but say what it typically lands at. Small thing: "unlimited knowledge bases" is a weak headline. The number of knowledge bases isn't what grows for anyone. Storage and question volume grow. On your actual question, hybrid rather than full PAYG. Full PAYG wrecks your own revenue forecasting and makes buyers anxious about a surprise invoice. Keep a floor plus usage on top. But I'd fix the units before touching the model, because the units are what's confusing, not the number.

Roast, as requested. The $10 is the biggest issue, and not because it's cheap. This thing sits in the data path of someone's product. If it breaks or you disappear, their app breaks. Hobby-project pricing on a production dependency makes buyers nervous rather than excited. I'd sooner pay $49 and believe you'll still be around in two years. Second, nobody can predict their bill from your units. GB of egress, embedding requests, GB of file storage. A buyer thinks in "documents indexed" and "questions answered per month". Right now they have to guess the conversion themselves, and people who can't forecast a bill just don't buy. Put a worked example right on the page: a 5,000 page docs site with 20k questions a month costs roughly $X. Third, and this is the one that would actually stop me: the page never says what happens when I hit a free cap. Hard stop, or overage billing? For something in production that ambiguity is scarier than a higher price. "Embedding costs at provider rate" also means $10 is not the real price. Passing it through is fine and honest, but say what it typically lands at. Small thing: "unlimited knowledge bases" is a weak headline. The number of knowledge bases isn't what grows for anyone. Storage and question volume grow. On your actual question, hybrid rather than full PAYG. Full PAYG wrecks your own revenue forecasting and makes buyers anxious about a surprise invoice. Keep a floor plus usage on top. But I'd fix the units before touching the model, because the units are what's confusing, not the number.

I'd keep a predictable monthly tier personally. PAYG sounds fair technically but as a customer I hate having to mentally calculate what using a product is going to cost me every month. Maybe $10 gets a clear amount included and then you charge overages after that. Predictable until you're actually using it heavily.