Pipeline
A pipeline review runs on whichever deals somebody remembered.
Which is not the same set as the deals that need it. The ones that need it are quiet — nobody raises a deal that has been sitting still, because raising it invites the question.
So the screen has to find them without being asked.
Three axes
A deal can be fine on two of them and still be the one to talk about.
How long it has been sitting where it is. What the recorded calls on it sounded like. And where its owner has placed it in the forecast.
They are independent on purpose. A deal that is moving and sounds healthy but has been parked in commit for six weeks is a different conversation from one that has gone quiet and sounds bad — and a single blended score would make them look alike.
| Deal | Owner | Stage | Days in stage | Calls |
|---|---|---|---|---|
| Okonkwo Industries | A. Mensah | Negotiation | 34 / 14 | Critical |
| Halvorsen Group | R. Ellis | Proposal | 22 / 14 | At risk |
| Tamura Logistics | A. Mensah | Qualified | 19 / 14 | No calls |
| Beaumont Partners | S. Iyer | Proposal | 16 / 14 | Healthy |
- The chips carry counts before you click —
So the shape of the quarter is readable without filtering — nine stale, four critical on calls.
- No call evidence is its own answer —
A deal with no recorded calls reads as exactly that, rather than borrowing a healthy band it has not earned.
- The band opens into the calls —
Which objection went unanswered, which way sentiment moved, how long the silence has been — each with the sentence that was said.
Being straight about this one
Two things on this screen are not yet what they should be.
The forecast chips do not filter anything. Commit and best case are derived from probability today, not set by the rep — so filtering on them returns nothing. The chips are there; the control that would populate them is not connected. It is the single most visible gap in the sales-management surface and it is on the list.
The staleness badge on this screen rounds differently from the filter behind it. A deal a fraction over the threshold can appear in the stale list without being marked stale in its own row. The rule is right; this one screen re-implements it instead of asking, and the two have drifted.
Neither is hard to fix and neither is hidden. We would rather you read it here than notice it in a review.
- It is one query, not a screen full of widgets —
Every deal, joined against all three axes at once, so the filters compose rather than fighting each other. Stale and critical on calls is one answer, not two lists to cross-reference by hand.
- Sorted so the worst reads first —
Deals with no call evidence sort last rather than appearing as healthy — an absence of information is not a good sign, and it should not look like one.
- The threshold is shown beside the count —
Thirty-four against fourteen, rather than a red number you have to remember the meaning of. A manager reading somebody else's pipeline does not know what threshold that team set.
›Can a rep see this, or only a manager?
It follows the same visibility rules as every other list — you see the deals you can see. A rep opening it sees their own.
›Does it notify anyone?
No. Nothing on this screen sends a message. The stale nudge goes to the deal's owner overnight; a deal crossing into critical on calls sends nothing at all, to anyone.
›Can I save a view of it?
No. There are no saved views anywhere in the CRM yet — the filters are chosen each time.