Emna Gariani

So we tested a lot, we had a lot of assumptions that were wrong, and some of which were true.

And even in pricing, like we charged, like we charge some people and then you know, like, then we decided to open it for free and give it for free till Q2 to retest for this assumption of stickiness.

Absolutely.

So we're having really awesome testers and they're liking it right now.

We saw some people get out because of some, obviously, instability in the platform or sometimes it's a management decision.

Meaning, let's say a product manager brought it in and then they're like, no, this is not the right time for us to have everybody use it.

So we had a couple of those, but right now we're seeing great adoption.

Around four.

Yes, because here's the thing.

The Vimli prioritization feed is on top, but they can still access their Slack and their JIRA and everything.

So they're working in these tools within Vimli.

Does that make sense?

Right now, I cannot give you an exact metric in terms of how much they're spending on each tool exactly versus looking at Vimly.

The goal is that they look at Vimly when they start the feed and then they work with it and then they're pulled back into the feed when something important shows up and they need to act on it and then they go back into their tool.

That's kind of like the user behavior.

So the value we're adding is really saving them time, meaning that usually they'll spend, let's say, two hours going through all their messages and comments on tickets and on pull requests and everything.

And then they're spending like 90 minutes instead of two hours or an hour instead of two hours.

So because what Vimli does, it goes and reads everything and brings all the important stuff on top.

And they can still do quick actions from Vimli that go straight to the original tools, like quick replies, creating tickets from them and more.

Yes, because as I said, Nathan, it's a workspace and the idea is they're accessing all their tools in one place as well.