A deal has been sitting in “Proposal” for 18 days.
Is that a problem?
Maybe.
For one business, 18 days might be completely normal. For another, it could be a sign that the opportunity has stalled.
That’s what makes sales-stage timing tricky.
There is no universal rule that says a deal should spend exactly five days in one stage, ten days in another, and two weeks in the next.
Your customers, sales cycle, pricing, buying process, and team are different.
So instead of asking, “How many days should a deal stay in this stage?”
A better question is:
“What does normal look like for our business, and when does a deal become an exception?”
That answer is already hiding in your CRM data.
Why Time in Stage Matters
Sales stages are supposed to represent progress.
A deal moves from one stage to another because something meaningful happened.
Maybe the prospect completed a discovery call.
Maybe the decision-maker was identified.
Maybe a proposal was sent.
Maybe the customer agreed to review the contract.
When deals consistently spend too much time in one stage, something may be getting in the way.
It could be:
- The customer needs more information.
- The salesperson hasn’t established a clear next step.
- The opportunity wasn’t properly qualified.
- A decision-maker hasn’t been involved.
- Pricing is creating hesitation.
- An internal approval is taking longer than expected.
- The stage itself is poorly defined.
The important point is that time in stage is a signal, not a verdict.
A deal being in a stage for 14 days doesn’t automatically mean something is wrong.
It means the deal is worth looking at.
Don’t Start With an Industry Benchmark
One of the easiest mistakes is searching for a generic answer.
For example:
“How long should a B2B deal stay in the proposal stage?”
You may find benchmarks suggesting a certain number of days.
But benchmarks can be useful for context without being useful for managing your actual pipeline.
Imagine two companies selling similar services.
Company A typically closes deals in three weeks.
Company B typically takes three months.
If both companies use a 14-day rule for every stage, one may be flagging perfectly healthy deals while the other may be waiting too long to investigate problems.
Your own historical data is usually a better starting point.
Step 1: Look at Deals That Actually Moved Through Your Pipeline
Start with closed deals from the past 6–12 months.
You don’t need a complicated analytics project.
For each stage, look at how long successful opportunities spent there.
For example:
| Sales Stage | Deal 1 | Deal 2 | Deal 3 | Deal 4 | Deal 5 |
|---|---|---|---|---|---|
| Qualified | 3 days | 5 days | 4 days | 8 days | 4 days |
| Discovery | 7 days | 10 days | 6 days | 14 days | 8 days |
| Proposal | 9 days | 12 days | 11 days | 18 days | 10 days |
| Negotiation | 5 days | 7 days | 4 days | 9 days | 6 days |
You can already start seeing a pattern.
But don’t just calculate the average.
The average can be distorted by a few unusually long deals.
Instead, look at the median.
The median tells you the middle value when your deals are ordered from shortest to longest.
That often gives you a more realistic picture of what a typical deal looks like.
Step 2: Find the “Normal” Range
Once you have your historical data, look for a reasonable range rather than one rigid deadline.
For example, you might discover:
Proposal stage
- Typical: 7–14 days
- Longer than normal: 15–21 days
- Needs investigation: 22+ days
This doesn’t mean every 22-day deal is bad.
It simply gives your team a point at which to ask better questions.
That’s an important distinction.
The goal isn’t to create a rule that forces every deal to move at the same speed.
The goal is to create a useful signal when something falls outside the normal pattern.
Step 3: Separate Healthy Delays From Process Problems
This is where the numbers become more useful.
Suppose your data shows that most proposal-stage deals take around 10 days.
One opportunity has been there for 24 days.
Don’t immediately tell the salesperson:
“Move this deal.”
Instead, ask:
Why has it been there for 24 days?
Maybe the customer is waiting for a board meeting.
Maybe the proposal is being reviewed by three departments.
Maybe the salesperson has a confirmed meeting scheduled for next week.
In that case, the deal may be healthy.
Now consider another 24-day opportunity.
There is no scheduled follow-up.
The last activity was three weeks ago.
The salesperson isn’t sure who the decision-maker is.
That’s a very different situation.
Same number of days.
Completely different problem.
This is why stage aging should trigger a conversation, not an automatic conclusion.
Step 4: Look at Time in Stage by Outcome
Here’s where your analysis gets much more interesting.
Don’t only ask:
“How long do deals spend in this stage?”
Also ask:
“How long do won deals spend here compared with lost deals?”
For example:
| Outcome | Median Time in Proposal |
|---|---|
| Won | 11 days |
| Lost | 24 days |
| Still Open | 31 days |
That doesn’t prove that longer proposal times cause deals to be lost.
But it gives you something worth investigating.
You might discover that deals extending beyond a certain point are more likely to:
- Lose momentum
- Go quiet
- Require repeated follow-up
- Get pushed into the next month or quarter
- Eventually be marked lost
Now your CRM isn’t simply storing information.
It’s helping you understand how your sales process behaves.
Step 5: Look for the Stage Where Time Changes
Another useful exercise is to compare stages.
You might discover something like this:
Qualified → Discovery: 4 days
Discovery → Proposal: 8 days
Proposal → Negotiation: 11 days
Negotiation → Closed: 27 days
That last number stands out.
Why does negotiation take nearly a month?
Maybe there are too many approval steps.
Maybe pricing isn’t clear.
Maybe contracts are being reviewed manually.
Maybe the salesperson isn’t getting access to the right decision-maker.
Maybe the stage itself combines several different activities that should be separated.
The point isn’t simply that “27 days is too long.”
The point is that the data tells you where to investigate.
Step 6: Define What Must Happen Before a Deal Moves
Time alone shouldn’t determine whether an opportunity advances.
Each stage should have clear entry and exit criteria.
For example:
Discovery
A deal can move forward when:
- The customer’s problem is clearly understood.
- The solution appears relevant.
- Key stakeholders have been identified.
- A next step is scheduled.
Proposal
A deal enters this stage when:
- The customer has confirmed interest.
- Scope or requirements are understood.
- Pricing or proposal information is ready.
- There is a defined next action.
Negotiation
A deal enters this stage when:
- The proposal has been reviewed.
- The customer has raised specific concerns or requested changes.
- The decision process is understood.
- There is a realistic path toward a decision.
The exact criteria will vary by business.
What matters is that a stage represents something observable.
That makes the time spent there much more meaningful.
Step 7: Turn Stage Aging Into a Useful Workflow
Once you understand your normal ranges, your CRM can help your team monitor exceptions.
For example:
Deal enters Proposal
↓
No movement for 10 days
↓
Create follow-up task
↓
No activity after another 5 days
↓
Notify sales manager
↓
Review opportunity
The automation isn’t making the sales decision.
It’s helping people notice something they might otherwise miss.
That’s a much better use of automation.
Kujenga’s broader approach to automation follows the same principle: technology should support a clearly defined process rather than being added simply because automation is available.
Don’t Automate the Wrong Question
It’s tempting to create a workflow that says:
“If a deal stays in Proposal for 14 days, automatically move it to another stage.”
Be careful.
That may clean up your pipeline visually while making your data less accurate.
A deal doesn’t become “Negotiation” simply because 14 days have passed.
The customer has to actually reach that point in the buying process.
A better automation might be:
“If a deal has been in Proposal for 14 days without activity, create a follow-up task.”
Now technology is supporting the process instead of pretending to understand it.
Review Your Time-in-Stage Rules Regularly
Your sales process won’t stay the same forever.
Your customers may change.
Your pricing may change.
Your team may grow.
You may introduce a new service.
Your sales cycle may become shorter or longer.
So don’t treat your stage-aging thresholds as permanent.
Review them periodically.
A simple monthly or quarterly review can ask:
- Which stages are getting slower?
- Which stages are consistently fast?
- Where are deals being lost?
- Are our stage definitions still accurate?
- Are deals being moved based on actual progress?
- Are there unnecessary steps?
- Are our aging alerts useful or just creating more noise?
The goal is continuous improvement.
Not constant change for the sake of change.
A Simple Framework You Can Use
If you want to start today, use this five-step process:
1. Pull your historical deals.
Look at closed opportunities from the last 6–12 months.
2. Measure time in each stage.
Calculate the median and identify the normal range.
3. Compare outcomes.
Look at how won, lost, and still-open deals behave.
4. Define the exception point.
Choose a reasonable threshold that tells your team when to investigate.
5. Build a response.
Use tasks, alerts, reviews, or automation to make sure exceptions don’t disappear unnoticed.
That’s enough to create a much more useful system without rebuilding your entire CRM.
The Bigger Lesson: Your CRM Should Reflect How Your Business Actually Works
The real value of tracking time in stage isn’t the number itself.
It’s what the number helps you understand.
If deals consistently slow down after proposals, investigate the proposal process.
If opportunities spend too long in qualification, look at your qualification criteria.
If deals move quickly but still have poor conversion rates, examine what your stages actually represent.
And if your numbers are inconsistent because every salesperson uses the stages differently, fix the process before relying on the reports.
This is why sales data and process design are so closely connected.
A CRM can tell you what is happening.
But the business still has to ask why.
The Takeaway
There is no magic number of days that every deal should spend in a sales stage.
The better approach is to establish your own baseline.
Look at historical deals.
Find the typical time spent in each stage.
Compare that behavior by outcome.
Then create reasonable thresholds that help your team spot exceptions.
Most importantly, don’t use those thresholds to force deals through the pipeline.
Use them to start better conversations.
A healthy sales process doesn’t move every deal at exactly the same speed.
It makes unusual behavior visible so your team can understand it and respond.
And when your CRM reflects the real process, your data becomes much more useful for forecasting, coaching, automation, and decision-making.
At Kujenga, we help businesses connect CRM structure, sales processes, automation, and data so their systems support the way their teams actually work. If your pipeline contains a lot of information but still doesn’t give you a clear picture of where opportunities are slowing down, it may be time to look at the process behind the data.
Better visibility starts with better process.
