a16z Podcast - How Mintlify Is Rebuilding Documentation for Coding Agents

Episode Date: January 23, 2026

Mintlify is a documentation platform built by cofounders Han Wang and Hahnbee Lee to help teams create and maintain developer docs. In this episode, Andreessen Horowitz general partners Jennifer Li and Yoko Li speak with Han and Hahnbee about how coding agents are changing what “good docs” mean, shifting documentation from a human-only resource into infrastructure that powers AI tools, support agents, and internal knowledge workflows. They share Mintlify’s early journey, including eight pivots, the two-day prototype that landed their first customer, and the “do things that don’t scale” sales motion that helped them win early traction. The conversation also covers why docs go out of date, what “self-healing” documentation requires to actually work, and how serving fast-moving customers has shaped both their product priorities and their pace.Follow Jennifer Li on X: https://twitter.com/JenniferHliFollow Yoko Li on X: https://twitter.com/stuffyokodrawsFollow Han Wang on X: https://twitter.com/handotdevFollow Hahnbee Lee on X: https://twitter.com/hahnbeelee Stay Updated:Find a16z on XFind a16z on LinkedInListen to the a16z Show on SpotifyListen to the a16z Show on Apple PodcastsFollow our host: https://twitter.com/eriktorenberg Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Hey guys, here's your docs that are way better now on middle. Take a look. And that's when I realized the beauty of having failed so many times, which was in failing so many times and building so many ideas that didn't work, when something did, there was no mistaking it. It's very important to solve one problem correctly. And even right now, as we're experimenting and launching new products, We're hyper-focused on getting one person who loves what we're building as opposed to a thousand people who are going to just feel meh about it.

Still the small things that don't scale that really spark the customer love and the thing that goes the extra mile, if you will, is how we think about things, right? If you go the extra mile that in a way that people don't expect, you know, imagine. For most of the Internet's history, documentation has been an afterthought. Something you write after the product ships, something meant to explain. where already exists. But what happens when the reader isn't human anymore? For decades, docs were written for people. They explained APIs, answered questions, and slowly drifted out of date as products evolved.

That decay was accepted as normal because documentation was treated as reference material, not infrastructure. In the last few years, that assumption has broken. Coding agents support bots and internal AI tools now read documentation directly. Docs are no longer just explanatory, but also operational input. When the wrong or outdated, systems break. This creates attention. Documentation matters more than ever, but keeping it accurate has always been one of the hardest problems in software.

Static docs don't survive fast-moving products, especially in an agent-driven world. In this episode, we explained how documentation is changing, why static docs are failing, and what it would take to build documentation that stays reliable as software evolves. Our guests are Han Wang and Han B. Lee, co-founders of Mittlify, joined by A16Z general partner Jennifer Lee and A16Z partner, Yoko Lee. I'll start the podcast with this question, given you're at the front center of seeing how agent has impacted coding because you're building a documentation product that's serving all the developer tools, the most popular ones. How have you seen the transition from the starting point of building Manlify to what a role of a coding agent plays now?

I mean, it's so different now, right? I think, and it speaks a lot to even how much has changed in such a short amount of time, right? I remember when Hanbi and I, you know, decided we kind of wanted to embark the jury. of wanting to go build something that helps developers, right? The first thing that came to our mind, this was like to paint the picture, like early 24, late 23, early 24. We were just like, let's go build something that could impact developers, help their journey as kind of like the impetus for why we want to start the company. And then landed on building like just better developer docs because we were like, let's go solve problems that, you know, like we can relate to,

right? And as people who've been building our entire lives and careers were like, we know that there's so many bad dogs out there. There's an audience we can relate to. It's a problem that we deeply understand and care about. Let's just go build that. And then, obviously, what changed from then till now was this tsunami of changing developer expectations, changing the way people build entirely.

So what initially started was just like a very simple platform for people to build, right, maintain better docs, read for other humans, start to transition to being something for humans and AI. And what eventually now it went from being an application to, it really feels like an infrastructure product. It's content that powers AI. It's content that trains support agents, coding agents, you name it. And I think kind of witnessing that change firsthand is not only a testament to how much the world has changed, but being front and center of it and having a role in something that, you know, we find particularly meaningful.

Obviously, nowadays, you know, like even before we invested, we see METlify all the time. Like every company we meet in the very early stage to enterprises, everyone is centralized on MNify. Was it always obvious to you? What's the, if you look back, what's a story that led up to this point? Yeah, yeah. A lot of, a lot of pivots and a lot of failure along the way. And by the way, you know, my opinion, too many people use us. You know, we need more varying.

in the world. That's what I think. More themes. Exactly. More customization. The honest answer, and I kind of want to speak on that is the fact that it wasn't the first thing that

Hanbi and I came up with, right? In spite of how much we see and how obvious the problem is in hindsight. It's a eight times, right? And this is the eighth time? Yeah. Oh my goodness. So essentially the story of all the pivots and it goes

For me and Hanbi, we started the company because we really know we wanted to build for builders. I was very fortunate to like started coding when I was very young, initially 11 years old. I was given a laptop like a MacBook Pro back in the 2010-2011 edition. And I found the joys of learning how to build products for people around me, community, my school, my friends, you name it. And that entire journey was self-taught like many other people who are very prominent builders. you know, in the ecosystem, I had to learn so much by myself. I had to go figure out through YouTube videos, a lot of bad docs, right? No Claude code, unfortunately. I wish that would have been great. It's going to help me figure out all the space. And then therefore, when we start

the company, we're like, that's just a thing that we can relate to so deeply. And because we know that building a company takes such a long time horizon, right? It's like the span of decades, if you want to build anything meaningful, you have to go pick a space that you can care so deeply about. For me and hobby, it's other people, other builders like us. And so that was the start of the journey, right? It wasn't all about docs at first. It was just like, how do we go build something

that can enable people to build a little bit better, a little bit faster because then they can go and impact people. And so then, you know, we started the journey and spent about a solid year and a half of wandering in the desert while chewing, glass. It's probably the best way I can describe that. What did you run into in the desert?

A lot of bad ideas. Too many to list and too bad to pitch at this point. But I think it was just a lot of things where, you know, we say like it was eight pivots, but, you know, truly it really didn't feel like that because all of it was really surrounded with kind of the same kind of like idea space, if you will. Right. It was always something for developers. It was always something about building for helping enable someone to go learn.

and build something faster. And so one idea after next, it went from something like, oh, using AI to auto just describe what your code does to something like, hey, could you just connect static content to the code? And then that was a bad idea, by the way. I don't know if anyone is doing that, don't. But then it eventually led us to where we are today,

which, again, in hindsight is the most obvious thing, right? Oh, duh. Should have built the docs platform. but at the time it was just about developers. And to this day and into the future, it still is. It's about enabling other people. And now we're growing beyond just developers into learning and building a little bit faster.

And I'm sure when you first launched MnlyFi, this current version of the product, there was a lot more mature products out there and more fully fledged, like feature-rich products versus how MNMefi came out back then. Like, how did you approach customers in the way that converted the first customer or the second or the third or some memorable stories around that time? Oh, man. Well, for starters, you know, the funny thing is the reason it took so long for us to even get to the idea that we're doing now is because we actually internalized that same opinion, which was, oh, there were so many of these incumbents, these existing companies that did it. There was a solution here, a solution that, oh, you could probably go build these things in-house. We just bought into that, right?

And at one point and throughout the journey of these many pivots, we kept talking to people, talking to users. And they kept saying, oh, well, while these other options existed on the market, I didn't find the right one for me. And here's why this is not great. And in fact, we kept hearing that again and again and just kept pushing that down because we're like, oh, no, it's actually great. There's the market's already there and yada. And as we kind of start dugging into the user feedback and we start thinking about our own experiences, we're like, my goodness, like,

I've tried building this so many times. Here's why all of these things were bad. So if we're going to do it right, let's at least do the one that we wish we would have wanted. As developers, because we believe that's, you know, who we want to build for. Let's just go figure out what we would have liked. And so the initial version of what Mintlify is

Today actually came out just from one weekend. It was two days. We were like, because at the time, we were like, all right, well, we just got to try everything and we'll just give it the amount of time we kind of have confidence in this idea for two days. That's all we got. And so we forced ourselves to build, like,

this very initial version of it. And then the next thing I knew, like we built out this like prototype and we just want to get validation. So at the time, my roommate who was going through the YC batch, you know, were building and pivoting into the API space, this company called Hyperbean. They were going from a consumer product to building an API product.

So we went to them and were like, hey, guys, here's your docs that are way better now on Midlify. Take a look. And that's when I realized the beauty of having failed so many times, which was in failing so many times and building so many ideas that didn't work, when something did, there was no mistaking it. And so there's a lot of grace and failure, in my opinion,

which is that like you learn a lot of perspective on things that don't work and the reaction customers get when they don't work. So in our case, it was many, you know, a year and a half of people who are like, oh, let's talk again next week. Let's, you know, you send them an invoice, they're not paying it. You send them a credit. Oh, we don't have budgets. It's 20 bucks, you know, to then the reaction.

Yeah. Exactly. To then the reaction of like, how do we get the setup right now? Like, I was like, okay, do you want to find time tomorrow to chat? No, like how do it right now? And then you send them like an invoice and they're like, they're done like in a minute. Right. And then for HyperBem and particular, they were like, let's get going. I was like, bet. I'll set up for you right now. Give me access to your cloud for DNS configurations. I literally went and changed it over. And that was our first customer. And that first customer led us to the second and the fifth. the 10th, 100th, and now into the thousands.

That's a great story. And that's still one of your current sales motion is to pre-built the dock and share it with the customer to see what the docs will look like in Milify, which is very powerful. Yeah. It's one of those things where I remember, like, maybe we were nearing like the first 100 customers. And, you know, Hanbi and I were still doing the painstaking job of like manually migrating everybody. And back by the way, back then, like before any of the bells and whistle,

for why someone should use us. You know, one of the reasons ways we got people to give us a try was like, hey, by the way, if you switch to Minlify, we'll actually go in and like actually help review your docs, we'll fix your grammar and we'll actually structure in a better way. It's a lot of like do things that don't scale. And we were doing that for a while. And I remember at one point, we had a like an office hour, if you will, with Paul Graham. The founder of founders.

Yes, founder of founders, the YC guy. And we were so many of my grades. Like, how do you, like, do this? I'm sure at one point, when you scale it out, you get to go do something a little bit different and a little bit better. He's like, no. This thing that you're doing now is going to be the thing that you're going to do forever. Just live with it. I was like, okay.

And then we hire a team and then build tooling. And then, you know, obviously, it's, you know, AI has helped a lot in that journey too. But, yeah, it's still the small things that don't scale that really spark kind of like the customer love and the thing that goes the extra mile, if you will, is how we think about things, right? If you go the extra mile that in a way that people don't expect, you know, imagine. I'd love to maybe just point out a few of those going extra mile pieces because I would love to dive into more of the product intuition and also the products you have built so far

because that's been an incredible journey, even in the short sort of lifespan of Miltify, they were just like non-stop shipping. And with sort of AI's change of how developers coding and how they're leveraging documentation. Like you have came up with a lot of really great ideas from self-healing dogs to sort of how to bring dogs into context for agents to leverage.

So I would love to sort of unpack that in the next few questions. And maybe we can start from where you start seeing these sort of areas that you can go further from the existing providers and how has AI impacted your thinking of building those functionalities. Yeah. Well, if I were to touch on some of the previous, like, topics as well, like, I feel like a lot of what kind of goes into our product intuition and how we build is, like, living and breathing, like, the mantra of talk to your users. And so, and also learning from our failures and being very data oriented and being very pragmatic and MVPing things very quickly. That was kind of a lot more than I was expecting to say. But I think that that kind of really encompasses a lot of just how. how we approach product and strategy in general. And I think a lot of people who start from an idea that they have are starting pragmatic enough.

And it's very important to solve one problem correctly. And even right now, as we're experimenting and launching new products, we're hyper-focused on getting one person who loves what we're building as opposed to a thousand people who are going to just feel me about it. And so we're, yeah, we're super focused on that. And then as for the future of the product and to touch on what Helen was saying about how AI has been impacting our product, like the future that we envisioned a year ago is here. You know, AI agents are the ones ingesting the content.

And like I'm constantly talking to founders who are talking to me about how like the documentation is the source of truth for making sure that their agents are working properly. And so this up-to-date documentation has all. always been important for developers, marketers, customer support. Everybody within the org views it as like a source of truth. And now there's an outsized amount of AI agents who are also relying on it. And so it's even more important now. And now AI is also here to help us solve that problem, where humans like natural inclination is not to update the docs. You know, your shipping code and you want to say it's done when you're done when you've shipped the last PR. but in reality, you need to, now it's even more important to update the docs.

And so with this increased importance, we're building tools to make the context stay up to date as well. Yeah. And in a different way of VC terminology, like your time expanded so dramatically, not just because on the supply side, you have a lot more to serve of people who are building tools and people who are, you know, building dev tools, agent tools. but on your demand side, you have this new persona that are not just developers, but also coding agents. So the demand of docs and great documentation, accurate ones, up-to-date ones, is getting much, much higher. Oh, I was going to say, and the vibe coders, too. That's right.

The whole new genre of developers are coming up, people who are so enthusiastic to build software. It's awesome. Yeah. And you guys are at such a vantage point of Silicon Valley. just because every single new AI company or established AI company, you know, use Milify today. So I guess like from all the things you are seeing on the market with the customers, what surprised you? What are the things that people are now using with Minlify and the AI models that I couldn't have done before?

Ooh. With Mintlify, there was a lot. But that hails in comparison to the number of people who are building things that are cooler that beyond, you know, our imagination. I was literally, you know, this is a little embarrassing to admit, got my driver's license, like, not that many years ago. I was literally two years ago even as an example. They started driving. No, literally.

And then I started driving nonstop. Maybe you don't need to drive. Just use Waymo. That's right. Exactly. Or the robo taxi. I was like literally preparing for the driver's test. And I came across like this document that was like, here's how you prepare for the written exams.

and it was on Minlify. And I was like, I would never in a million years have imagined that this is like a place I would just come across. And to your point, like in a lot more places than I can even imagine. And this is kind of like a common misconception I think people even have about Milify today, which is that, you know, they're like, oh, it's Milify. They're the docs company. And while it's not incorrect, of course, right?

It's, of course, what we do. 25 has been a big year for us because it also dramatically expanded the surface area of what we actually cover. So there's a lot more help centers on Minlify today. There's a lot of internal docs. In fact, actually, we recently replaced our entire internal knowledge stack

with just Minnify as well, largely because of the automated AI tooling, the Q&A bots. Everything just asks a question on Slack. You tell us to go update things on Slack, right? You give a natural command and it just evolves over time is something that I've been personally

getting so much use out of that I, and for many other companies that we work with, you'd be surprised by, they do use us for a public docs instance, and that's kind of obviously the thing we can showcase. But deep down, they have two sets of internal docs that we now work with, for maybe their engineering team, for maybe even their HR team, who's talking about, like, their health care policies. And I think as we grow, it's going to evolve from not just quote-unquote docs, but like more knowledge management more broadly. And I think kind of seeing that shift in 25 and hopefully more into 26 as well is something that we're very excited about.

And why do you think the customers are using Mnified that way? Because, you know, the original and the most prominent branding is you have this very well designed external facing dots. But the internal workflow could be pretty different. There may be more options of using notion or confluent. Like, why did people, even outside of the developers, are choosing Mnlyify for these use cases? Yeah, that's a really good question. So there's a lot of different things about this. The first and foremost is that you have to actually go build for, you know, obviously a great editing experience beyond just the developers, right? So when Hanbi and I started, we took the opinion that it should just be developers,

and so we really optimized for that flow. But of course, as we kind of grow in more use cases, larger companies, when you're talking like Fortune 10s, you know, they're not just all developers. There's a lot of stakeholders. And so you try to build a better editing experience. So there's a point about product and features in their side. But the larger one that actually I think has been shifting in this is that a lot more of the world is also on the other side getting more technical.

To Hamby's point earlier, a lot more people who are vibe coding now. A lot more people who can understand markdown now because it's a language about LEMs. So the syntax that might be somewhat foreign for most people is now commonplace. A lot more people outside of just developers are using cloud code and these tooling, like the cursors, to go ahead and do creative work, writing blogs. I remember Yoko you mentioned you wrote a blog, right, using it as well. And all of that's done in like this developery way. And so especially now where AI agents are also powering so many different workflows,

the engineers themselves too get also very involved in the process. So back then, if you want to go sell a support product, right, you're selling to the support teams. If you want to sell helps and it's selling to the support teams. But now if you're basically like the support strategy is like 80% of the tickets are built and managed by AI agents, the engineering team gets involved. Right? And so then they have a say in terms of how you want to go build a platform. How do you want to maintain it?

And so there's kind of the early bet that we took, which is being four developers, also kind of became this tailwind for us, as we saw. I wish it was more intentional than it was. It's my honest answer to. I guess what was it like building it? We had this async discussion on Slack just very recently. There's just so many net new things that you can ship into the product. like when the coding models are getting better.

So for example, workflow automation, self-updating docs, like the extra things that non-developers or like newly technical users can now do, Manlify, how did you all wrap your head around all these new trends in AI? How did you build it? Still trying to, honestly. I wish I had a better answer for that. I think this is going to, you know, what Hanvi mentioned, the pragmatic side about all this, right?

which is on one hand, we can sit here and talk about the theory of all, right? The general macro trends that enable products like this. Whereas, you know, from the, you know, the battle scars that me and Hanbi had, you know, and this is going back into the pivot days, is we also learn that it's so important to figure out how to bring that to the actual problem that people care about, right? Yes, self-updating docs. Very great thing to have, right? It's been asked for about 25 years now.

And now there are a bunch of reasons why it can and should exist. But at the same time, there's about a thousand product decisions that need to be made from now until then. What is the actual way people do that? What is the actual experience of how those updates should happen? What sources should they connect? How are those connected? What is the actual flow of it all? Those are the things that you still have to get right.

And so tying it back to it all, there's, of course, this big element that we want to pursue. But then it's going to come down to the day and the day. and day out, the users and the problems they face and how they would like to see it. And that's kind of like this kind of, the messy middle, if you will, of frogs. Yeah, I feel like there's a lot of buzz going around in AI nowadays. And, you know, like, even like people are scared because it's moving so quickly and they don't know what's going to come next and like AGI, like, Dumesday, like sci-fi-esque scares going on. But the way that Hauna and I view it is that it's, AI is really just another tool in the tool.

toolbox. And it's just so powerful and useful and valuable. And we're just, we just now have this extra tool in the toolbox and we should feel very open and embrace it in terms of utilizing it to help others and provide value for others. And I feel like we could abstract a way, don't think about all the scary media around it and just view it as a helpful tool to help us get to point A to B, to help people understand products better, to help learn how to code faster. All of these, that's what AI is here for. Yeah.

I kind of agree more with that. I think there's certainly a lot of things that coding agents and AI has surprised us of what its capability, but at the same time, there's still the limitations that we need great tooling to work around it with. And that's why contact and documentation is so important

to continue to feed the right pieces into context and for the agents to perform. And that also goes to sort of the maintenance piece, how you mentioned earlier. It's always been the case where authoring is like a big chunk of documentation. It's an important part, but it's sort of one time. But the maintenance side of maintaining dogs and keeping it fresh has been the biggest burden for organizations to make decisions on if this is the right

version, this is right version, what's the source of truth, what's the UI that's actually showing in the product today? And is it the right one showing the dogs? There's just a lot of thousand paper cuts that's making it so time-consuming and cumbersome, where now we can probably have a really capable assistant to help us do that a lot easier. And I think that's sort of with your self-haling dogs you're trying to solve now. And maybe not just for dogs, but for a lot of knowledge work overall. So I'm curious and want to hear about what are some of the, I guess, bigger chunks of content you want to go into,

also how you're solving that problem to. reconciliate and come back to the source of truth, that kind of decisions you're trying to make now. Yeah, absolutely. Well, I first want to unpack that by breaking down, I think, a few different elements. The first and foremost is like why quote-unquote docs, you know, have been historically out of date and difficult manage. And make no mistake, this is a problem that I'm sure everyone who is listening or understands this. This is something everyone feels. No one ever feels good and has gone in bed and be like, oh, I have great docs. if they think about it all, let's say. It's like your closet that you're always like every season,

can I have to do it? Yeah, it's like you just throw some skeletons in there and then you don't look at it. And I think there's a few different reasons for that. Remember first and foremost is like there's a lot of organizational dynamics or team dynamics that prevents that from being the case. Like I even break it down from an example of a software company, right? Like the people who somehow have the most context for how things work, let's say you're documenting a product or specific features.

features or infrastructure, you name it, are people who probably wrote it themselves, which are often the engineers, the people who are not often themselves maintaining the docs or content in general. They're the ones who have most context, most know-how on how to go and write the docs. They're not the ones who want to or incentivized to, and they're not the ones who are paid to. Now, I have to be the one responsible for writing. Well, that's just not my job, right? And at the same time, it's like there's an aspect of organizational dynamics and an aspect of human nature and part of this too. People just don't really want to. It seems like a weird judge of a job. But now, right, where you're feeling real time the consequences of out-of-date docs, because let's imagine

you're building a support agent and it's trained on your company's source of truth. Let's say the docs or the knowledge base, you name it. And there's a question and some, and there's a section of the content that's fundamentally incorrect, right? Let's say it's just mispricing information. That source of truth becomes the enabler for the agent. to go ahead and give answers. And if that's incorrect, and you're talking about thousands, if not tens of thousands of agents

across the board, the consequences are real, right? Where it wasn't back then. And so the need of this problem, like in solving that, is very much there now. And so people are really scratching their head in terms of how they solve it.

And the number two is, I think, a big part of what's kind of like enabling the convergence of, you know, self-updating, self-healing docs. You mentioned, Jennifer, is like also the capacity of the models. So there's a need. The models are smart enough now.

I think Opus 4 or 5 was actually a big unlock for us because we've iterated and tried this idea of self-opening docs for many months in 25. At one point, it became clear that the model is reliable and says nothing can actually go do it. And then lastly, and I think this is the most important part of why this problem is going to get solved is it's also because the convergence of trust

and the environment that allows to do so. A lot more. companies, especially enterprises, are a lot more comfortable suddenly giving away a lot of their context for LM agents, right? That was not the case two years ago. I can assure you of that. We tried very hard. But now they are. And so you're kind of seeing this like need happening. You're kind of seeing the capabilities. And then you're also kind of getting this environment of this kind of. And then therefore it kind of is like the first time I think in about 20, maybe 30 years where there's a long-held problem of content knowledge going out of date is going to get solved.

And I think this is also one thing that excites a lot of developers because, you know, I'm not going to lie, as someone who day in and days out builds a knowledge and docs products, I don't always love updating the dogs either. Totally. It's also the time where the knowledge and docs gets updated the most frequent. Yeah, exactly. Exactly. And but the new workflows that, you know, are not coming out. It's not possible. you know, in similar fashion to coding has just made the job so much easier. And we're very excited about it. Definitely. And maybe I'll add on to that question with one more is now knowing that you're not

just designing for the authoring experience, the human authors, the developers that are contributing to the docs, but also the agents are reading and benefiting from the product. Like how has it changed your design decisions and what kind of functionalities to focus on, whether it's more, you know, end-user-facing UI level versus the infrastructure component you mentioned, that this becomes sort of the fundamental tooling the powers how Koon agents function? Like, how have you changed your thinking around that? Definitely a lot less of an emphasis on the way it looks. This was honestly something that Han and I did focus a lot on in the very beginning.

And then over time, you know, maybe because we were able to focus so much on it in the beginning, we're able to take our focus off of it and focus more on the markdown on the content itself. We're realizing that I think Andrew Karparthi tweeted English language is the next hottest new programming language. And so I feel like a broken record, we're constantly saying how important the content is, but that's genuinely like how we have been focusing more on that as a company as well. And a lot of, as opposed to like looking at the look and feel, we're kind of just like putting it into cloud code and seeing whether that works well and using that as the interface as opposed to just like the way the humans are reading it. And of course the human interface is still important too,

but definitely the other ways, the other entry points in which people are accessing the docs are equally if not more important. And also one thing though on the human side I would say is that a lot of people are expecting a chat interface where they're expecting to put in an error message or be able to just find exactly where it's supposed to be in the docs by just typing a couple words as opposed to manually looking at it themselves. I think I personally expect that too. It's just so much easier.

Yeah. I think the days in which the battle for the developer experience being in how nice it is and how the experience is just way past us, that was a 2010, really. The frontier now is about how good the content is. where if you have the nicest developer experience in the world, but the content is just absolute crap, then it doesn't even matter.

You know, it's just a window dressing at the end of the day. So the frontier is truly about how great and up-to-date the content is going to be, and I think that it's moving forward because, you know, when an agent goes to your docs, it could not care less. Right? If it's just reading raw HTML or markdown, it doesn't care, you know?

And the caveat that I would say to this is, you know, people also go, oh, well, like, his docs are even going to exist in a few years, right? And to that, I would say, yes, definitely, in the same reason why books are still exist today, right? There is still going to be an element of a human who needs to go read something, right, front to back, a need of someone who needs to like actually go and know what they don't know or just for humans still trying to understand the world too, right? This world will still be, we'll still have us in it, hopefully, you know? and building for that experience is still going to be paramount.

It's just going to be like, let's say, you know, now if we're thinking docs are 50% for humans, 50% for AI, it'll maybe be like 10% for humans, 90% for AI by the end of the year. But that's not necessarily because a lot less people are going to it, but because there's just going to be much more prevalence of AI agents, right? That is going to just be the massive majority of the workforce. But still, you still have to have a human element into it. And so these things are never going to go away. If suddenly you're like, oh, next year, all docs are just going to be like,

just straight up markdown files. I would not be happy about that, too. Kind of related to what we kind of talk about earlier, it feels like there's two sides of the market. There's one side of its agents or humans producing software, like software people can use. I mean, agents, although they're writing code, they're still using all the NPM packages and NPM packages.

It turns out you need a lot of context to know how to use them. And then there's the other side. which is agents of humans continue to use already built software to produce new software, right? This cycle just never ends. So to some extent from our observation recently, it felt like there's like a new layer abstraction between models and models, right? There's the production side, there's a consumption side. How have you seen the usage pattern or like interesting use cases that evolve?

Like maybe it was different audience, maybe with different ways of using MNify. Like since we're just producing software, so that's, differently now. Yeah, that's a really good question. Well, I would say that. The first thought is like, even today we're seeing these cases of, you know, for instance, auto-generated docs and change logs, that then is then becoming fed for other agents, right? And I think in the world of, you know, like really kind of going and building into that, like just really reimagining the role of not only the viewers, but also the authors of who's going to be editing the content is kind of paramount. I'm not sure if I have any more unique things or insights on that particular front

because I think that this is something that's still going to unfold very quickly in front of our eyes, right? What is the role of context? How are humans still going to be able to communicate their facts to the world? What is that interface going to look like? Is stuff that we're kind of asking ourselves day in and day out. And then I'm just trying to figure out how to build that into a way that solves problem for customers today. Right.

So I think Guillermo Rouch said something along the lines of, like Waymo's are driving within like the infrastructure that already exists of our roads. Like we still are very much operating within the world that we have today. So it's kind of like a weird balance of building on top of what we already have. And also like this new hot technology that's coming out, that's like adapting to our, the world that we have today. And so I still think that there is a lot of leveraging what's already out there. But of course, like I would say that the, it's not like the AI is just building.

things that are net already there. I definitely think there's like new innovation happening on top. But I think that a lot, it's still being built using the current technology built by humans. Yeah. Maybe just pivoting more towards the go-to-market side. Mellifai is a relatively young company. Have some of the best logos on the website and in the market that includes, you know, Anthropic, Microsoft, Coinbase, just to name a few.

What is like to serve some of the most demanding customers today is the first question. Second is more informative maybe for the founder listeners. How are you able to get some of these really demanding logos as a young company? Yeah. Well, I'll start by saying that we're very fortunate to work with these companies, right? It's not lost on me that it's a privilege, not a right, and not something that we can take for granted. And so being able to serve, I mean, not just anybody, but a lot of the best in the field and kind of the work that they're doing is like truly inspiring for me in Hanbi. and especially to the mission that we're on.

As far as what it's like to work with these very demanding companies and fast moving, well, you've got to be demanding and fast moving right back. For sure. And then that's really one thing. I remember, like, as an example, some of these AI labs, right?

When we were working with them, we were just shell-shocked by how quick they respond to everything and how quickly they're able to do things. So you would send a Slack message to them about anything. you would consistently, depending, it doesn't matter what time. It could be like five in the afternoon until 2 a.m. in the morning, someone's going to respond within 10 seconds. And you check it's not a bot on the other side.

There were many times I was so convinced there was one. I was so convinced there was one. And I just dig it a little bit. Where do you live? Yeah, because that's what we ask. What's your social security number? We need to confirm. But if you kind of see those.

companies and you're kind of seeing and observing the kind of cutting edge, you get inspired by what you could be as well, right? And that's like a big source of inspiration for us. Look, if these companies at this scale even are working at this kind of pace that they are, then there's no excuse for startups for ourselves not to hold ourselves to that standard too. And so we hold ourselves that bar with, you know, with not just, you know, these logos, but everybody, right? Someone responds, look, you got to respond right back very quickly. I remember it got to a point where Anthropic in particular, they sent a message and then we respond within a few seconds. And then their response was like, do you guys get on call whenever we send a message?

And that was like a big compliment for me. For sure. We don't. Everyone is on call all the time. Yeah, exactly. But I think it speaks to kind of like the expectations that exist now. And my point is like having now worked with some of these really great logos and especially the larger ones, we have been so surprised by. the pace of which these companies and teams are moving, you know, just to shout out Microsoft.

My goodness, for a company that's as large as they are, they are moving lightning fast over there. And if like, you know, the stereotype of what large companies was just a few years ago is not really the case anymore, right? And that should be an inspiration for everybody, in my opinion. For sure. If I recall correctly, I think I remember some of our biggest customers came in into our Slack community on like a Saturday. And like you would just respond just casually. And then it would end up becoming a huge customer that like we, we had no idea like they were evaluating the product.

So it goes to show that everybody is working, but dare I say, 996. All the time. And has the way that these companies use the product informed to you how you want to build the product at the same time? Do they use the product a little bit differently from, you know, the rest? of the customers, or it's more about sort of the working culture and speed that's been inspiring the... Oh, man. I mean, absolutely on the former. When you work with these great companies, they have some great ideas, right? And we've taken, we've been very grateful by kind of taking

and bouncing off of these ideas, these thoughts with these companies to then go ahead and actually go and implement them and scale for others. Again, I remember when we first started working with Empropic, this was, again, two years. ago now, I want to say. We were a pretty early customer. And I remember we just got back and like online this morning and we noticed that all of their docs were suddenly from English to 12 other languages, right? We're like, how did you guys do that? Did you guys like go and get translators for this? No, we built a pipeline that went ahead and just translated them all in real time. Again, this pretty like commonplace now. And I think it'd be a pretty like non-trivial thing

for us to imagine how someone would build that and why someone should now. But the two years ago, we're like, what? You can do that now? I did not know that was a thing. And then they were like, oh, you should go do it too for other customers. And then we did. And so I think just kind of getting those kind of the caliber people. And it doesn't really necessarily take, I think, just working with the best to kind of get that, right? I think a lot of these people, too, themselves are still, you know, figuring out and they kind of rely on even the startups to figure out, you know, what it means and what the next chapter is too. Definitely.

I guess looking to the future, since you've worked down Mintlify for quite a while, what excites you the most about things you will build, things the community will build, help people and new customers will be using you? I think the first thought is, you know, I think what excites me about Mintlify is the same thing that excited us from day one. And that is that Hanbi and I wanted to go embark on the journey of building for people that we care about in a space that we believe genuinely impacts, you know, the broader ecosystem and the community that we've been in our lives. So the sense of empowering builders, if you

will, that got us going, got us on this journey and got us to this product today, that we get to do that in scale and even broader impact in ways that we never imagined still gets me the most excited. The thing that, like, you know, people are like, oh, you know, it must be great. You're growing. You're like, you know, scaling. You're working with these companies and, you know, getting all the commercials, I'm like, yes, of course, that's great. Of course, you know, that's something that we'll continue to do. But what really gets me out of the bed in the morning is knowing that as of last month as an example, like 20 million people, right, came across a site that was power. Whether they know it or not, right? It doesn't matter to me if they know it or not. But what

it matters to me is knowing that those 20 million people, there were probably many of them that was like the Han when he was 11 years old that learn how to code for the first time, then go ahead and use the information, let's say, on whoever's docs to go and build something that was helpful for maybe, you know, their community and their school. And the sense of having that impact into the world is something that truly excites me and Hanbae about our work. And I know we'll continue to for hopefully years to come. There's two things that I'm excited about. One is building more AI agents. And I'll go into that more. And then secondly, building for more people as well. So first for the AI agents, like,

I think it's so cool to build AI agents because you build something and then it surprises you at what it could be doing or like its capability surprise you. And so I'm excited to continue to iterate on that process and continue to be surprised by the stuff that I'm building. And secondly, we've constantly been like, you know, honing in on the fact that we love to build people, build for people that we really empathize with. And I like to believe that over the course of the three years, that haunted and I's worldview has increased. And we've, you know, interacted with more people and, like, faced new problems from when we first started the company. And so I'm excited to continue to expand our worldview and build for more people as our worldview changes. Like, for example,

we have customer support now as well. And, like, we have new problems at the stage of the company that we're at today. And that's more people to help. Awesome. I'll conclude the podcast by saying may everyone that's a builder in 2026 being able to build more, encounter with more fresh minty dogs and rain to less that ends. And thank you so much, Han and Humvee, for coming and join us today. Thank you. Thank you so much for having us. Thanks for listening to the A16Z podcast. If you enjoy the episode, let us know by leaving a review at rate thispodcast.com slash a16Z. We've got more great conversations coming your way.

See you next time. As a reminder, the content here is for informational purposes only. Should not be taken as legal business, tax, or investment advice, or be used to evaluate any investment or security and is not directed at any investors or potential investors in any A16Z fund. Please note that A16Z and its affiliates may also maintain investments in the companies discussed in this podcast. For more details, including a link to our investments,

please see a16z.com forward slash disclosures.