Needle - The proactive GTM agent in Slack and Teams
by•
Most sales AI waits for you to ask. Needle is proactive. It works like a GTM engineer on your team: it watches your pipeline and acts before you do. Spots stalled deals and drafts the follow-up, preps you before calls, keeps your CRM tidy, surfaces real buying signals. It lives in Slack and Teams, wired into HubSpot, Gmail and Gong. Unlike horizontal agents, it is built for revenue teams, acts through your permissions, and your context and memory stay portable. No lock-in. Not another dashboard.

Replies
Needle
@jan_heimes Congrats. Quick question for the team: which early win should a RevOps leader expect in the first 30 days of using Needle; fewer stalled deals, cleaner CRM data, higher meeting prep coverage, or something else; and what measurable signal would show it's working?
@jan_heimes Love that you're embedding the agent directly in Slack/Teams instead of forcing context-switching. How did you decide on proactive vs reactive triggers — was it user feedback or did you ship reactive first?
Needle
@clquek Yes we talked with +100 head of sales / head of rev-ops and that is what all the conversations pointed towards.
This looks genuinely useful - taking the admin work off a sales pipeline is exactly where I would want the help. One question before trying it: is it usable for a small, early team, or does it assume an established sales org already on HubSpot and Gong?
Needle
@alieksia you're not on HubSpot or Gong yet, Needle still plugs into Slack, email, and calendar and helps from there, the value shows up earlier with an early team since there's usually no one dedicated to keeping things tidy. It gets sharper as more of your stack connects, but it's not gated behind having an established org first.
@jan_heimes @onur_o Thank you, that is clear and good to know. I will keep Needle in mind as our sales side grows :)
Needle
@alieksia glad to see you find it useful! you don't have to have an established sales org. you can plug it into your stack.
Congrats on the launch!
1. Curious how Needle decides that something is a signal in the first place. Is it mostly based on rules the team sets, or does it infer patterns from HubSpot, email and call context?
2. And once a rep acts on a suggestion, can that close the loop? Meaning, can Needle learn which plays worked, which got ignored, and turn that into better GTM moves over time?
Needle
@ataniz thanks for the support!
Needle agents analyze won/lost deals and recognize the patterns and learns what is a signal or not.
i think my first point also answers this
@onur_o Awesome, looking forward to playing with it!
Needle
Super excited to finally see this out in the open 🚀
One thing that stood out while building Needle is how much of a rep’s day is spent on everything except selling: research, CRM updates, follow-ups, finding the right context, preparing for calls. That’s exactly the problem we wanted to solve.
Proud of what the team has built, and we’re just getting started. We’d love to hear what the Product Hunt community thinks!
Needle
@valentin_po Couldn't have said it better. The wildest part building this was realizing how little of a rep's day is actually spent selling. We built Needle so that everything else just happens in the background. Proud to be building this with you 🚀
Finally gave this a spin in our Slack and the pre-call prep nudge saved me from walking into a discovery call blind. The stalled-deal drafts are a bit generic but honestly useful as a starting point.
Needle
@berktrh4 Really appreciate the honest take, especially the generic part. That's fair, and it's exactly the kind of feedback that helps us tune it. The drafts are meant as a starting point Needle builds from what it knows about the deal, but there's clearly room to make them sharper and more specific. Glad the pre-call prep already earned its keep though, that's the one I personally use every day.
the deal nudges actually got me to follow up on stuff i'd completely forgotten about, which is rare for any tool i've tested
Needle
@hiranurerkasap That's exactly the reaction we were hoping for. The stuff that quietly slips through the cracks is usually what costs a deal, glad Needle caught it for you!
most ai waits to be asked. this one talks first. that flip is where the trust question gets real. reactive is easy because the worst case is a bad reply. proactive is scary because the worst case is a bad action nobody signed off on. the design job is making sure the actions are the ones the human would have taken 5 minutes later anyway.
curious how you handle disagreement. when needle drafts follow-up and the rep would have written it differently, does the rep edit and move on, or does needle learn to write more like that rep over time?
Needle
@thenameisarian thanks for the question, great one! the agent is highly customized based on the preferences of the rep, it learns their style and how they handle conflicts. it always self-improves.
Needle
@thenameisarian this is exactly the right framing! To your question: both, in sequence. Early on the rep edits almost everything, that's expected and fine, we treat every edit as a signal, not a failure. Over time the gap between what Needle drafts and what the rep would have written shrinks, but we never let it fully auto-send on judgment calls like tone or relationship nuance. It has memory.
Postproxy
Wow, great stuff! Congrats on the launch!
Love the video 🖤
Needle
@dmitrysereda thanks a lot for the support! 🖤
Needle
@dmitrysereda Appreciate you and yeah shoutout to the team. The video was teamwork.
'Proactive' is the interesting word here - most agents wait to be asked, and the value is in the ones that surface the thing you didn't know to ask about. How do you keep the proactive pings from becoming noise? That threshold (helpful vs annoying) is the hardest dial to tune in any agent I've shipped. Congrats on the launch.
Needle
@david_marko thanks for the support! the agent learns how the rep and the company operates and matches the vibes so it learns not to be annoying.
Needle
@david_marko fair callout, and I'll be more precise than the vibes answer above. Two things keep it from becoming noise. First, thresholds are explicit and rep-configurable. Second, and more important, every ping is scoped to something with a clear action attached, re-engage this person, review this field, not just an observation. If there's no decision for the rep to make, Needle doesn't ping.
How do you handle permissions?
Needle
@darian_weingartner Permissions aren't a separate layer you configure, they're inherited. Since every agent is personal, it only ever sees and acts on what you can, across CRM, email, Drive, and Slack. What an agent can do maps to what the person behind it is allowed to do.
Needle
@darian_weingartner the agent is basically a shadow of your own permissions by default, but that can also be adjusted.