Sales Pipeline Aging: A 30-Day Deal Review System for Indian B2B Teams

Sales pipeline aging helps you find deals that have stopped moving before they distort your forecast. Here is a practical system for Indian B2B teams.What sales pipeline aging measuresPipeline aging tracks how long an open opportunity has existed and how long it has remained in its current stage. Those are different numbers. A deal created 60 days ago may have moved to proposal yesterday. Its total age is 60 days but its proposal-stage age is one day. Both matter. Total age shows the overall selling cycle; stage age helps managers find stalled work. A B2B founder who only checks pipeline value may believe there is ₹40 lakh of potential revenue without noticing that half the deals have stopped progressing.Build a simple stage modelUse stages that match observable buyer actions, not a sales representative's optimism. A small industrial supplier might use Qualified, Requirement Confirmed, Technical Review, Quotation Sent, Negotiation, Won and Lost. Define what evidence is required before moving a deal forward. A verbal “looks good” is not the same as a signed purchase order. Record the stage entry date whenever a stage changes. Preserve the earlier stage history rather than overwriting it, or the team will lose its ability to calculate dwell time.The three formulas to calculateMetricFormulaUseTotal deal ageToday minus creation dateFind long-running opportunitiesStage ageToday minus stage-entry dateSpot stage-specific delaysStage aging ratioStage age divided by stage benchmarkCompare against your own historyFor example, a quotation has been open for 18 days. The team's historical median for that stage is 12 days. The ratio is 18 ÷ 12 = 1.5. It has spent 50% longer than the median. That does not prove the deal is lost. It tells the owner to investigate. Use working days or calendar days consistently, and label which method you use.Why averages can misleadA few very old deals can distort the average. Imagine five proposal-stage deals aged 3, 4, 5, 6 and 42 days. Their mean is 12 days, but their median is 5 days. A benchmark based only on the mean could hide a deal that is taking unusually long. Calculate both median and a high percentile if the sample is large enough. Segment by product, deal size, customer type and channel. A government procurement opportunity may follow a very different cycle from a repeat order by a private distributor. Do not compare them without context.An example for an Indian B2B companySuppose a Pune equipment distributor has 30 open opportunities worth ₹60 lakh. Twelve opportunities worth ₹18 lakh are older than the team's historical stage benchmark. Another six worth ₹15 lakh have no confirmed next meeting or customer action. The owner should not assume that ₹33 lakh is lost, because the groups may overlap. Instead, create a deduplicated review queue and record why each deal has stopped. Common causes include pending technical approval, buyer budget review, an incomplete quote, competitor evaluation and missing decision-maker access. Assign a concrete next action to each opportunity.A spreadsheet you can build todayUse one row per opportunity with columns for opportunity ID, company, owner, product, estimated value, stage, created date, stage-entry date, expected close date, next customer action, next-action date, last meaningful customer interaction, loss reason and confidence note. Use formulas to calculate total and stage age. Add a separate history tab if deals move between stages. Protect date fields from accidental edits. Use filters to find deals with stage age above your chosen benchmark, missing next actions or close dates repeatedly pushed into the future.Set useful review triggersA trigger should prompt investigation, not automatic blame. For example, flag a proposal after 14 days if that is materially above the team's normal cycle, flag any deal without a documented next customer action, and flag deals whose expected close date moved three times. These are example operating rules, not industry benchmarks. For a low-volume sales team, review individual cases weekly. For a larger team, compare segments and watch whether a specific stage consistently becomes slower. If many deals stall after quotation, examine pricing clarity, technical documentation and follow-up quality before demanding more calls.Distinguish activity from progressA salesperson can send five reminders without moving a deal forward. Progress means the buyer has completed a meaningful step, such as confirming requirements, introducing the procurement owner, scheduling a technical evaluation or approving commercial terms. Record the date of the last meaningful customer action separately from the date of the last salesperson activity. This prevents a busy pipeline from appearing healthy when customers are not advancing. Ask the team what evidence would change its forecast, and keep that evidence in the CRM or spreadsheet.A 30-day improvement planWeek 1: export all open opportunities and clean duplicate records. Define stages and required entry evidence. Week 2: calculate total age, stage age and stage medians from recent completed deals. Review obvious exceptions. Week 3: assign next actions to every stalled opportunity, close genuinely inactive records with honest reasons, and check whether proposals need clearer scope or pricing. Week 4: compare the age distribution with the baseline, review wins and losses, and agree on one stage-specific process improvement. Repeat the review monthly and retain the baseline so the team can see real change.Measure business impact carefullySuppose the team reduces the median proposal-stage time from 15 days to 11 days. The change is four days, or 26.7% of the original 15-day period. That is a process improvement, not automatically a 26.7% revenue increase. To understand commercial impact, also measure the proportion of deals that reach a decision, win rate, realised gross margin and the time from initial qualification to cash collection. If faster follow-up increases discounting, speed alone may not improve profitability.Common mistakesDo not delete slow deals simply to make the dashboard look better. Do not treat every old deal as a bad deal. Do not allow reps to reset stage-entry dates to avoid aging alerts. Do not count a meeting booked by the seller as a customer commitment until the buyer confirms it. Do not use a single stage benchmark for radically different deal types. Do not forecast a deal solely because it has a large value. Review data quality before discussing team performance.FAQsWhat is a good pipeline aging benchmark?There is no universal number. Start with your own completed deals, segment by deal type and use a median stage duration as a working reference.Should weekends count?Either method can work. Choose calendar days for elapsed time or working days for operational response time, then stay consistent.How do I handle deals waiting for tender decisions?Tag them as a separate segment with documented milestones rather than forcing them into a short commercial sales cycle.Can a spreadsheet replace a CRM?For a small team it can support the first version. A CRM becomes useful when activity history, permissions and multi-user updates become difficult to manage.Start with five opportunitiesTake the five oldest deals in your current proposal stage. For each, identify the last buyer action, the current blocker, the decision owner and the next dated step. If you cannot identify a next step, revisit the qualification rather than assuming the deal will close. This small weekly habit can make your pipeline review more useful than another high-level revenue forecast. For related foundations, read Nitross's published guides on sales forecasting and B2B proposal win rate.