No, this looks like a product for companies who sell API access.
Our product is performance-based, rather than unit-based, and there's no exposed API. We would like to have a detailed itemized invoice (think a phone bill). Our options are build from scratch or shoe-horn existing solutions. It'd be nice to not have to reinvent the wheel and also keep our customers within our UI.
It has a concept of percentage-based billing where you can specify an input amount and you can specify to bill a percentage of that and handles generating a detailed invoice.
Our product is performance-based, rather than unit-based, and there's no exposed API. We would like to have a detailed itemized invoice (think a phone bill). Our options are build from scratch or shoe-horn existing solutions. It'd be nice to not have to reinvent the wheel and also keep our customers within our UI.
Our company audits shipping invoices and bills the customer based on a percentage of what we save them. It's a common business model outside of the tech/SaaS landscape (utility bills, property taxes, etc)
I guess there's a lot of complexity I'm missing. Is it something like this:
1. Customer original bill (variable - user provided) e.g. 100
2. Saving (variable - user provided) e.g. 9
3. Saving percentage (calculated) e.g. 9%
4. Billed Percentage (variable based on savings percentage?) e.g. 25% x 9
So you would have a billed percentage "rate card" that depends on variable factors like the customer bill plan, the amount/percentage saved etc? Is that the tricky bit?
It's closer than I've seen elsewhere, but not quite there. There isn't a good way to predefine what they consider "billable metrics" for the use case I'm considering.
