Sales Stack → Pricing Sign Up →

Tag: opinion

  • Notification Overwhelm Isn’t Inevitable

    Notification Overwhelm Isn’t Inevitable

    One of your reps said it recently, maybe not to you directly: “I’ve got so many notifications I don’t read any of them.”

    That’s worth sitting with. Because if your team has stopped reading notifications, the problem isn’t Slack. It’s that everything got the same weight, and when everything is urgent, nothing is.

    The mess usually has an enthusiastic origin

    Most notification chaos on sales teams doesn’t come from neglect. It usually starts with good intentions and a HubSpot workflows tab.

    Deal stage changes, activity reminders, overdue tasks, lead assignments, pipeline thresholds: all firing into Slack. Each one individually defensible. Collectively, a wall of identical pings that your team learns, very quickly, to ignore.

    And that’s before you count everything else that’s been connected to Slack. Intercom, Jira, Google Calendar, whatever the team voted to add six months ago and nobody uses anymore. The HubSpot notifications are just the ones you built yourself.

    And once the ignore habit forms, it’s hard to break. You can send the most important message of the quarter into that channel and it lands with the same visual weight as a notification that a contact’s job title has been updated in HubSpot.

    Save your DMs for when they actually matter

    The same logic applies to any bot nudge you’ve set up to chase pipeline updates or prompt follow-ups. A bot reminder is easy to dismiss. A direct message from you asking where something stands is not. That difference matters, because you only get so many of the latter before people start dreading them.

    Use reminders for the things that genuinely need a prompt and they’ll land. Run them constantly and they become part of the noise, dismissed along with everything else.

    “Does this spark joy?”

    Most teams never do this. They add notifications over time and never go back. So go through them. For each one, ask: does someone actually need to know this right now? Not eventually. Not as a nice-to-have. Right now, in the middle of whatever they’re doing.

    Most of it won’t survive that question. A deal crossing a significant threshold probably does. A contact’s job title updating in HubSpot probably doesn’t. The things that require action today stay. Everything else gets moved somewhere people check on their own schedule.

    What this looks like in practice

    Next time a notification lands, stop for a second and ask whether it earns the right to be there.

    It sounds like small work compared to closing deals. But the notification environment your team works in determines whether something important actually gets seen or disappears into the feed with everything else. Just because you can automatically create a channel for every deal in the pipeline doesn’t mean you should.

  • HubSpot is the record. Slack is the pulse.

    HubSpot is the record. Slack is the pulse.

    Most sales teams treat HubSpot and Slack as two separate things. You log stuff in HubSpot. You chat in Slack. The two worlds don’t really talk to each other, and that’s just how it is.

    That’s the problem.

    HubSpot is the record. It tells you what happened: what deals are open, what stage they’re at, what was said in the last call, what the close date is supposed to be. It’s accurate (when people update it), it’s structured, and it’s permanent. It’s where the data lives.

    Slack is the pulse. It’s where the team actually lives. It’s where you notice that someone who’s usually first to respond to anything hasn’t said a word since Monday. It’s where someone asks if anyone has dealt with a procurement team like this before. It’s where a win lands in a way that actually feels like a win, not just a field update in a CRM nobody checks in real time.

    One tells you what happened. The other is how you find out what’s actually going on.

    The teams that get this right connect the two intentionally. The right HubSpot data shows up in the right Slack channels, as useful signals. A pipeline review starts and the manager already knows where things stand. A forecast call opens with everyone already looking at the same numbers.

    The teams that don’t are winging it in pipeline reviews or opening a dashboard while the rep runs down the clock about the great demo they just did. Or spending the first ten minutes of a forecast call going round the room getting everyone’s commit before discussing anything useful.

    It’s one of those things that just becomes the cost of doing business, so familiar you stop noticing it. But if you step back and look at what it’s actually doing to your team, it’s probably bigger than you think.

  • Your wins channel is producing noise, not recognition

    Your wins channel is producing noise, not recognition

    There’s a channel on your Slack called something like #wins or #closed-deals or #revenue. Someone set it up with good intentions. A deal closes, a notification fires, the team sees it. Simple.

    Except it isn’t working. You know it isn’t working because the channel gets ignored. Because when something genuinely big lands, it disappears into the same feed as everything else. Because you’ve watched a rep close the biggest deal of their career and get three emoji reactions before the conversation moved on.

    The problem isn’t that people don’t care. The problem is that your wins channel treats every deal the same — and when everything gets the same signal, the signal stops meaning anything.

    A notification is not recognition. This is the thing most teams miss when they set up a wins channel. They’ve solved the information problem — the team knows a deal closed — but they haven’t touched the recognition problem at all. They’ve just created a feed.

    Recognition requires weight. It requires the moment to feel different from the one before it. A €500 renewal closing is information. A €50,000 new logo closing is an event. If your Slack channel pings identically for both, you haven’t created a wins culture. You’ve created a ticker.

    The rep who just closed the big one knows exactly how that close landed in Slack. They remember. It either felt like something, or it didn’t. And if it didn’t, that’s not a small thing — it’s a signal about whether this team actually sees what people do.

    The fix isn’t complicated, but it does require a decision most teams never make: what actually counts as a win worth calling out, and at what level?

    This means setting thresholds. Not arbitrary ones — thresholds that reflect what’s genuinely hard to close on your team, what represents real progress, what the team would actually want to celebrate. A five-rep SaaS team scaling from €50k to €500k ARR has different thresholds than a team running high-volume transactional deals. Both can have a wins channel that works. Neither will by accident.

    Thresholds also solve a second problem: they stop the channel from becoming a compliance exercise. When everything posts automatically, nobody feels like they chose to celebrate anything. The wins channel becomes maintenance rather than meaning. When there’s a threshold — when something has to actually earn its place there — the posts that do land carry more weight.

    There’s a related question most teams also skip: who needs to see what, and in what form?

    A team-wide channel makes sense for deals above a certain size, or for new logos, or for anything that represents a genuine milestone. But the rep’s manager probably wants to know about every close. The CEO might want a weekly summary rather than a real-time feed. Finance has different needs again. Most teams end up with one channel trying to do all of these jobs, and doing none of them well.

    The notification that reaches everyone should be the exception, not the default. The exception is what makes it feel like something.

    None of this requires a complex Slack setup or a new tool. It requires someone — probably you — sitting down for thirty minutes and making a few deliberate decisions. What’s a win? What size warrants a team-wide callout? What does that callout actually say — is it just a deal name and a number, or does it include something human, something that tells the story of the close?

    That last part matters more than most managers think. A message that says “Deal closed: Acme Corp, €45k” is information. A message that says “Emmet just closed Acme Corp at €45k — six-month cycle, three competitors in the mix, closed on a Friday afternoon call. Huge one.” is recognition. The difference is thirty seconds and the decision to treat it like it matters.

    Recognition that feels real doesn’t happen automatically. It happens because someone decided it was worth doing properly.

    The wins channel is a small thing. But the small things are usually where you can see whether a team’s culture is intentional or just running on default. Most teams are running on default. The channel exists, the notifications fire, and everyone quietly knows it isn’t quite working — without ever stopping to ask why, or what it would take to fix it.

    It wouldn’t take much.