aditya1081

any other feedback? did you get to checkout the interactive demo?

thanks, will add them

We are building Bree - a better way to create and maintain technical docs.

Here to discuss what pain points do people face in creating and maintaining proper internal docs. For me it was - capturing valuable discussions from Slack into a doc that can be accessed later.

PS: We are looking for early paid pilots - preferable series A to B startups.

Yeah thats the main differentiation - our backgrounds are in search, and we think its pretty hard to use traditional chunk -> embed -> retrieve- > rerank for structured data (they work well for unstructured data).

So we use a different approach where we create the code graph and apply classic ML (like clustering) to find abstracted patterns in the graph. We have AI agents that traverse these abstractions to create knowledge which we search on.

This enables better quality responses for more complex questions about generic higher level concepts.

We think of it in the following way: Cursor etc will be extensively used to write code. Our tool comes into play when you don't know exactly where to start, which is why we focus on KPIs like new eng onboarding times, reduced eng hours on KT, etc - overall developer efficiency. Lmk if it makes sense!

Yeah the PH launch was just aimed at getting some bottom up users, we ideally want to sell top down. As far as code privacy and security is concerned, we deploy depth ai in your private vpc, so your code never leaves your cloud.

We just launched, so we are looking for design partners and / or paid pilots (pricing would depend on number of users and we can discuss it more case by case).

Lmk if that answers your questions!