Clidey: Automatic technical documentation for codebases — $3K revenue and 30%+ week-on-week growth in first 2.5 weeks
Jun 11, 2025 · Full transcript · This transcript is auto-generated and may contain errors.
Featuring Founder 1
Do we have anyone else? There's a little bit of lunch break going on. Giving you some inside baseball here at YC Demo Day 2025. But we have one more team. They don't need to take lunch breaks. They're owning purple. They're working. They're owning purple. And and the Pit Vipers have made a return.
I think it's all one pair of Pit Vipers. Recycling. We know the Pit Viper family. There's not enough color going on here. Let's put on some yellow hats as well. Let's just really get crazy with the the the the fever dream that's going on with the orange, the purple, the yellow. We love clity. What are you guys up to?
What are you guys building? Uh we're building automatic technical documentation for codebase. So saving 30% of uh employee time. Okay. Yeah. Um explain the first customer. Are you going after larger enterprises? Are you selling to other YC companies? Yeah.
Uh ideally to enterprises, but we're starting off with series AB onwards companies. Um majorly because that's when you start onboarding people. you need internal documentation to actually give like technical specification for your product so on.
So yeah, initial focus is series AP on specifically for companies that are uh delivering APIs that they sell access to. Not just APIs but any any sort of like right now it's a web application but any sort of application um in theory. So like API is part of it. Yeah. Yeah.
I I there's a number of open source projects that kind of allow you to uh stand up a boilerplate for open source documentation or or API documentation. uh how is your product different? What what what are you hydrating?
Because at a certain point if there's kind of internal sacred knowledge around how an endpoint works, you have to get that from the person that designed it or can you instantiate everything from the code? Yeah, that's the plan. Like the idea is for us to not depend on one person.
The idea is like uh we actually go across the organization all the code bases and uh understand those like technical specifications from like in the background, right? So there's no different. How are you dealing with security?
I imagine that if you're going across all the code bases, all of a sudden there's like secrets that could leak. There's there's internal tooling that they maybe they don't want to have out there in their documentation. How do you think about that? So, we make it completely self-hostable, the best part.
So, um especially for an enterprise when they have to be compliant, regulations and so on. So, we completely make it uh self-hostable. People can actually just use our product like it's packaged so you can spin it up, put the repositories in and nothing leaves their network. How did you guys get to YC?
Uh like in terms of the place. Yeah. What's the backtory? You want to go car plane. What was Yeah. I mean I mean through plane that was the last time but I've known this guy. We've been through so many places. I've known him for about 10 years. We met in uni hackathons tons of projects. Very cool.
Um and to get to YC just a couple failed applications and here we are now. Always so many. Everyone has one at least in your belt. Um how's the traction been? What what are you sharing today? Yeah. So in the we launched about two and a half weeks ago. Uh we already are around 3,000 in revenue. Congratulations.
We have we have about six six seven customers now. Um so we are Yeah, it's it's going well. We have we're increasing 30 over 30% week on week actually. There we go. Week on week on week. Just do that for the next like a thousand weeks. We get to go hopefully. Yeah. 73 days again. Nice. How's how's fundraising going?
You guys in the midst of it? Yeah. Uh we're about 40% there. Uh 40 50% there. So we're getting we're getting close. Um hopefully. Yeah. Uh what is it just you on the team right now? Do you have anyone else? Just keeping it that way for a while or you think you'll you'll start really scaling?
We we are thinking of getting people on board. Um but uh yeah, we want to make it we want to keep it lean. We're trying to automate documentation. So you got to automate, right? Yeah. Exactly. You got to live it. That's great. Uh well, thank you so much for coming on the stream. Awesome day. Thank you so much.
We'll talk to you soon. Thank you guys. Bye. And we are ready for our next guest