Poth Labs

Really like the idea of reasoning over relationships instead of just retrieving documents. Curious - do you see Poth staying focused on customer intelligence or is that just the first step toward becoming a broader knowledge layer for product, marketing and other teams?

Good direction but a tough one to crack.. most customers don't talk till they are coaxed to share, still your beginning is correct for collecting all behaviours, and reasons.. the chances of catching a detractor is higher when you know that a churning customer your system knew about, had many signs that match with the current customer behaviour.. good wishes for your success..

Churn in developer communities doesn't show up in the CRM first. It shows up in Discord going quiet, GitHub issues tapering off, forum activity slowing down weeks before anyone cancels or even thinks about it. Does Poth connect to sources like that, or is the knowledge graph limited to CRM and support integrations? That gap is the one I'd actually want closed.

Alex is pointing at the real hole. I would go one step further.Staleness never throws an error because absence of data and absence of change look identical to any system built from ingested artifacts. No ticket, no call, no email. The graph reads that as a quiet, healthy account. It is usually the opposite.We learned that expensively once, with a customer who was signed, warm in every conversation, and had not used the thing a single time. Every source we had said green. The only honest signal was usage, and nobody was looking at it.So: does Poth model silence as evidence? Not "no data on this account" but "this account has gone quiet in a pattern that has preceded churn before."And on Artem's question, when the CRM and the support tool disagree, does Poth pick one or surface the disagreement? The disagreement is usually the actual finding.

relationships rather than documents is the right framing. the hard bit is that a relationship goes stale without ever throwing an error, nobody files a ticket when a champion quietly leaves, so the graph keeps looking healthy right up until the renewal.

Hello Product Hunt! We started Poth because companies already know a lot about their customers—but that knowledge is scattered across calls, tickets, CRM records, analytics, surveys, and internal docs.

Questions like “What’s driving churn among our highest-value accounts?” rarely have an answer in one place. Teams have to manually connect what customers said, what they did, and what happened to the account.

Poth originally generated hypotheses and ran adaptive customer interviews and surveys. But to ask useful questions, it first had to understand everything a company already knew.
That led us to build a living model connecting customers, accounts, features, behaviors, and conversations across different systems. As teams began using that model to answer questions across their existing customer knowledge, we realized it needed to become a core part of Poth.

Today, Ask Poth reasons across your customer knowledge, grounds every conclusion in evidence, and shows what information is still missing. When the answer isn’t there, Poth can collect it through adaptive interviews and surveys.

We’d love to hear your feedback!