Griff Parry

It can be the amount of usage data that they're ingesting.

So it can be very high volume and high velocity.

But there's different vectors.

So it's not just the amount that you're ingesting in.

It's also how frequently you're calculating the bill.

Because if you calculate the bill just once a month for billing purposes, you won't do many bill calculations.

But if you're calculating them every 15 minutes so that there's an up-to-date sort of how your bill is tracking available on a dashboard.

Yeah.

I don't see that as a big number because of our GameSpot experience.

That will sound...

I'll use GamesBox as an example.

So we were doing about 40 billion API calls a month.

And we were smaller in earlier stage than our ideal customer.

So it just depends.

I mean, if you're doing things in cloud infrastructure, they can be very high volumes.

In different verticals, they can be lower volumes.

It's not, but I wouldn't say that they... I wouldn't think that way because...

They could be trying to cope with a high degree of price complexity that might not have a huge amount to do with the volume of usage ingest.

So it might be whatever, like a million, 10 million, 100 million, it doesn't matter.

But the reason that they might be having real headaches is they've got a lot of customers and they've got a lot of SKUs and they've got a lot of complex bundling and they need to do a lot of complex billing logic and they want to change prices.