What do you do at DevSkiller?

My name is Jakub Kubryński and I am the CEO of DevSkiller.

What’s the problem that Probe is solving for you?

The number one problem for me was that I did not trust the numbers. I tried many tools and had to spend hours fixing the data. There were different problems: handling exchange rates, reflecting changes to original invoices, support for overdue payments and others. Probe addresses all these issues and I don't have to think about quality of the data, instead I focus on analyzing it.

I’m also able to share my KPIs effectively. Investors kept asking for the metrics every month. This meant that every month I had to prepare documents to share. Now I simply share one link which is up-to-date all the time.

Which other solutions have you tried before Probe? Why did they fail?

We use Chargebee so it was natural to try RevenueStory. We also used ChartMogul and ProfitWell. The problem with those tools for us was that the metrics presented were simply off.

Big issue for me was how multiple currencies are handled. We invoice customers in USD and EUR and to present numbers we need to do conversion. Sadly, using these tools, we noticed huge discrepancies in our data due to this not being done correctly. I remember MRR from one of our top customers being off by 20% because of this!

I also had constant problems with how churn and renewal is calculated because of overdue invoices. Whenever someone was late with a payment they got classified incorrectly. Later changes were not reflected in metrics resulting in a lot of manual work to fix this.

What was important for you when trying to solve this problem?

There is a lot of nuance when calculating many of those numbers and I really feel that the Probe team got those details right. When talking with them I get the feeling that they truly understand each and every metric.

I also like the idea of being able to manually fix single data points. Sometimes it’s too late to change the invoice in Chargebee. Probe gives us the opportunity to update the underlying numbers anyway - something that was not possible for us with other tools.

What did the implementation process look like?

Native integration with Chargebee was very important. With previous tools we had to integrate via API which isn’t ideal. We also got full support from Probe.

Probe works very closely with us, whenever we have some need or question they engage and react super fast. In my opinion it makes them very well adjusted to B2B market.

Additionally since Probe is still relatively small, they keep us included in the product development process.

How did it change after adopting Probe? Did it become easier? Faster? Do you have any numbers to back this up?

Now I have full confidence in the results I see. With previous products fixing problems used to take up a lot of my time and I was never trusting the numbers I saw anyway. Now with Probe I can really focus on getting insights and use this data to help me make business decisions.

I used to wait for accounting team to get the results but it took too long, often 1-2 weeks after the month has passed.

Now I have all the numbers realtime, so I have full visibility all the time.

Other
case-studies