Skip to main content

Growth

As a startup we try to monitor a variety of metrics. And when sharing with media and doing PR, we generally fall back on vanity metrics. Vanity metrics are good because they can help you inflate your ego and give you a sense of achievement.

So when we say that we are nearing 2 billion calls handled on the platform, we feel proud. Or that we are present in 150+ countries. Or maybe that our employee count is nearing 100. Or that there are more than 10,000 developers on the KooKoo platform. All metrics are good and give a sense of achievement. But they dont give a sense of the true health of a business.

For any serious business,especially in the B2B space,most of the time, the only metric that matters is revenue growth. How fast are your growing? How much are you growing?What are your margins?

So in many ways, the award that we are most proud about is the Deloitte Fast 50 award. The reason is because they give the award to the fastest growing companies on audited accounts.

It gives me great pleasure in announcing that Ozonetel has been selected as a Fast 50 company for the second year in a row running. And this time we are in the top 5. We are one of the top 5 fastest growing companies in India and it feels awesome :). And the thing that makes it doubly sweet is the fact that we are bootstrapped.

This years growth is extra special because it is at scale. Growing from 2 lakh to 20 lakh is easier when compared to growing from 2 crore to 20 crore. Also, this was the year we proved there is a huge market for cloud communications. This year our revenues crossed the market size figure put forth by the VCs couple of years back.

Now, we need to make sure we are in the Fast 50 3 years in a row :)









Popular posts from this blog

First Post

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

Integrating Arborjs with Angular to create a live calls dashboard

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 get s

Mashing up Freshdesk with KooKoo for customer support ticket management

Sorry for the delay in writing a blog post. I have been caught up in too many things since last month(we are growing, so its all good :)) Anyway, this week I thought I will look at how we can use the latest rockstar startup from India, Freshdesk . Freshdesk, as most of you know is one of the best "Social Helpdesk" systems out there. I am sure most of you are already using Freshdesk to support your customers. In this blogpost I will explain how you can add telephony to the mixture. In particular I will show some code which you can use to : Welcome the caller by name Ask him to enter his ticket id Play out the ticket status Connect the caller to the correct agent handling the ticket. Luckily for us, Freshdesk has a very well defined API and it was a pleasure to work with it. The engineers were also very supportive and answered all my queries quickly. So lets get into the code directly. 1. First we need to get the caller information. For this we need to a