Vedran Sindrik

So that's what we kind of spent at least, I would say, six months testing, doing, developing, and perfecting.

And once we were done with that, then we got more confident about Treble and what it can do.

That's what we think at the moment that are right.

You have to understand that, like you said, I am coming from a developer background and one of the things that I hate is complicated pricing, right?

If I see a product and I've seen many products, the worst things that I could see is you want feature A and that feature is only available in the highest plan.

That's just going to turn me off.

So the thing that we wanted to do here is we wanted to give everybody all the features and you only pay for essentially what you use.

We think that is the fairest offer we can make.

So nobody loses money and you get both of both.

you know, both of both words, sorry.

I think if they grew that much, Treble would be their best friend because in that amount of time, we would have provided so much value and saved them so much money and time to them and their developer just on everything from debugging to writing documentation that they would be actually happy instead of sad.

So far, no.

So far, we haven't heard a bad word about it.

Yep.

We're trying to set that up, but we have seen a lot of cases where people, usually when expansion happens is like you mentioned, when somebody's API becomes popular.

So usually what we see people do is they start with lower plans and then move to higher plans as their API scale.

So while you're developing, you probably don't need the highest plan because your API is being used by a couple of people.

But by the time you launch,

And if you have a successful launch, your API is potentially used by thousands, if not millions.

So roughly around 8% of that, 8 to 10% of that amount is our cost.