Scanning connected pipelines hourly
Deals go quiet. Yours won't go unnoticed.
Every hour, it checks your HubSpot pipeline against the rules you set — sitting too long in a stage, missing a next step, no owner assigned. Then it reads the deal's actual context and drafts the re-engagement message, so the alert arrives with the next step already written.
🔒 Read-only access. It never creates, edits or moves anything in your HubSpot.
14 days free, no card required. Connects to your existing HubSpot account in under a minute.
Appointment Scheduled
1Riverside Roofing — Full Install
£2,222
6d in stage (limit 3d) — STALE
Wanted to circle back on our meeting that we had lined up. Haven't heard much since then — is there anything that's changed on your end, or would it make sense to reschedule?
Copy message
A deal doesn't need a bad rep to go stale. It just needs nobody to notice for a week. By the time it shows up in a pipeline review, it's already cold.
Built around how deals actually go quiet
Staleness isn't one number
A deal sitting quiet for 5 days in early discovery is normal. The same 5 days at contract stage is a problem. Rules are set per stage, per pipeline — not one flat threshold for everything.
Reporting alone doesn't fix it
A dashboard nobody checks changes nothing. Alerts go straight to the rep by email when it happens, and to a manager only if it stays unresolved — visibility with real follow-through, not another report to ignore.
Monthly review is too slow
By the time a manual pipeline review catches a stale deal, it's often been quiet for weeks. An hourly scan catches it while there's still a real chance to save it.
A next step is the real problem
Time-in-stage isn't the only warning sign. A deal with no next activity logged, no owner, or no dollar amount is just as much a hygiene problem as one that's gone quiet.
Six ways a deal can go stale
Set the ones that match how your team actually works. Combine them per stage for a fuller picture than a single day-count ever gives you.
Time in stage
Flag a deal once it sits in a stage past your limit — the original, simplest signal.
Missing next step
A deal can look active and still have nobody planning to touch it. Catch the ones with no next activity logged.
Overdue close date
A close date that’s already passed is a forecast quietly lying to whoever’s reading it.
Unassigned deal
Nobody owns it, so nobody’s chasing it. Revenue with no name against it tends to stay that way.
Missing amount
Invisible revenue — a real deal that your executive forecast is silently excluding.
No activity
Not time-in-stage — real recorded activity. A deal can be brand new in a stage and still have gone quiet.
For teams where someone has to answer for it
An alert nobody acts on is just noise. These are the parts that decide what happens after a rule gets broken.
Escalation that escalates
The rep hears first. If it's still unresolved after the window you set, it goes to their manager, then to a director. You decide the timings.
Stricter rules for bigger deals
Target a rule by deal value, so a £25k opportunity gets a tighter leash than an early-stage conversation. Business-day counting, so weekends don't burn the clock.
Exceptions with an expiry
Some deals are genuinely paused. Snooze one with a reason attached, and it resumes being checked automatically rather than being forgotten.
A weekly digest for managers
One summary email on the day you choose, to whoever should get it — open breaches, revenue at risk, and where the problems cluster.
Breach history that sticks around
"Has this happened before?" becomes a question with an answer — resolution times and repeat patterns by rep and by stage.
Rules applied in one go
Build a policy once and apply it across a pipeline, instead of configuring every stage by hand each time something changes.
Manager escalation and the weekly digest are on Growth and above. Director escalation, deal-value targeting, business-day counting, breach history and policy templates are on Business.
You already have HubSpot. Where does this sit?
HubSpot does surface deals that are moving slowly. The difference is what it's measuring against, and what happens next.
HubSpot on its own
With Pipeline SLA
How a stalled deal gets noticed
HubSpot on its own
A “Stalled Deals” view in the sales workspace lists deals that have sat in a stage at least 20% longer than the average for that same deal owner. Someone has to open the view.
With Pipeline SLA
An hourly scan against the limit you set, and an email to the deal owner when it breaks. Nobody has to remember to go and look.
What counts as too long
HubSpot on its own
Measured against that deal owner’s own average time in the stage — so a rep who is consistently slow quietly raises their own bar.
With Pipeline SLA
A fixed number of days you set, per stage and per pipeline. The same standard applies to everyone.
When nobody acts on it
HubSpot on its own
Workflow notification actions are in-app, internal email, Slack, Google Chat and create-task. HubSpot’s documentation lists no escalation action and no routing based on the owner’s manager.
With Pipeline SLA
The rep first, their manager after the window you set, then a director. Manager escalation on Growth, director on Business.
A record of what broke
HubSpot on its own
SLA goals are documented for help desk tickets and inbox conversations. HubSpot’s SLA documentation does not cover deals.
With Pipeline SLA
Every breach is kept — when it was flagged, when it cleared, how long that took, broken down by rep and by stage. Business plan.
Pausing a deal on purpose
HubSpot on its own
Snooze is documented for help desk tickets, and HubSpot notes it is not available on the ticket record itself. Deals are not mentioned.
With Pipeline SLA
Snooze straight from the alert for 3 or 7 days, with a reason your manager can read. It resumes being checked on its own. All plans.
What it takes to set up
HubSpot on its own
A workflow can enrol deals on the “Time in current stage” property, so a version of this can be hand-built — per stage, per pipeline. Workflows need a Professional or Enterprise subscription.
With Pipeline SLA
Pick a pipeline, pick a stage, type a number of days. From £49/month.
HubSpot behaviour described here is taken from HubSpot's public product documentation at knowledge.hubspot.com and was checked on 18 September 2026. HubSpot changes its features and subscription tiers from time to time. Pipeline SLA is an independent app and is not affiliated with or endorsed by HubSpot, Inc.
How it works
1
Connect HubSpot
Authorize read access to your pipeline. It never edits or moves anything in HubSpot on its own.
2
Set your SLA rules
Per stage, per pipeline: how long is too long, and what counts as a warning sign.
3
Get alerted before it's too late
An hourly scan flags breaches, emails the rep, escalates to a manager if it's still unresolved — and suggests a re-engagement message when a deal's gone quiet.
Plans from £49/month
Every plan includes a 14-day free trial with full access — no card required to start.
Compare plansHow healthy is your HubSpot pipeline?
Answer 8 quick questions and get a score out of 16 straight away, with the areas most likely to need attention. No signup needed.
Take the health check