JB: How did you start Calendly?
TA: I didn’t start off with a position that a business needed to be started. I started off with the position that this problem needed to be researched. I needed to understand the depths of the problem and understand where there was an opening in the market.
JB: Where was the opening in the market, besides better support?
TA: I thought the existing products did not look good. Keep mind this was early 2013. At the time, Apple was kicking ass and everyone was beginning to pay a premium for design. I felt like a lot of the existing tools at the time looked and felt like they were built in the 80’s. I thought users in 2013, wanted better usability, better user experience, and things to look good, and I thought I had a good eye for that. During my time at Perceptive, I demoed the software hundreds upon hundreds of time. In demoing a lot, I learned how to tell the story of a product and how people came to understand software. And, by the way, I think that is a great skill for anyone to have, but that’s how I learned a lot about usability. In demoing software, you can show them all the features, you have to be able to roll it out to the customer in a way that makes sense their business process and workflow, and that, by the way, is why I felt like I had good instincts around usability and user experience.
JB: So was the first step? You making designs?
TA: It was not. I was not committed to making the designs yet. I was committed to do as much research as possible. The more I did the research, the more I became convinced there was a huge gap in the market. After I drew conclusions, I decided I needed a technical co-founder so I could build this.
Oh, let me step back. Before I made the decision to get a technical co-founder, I sketched out and made a very detailed list of product requirements. From all the observations of my research, here’s what the winning set of features would be, and then I began to seek out a co-founder.
JB: Everything is spec’d out, now you’re looking for a technical co-founder. So many entrepreneurs are looking for technical co-founders. How did you start that process?
TA: First thing I did was reach out to my network. There was an old co-worker who was one of the lead engineers and we’re friends and he’s a brilliant guy. And I was like, “Hey, we should do this together.” I liked him, but it never panned out.
JB: Why didn’t you build it? You do have a Comp Sci background.
TA: I could have built it, or at least some of it, but I didn’t have the time. I needed someone else to build it and to hire someone to do it.
JB: So how much do you have in the bank at the time? $100k?
TA: More like $200k.
JB: Were you ready to put it all in to the idea?
TA: Definitely. I was ready to put all of it into it. All of the other ones, I was trying not to lose money, and this one, I was ready to put all the money in, and borrow some to get this off the ground. I was ready to go.
Looking back on it now, it could have been so bad.
Laughs fill the room from both of us.
And also with the past failures, I knew what failure felt like.
I couldn’t find a technical co-founder.
JB: Why couldn’t you find a technical co-founder?
TA: Well I couldn’t find a technical co-founder because all of the best engineers are making a lot of money, and from my experience, most of them have a lower tolerance for risk than business people do and the ones that don’t have a low tolerance for risk, just feel like they can build it themselves and they don’t need to share ownership with someone else. Also, I think a lot of people approach them. I think that is why it’s difficult.
Now, I also think if you’ve done it before, it’s less difficult for those people. I think that is one thing that could put you head and shoulders above everybody else.
JB: But not finding a technical co-founder didn’t stop you?
TA: That’s right. I was going to get this built. So I start researching, looking for different people. I talk to local dev shops. Got it spec’d out. Many shops just immediately want to know if you have money. Many of the dev shops were motivated by the amount of money they would get from the project and they were more concerned about whether I could pay them or not, than they were excited about bringing this idea to life, and launching it, and serving customers, and changing the industry.
The company I did find was a partner from day one. Obviously they want to get paid, but they were more excited about what we could build together.
JB: And how did you find them?
TA: Internet research. Basic Google Searches for Ruby dev shops.
JB: What made you pick them?
TA: Every time I got on the phone with them, I learned a bit more about the process. They were excited about the work and very knowledgeable. Eventually, I flew to Kiev to meet them. We had an intense 2-day planning session where we scoped out the entire project. It was intense because we had to make a lot of decisions about which calendars do we integrate with and when and much more.
JB: Initial quote?
TA: They didn’t give me a specific quote. They provided a rate and then clear process of the order we should build stuff.