Half the pipeline is deals nobody wants to mark lost. They sit at the same stage for months, still counted at full value.
AI solution 10 · Pipeline intelligence
Dead deals inflating the forecast
Every deal that has not moved in 60 days flagged for a decision, and the forecast rebuilt on stage probability instead of rep optimism.
Custom app · Forecast
Every deal that has not moved stage or seen real activity in 60 days is flagged and needs a decision, and the forecast is rebuilt on stage probability instead of rep optimism.
A forecast the founder can trust, and no dead deals to hide behind.
The problem
The forecast is inflated, sales reviews are spent discussing deals that died long ago, and the founder has stopped trusting the number.
Why it happens
- Marking a deal lost feels like admitting failure, so reps leave it open.
- Most CRMs do not force a decision when a deal stops moving.
- Forecasts that sum deal values at face value reward optimism.
How the system works
- 01
Detect stalled deals
Any deal with no stage change and no real activity in 60 days is flagged. The threshold can be set per pipeline.
- 02
Force a decision
The owner is asked to move it forward, set a dated next step or close it as lost, with a reason.
- 03
Weight the forecast
Open deals are valued by the probability of their stage, based on your historical conversion, not by the full deal amount.
- 04
Report the change
Managers see stalled deals by owner and the gap between the raw and the weighted forecast.
Where AI does the work
Rules first, AI second. The model runs only where judgement on text is needed, so running costs stay low as volume grows.
Flagging stale deals
Days since last movement is a simple rule, so no model is involved.
Weighted forecast
Stage probabilities come from your own history and are calculated, not guessed.
The decision on each deal
Whether a deal is alive is the rep’s and manager’s call.
What changed
- A forecast the founder can actually trust.
- Sales reviews spend time on live deals, not dead ones.
- Reps can no longer hide behind deals that died months ago.
Works with your stack
Works inside Zoho, HubSpot, Salesforce, Pipedrive or Freshworks, using the stages and activity you already record.
Nothing is replaced. It is a layer on top of the tools you already use, built on your accounts, so the data stays yours.
Questions
Why 60 days?
It is a sensible default for B2B cycles. Long project sales may need a longer window, and transactional sales a shorter one. It is set per pipeline.
Will this make our pipeline look smaller?
Usually yes, at first. The pipeline that remains is real, which is the point.
Where do the stage probabilities come from?
From your own closed deals: how often deals at each stage went on to be won. They update as more deals close.
What does it cost to run?
We build it in your own environment, and the AI runs on your own Google (Gemini) or OpenAI account. You pay them directly, pay as you go, only for what is used. We add no markup and charge nothing per message or per seat. Because rules handle most of the work before any model is called, the AI bill stays small.
Running cost and data
What it costs to run
We build the system in your own environment. You pay only for the AI it uses, directly to the AI provider, with no markup from us.
The system is set up in your own cloud account. Conversations, recordings and CRM data move between your systems and the AI provider you choose. They do not pass through our servers or a separate chatbot platform.
The AI runs on your own account with Google (Gemini) or OpenAI. You pay them directly, only for what is used, at their published rates.
We do not resell AI usage or charge per message, per conversation or per seat. Our fee is for building and improving the system, and it is agreed upfront.
Rules and plain code do most of the work, and the model is called only where judgement on text is needed, so the AI bill stays small as volume grows.
WhatsApp and calling charges, where they apply, are billed by your provider as they are today.
Related solutions
An analysis layer on top of the CRM that answers the questions it never could: which sources close, which industries you win, and where deals die.
Read the case study →09 · Pipeline intelligencePipeline buried in inboxesTeam inboxes checked for conversations with companies the CRM does not know about, with new contacts created from email signatures in one click.
Read the case study →13 · Team performanceNo way to see who is dropping leadsOne scorecard per rep, pulling from every tool the team uses, so the sales head can see who responds fast, who converts and who lets leads go cold.
Read the case study →Sound familiar?
Thirty minutes is enough to map where leads come from and where they drop off. If there is a fit, you get a short written diagnosis of the two or three problems worth fixing first, with a rough investment range.