1. Podcasts
  2. Pattern Breakers
  3. Mitchell Hashimoto: How Solving His Own Problem Sparked HashiCorp
Pattern Breakers

16 Jun 2025 · 39m · 19 chapters

Episode artwork

Mitchell Hashimoto: How Solving His Own Problem Sparked HashiCorp

In short

Mitchell Hashimoto explains how he built Vagrant to solve a real pain (setting up client dev environments), then expanded into HashiCorp’s cloud-first infrastructure tools (Packer, Vault, etc.), navigated pivots during Docker/containerization and low revenue, and later chose to leave HashiCorp to keep building new technical products (Ghosty).

Guests

Mitchell Hashimoto, founder/early builder behind Vagrant and HashiCorp; later worked on Ghosty. Mike Maples Jr. (Floodgate) hosts the Pattern Breakers podcast.

Key claims

Founders should chase problems they care about for 5–10 years, not just TAM; “flag planting” and product breadth can reset market expectations; bring in a CEO when founder time is better spent on product/engineering; focus beats being a “special CEO”; acquisition offers can be distracting—use “least regret” thinking.

Notable examples

Vagrant’s “double click” client.exe idea; WhiteHouse.gov couldn’t use the name “Vagrant”; 2014 down year from containerization/Docker; pivot to focused enterprise products (Vault Enterprise) for Global 2000; nearly accepted a ~$30M acquisition then asked for ~$100M and it nearly failed.

Written by AI. May contain mistakes.

Chapters

0:45

Mitchell Hashimoto's Journey Begins

Mitchell discusses his early influences and motivations leading to HashiCorp.

“of Floodgate, and it's Go Time with Mitchell Hashimoto.”
2:08

The Birth of Vagrant

Mitchell shares the origin story of Vagrant and its initial purpose.

“Maybe we should start even before the beginning.”
4:50

The Decision to Go Full-Time

Insights into the circumstances leading Mitchell to pursue a startup career.

“Did you ever imagine yourself as a software startup founder?”
7:40

Identifying Market Opportunities

Mitchell outlines the market gaps he aimed to fill with HashiCorp products.

“And, you know, at the time you had other infrastructure players, right?”
9:12

Expanding Beyond Vagrant

Discussion on HashiCorp's evolution and the development of multiple products.

“You rolled out a bunch of tools pretty quickly, like Packer, Reform, and Vault.”
11:02

Leadership Decisions and Challenges

Mitchell reflects on the leadership choices made during HashiCorp's growth.

“One thing I've always found interesting about your journey from a distance is a lot of the founders want to be the CEO the whole time forever.”
14:00

Transitioning Leadership: The Search for a CEO

Learn about the challenges and considerations of finding a new CEO.

14:40

Navigating the CEO Transition

Discover the dynamics of transitioning to a new CEO and maintaining company culture.

“And, and did you learn anything about, so a lot of times I find that when a startup brings in an external person to be the CEO, you're introducing something totally new into the equation.”
18:10

The Importance of Passion in Work

Understand how working on what you love can lead to better outcomes.

“there was necessarily a market study that you did.”
20:00

Finding the Right Problems to Solve

Learn how to identify problems worth solving in your professional pursuits.

“So I get, especially now, you know, I've been out of Hodgecore for a couple of years and I get a lot of emails from founders or prospective founders.”
Show all 19 chapters
22:40

Overcoming Early Struggles

Explore the existential challenges faced during the early days of a startup.

“academically, I was pretty run of the mill, nothing special, no awards, nothing like that.”
24:40

The Pivotal Moment of Change

Hear about the pivotal moments that led to a successful pivot in strategy.

“I mean, like my that was that was the only time in my life where my wife and I, we were we were just dating and we were married, but we broke up for a period of time.”
27:00

Sales Conversations and Market Fit

Gain insights into how product focus can transform sales conversations.

“but we're just going to go and tell them this product's gone.”
28:00

Sales Conversations Shift to Interest

Learn how sales conversations evolved from passive listening to active engagement, indicating a shift in customer interest.

“We're going to try to find people that believe in us and see if this makes sense.”
28:48

Turning Down a Life-Changing Offer

Explore the pivotal moment when a significant acquisition offer was turned down, emphasizing the principle of least regret.

“And again, this is sort of the process of it sort of trickling upwards and things looking better and better.”
31:18

Advice for Founders on Acquisitions

Discover important advice for founders facing acquisition offers and the distractions they can bring.

“And we just, they went from 30 and we just asked for a hundred.”
33:13

Navigating M&A Conversations

Hear insights on handling M&A talks and the importance of maintaining focus on company goals.

“And, you know, I challenged founders to do the same thing.”
35:35

Deciding to Move On from HashiCorp

Understand the factors leading to the decision to leave HashiCorp and pursue other interests.

“And it was really just like, I'm doing my thing and, you know, I need to stay focused.”
37:15

Finding Joy in New Projects

Learn how exploring new technologies and projects can lead to exciting opportunities.

“And so how have you decided what to work on in recent years then?”
A man walking through an airport, asking his phone a question

Ask about this episode

Get the gist, explore an idea or ask about something said.

Claude

On Pattern Breakers, what are the key points of this episode?

Searching your listening

Transcript

Automatic transcript. May contain errors.

0:00I've never found a shortage of problems. When you work in a real industry, whatever industry, every industry I've worked in, it was really like, what do I really care to solve? Like, what am I going to work on for at least five years? But probably, you know, more like 10 to really solve this. And so, like, I always tell those people, like, go back to work, soak it all in and find something you like really care about. And it's going to be great.

0:23Mike Maples, Jr.: Mitchell Hashimoto didn't set out to start a company. He set out to fix what frustrated him. In 2009, he began hacking nights and weekends, open-sourcing the tools he wished existed. For over a year, barely anyone noticed. But he kept building. And that quiet persistence ignited one of the decade's most influential cloud companies, HashiCorp. This is Mike Maples Jr. of Floodgate, and it's Go Time with Mitchell Hashimoto. This is Mike Maples Jr. and welcome to the Pattern Breakers podcast, where we explore why some founders radically change the future and how they stand apart. Together, we'll learn about the counterintuitive mindsets and actions behind their remarkable success.

1:08Mike Maples, Jr.: Brace yourself for a world where chaos is welcome, naysayers are often a positive signal, and movements galvanize misfits who transform the impossible to the inevitable.

1:30Mike Maples, Jr.: the most successful founders don't usually chase startup ideas instead they're pulled toward problems they can't ignore and Mitchell Hashimoto is a perfect example as a college student he built vagrant to streamline dev setup which in turn led to HashiCorp and later Terraform vault and console tools that power the modern cloud. Today with Ghosty, he's still building from where his curiosity leads him, and not by following the latest trends. Let's talk to him.

2:08Mike Maples, Jr.: Mitchell, welcome to the podcast. Thanks for having me. Maybe we should start even before the beginning. How did you get introduced to computers and software, even before you were at the University of Washington? I mean, my introduction to a computer was just my dad bringing a Macintosh home and, you know, we using it for word processing and stuff. But I think jumping forward to where I guess I got really into computers was computer games. And I think a lot of kids will say like making computer games. I was more on the cheating computer games side of things. I wanted to, I wanted to bot them. I wanted to like do like infinite resource glitches.

2:45I was just really interested in reverse engineering, not even know how they work, just how they worked enough to cheat them. So that's how I really sort of got into the more engineering side of things.

2:55Mike Maples, Jr.: So you ended up at the University of Washington, and you started this side project called Vagrant. What motivated you to do that? What was the origin story for Vagrant? So the job I had was a consultancy, and I was a junior web developer. And so we would see all sorts of clients, all sorts of projects. you would get assigned to a project and if you needed help from someone else or someone else needed help from you it took so much time to get the environment set up to be able to like do that help and it was like non-billable hours so just kind of an annoying amount of time at this consultancy and you know the joke i made kind of windows centric joke i made was i want to double click and be in the working environment for any client i want to like client.exe for whoever it is and double click um that's what i ended up doing vagrant was a you know dev tool to spin up dev environments.

3:45And yeah, it sort of propelled me into everything else. But that was the original motivation. And why why the name vagrant? It was just I was trying to come up with some sort of name where it was like a very temporary working environment, a very moose from client to client. And the analogy was, you know, vagrants move from city to city. And I was, you know, I was 19 when I came up with the name. So it is what it is. I think the funniest story there was at one point during an Obama administration, the CTO of America, I forgot his name, but he emailed me and was like, we're trying to use Vagrant within the WhiteHouse.gov and some other properties, but there's this mandate for the administration that they can't endorse.

4:28I think it was like homelessness or something. And they were like, I know it's really stupid, but just the name, we can't use it. So I had to provide like a separate, like white labeled binary release version that they could use so that they couldn't say they used to. Homebody. Yeah. And it's such a superficial thing, but I found that amusing.

4:49Mike Maples, Jr.: At the time, did you even think of yourself as having an entrepreneurial bent at all? Did you ever imagine yourself as a software startup founder? When I look back in hindsight, I think there was a bunch of signs that I was heading in that direction. But in the moment, I definitely didn't consciously think I would ever start a company around it. That wasn't my intention when I started the project. I really, I have a few like chat logs with like old chat logs with friends where I said, I hope this gets me a job. You know, that was my thinking. Like, I hope this eventually just helps me become employable because I was still in university.

5:23But there was like all these signs that I liked trying to use technology to generate income. And so, you know, it's not a huge jump to think I would try to do it with this project. I just didn't think so in the moment. Yeah.

5:36Mike Maples, Jr.: So how did Armin enter the picture then? And how did you guys decide to start collaborating and build a company together? Yeah, he was already my best friend in college. And he was one of the first people I showed Vagrant when I built it. I did build Vagrant. Vagrant was sort of the only project I built without his involvement in any engineering capacity. But he was certainly gave me early feedback. And yeah, it was so casual. I mean, And as I think as all university students are, it's so casual. We were just at lunch at the university cafeteria and I flipped my laptop around. I said, check this out.

6:08What do you think? That's how that started. But we always just collaborated on ideas. And he was super into sort of the same problems that I was chasing down, even though we weren't exactly working together at the time. We were on the same research project together, but we were sort of on different teams. He was my boss.

6:24Mike Maples, Jr.: So like what got you to thinking then, okay, we should start this together as a company. So I was at University of Washington up in Seattle, got a startup job in the Bay Area with an early like Series A funded company that didn't quite make it. And there's two things that really pushed me to start a company. One was the growing popularity of it, just an open source. I mean, I was spending eight hours working on my startup job as just an engineer. And then I would go home and spend anywhere from four to eight hours working through GitHub issues, working on roadmap stuff. It was super unsustainable.

6:58So that was one side where I just didn't see how I could do that long term. And then the other side was I was, you know, as a young graduate meeting people and things. I was going to sort of professional working events. I was meeting other people in similar jobs. And I was quickly realizing how many of these companies, at least in this sort of my bubble of early stage tech companies, how many had the same challenges that I was having. And the word of mouth started getting around me like, hey, I heard you built something to solve this problem. I was like, sure, here you go. And just like, you know, send it to them.

7:28And that sort of got my brain thinking, okay, we got this thing that's taking up a ton of time. And then we have these problems that really exist and they're related. So should I just go and work on this full time? And that was, yeah, that's what kicked it off.

7:42Mike Maples, Jr.: And, you know, at the time you had other infrastructure players, right? You had Chef and Puppet and folks like that. Like, what was the kind of the core insight that convinced you that there was enough white space to fill? Was it just the fact that people were using the product and it was kind of an existence proof or was there some type of a position in the market that you thought was still unfilled that you wanted to go chase? Yeah, pretty much that last point. I think that I knew the founders of Chef and Puppet very well. I had no intention of taking on config management. I thought there was enough space around the outside that needed to be solved.

8:19And that's what I sort of was chasing. I felt that infrastructure software was sort of either entirely missing certain categories or the things that were there were very tuned to sort of like physical data centers or, you know, what I would call a legacy way of thinking even in that moment. What I was really noticing was, you know, my bubble with Silicon Valley tech startups that every Silicon Valley tech startup was using was the cloud, was specifically AWS at the time, because even Google Cloud and Azure were either non-existent or very nascent. this tooling just didn't either fit right technically or didn't fit right commercially, like the way they licensed it was per core or something like it just didn't work in the cloud.

9:00And yeah, I thought, let's build software that's sort of cloud first in terms of recasting a lot of these problems that existed, but don't have solutions in the cloud world and go from there.

9:11Mike Maples, Jr.: And then I noticed that when you started HashiCorp, it wasn't just Vagrant, right? You rolled out a bunch of tools pretty quickly, like Packer, Reform, and Vault. So what drove your thinking there, and how did you decide between going super deep in one product versus being sort of broad? A lot of it was flag planting. Claim some free land until someone challenges you, and we expected someone to challenge you, but there's value in being the first person to throw your flag down, so part of it was that. Another part of it was that people viewed me, us, the general company, as this dev environment only company because of Vagrant.

9:50And I knew we wanted to head into these other categories, but we were constantly dismissed as like, oh, they're the dev tool guys. And so in addition to planting all these flags, we wanted to like sort of show the range that we were capable of operating in and re-normalize the conversation to expect to this range. And, you know, the first few that we released outside of the dev tool, people definitely were like, why? Like, this is super weird. And the other side was Armand and I had sort of this like audacious goal. I think we're like, if we're going to do the venture back thing, let's like, let's really go for it.

10:20And our goal was sort of like, the same way sort of, you know, IBM or Microsoft or any of them sort of said, like PC in every household where like we want HoshCorp software in every data center.

10:33Mike Maples, Jr.: So the decision to raise venture and not just go full bootstrap mode, what caused you to kind of take that leap? It was really that audacious goal that caused us to take that leap. We're like, let's just go big and let's go fast with sort of the mindset. And can I do the VC thing? Let's like challenge myself. Let's give it a shot. So there's there's a little bit of that involved. And then I think the last part is that was the norm. Everyone seemed to be doing it. So how hard could it be for better or worse? One thing I've always found interesting about your journey from a distance is a lot of the founders want to be the CEO the whole time forever.

11:11Yeah.

11:11Mike Maples, Jr.: You know, you guys made a pretty intentional decision, it seemed, pretty early to bring some folks in. What was your thought process there? And were you resistant to the idea at first or did you know pretty soon, hey, there's certain things I like to do and there's things I don't want to do and it's time to bring in that help? I always describe to early stage founders somewhere between 15, 10 to 15 to around 40 to 50 employees is when the cracks start showing up in process, but you're not quite big enough to solve them the traditional ways. Like you can't just hire someone focused on a very specific thing because you're still too small to really like have that level of management and focus and things like that.

11:56You really need these people that could do multiple things, but they're probably not doing it as well as you have. And the culture is not solidified. There's just all these challenges at this period. And it was right in that period where I like to say the CEO job becomes a much more defined, serious role where you're really focused on corporate structure, financing, vision and roadmap and direction and things like that. And it was really taking away from my time that I was used to being able to work on products and think about products and things like that. And I think it was one of our board members, investors told me, as a startup, you're very likely to not succeed.

12:32Like the odds are very much stacked against you. And for an investor to invest in a startup company means they see something, some quality somewhere that they think you have a chance to not fall into the majority. You're going to be an exception that actually breaks free. And sometimes that's because you have an all-star CEO. Sometimes that's because you have an all-star product or a very unique view of the future that, you know, it's just worth the risk to give it a shot because it's very unique. You know, there's all these different categories. And for us, we fell into the category of sort of they felt we had a particularly unique product vision and execution capability.

13:10So it wasn't the CEO part. And every minute you spend doing something that isn't in that special category regresses you back to the mean of more likely to fail because you're not special there. And so, you know, I'm a strong believer in focus on what makes the company special because that's also what gives you the highest chance of success. And so we had this idea of we're not special CEOs. Can we bring in someone? We don't even need a special CEO, although I think we found one. You know, we just need someone that's good enough and won't tank the company, won't get in the way so that we could do what's really special in the company, what we felt.

13:46And and we're like, but if we don't find the right person, we're going to do it. So we just we were doing standard corporate building out our sort of corporate leadership, you know, VP of finance, marketing, the sort of standard things you do around that scale. and at the same time we put out a search for a ceo we had a board meeting where we were going over we had just engaged some you know corporate search uh search firm and and we were we were all on board we were already searching for a vp sales vp marketing those were the two that we were actively searching for and in that same board meeting don't know exactly how it's phrased but i remember we introduced hey also we want to do this president slash ceo search and the analogy we made which you know has its own flaws analogies always have flaws but the compare the comparison and we made was, you know, if we could find, you know, the Google CEO at the time, Eric Schmidt to Sergey and everything, you know, that we could find that relationship, then let's, let's find that relationship.

14:37And that's what, yeah, we hunted out.

14:40Mike Maples, Jr.: Okay. And, and did you learn anything about, so a lot of times I find that when a startup brings in an external person to be the CEO, you're introducing something totally new into the equation. And some, some companies handle that transition way better than other companies. What do you think you got right when you brought David on board and what did you sort of commit to doing to make the transition effective? Or did it just work out because you just did the right things almost by instinct? It's both. You have to have the right instinct, the right mentality, the right personality, but then at the same time, there's a lot of conscious decisions.

15:18So one thing that really helped is Dave, me, and Armand were all very methodical very you know for better or worse non-emotional decision makers um we look at everything we look at pros and cons we look at the directions we could go and so i think that helps be very non-reactionary very non-emotional when it comes to things it's it's it's good and bad and i think the other side was we had a lot of respect for each other and so you know we we put in process for the fact that yeah yeah dave was coming in as ceo but he would ask us for any final decisions. This is what I'm thinking. Are you okay with it?

15:52He was very deferential in the fact that when he joined, he said, companies are something led. And this is clearly a product and engineering led company, and I'm not going to change that. And you're the product and engineering leader. So I think you could feel that throughout the growth period.

16:07Mike Maples, Jr.: Was there anything about his leadership style, sort of looking back on it, he imparted something to you about, okay, here's what a good CEO does that maybe you didn't even realize at the time, but in hindsight, you realize was super additive. Yeah, it's, it's, I mean, it's hard to pick out any single thing. I learned so much from Dave. And I think generally most people, it's just like, you make a lot of good decisions, like a lot of small good decisions that, that add up versus like the one big one and Dave's background. And we were specifically looking for this in a CEO search. Dave's background was formerly sort of marketing professionally.

16:44I just learned a lot about how you talk to customers, how you talk to the market, how you talk to analysts. I mean, I think he helped a lot with that. And it wasn't anything super flashy. Honestly, the opposite, it was really clear. I think that was what was really helpful. He helped distill something that we could go to market with that was really clear on what we were trying to do first. And before he joined, I remember we were really struggling to explain to non-technical people what the hell it was we were trying to do. And then just when we met and did big company planning, like hiring sales type fundraising planning, the way he methodically backed into answers was really nice.

17:28It felt like before that, you know, when do you raise? How much do you raise? What valuation looking for? Like it really felt sort of like seat in my pants. Like this sounds good. This sounds right. And and that changed with him. I mean, that was very much like we're trying to. Yeah, yeah, there's comps out there, of course. This is what the market is, but we're trying to hit these numbers. And to hit these numbers, we need this many people. And we're trying to do this on the product side, and that'll need this many people. And if we hit that, then our valuation will naturally be this at current multiples.

17:55And you can just keep working backwards through all this stuff. And it just became, I liked looking at things and being like, I understand this. This is a rational decision.

18:04Mike Maples, Jr.: It seems like a lot of the projects that you've been part of that have been successful were things that you did because they were interesting rather than there was necessarily a market study that you did. So it's kind of like a lot of the Hashi Corp kind of became an extension of the expression of what you were already doing because it was interesting for its own sake. And even what you're doing with Ghosty now, it seems like you're not necessarily advertising that it's going to be the next billion dollar company. It's more like, this is the most interesting thing I'm working on and that's enough, right?

18:37Mike Maples, Jr.: If it's interesting for its own sake, you just follow the thread. And so not everybody thinks that way when they think about their product. And it seems like you kind of do. Yeah, yeah. I think I've gotten very lucky, but I think there's also a bit of method to the madness. I think that if you work on something you really care about, you do much better work. At least if I could speak for myself, When I work on something I really care about, the work is night and day, you know, 100 times better than something I'm forced to do. And so I've always had this, I don't know, arrogant ideal where I always, you know, from a child to university to getting out, I always said, I just want to work on what I want to work on.

19:18And I'm going to figure out a way to make that work. And so I got lucky. I wanted to do sort of web development. And I found a place where I could do that. And I wanted to work on infrastructure stuff. And I joined a startup out of college where I could be an infrastructure engineer. And I always chased what I wanted to do more than offer letters or anything else that was going or what the market was doing or anything. And I think I got very lucky in the sense that those opportunities were available, but also infrastructure ended up being a very high growth, exciting industry. But it's not just luck, right?

19:51I think that part where you do really good work in those environments starts to speak out where I felt like people could feel the difference in the products we were building because there was a lot of care put into it and the interactions we had with the community and all that sort of stuff. So I get, especially now, you know, I've been out of Hodgecore for a couple of years and I get a lot of emails from founders or prospective founders. And one of the things that I get a lot is I'm looking for a problem to solve. Or like I found this problem. What do you think? Is it real? Whatever. And I would say it's my most negative response to those questions is throw it away.

20:27Don't do it. It's a real problem, but you're not the guy, right? Or girl. Like just don't do it. I've never found a shortage of problems. When you work in a real industry, whatever industry, every industry I've worked in, you know, and there's only been a few, but every industry I worked in, it was really like, what do I really care to solve? Like, what am I going to work on for at least five years, but probably, you know, more like 10 to really solve this. And, and so like, I always tell those people, like, go back to work, soak it all in and find something you like really care about. And it's going to be great.

20:57Don't get too stuck in on total addressable market and all this stuff. I mean, I think it has a way of working itself out when you work on something you love.

21:06Mike Maples, Jr.: Yeah, and it's interesting when you kind of study the field of breakthroughs, quite often it's similar that the breakthroughs come from people pursuing something that they're interested in for its own sake. And part of the advantage becomes that the people who only pursue stuff that they think is going to be a high return on investment in their time, they end up pursuing things that are conventionally interesting to other people, you know, kind of in the status dominance hierarchy. But the breakthroughs come from exploring the unexplored with a vengeance that the odds that you're going to find something truly novel go way up because you're just you're pushing past the frontier of what other people are pushing past.

21:48Mike Maples, Jr.: And that's that's where the uniqueness starts to happen. Right. By you experiencing a problem, you're already sort of on the frontier of that problem usually. And then the other part is, you know, I felt a ton of confidence. I always say founders have to have a certain amount of hubris associated with them, right? You get too much and you get sort of toxic, but you have to have the right amount. And my sort of hubris that I had through my 20s and starting HashiCorp was really like, I was sure that I was at least top five in terms of people, like the amount of time I spent thinking about this problem.

22:17I was totally obsessed in a way that probably people would view is unhealthy, but it was also like what I loved and what I wanted to do. And I think that helps a lot. And I think that that's part of it, you find something you truly care about. And you're gonna at least in terms of time, you know, maybe not in terms of quality, but you're gonna outthink the everyone else. And I think that's a really important just thing to have as a in your back pocket. And I think that I always tell people, there's so many people like academically, I was pretty run of the mill, nothing special, no awards, nothing like that.

22:46Like, you know, Armand's a genius, but I was not that person. And I felt like I needed to spend more time to, like, make up for that. Right. And yeah, and I think there's no downside to doing so.

22:56Mike Maples, Jr.: You know, so far, we haven't really talked about whether there were any near death experiences early on. Were there any moments early on where you're just like, oh, my gosh, this might be existential or, you know, maybe I should have started this after all? Yeah, plenty. I mean, plenty. I think there's two categories of this, and I think they're kind of interesting. The first category is a classic, like, you're just not doing well. We had plenty of those, and I'll give you an example. And then there's a second category, which I think is less common, which is acquisition offers. Early stage acquisition offers more than not end the company rather than continue the company.

23:32And the first category, I mean, I think that the first thing that happened, which really threw a wrench in everything, was sort of the rise of containerization. containerization. It's sort of like the external factor that comes in that you couldn't really plan for. For us, it was sort of containerization as a trend and Docker as a company. Although we were never like directly competitive, it changed the pattern of infrastructure usage significantly in a way that we had to react. And that didn't feel good. It felt scary. I think on the non-technical side, it was really, we had millions of downloads and zero in revenue.

24:07And we spent a year working on a commercial product, building the company around the commercial product, and we could not close a deal to save our lives. And there was a moment where I think we made a critical pivot. But, you know, in the moment, it felt like there was a lot of sunk costs we were throwing away. We were well in the middle of the sort of time between fundraising where we had money in the bank, but we certainly spent a lot. And it felt really scary whether there was a commercial opportunity here. Like, clearly, there was a technical interest there, but like, how do you convert that?

24:36And and so that was, I think, the one where there was a specific year 2014 for me where it impacted every part of my life. I mean, like my that was that was the only time in my life where my wife and I, we were we were just dating and we were married, but we broke up for a period of time. That was all my fault. I was contemplating moving. I was going through all these crises in my life and it sort of all stemmed from this panic. This was it. This was then this was the final year. And yeah, so they exist. And what what caused it to turn the corner, do you think? I don't think I like exhaled and said, like, we're going to be OK for a few years after that moment.

25:14But like that, what started what sort of switched the slope line to head back upwards for me was we had this board meeting. Nobody was mad, but it was one of those things where I say you in the same way that when your parents are mad at you and they don't say you're mad, they're mad at you, but you know they're mad at you or not happy with you, I should say. and we left this board meeting. Armand and I were silent on the entire drive back from South Bay up to the city and we always would get dinner and just go to his apartment afterwards and none of us said anything and we drove straight to the office.

25:48Probably like 7, 8 p.m. by the time we get up there. Didn't eat and we sort of finally talked about it and said, okay, this is not good. We challenged ourself, which is if we started over, what would we do differently today? And we had a whiteboard. We whiteboarded out this idea. And then Armand, I think it was, was sort of like, what if we just did this? What if we just threw it all away? And I was like, I guess. And that was a Friday night. We scheduled an all-hands for Monday. Monday morning, basically the decisions we made were we were trying to make this unified product over our open source.

26:28We decided we're going to break that down into product-specific enterprise versions. No unified product. It's going to be a focused, if it's security, it's a security enterprise product, infrastructure automation, infrastructure automation, et cetera. We also clarified that our market segment is going to unapologetically be the Global 2000. If you're the 2001th biggest company, we're not talking to you. And the sort of third thing was everything we had done previously. The two contracts we did happen to close, we're just going to burn it. We're just going to figure out how to repair that relationship, but we're just going to go and tell them, figure out legally what we could do, but we're just going to go and tell them this product's gone.

27:02We had this all hands. We told everyone. I was super scared. I thought people would leave. I thought people were joining a company where enterprise was, you know, boring and kind of nasty and they wanted to do this open source work and quite the opposite. So this was the first positive thing that happened was at the end of the all hands, you could just feel everyone's so excited. And that was sort of the first sign of everything ticking up where I think people were just so happy to see so much focus. And we were going to say, we're going to focus on this. Like if this doesn't work out, then we're just going to end it.

27:35But at least we're going to go out with a hell of a lot of focus. And that's what we went with.

27:40Mike Maples, Jr.: And did it start to work pretty much right away once you kind of pivoted in that direction? Or did it still take a little while? Yeah. So if I remember correctly, that we spent one quarter sort of building our first product. We focused on it with Vault Enterprise. And we were focused on that. We shipped two features. And we started talking to these prospects that we were pulling out of our open source users. and we're going to try to charge for future roadmap. We're going to try to find people that believe in us and see if this makes sense. And immediately the sales conversations, you could just feel it.

28:08And we were doing a lot of them. Me and Armand as founders were doing a lot of them. You could just feel before the way the sales conversations went were like this. We would spend 30 minutes pitching our thing. They would silently listen, nod their head. And at the end of the 30 minutes, they'd say, okay, thanks, let's talk about Vault. This time we were talking about Vault Enterprise or whatever, we were building Vault Enterprise. We're talking about Vault Enterprise. And at the end of it, there was questions about the product. There was how much is this going to cost? Like the questions of interest.

28:36And so you could feel that. And then, yeah, I think it was January, February, the beginning of the next calendar quarter, we closed as much in sales as we did the entire year previously on the old product. And it felt different. And again, this is sort of the process of it sort of trickling upwards and things looking better and better.

28:55Mike Maples, Jr.: Were there any other major sort of decisions along the way that you look back on and that was kind of a fork in the road that made a huge difference in your success? Yes, but I think the interesting one to bring up, because it's in the second category I talked about with sort of the acquisition type stuff. It's a big decision. It's not wrong to say yes. Like I'm not shaming anyone who says yes to that. But basically what ended up happening for us, and I've already made this public years ago, so this isn't anything secret. a big tech company approached us. It was just me, Armand, and one of their employees.

29:26Three employees. Might have been seed round still, not even a Series A. Not so quickly. We went through a lot of meetings and eventually got to the point where it was clear what they were trying to do and basically threw down an LOI and said, look, we want to acquire these assets. I think they offered us$30 million. We had raised a million at that point. Armand and I owned 85 % of the company, or whatever it was, it was life changing. And it was, it was exciting. I mean, we were walked out of that with that paper, we didn't, of course, we had to not we didn't sign it there, we had to think about it.

29:57And we took it out. And we were we were buzzing. I mean, like, so exciting. And our life's about to change and talking about the things we're going to do and all this stuff. And then we slept. And then the next day, we came into the office. And both of us were kind of down. we liked them but we just knew that we were too small to make a difference and so we sort of knew that this is the end this would be a financial outcome but our technical vision was gonna be over we would be merged into the machine and it wouldn't be great it wouldn't be fun and we started to ask ourselves you know if it's a good idea or not and so Armand very you know the genius proposed that we apply this principle of least regret to this choice.

30:43And he said, let's just go our own way and think about it in another 24 hours and figure out what we would regret and what could we ask for either financially or structurally so that we could look back and in the worst possible scenario, have the least regret possible. So we applied that and we sort of arbitrarily, to be totally on us came up with this silly number where we said we're not really ready to give up this vision, but to give up everything, to give up this window of opportunity, we're going to need more than what you offered us. And we just, they went from 30 and we just asked for a hundred.

31:21The funny thing is they didn't say no. They took that to the board and they needed a unanimous decision. We didn't know this at the time. I know this is hindsight. They needed a unanimous decision to have a deal of that magnitude, given the given there's, you know, the revenue and things like that. And one board member who I honestly believe still had a conflict of interest, I shouldn't have voted, but one board member voted no. And so it almost went through and I'm so thankful and with hindsight that it didn't. But it took me years, a couple of years to really get over the fact of whether that was a mistake or not.

31:56But I was still excited about what we're working on. But, you know, you definitely walk away and you're like, oh, boy, like, what did I just do? I overplayed my hand. Yeah, yeah. I made a mistake. I should have said yes. And that was prior to that 2014 down year that I talked about for me. And so definitely in those moments, I was really looking back and wondering if I made a huge mistake with my life.

32:19Mike Maples, Jr.: Now, you'd said earlier that founders approach you about, hey, should I take this acquisition offer or should I take it seriously? What have you found in those discussions? And, you know, you've probably now seen a bunch of people who did take the offer. What kind of advice would you give to founders when they get inevitably approached along the way for this? First thing, no shame in whatever decision you make. I mean, I think that that's it is, you know, at the end of the day, it definitely is an impactful event. So do what's best for you, but give it some thought. It shouldn't be automatic. It's not there's no free lunch.

32:54You're going to be giving something up by making this decision. And you just have to ask yourself whether it's worth giving up. And I'm a big believer in windows of opportunity. And a good idea at the wrong time is no different from a bad idea. It's just you have to hit both the idea and the correct time in order to make something work. And I really felt we were in that place with infrastructure. And, you know, I challenged founders to do the same thing. Because a lot of founders, the initial reaction is, I'm just going to say yes, work for a few years, and then I'm going to start another thing.

33:24And it's fine. And I'm like, yeah, okay, but you have traction now. Like that other thing might be wrong. You might, one, you might not find it too. Might not be the wrong thing. And then also, you know, on the low end, don't discount how unhappy you might be for those three years, three years, a long time when you're unhappy. So, um, you know, think about it and yeah, I mean, ultimately you make your own decision, but you got to weigh that sort of thing. I think part of what's tricky about it too, is there's no such thing as a compelling company

33:52Mike Maples, Jr.: that somebody won't want to buy someday. Every great outcome had smaller options of smaller outcomes along the way. But I also find that it can be just endlessly distracting. And you get into these conversations and it's not even clear that it's going anywhere or should go anywhere. And it's a terrible way to stay focused on the product and the stuff that really matters to success. Yeah, it's hugely distracting. And then, of course, there's the side effect of you go home at the end of the day and you're thinking about it. It's just like not something you need to be thinking about. We never employed this or anything, but I always suspected or said, you know, big companies should they should engage in these M &A talks more often with bad intents, because it's a great way to just throw your competitors way off kilter for a month.

34:44And if you know you're going to strategically do that, what can you what can you do with that? So I started to get really suspicious about some stuff later on. We were really dismissive of some people that tried to talk to us. And I feel bad in a sense. It was kind of rude. But I got, I don't know, more experience. I mean, there was another one of the big tech companies that approached us at a certain point. Two emails in, I sort of felt like what was happening. And I just responded. This is like bad negotiating. But I was so uninterested in an acquisition by that point. We were doing better. that I just threw out a number and I said, if you're not going to even come close to this number, then let's stop talking right now.

35:21And I never got a response and we never talked ever again. So it worked. I think they were I heard later on that the BD people talking to us were like they thought we were the most arrogant, prickish people of all time. And it was really just like, I'm doing my thing and, you know, I need to stay focused. So I don't know.

35:40Mike Maples, Jr.: So when did you decide that being at HashiCorp kind of wasn't going to be your thing anymore? Like, what did you decide that you wanted to pursue other interests? We had a really explicit conversation about it where we really laid out a timeline. I think it was spring, summer 2022, so about 18 months before I actually left. I didn't bring it up like I want to leave right now. It was more of a, hey, I just want to make sure that we're properly planning for this because I don't plan on being around. I think the number I threw out was I don't plan on being around in three years. And the motivation is that everybody has different phases.

36:18And especially being a founder, you learn a lot about yourself because you have to put on so many hats. So you get to experience so many things. You learn really quickly what you like, what you dislike and when, what size and stuff. And by then, we were heading on, we were about to be public. So it must've been 2021 actually because we weren't public yet. So it was over two years in advance. We were on the path to becoming a public company and already at the scale we were at, I could sort of see things where I didn't have as much joy in what was going on. I think I'm a smaller scale person. And also I like working on directly on the product.

36:58And that wasn't the most beneficial. I wasn't doing that already, but it also wasn't what the company needed at that phase. And I knew it would be more detrimental for me to, to dive right in while I was doing my CTO duties. Um, so yeah, it was a confluence of factors that came in. And so how have you decided what to work on in recent years then? I get a lot of joy out of building technical products, like programming and designing them. And it's just, I would do, you know, I clearly I do it for free. I would do it for free. Um, and, uh, what I decided to work on, I like to just be aware of what's going on.

37:34So step one is just new technology, pick it up, give it a shot, see what happens, build a toy project. And what I found, what happened with Ghosty was that I was going through that pattern and you find something that you're like, Hey, I've worked on it a month. I don't want to stop working on it. I'll work on another month. And then it sort of keeps going. And then it sort of opened up into, there's actually a lot of opportunities here and it's exciting of what might be possible. And I just kept going. And that's just where I am right now. And that was sort of what happened with, with Vagrant way back, it was hyper focused on this double click to get a client's environment.

38:10But that led to me discovering infrastructure and config management, I didn't know what that was before then. And, and then that led to, you know, more interest in in cloud computing and things like that. And, and it just sort of like slowly opened up to the point where it fully opened up. And I was like, this is the best, like, I want to work on this. This is so exciting. And I feel like that's sort of like the path that's happening here.

38:40Mike Maples, Jr.: All right. Well, Mitchell, thanks for taking the time. I think this is going to be good. Good questions that led to hopefully helpful things. It was easy to get through. Thanks for listening to the Pattern Breakers podcast. You can follow me on X at M2JR, and I encourage you to check out our newsletter at patternbreakers.substack.com. I'd love to have you subscribe wherever you get your podcasts so you don't miss an episode. And if you like the show, I'd be grateful if you could leave us a review. Until our paths cross again, I hope you embrace the power of thinking and acting beyond the conventional boundaries.

39:16Mike Maples, Jr.: It's the people who dare to be different who truly make a difference.

39:23Bye

From the publisher

 The most successful founders don't usually chase startup ideas. Instead, they're pulled toward problems they can't ignore. Back in 2009,  Mitchell Hashimoto set out to fix what frustrated him by hacking nights and weekends, open sourcing the tools he wished had existed for over a year. His quiet persistence and commitment to fixing the problem ignited one of the decade's most influential cloud companies: HashiCorp.

In this episode, Mike Maples, Jr. of Floodgate speaks with Hashimoto about those early days, building Vagrant to streamline dev setup, the dawn of HashiCorp, and the tough decisions Hashimoto faced when hiring a CEO and deciding if he should sell the company he built from scratch.  

Check out the Pattern Breakers Blog at patternbreakers.substack.com for
even more Pattern Breaking content from Mike.  

Mike's book Pattern Breakers is available now wherever you buy books.

Follow Mike on X!

More from Pattern Breakers

All episodes