Cake
  • Log In
  • Sign Up
    • Oh, yes. So I came from a background of AI, and everyone in the world of AI uses time series tables, like data modeling. And that problem doesn’t exist when you’re just doing algorithms. In the startup community, every question you have to answer is very difficult, because of the vastness of the sources and how unusable the various data structures are. So to give you an example, our data structures that we have are designed for machines. You have a ticket object, and the ticket has a status on it, and that ticket has a bunch of comments on it. It’s designed to be about the ticket. And when people ask questions, they don’t ask questions about tickets. They ask “How many people visited the FAQ page, then submitted a ticket right after?” That question takes, like, HOURS, if not days, to do by hand. And it seems simple! Because you’re like “Duh, I can see I did it!” But computers are independent systems with independent data with independent structures, so that simple link is actually very hard to bridge. So that is what inspired me to build Narrator.ai. I was sitting there, doing that work, and knowing that there’s a world when you structure information better you can answer questions faster. So instead of spending a day on it, you’re spending a minute. So that’s the first biggest component. I felt there was a lot of wasted time analysts spend on dealing with data-structured bullshit. Every 2 years, people think of initiatives to re-design the system, it appears good, and then as time goes by, it quickly fails again. We are all in that world reinventing the wheel. So the whole structure of Narrator, a standardized globalized schema that we know will work when you’re $100 billion dollars or a 2 person startup, sets you up for success. And if I had this product during my time when I was working as an analyst and data scientist, I would have been 100x more efficient.