Stale deal nudges

Each week the automation reviews deal activity in HubSpot, finds the opportunities that have gone quiet relative to their stage, and drafts a tailored follow-up for the owner that references where the conversation left off. The draft is delivered to the rep in Slack to send, edit, or hold.

No live deal goes cold just because the week got busy, and keeping the pipeline warm becomes a quick review.

Scoped access

• HubSpot, read deal activity
• Slack, deliver drafts to the owner

How it fails silently

Stale deal nudges fail silently when the deal is not actually stale, it is over. The opportunity is quiet because it already closed-lost, or the champion left the company, or it was won and not yet marked. The automation reads quiet as needs-a-nudge and drafts a cheerful follow-up asking about next steps, and sent unattended it reaches someone who has moved on, or a buyer who already said no. It makes the rep look like they have not been paying attention to their own deal. The run looks productive. The nudge lands as out of touch.

What the overseer catches

Once a follow-up is drafted, the overseer checks it against where the deal actually stands. When a cheerful nudge assumes the deal is live but the record shows it closed, lost, or its main contact gone, it flags the draft for the rep instead of leaving a tone-deaf message sitting ready to send.

Genuinely stalled deals get a tailored draft delivered to the owner with no extra steps. The routine re-engagement is prepared for the rep.

What surfaces for a closer look is the deal whose state is unclear or contradictory: the one that may already be closed, the one missing its contact. The draft reaches the rep flagged, so a tone-deaf nudge is something they catch before sending rather than after.