useDan is an AI-native business intelligence platform that helps teams ask business questions in plain language, understand what changed, and move from insight to action faster. Built by Company8 for founders, operators, growth, finance, and data teams who need clearer answers without waiting on another report cycle.

Hey Product Hunt 👋 We’re launching useDan by Company8 today. We started building useDan because business intelligence still feels slower than the decisions teams need to make. Most teams already have more than enough tools, reports, dashboards, and data. The problem starts when someone asks: “What changed?” “Why did it happen?” “What should we do next?” That answer usually takes too long to find. useDan is our attempt to rebuild business intelligence for AI-native teams. You can ask business questions in plain language, investigate what changed, and move from insight to action faster. We’re building for founders, operators, growth teams, finance teams, RevOps teams, and data people who are tired of waiting for another report cycle before making a decision. We’re early, learning fast, and would genuinely love your honest feedback. A few things we’d especially love to hear: 1. Is the product clear in the first 10 seconds? 2. What business question would you want to ask useDan? 3. What would make you trust an AI-generated business insight? Thanks for checking us out. Brutal feedback is very welcome.

One thing I'd love to see is a way to save and annotate specific query threads so my team can revisit the reasoning behind a metric decision weeks later without retyping the question. Right now it feels like each insight is a one-off conversation.

@jorvik_ho Exactly, Jorvik. A useful answer should become reusable context for the team, with the reasoning, annotations, decision and eventual outcome kept together.

We think of this as decision memory, and it’s closely aligned with where we’re taking Dan.

When your team revisits a thread, what matters most: the original reasoning, team annotations, or the decision and outcome?

@jorvik_ho Exactly, Jorvik. A useful answer should become reusable context for the team, with the reasoning, annotations, decision and eventual outcome kept together.

We think of this as decision memory, and it’s closely aligned with where we’re taking Dan.

When your team revisits a thread, what matters most: the original reasoning, team annotations, or the decision and outcome?

useDan by Company8

Ask your business anything. Get answers that lead to action.

Ask your business anything. Get answers that lead to action.