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, and surfaces real buying signals, all from inside Slack and Teams. Wired into HubSpot, Gmail and Gong. Not another dashboard.
This is the 5th launch from Needle. View more
Needle
Launched this week
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.
Free Options
Launch Team / Built With
Congrats on the launch! The Slack and Teams-first angle makes a lot of sense here, especially for the “act before someone opens the CRM” moments.
Curious how you handle trust when Needle suggests an action. Do reps get a clear reason for why something was surfaced, like the signal, source, and suggested next step, or is the goal to keep it mostly invisible unless they ask?
Needle
@akashnawani not invisible, that would make it impossible to trust. Every suggestion comes with why it's showing up, what signal triggered it, where that signal came from, and what the suggested next step is. No black box nudges. The goal is you can glance at it and immediately know whether to act, snooze, or ignore, not have to go dig for context first. If it can't explain itself, we don't ship the nudge.
I like the vision but I'd probably want to start with recommendations before giving an AI permission to take actions automatically. Is there a gradual adoption path for more cautious teams?
Needle
Hi there @gordon_bennett yes you can adjust it accordingly and state how autonomous you want it to be.
Proactive feels right, it pinged me about a stalled deal before I even opened HubSpot that morning and drafted a solid follow-up. The Slack-first setup keeps it out of my way.
Needle
@erolsalmaney2h This is exactly the moment we built it for, catching the thing before you even go looking for it. Thanks for your comment!
Interesting approach 🙂. The 'mirrors your permissions' model avoids a lot of the config headache. Curious how it handles document-heavy steps (proposals, contracts, PDFs) in the pipeline. That's often the messiest part of automating a sales workflow.
Needle
@benjouss
Great question, and you're right that it's where most sales automation quietly breaks. Today Needle reads the docs already living in the deal (PDF proposals, email attachments, HubSpot files via Gmail/Drive/HubSpot) and treats them as context: it pulls the key terms, flags what's missing or inconsistent, and drafts the follow-up or proposal off the actual document instead of a generic template.
What it won't do yet is generate a fully redlined contract end to end. Curious which doc step is messiest for your team, proposals or contracts?
@jan_heimes I work on the document infrastructure side (PDF/OCR/e-signature APIs), so I was asking more from that angle.
What's your read on it internally, is it more that contracts pile on complexity (redlining, e-signature compliance), or that proposals are just as messy but higher volume?
the part that gives me pause is "tidies the CRM on its own" - CRM data being wrong silently is worse than it being stale, because nobody double checks a field that looks filled in. is there an audit trail showing what it changed and why, or do you just have to trust the drafts before they go out
Needle
@omri_ben_shoham1
The goal is that "tidy" never means "confidently wrong." Can start with propose only and write only if agreed / review. Once you trust after some time to you can let it run automatically end to end. Also has memory so it learns over time.
propose-only as the default makes sense to me, that's basically the tradeoff every agent tool ends up making eventually. curious how long people usually stay in review mode before flipping to auto - is it a fixed number of clean runs or fully up to the user
memory learning over time is the part that actually sells me on it, most propose-only tools just stay propose-only forever because nobody bothers to loosen the leash. is the trust threshold something you tune per workflow or does it apply globally once it kicks in?
A lot of tools try to be proactive, but end up just adding another layer of noise.
The interesting part here is the judgment layer - deciding what actually deserves attention vs what can be ignored.
How do you approach that early on, before there’s enough data to really tune it?
Congrats on the launch!
Needle
@jared_salois Great question, this is exactly the right thing to push on.
Honest answer: we don't start from zero. Two things carry the cold start:
The signal already exists in your stack. Call transcripts, email threads, deal age, last activity, who went quiet after a proposal. Needle reads what's already in HubSpot/Gong/Gmail from day one, so the first stalled-deal list is useful before any tuning happens. Had a call today with a CRO sitting on 5000 old deals: the judgment there isn't ML magic, it's "no activity in X days + proposal sent + no reply" logic that's right often enough to earn trust.
So: rules + existing CRM signal first, personalization second. Being right 8/10 times with few pings beats 9/10 with spam, because after 3-4 ignored nudges reps tune you out forever.
Curious how it handles the noise though - does it learn from feedback when a flagged "stalled deal" is actually just going slow on purpose, or does it keep pinging you the same way every time?
Needle
@adem1368780 that is a good question, it has memory and learns over time from your feedback and behaviour.