This week's guest is Hahnbee Lee, Co-Founder at Mintlify. Prior to founding Mintlify, Hahnbee co-founded pe•ple and worked as a software engineer at Duolingo. The best developer companies (think Stripe, Twilio, MongoDB) have effective and user-centric documentation at their backbone. Mintlify helps any company achieve the documentation they need effortlessly, so that they can focus on building what they do best. Evil Martians transform growth-stage startups into unicorns, build developer tools, and create open source products. Podcast host is Victoria Melnikova
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
This is Dev Propulsion Labs, the podcast about building successful developer tools hosted by Evil Martians. Hi, this is Dev Propulsion Labs and I'm your host, Victoria Milnikova. I'm very excited to introduce today's guest. Please welcome Hahnbee Lee, co-founder at Mintlify. So maybe we can talk a little bit about the background. Hanbee, do you want to introduce yourself and give us a bit of the context? Who you are and how you got here?
For sure. Hi, everybody. I'm Hanbi. Thanks so much for having me, Victoria. I'm super excited. I kind of just like really jumped into software engineering and really just enjoyed coding. And I also just really enjoy working with other people and like working on problems that aren't just impactful problems that provide value to people. And I would say that like Duolingo also really enforced that into me because it was just such a fun product. And it was like the culture was so great and they would always talk about how we could be providing value to people.
And I think that has like really been ingrained into me. Like I really enjoy working on products where I can really relate to the user. And so I think that's how I kind of really got into startups as well, because you're really on the ground and really trying to talk to your customers. And figure out how you could be providing value to them. Sounds pretty awesome. From Cornell University to Duolingo, the co-founding people now Mintlify. Sounds like quite a journey. How have these roles shaped you?
Maybe you can talk a little bit about each experience and what it gave you. For sure. So I kind of already spoke about Duolingo. I was there when they IPO'd, but when that happened, there were around 300 people. And despite the fact that they were at that stage, it still felt very startup-esque. So still very focused on the user, still very product-oriented and experimental. So I would say I learned a lot from that. And I also really like their culture because it's super diverse and everybody knows another language.
And it's just like the type of work environment that I want for my company as well. As for Cornell, I would say that I learned my computer science fundamentals. And we're surrounded by super, super smart people and super inspirational people. And I would say that I learned a lot from being surrounded by people who are that talented. And it's also where I met my co-founder, Han. Him and I also co-founded People Together, which was a community platform that we launched together.
That was a very cool experience because I would say that he was into startups a lot more than I was. And so I remember we were just really going at it, really coding and trying to figure out this product. And I remember at one point I was like, Hahn, why are we even doing this? And he was like, one day maybe we'll make a company together. And here we are now. So people always say that startup years are like, they feel really short, but you learn a lot in that time period.
And I would definitely say that's true because from working on our previous startup together and our startup now, I definitely feel like I've grown a lot, not only technically, but in business aspects and professional aspects as well. There's just so much to learn and grow. And so with Mintlify now, I'm constantly being challenged to figure out new steps. People also say that startups are kind of like a video game where each stage is just like a different boss,
and you just have to figure out how to defeat that boss. And so I've definitely become a lot more flexible, a lot more open-minded in terms of the problems that we need to solve. And tackle on a day-to-day basis and at a larger scale. Sounds pretty awesome. And also sounds like a very kind of like intense experience, you know, because you have to go through all those stages, as you mentioned, which often feel like bad bosses in games, you know, Dark Souls kind of bosses.
But, you know, it all makes sense in the end. And the reward you get when you pass over certain like hurdles, it makes it all worth it. I also want to share a quick story. So I recently interviewed Monica Sarbu, the co-founder of Xata, and she was at Elastic when they went through IPO. So it's super cool to hear those kind of like parallel stories that happen sometimes in like parallel universes. And she said that it's actually so rare to be at a company when they go through an IPO, especially in the current economic climate.
And I'm so excited to have you both on the season because you both did that, you know, and that's pretty badass. It was super exciting and I was so grateful to be there to experience it. And hopefully one day I get to be at the table ringing the bell as well. Take us to the origins of Mintlify. How did it come about? When Han and I were co-founding People, we quickly realized after launching the product that we did not know much about SMBs
and why they wanted to build a community and what they wanted to do with it. And we quickly realized that we didn't empathize with the end user as much as we wanted to. And so the next time that we got together to build a product, we knew we wanted to build developer tools because Han and I are both technical. And so we like at the very fundamentally, we could very much relate to developers. And so Mintlify originally started out with being a documentation generation platform where basically you select code and then it generates a docstring on top of it.
And we came up with this because like we as developers did not like writing documentation. And so we just thought, oh, like this is we think this could be useful. And that was proven correct because a lot of people still use this product up to this day. But we also quickly realized that individual developers have a very low willingness to pay. And so we decided to kind of move away from that product. But we are really thankful about DocWriter because it introduced us to the idea space of documentation.
And we also got into YC with the idea. And when we were in YC, we started talking to other founders about documentation. And they kept on telling us that public facing documentation is not solved. And for the longest time, we ignored that. We're like, oh, we're not doing public facing documentation. Like, we already know that other competitors already exist in this space. But then one day we just tried doing it and we've kind of been running with it since.
So there's a clear need for it. I think that the market was in the need of disruption. And a lot of our customers right now are our fellow friends in our YC batch and YC in general. And we're continuously building and trying to advance with them. Yeah. I mean, Y Combinator is one of those accelerators that put startups on the map. And it's a challenge to get in. But I think it's very rewarding in the end.
So can you share a little bit more about your experience at YC? When we applied, we were still students at the time, actually. And we told each other that we would drop out if we got in. And so I would definitely say that out of our entire startup journey, I feel like getting into YC was definitely one of the most pivotal, foundational moments of it. It definitely validated a lot of the work that we were doing up until then, where it kind of felt like we were really in the shadows trying to just do whatever we can
and just figuring it out without a lot of mentorship. And so it was super gratifying and super validating to get that acceptance. It was an amazing, amazing experience. We participated in the Winter 2022 batch. And this was the last remote batch, although we did fly to SF then just to see some other people and just experience San Francisco. Truly just having the group partners there to be a sounding board, to tell them, hey, we're thinking of doing this,
and then them telling you whether they think that's a good or bad idea, it's so much guidance. There's no right or wrong answer when you're working on startups, but just knowing that they have so many data points and they've obviously all been successful founders themselves, it's just super invaluable. And I would also say that despite the fact that we were the last remote batch, we also met a ton of other people. And it's very rare that you find other founders that are at the exact same spot that you are at.
And up until this day, we still catch up every now and then with our fellow batch mates. And it's really nice that we all obviously have different journeys, but just catching up and it's super motivating to be surrounded by like-minded people. Like-minded, but also completely different and completely diverse in terms of what they're working on, and everyone is just changing the world in a different way. So I highly recommend YC to anybody who's considering applying. Yeah, and also they have some free resources available.
I mean, we can start with Paul Graham's essays, and we can finish with the YC Startup School videos that are really highly educational. And you can go onto YouTube, check YC videos, and it's just packed with great useful information. We work with different founders, and we noticed that especially engineers, founders with the background in engineering, they often get carried away with building that technology, you know. But the business aspect of it is really important.
And sometimes you need guidance to kind of like understand what your next step is. And basic concepts like talking to your users and moving fast, you know, some of those things that YC really teaches you to do. 100%. It's also nice to have the YC badge next to your name. It's just like a nice thing to have. All right, let's focus on Mintlify for a second. So Developer Tools is one of those industries that has specific go-to-market technologies.
And actually documentation is extremely important for Developer Tools because it's one of those, it's kind of like the screen through which the startup communicates with their users. It's their first kind of like engagement with their users, right? And GitHub did the survey in 2017, pointing out that there is a huge problem with documentation. It's not easy to navigate. It's overbearing. There's a lot of things going on. And it's also, if you ask any developer how much time it takes to write documentation, it takes a ton of time.
So it's extremely time consuming as well. How do you think the scene has changed since 2017? And what is Mintlify doing about those old challenges and the new challenges? I like to think that we're making documentation more sexy. Like people are paying more attention to documentation. And like you said, it is like a super important part of a Developer Tool company's products, especially if you're an API company. At that point, the documentation is the product because it's really the one part that your users are really interacting with.
In order to use your API. One of the things that we like to say about Mintlify is that it's infinitely flexible when you need it to, to customize it. But it's also opinionated so that you can get your docs up and running as quickly as you can, but also still match your branding and still be up to par with the rest of your product. And so we're super developer centric. Our product essentially connects to your GitHub and uses markdown files that live inside a GitHub repo.
And it automatically syncs with the website, automatically syncs with your GitHub repo with the content. And so it's super convenient for developers to use and maintain. And we're also big on developers maintaining the documentation as since it's for a technical audience. And we think that developers are like know the products are very close to it. And I think it's important that developers can easily access and maintain it. Yeah. Empathy is huge, honestly, especially in developer tool space.
You know, developer experience is something that is changing, disrupting the industry. Can you tell us about lending your first Mintlify users? So you mentioned how YC is kind of like a cheat code in that sense, because you get exposed to so many startups that are in the same batch. So you guys are kind of like comrades, so to say, right? So you're kind of like willing to test out each other's products. Can you share more about getting those first users? How did it happen? What do you guys do to get those first users, whether paying or not?
Yeah, I know the early days was super interesting because since we're both technical founders, we've had the mentality of like, if we have an idea, then we want to MVP it as quickly as possible and then throw it out there. And so the first version of Mintlify was basically just like a static website that we maintained. Our first customer, like they couldn't even edit the docs themselves. Like we manually migrated their content and then we're like, hey, like, would you pay for this website? And then like, surprisingly, they said yes.
So that was like the first version of Mintlify. And since then, we've obviously added like the automation so that like you can sync it with GitHub. Obviously, edit the docs yourself. But the first few customers were a lot of the people we were closest with during YC. Thankfully, yeah, like you said, they were nice enough to like test our product from the early days and use it. So that was super interesting time. A lot of manual work, like just doing things that don't scale of like copying over content from their existing documentation to like,
hey, like, please, like, just check this out. And like, if you like it, like, feel free to use that kind of thing. Awesome. So documentation revolves around users. It's very important to take user feedback and apply it. How do you leverage feedback on documentation or in general user feedback to drive your product forward? Yeah, yeah. Recently for our customers themselves, like since they're also companies that should be listening to their customers,
we recently launched a feature where you can the user can like give like a thumbs up or thumbs down on the documentation page. And then through our dashboard, you can see which pages that the users like and dislike. So that you can move from there for ourselves. I think like everyone always says, like, like, we probably don't talk to our customers enough, but like we have a community that we maintain and always try to prioritize and make sure that our current customers are happy while we're iterating on the product.
Like, this is a good reminder that I should be scheduling more calls on their users to continuously like have that feedback loop into moving our product forward. So Mintlify journey or to be honest, any startup's journey is not linear, right? Ideas change based on what you're hearing from your users, things you kind of adapt your product to meet, you know, to get the market fit. Can you tell us about the pivots that Mintlify went through? How did you shape them? How did you find? What's the next step for you?
Yeah, for sure. So I also kind of briefly touched upon this before. But like I said, we were working on a more B2D product directly to the developer before we started working on the B2B product that we're working on now. Since then, we've also had like we had a couple pivots before that product, a couple pivots in between. But just a lot of iteration, a lot of just not being afraid to throw something out there and put it out into the world just to get that reception.
We also have like the mindset that everything is like kind of a hypothesis until you get the market reaction out there. If somebody believes in an idea more than the other, then we like we still support each other. And we're like, OK, like, let's let's admit that we don't know, like, how the market's going to react to this. Like, let's just see what's going to happen after we throw it out there. And so like, we've definitely been through a lot of pivots. And I know like the age old question is like, oh, like, how do you know if you're pivoting too much or not enough or like too early or too slow?
And like, obviously, we'll never know the answer to that. And it's different per person. But we're of the opinion that like people or I think most people are of the opinion that people don't pivot fast enough because they're a little bit too attached to their product. But I actually remember one of our first office hours with YC, like we were contemplating going through a pivot because we applied with another idea, but it wasn't really working out. And then we had the Docker idea and we asked them what we should do.
Like, we're thinking of pivoting. We're not sure. And then I remember their advice was like, don't be too attached to the product. And that has stuck with me really for it has really stuck with me because I feel like the the media perception of startups is kind of like Facebook, where it's like, oh, like, they just launched this product and it worked. It just blew up. And like, everybody loved it. But that's like so far away from reality. Like, it requires so much like just throwing things at the board and just a bunch of different like tries until you get it to work. And the product is just like a means to get to the customer.
Like, you're really just trying to provide value in some way, shape or form. It doesn't even have to be software. You're just trying to provide value. And so like being attached to the code or like the physical product is like really does you more harm than good in the long run. So that's still my mindset now that like we're just trying to provide value to the customer. I think that's going to be the insight that I take away from this conversation. Just that alone is something that I think a lot of founders need to adapt to adopt in their mentality because it is a mentality shift.
You know, you have to kind of like go to the next level of abstraction and think about it differently, which is hard to do. You know, especially when you spend so much time on the technology and you kind of like did so much work to make it happen. You know, so it's kind of counterintuitive, but it actually, you know, what makes startups successful at the end of the day. Like even big guys like Airbnb, originally they were a different idea that pivoted, pivoted, pivoted and became something else, you know.
So with Mintify going big on the premium front, what should we expect next? What do you have in store? We have been super focused on developers, but we also want to kind of expand our audience. And so we are currently working on a web based editor so that non-technical parts of the team, such as designers or product managers can also edit the documentation and be closer to it because the more up to date or more people have the ability to do that, the better it is.
Because I would say stale and incorrect documentation is worse than no documentation at all. So we're super excited for that. We're actually hoping on launching that next week. So fingers crossed that we that happens. Looking even further on, I could really see us, you know, going towards just being like a developer communication platform where right now we're really focused on documentation. But, you know, there are other ways in which like you have to communicate with developers, such as like through change logs or status pages or, you know, even like a public facing roadmap.
And so I'm super excited to kind of like expand our like feature set and hopefully go into more areas like that to help that communication happen between companies and their end users. Sounds ambitious and I like it. Good luck with that. Thank you. How is Mintlify engaging with open source communities? Do you have any cool collaborations, you know, in your back pocket?
Yeah. So if any open source companies are watching this, we offer like a deal for specifically open source companies. So like they could reach out to us and we can help set up documentation for them. We love the open source community and we I obviously have benefited from it like myself. Like there's just so many cool things on GitHub. And so we're, you know, hoping to open source more of our code base as well. You know, open source our components or like our parser in the future so that other people can take advantage of that and use it in their code base if they would like to.
Yeah, we've like a big fan of open source and just want to continue to, you know, support the community and give back as much as I can and, you know, work with anybody who needs documentation and we can just provide it for them. And it's it's I would say that our product is also super convenient for open source companies because of the fact that the documentation lives in the code base. It's super easy for their users to also go in and make a suggestion because like everybody's technical knows how to use GitHub in the open source community.
And so that's definitely a way in which our product is designed to be in favor of open source companies. Sounds pretty cool. I mean, for us at Evil Martians, we kind of invest a lot of time and resources into open source and some famous open source frameworks are done by Evil Martians created by Evil Martians like post CSS and nano ID some pretty big open source projects. So I can definitely see how, you know, open source community, especially early stage ones could benefit from something like that for sure.
Documentation is one of those things that's kind of like the lifeline for developers. It's extremely important. Do you have any gold nuggets of advice for techies who are trying to solve similar type problems, similar to what you're doing with Mintify? Yeah, for sure. So I obviously spend a lot of my time thinking about documentation. And one of the things that I'd have to say, like, I would say documentation itself is a very hard problem because like people don't want to write it.
And fundamentally, I wouldn't say that there is like a one size fits all solution to having great documentation. But I think one core thing that I learned about it is that like, we're going to try to fix as many problems as we can. But some parts of it are fundamentally cultural, and that like, I think a lot of the reasons why Stripe has amazing documentation is not only because of like the resources that they devote to it, but also because of like the strong writing culture that they have
instilled in their company. And that's not something that you can just fix with a product. And so I think that's like something that's super important to be aware of fundamentally, because I know that there are a lot of other companies that try to fix documentation, specifically like, oh, like, how do I prevent documentation from going stale? Or how do I, you know, even like, like, MitlaFi right now is focused on public facing documentation. But for internal documentation within a company, like, how do you make sure that
everything is centralized, like discoverable, stays up to date, and no one disagrees that that isn't a problem. But also, I wouldn't say that there is like, that I could just sit here and conjure up a product that could fundamentally solve that, like instantly. And so I think like, that's kind of why we're working on like, what MitlaFi is working on now, which is like public facing documentation specifically, because, you know, like, we think that this is like a good problem space that we can focus on and it's ripe for
like problems to be fixed that we can fix, and also grow from there and then hopefully, you know, go into the larger cultural problems like here and there, but like, we're starting at like a lot of a smaller problem space than the vast one that exists. So I would say my, my advice is to kind of be aware of that. Like, I think fundamentally, you can try, you can try to fix like these larger problems like we have like we've, we've gone through it and like, you know, I guess you wouldn't know for sure whether you can fix it or not without trying. So I wouldn't discourage you from trying, but also like, just to be aware of the fact that like, it's not just a product that can solve these problems at times.
So would you advise, be start with the smaller problem, like a specific problem that you're solving and then try to approach the bigger fundamental issue and just, you know, kind of you have to make peace with the fact that it is possible that your product would not be solving the big issue. Yeah, to some extent, because like, I think you also have to balance the fact that you have to be realistic with what you're capable of doing, you know, with the whole other mindset that I was talking about of us iterating and MVP quickly.
Like, I think you have to be realistic about which problems you can solve in the time that you have. And so with those two constraints, I think that the best way to even inch towards thinking about those larger problems is to start smaller and grow towards them. That sounds fantastic. Your journey as a female founder of color in tech is truly inspiring, especially in the developer tool space. It's pretty rare, as I mentioned, to come across female founders.
And I'm sure for many people, it will open up doors because sometimes it's enough for us to see just one role model that's going through it, you know, to realize that that's even possible. Can you maybe share some words of encouragement to others from diverse backgrounds looking to venture into tech or startups or developer tools specifically? Yeah, for sure. I love this question. It's definitely been quite an experience. Like, it's definitely super male dominated. And as you said, in DevTools specifically, I would say that like, there are definitely not as many female founders.
But my words of encouragement, like you got to kind of just throw yourself out there and do it. You can't be scared. I think that, you know, people underestimate us. But like, there's nothing that sets me different from other people who are doing the same thing that I am. And so I will admit at times it is hard, like, you know, being like walking into a room and it's like, I'm the only woman there. And but it's encouraging to me to know that I'm setting a precedent and I'm hoping that like you said, more people will be willing to, you know, go into these positions and like, you know, believe that they can do this themselves because other people are doing it as well.
And so it's super fun. And it's what I enjoy doing. And so like, if there's other people out there that are scared of doing it, but just want to go for it, like, I also highly encourage people to reach out to me if they want advice or any sort of mentorship in this aspect, because I obviously want more diversity and more more people, more women, more people of color in this space. That's very sweet of you. Thank you. I'd like to end the episode with what I call a warm fuzzy. It's sharing something that makes you feel great about what you're doing at the moment. Can you share your warm fuzzy with us?
For me, I would say that what I love about what I'm doing is purely just like the people that I work with and the people that like, and our customers, like, I love that. I love it when people like tell us that our product is working well and they enjoy it and like have that sort of validation where like, oh, like, we are providing value. And so that's definitely what keeps me going. Sounds awesome. Last but not least, can you give our audience a call to action, whether it's to test Mildify for themselves or something else?
Yeah, for sure. Yeah, check out Mildify at Mildify.com if you need documentation for your product. Sign up, join our community and I'll be more than willing to help people get set up and yeah. Thank you. This was awesome. Thank you for this episode. Thank you so much. For sure. Thank you, Victoria. Thank you for catching yet another episode of Dev Propulsion Labs. We at Evil Martians transform growth stage startups into unicorns, build developer tools, and create open source products.
If your developer tool needs help with product design, development, or SRE, visit EvilMartians.com/DevTools. See you in the next.
William Imoh, founder and CEO of Hackmamba (https://hackmamba.io/), sits down with Victoria Melnikova to talk about why AI search optimization is mostly just good SEO that has had time to compound, how developer-facing...
Kate Holterhoff, senior analyst at RedMonk (https://redmonk.com/), sits down with Victoria Melnikova to talk about what AI is doing to open source, developer tools, and the analyst business itself. She also shares her...
Matt Biilmann, CEO and co-founder of Netlify (https://www.netlify.com/), sits down with Victoria Melnikova to talk about why agent experience (AX) is replacing developer experience in developer tools. He also shares how...
Max Prilutskiy, CEO and co-founder of Lingo.dev, sits down with Victoria Melnikova to talk about why localization is still far from a solved problem in the age of AI, how a six-person team ships 56 pull requests a week,...
Amir Rustamzadeh, partner at Firestreak Ventures, sits down with Victoria Melnikova to talk about how to spot a force-of-nature founder before anyone else does, why most developer tool ideas are no longer venture scale,...