Where Revenue Gets Stuck: Find It Without a CRM Rebuild

You can see where pipeline stalls using the CRM you already have — if you stop counting activity and start measuring movement.

Published 2026-07-29 · Data as of 2026-07-29 · Market & data intelligence · Educational, not advice.

Every quarter, a RevOps lead somewhere proposes a CRM rebuild. New stages, new required fields, new automation. The pitch is always the same: once the data is clean, we will finally see where deals get stuck.

The rebuild ships. Reps fill in the new fields for a month. Then the forecast is just as foggy as before, because the problem was never the schema. The problem is that a CRM records state — what stage a deal is in — and says almost nothing about motion. A deal can sit in "Proposal" for ninety days and the CRM will report it as healthy pipeline the entire time.

Stop counting activity. Start measuring change.

The Delta Arc idea is simple: the useful signal is not the number, it is the change in the number. Applied to a pipeline, that means the question is never "what stage is this deal in?" It is "has this deal moved since last week, and in which direction?"

You already have what you need to answer that. Most CRMs stamp a last-modified date, a stage-entry date, and a next-step field. Those three, read together, tell you more than any custom-object rebuild.

Take the stage-entry date and compare it to your typical time-in-stage. A deal that has been in one stage for three times the median is not progressing — it is parked. It does not matter that a rep logged four calls this week. Activity is not motion. A rep making a hundred calls into a dead account is still going nowhere, just loudly.

This is the trap in most pipeline reviews. They reward the appearance of effort. A buyer who sends ten emails and a rep who books five meetings both generate activity, and activity feels like progress. But if the deal has not changed stage, changed close date, or produced a committed next step, nothing has actually moved.

Convert the change into a direction: who owns the next move?

Measuring change tells you a deal is stuck. It does not fix it. The second half of the method is turning that observation into an owner.

Every stalled deal is stuck for one of a small number of reasons, and each reason has a natural owner. The buyer owes you a decision. Your rep owes the buyer a proposal. Legal owes both of you a redline. Finance owes an approval. When a deal stalls, the real diagnostic question is: whose move is it, and how long have they owed it?

Write that down as a field if you have to — "next move owner" and "waiting since." You do not need new stages for this. You need one honest sentence per open deal. If a rep cannot name whose move it is, that is your answer: the deal is stuck because nobody owns the next step, and the review just surfaced it.

This reframes the pipeline review from a status recital into an accountability pass. Instead of walking every open deal, you walk only the ones that have not changed, and for each you assign the next move to a named person with a date. Everything moving gets a nod and a skip.

What this looks like in practice

Pull three columns for every open deal: days in current stage, days since last meaningful change, and the named owner of the next move. Sort by days-since-change, descending. The top of that list is where your revenue is actually stuck, regardless of what the forecast rollup says.

You will usually find that a small number of deals are old, silent, and ownerless — and that they are inflating the forecast because nobody wanted to be the one to slip the date. Naming the owner is what unsticks them. Not a new field. Not a rebuild.

The activity mirage, one more time

It is worth saying plainly because it is the most expensive habit in sales analytics: high activity on a non-moving deal is a warning sign, not a good one. It usually means a rep is working hard on a deal that has already told them no in every way except words. The change metric catches that. The activity metric hides it.

You already own the raw material

None of this requires ripping out your CRM. Stage-entry dates, last-modified stamps, and a next-step field exist in nearly every system. The work is reading them as change over time and forcing a named owner onto every stall.

This is exactly the layer Delta Arc CRM Intelligence surfaces live on top of the CRM a team already runs — the movement, not just the state, and the owner of the next move. But the method stands on its own, and you can start it in a spreadsheet this week.

The next question, once you can see which deals are stuck, is harder: how long should a deal be allowed to sit before it stops counting as pipeline at all? That threshold is where forecast honesty actually begins.