Skip to main content

SaaS Metrics for India B2B

By C Chaitanya
When we started selling our Cloud telephony platform, we had very little idea of what metrics to concentrate on. So we just built the product and winged it :)

Now after 4 years, we have a pretty good command of what metrics to concentrate on. What works, what doesn't. Which channels are better and which sales techniques work. We learnt this the hard way and by reading blogs by David Skok, Jason Lemkin and Tom Tunguz. They did provide some benchmarks to go on. But nothing specific to the circumstances in India.

Looking around, we realize that we are in a very special situation. Since we concentrated only on India for our product, we have SaaS revenue from only Indian customers. This gives a nice opportunity to start creating some benchmarks.

Unfortunately there are not many hard numbers out there which can help new India B2B SaaS companies. So in the interest of transparency, we are sharing the SaaS metrics for our Cloudagent product. Some important points:
  • Cloudagent is a contact center product. It is a high touch point product with a big sales cycle.
  • All revenues and numbers are based only on Indian customers. We are in fact one of the very few companies out there serving only Indian customers :). May not hold true this year though.
  • We are doing this as an experiment. Looking at how it goes, we will open up more and more of our numbers, similar to what Buffer did. So be good to us :)
  • None of the metrics are set in stone. This is what works for our business and we are all learning. Please comment here our mail me at chaitanya@ozonetel.com or follow me @nutanc on twitter. Would love to hear your thoughts.
  • We will be updating this page on the 10th of every month. So please check back in to see how our business is doing :)
Building a SaaS machine is hard. But once it starts rolling, it is almost like clockwork. The numbers presented are what helped us to fine tune our process. Looking at isolation, each number may not make sense. But the way they all interact to run the SaaS machine is what is most important.

So without further ado, the SaaS metrics for Cloudagent

Popular posts from this blog

Integrating Arborjs with Angular to create a live calls dashboard

By C Chaitanya
Arborjs  is a cool graph visualization library. Angular  is one of the best JavaScript frameworks and we have been using Angular in a lot of our front end development. When you handle millions of calls, proper visualization becomes very important. Without proper visualization, you can get lost in the mountains of data. So we spend a lot of time to come up with good visualizations to represent the data. Since we loved the cool way in which Arbor represented graph data, we could not wait to hook it up with Angular. Because of Angular's two way data binding, when you hook up Angularjs with Arbor.js you can get a dynamically updated visualization of graph data with cool animations. To give back to the community, we have put up the code online at Github . Basically we have created an Angularjs directive for Arborjs. Please feel free to fork the code and add extensions and use it for your own visualizations. The code is self explanatory with comments inline. Best way to ...
Read more

First Post

By C Chaitanya
In this blog, I will be talking about my experiences in trying to build a cloud telephony platform , KooKoo . Along the way I will also be talking about different design choices I made, good programming practices and the IVR domain in general. For technoratti: NNFJW8EW86C3
Read more

Google business messages and chat agents-A match made in heaven

By C Chaitanya
Google has launched Google business messages without much fanfare. It's just a small button that pops up when someone searches for your business on Google. But from the conversation industry perspective this is HUGE .   Do you know that the small call button drives millions of calls i n a year for pizza joints and other retailers in the US. Businesses spend more than a trillion dollars supporting billions of customer service calls each year. Now imagine how many chat conversations the "Message" button can drive.  Think of how customers interact with business. 1. Search on Google. 2. Click on web site link. 3. Web site shows chat pop up and tries to force the user to chat.(Annoying. I know :)) 4. User clicks on chat and starts conversing with a bot or an agent. This flow can now be completely changed. The new flow can be: 1. Search on Google. 2. User clicks on Message and starts conversing with a bot or an agent. What if you could design a customer experience that helps...
Read more