Prospector by Synter - Your outbound agent, right inside Slack

by
Nobody likes dashboards. So we built Prospector instead — an outbound agent that lives in Slack. Just ask: How are my campaigns doing? Who engaged with this post and is worth reaching out to? It reads your outbound, builds lists from real engagement, and answers in a sentence. Prospector runs outbound, Synter runs paid media, and they share the same audiences. Try it: /prospector /pipeline /campaigns /contacts /report

Add a comment

Replies

Best
Hey Product Hunt, Joel here, founder of Synter. I built Prospector because I was tired of outbound dashboards. They never really told me what was working, and I could not just ask them a question. So I made an agent that I talk to in Slack instead. Now I ask things like "how are my campaigns doing" or "pull the people who engaged with this LinkedIn post and dedupe them against my contacts," and it just does it. Same idea as Synter, our paid media agent, but pointed at outbound. One thing I care about a lot: a lot of tools that connect AI agents to your accounts are careless with credentials. We are not. Prospector handles access in a safe, secure, and reliable way, because an agent is only as trustworthy as how it stores your keys. Happy to answer anything about how it works, what is under the hood, or where we are taking it next. What would you want an outbound agent to do for you?

The "pull people who engaged with this LinkedIn post and dedupe against my contacts" use case is the one I'd actually build a workflow around. Most of our outbound coordination already runs through Slack, so keeping the agent there removes the context-switch tax completely.

Two questions: how does ICP filtering work before building the list - do you configure that upfront or is it prompt-level? And does it connect to existing CRMs like HubSpot so the dedup is against real pipeline data, not just a local contact list?