This is the sixth and final post in a series about Lean Startup on elmah.io. Check out the other posts here:
When looking back on the last 4 years, elmah.io has pivoted multiple times. My original idea with elmah.io (hence the name), were to implement a remote logger for ELMAH (the open source project). Being a frequent ELMAH user, I got tired of the limited search capabilities and setting up SQL Servers. So elmah.io was born.
First pivot came around 2014. I talked with a lot of people who liked the product, but didn’t see huge benefits over ELMAH. I think it actually had back then already, but I was not good enough at communicating that.
It’s a common mistake for entrepreneurs with technical background as myself, to think that visitors think that the product is as cool as you do yourself. Communicating features are often communicated in a lot of technical terms, rather than highlighting the why’s.
The pivot where a number of integrations for popular .NET logging frameworks and a major redesign to support structured log messages with severities other than just errors. At the moment, my belief in the product where, to compete with successful products like Logentries and even Elasticsearch. I even started thinking about (and even coded a bit) on a new metrics product, which were meant as a supplement for the logging part, able to log everything from website clicks to performance numbers.
During the next year or so, people started to be confused. No-one (even me) knew if elmah.io was a cloud logging platform for structured log messages or an error management system for websites. After spending quite a lot of time being confused and trying to explain to users what elmah.io was and it wasn’t, I decided to change the path of the product once again. In many ways, this pivot returned elmah.io back to its original vision: Providing error management for .NET web applications. This time not only using ELMAH, but for any logging- and web-framework.
In the last year, elmah.io has gained a lot of new features. Features like Deployment Tracking and Uptime Monitoring were added to the suite, and while they can be looked upon as separate products, they very much support the vision of delivering the best error management system for .NET web applications.