The Story Behind StatusPage
Steve Klein, Co-founder
What inspired StatusPage?
After leaving ReverbNation our plan was to build a handful of niche products that would throw off passive income for us. To fund development, we did a bit of consulting on the site. Funnily enough, our first project was actually StatusPage.io.
When we were at ReverbNation, we were talking to one of the PMs about an idea for an some iPhone App that had to do with concerts…anyway one of the features of the App involved receiving text messages. The PMs first objection centered around having to build out the tech to send and receive SMSs so we brought up using Twilio. He was suspicious of relying on a third party for such an integral part of the App.
We didn’t really have a great response. We pointed to the fact that they had recently raised a few million dollars but that didn’t really seem to affect his opinion too much.
From that experience, we kind of knew that if companies could be more transparent around how they were performing, they would be able to win new customers. Not only that, they might be able to keep existing customers happier by providing a better experience during downtime just by keeping them more in the loop about what was happening.
We saw that a few companies like Github and Heroku had these incredible, bespoke status pages that did exactly what thought everyone should be doing. So we decided to make a productized version of what they had built for themselves.
How did you get started?
We started working on StatusPage.io in our spare time while we were still consulting. Luckily, our skillets complement each other really well. Scott was in charge of server wrangling and backend development…I did all the design and front-end development.
Our work flow usually goes something like this:
- We both talk about what feature to work on next and how it should work
- I design and then stub out how it will look in HTML/CSS
- Scott comes in and actually hooks it up to the database
Figuring out what to build and how it should work was pretty easy because we were building StatusPage.io for companies like ourselves. We kind of intuitively knew what needed to be in the MVP and what didn’t.
We worked part-time for 2 months and then full-time for 2 months before we launched. We actually got into YCombinator and Danny came onboard shortly after that and the rest is history.
When we started out we were pretty committed to building a remote team but decided it wasn’t for us. As we continue to grow, we plan on building out our team in Denver and San Francisco.