1. Who are you and what is your connection to ErrorStream?
I’m the founder of ErrorStream.
2. What is your background and what did you do before working on ErrorStream?
I’ve been leading development and IT for almost 10 years at a couple of companies.
3. Can you explain what ErrorStream is and where the idea came from?
ErrorStream is a tool for developers to capture errors that occur in their applications. All they have to do is install one of our packages into their projects, and they can start logging all of the issues that come up in production. The website provides visibility on those issues, which is incredibly valuable when businesses rely on their software stack working correctly. Engineers feel better about pushing new code into production because they have the tools to monitor their code once it’s passed QA and entered production.
The idea came about when Facebook changed their social login API. They changed how they delivered the new users name, and one of our websites stopped registering new users. I thought there had to be a better way. So I made ErrorStream. We installed it, and it captured so many small things that I knew I really had something special. By being knowledgeable about what was happening in production, we increased revenue 20%.
No amount of QA or unit tests could have prevented the issues we saw that day. They were only present when under a large amount of use.
4. Did you do any validation for the idea of ErrorStream before building it?
I did closed beta with my own team, then an open beta, and now we are open for business. Validation is incredibly important as you are developing new services. You need to know not only that people are willing to use your product, but are willing to pay for the benefit of using the product.
5. What are you short term and long term plans for ErrorStream?
Short term, we are expanding functionality within the website. Adding all of the features we think are must-haves. We have to be very careful that we don’t create a bloated UI in that process, so some things take a little time to get just right.
Long term we are planning on rolling out a lot of different integrations. Node and Ruby packages are in development. Other JS frameworks like Angular.js and Vue.js are in planning stages. We want to increase our reach by making it so simple to install a package that no team would ever say no.
6. And finally, do you have any final words of advice for aspiring entrepreneurs?
Just keep trying things! Don’t be afraid to fail. You’ll never learn if you don’t fail. The thing that separates you from everyone else is that you’ll keep trying, learning and evolving yourself until you really do become successful. Validate your ideas, and pursue whatever it is that you’ve been able to access the market with. Did you convert well on beta list websites? Keep going. Did you get a good response from a private beta? Keep going. Did you get a paying customer in open beta? Keep going. The only thing you don’t want to do is to bet all of your money and time on a product that people don’t respond to. If you’ve made something people don’t respond to- learn from your mistakes and keep that information for your next iteration.
If you want to learn more about Kevin’s startup ErrorStream just click here.