A ₹180Cr regional snacks brand. Three consecutive quarters of flat growth despite adding 8 reps. The problem was not the team, the territory, or the market — it was four simultaneous execution failures visible in the data the field force was already generating every day.
"The explanations kept changing. Three consecutive MBRs, three different root causes for the same trend in the same territory. The data was right in front of us the whole time — we just weren't reading the right signals."
The brand had everything it needed to grow. A full field force of 48 reps across Bihar and Jharkhand. 57 distribution points covering 12,000 outlets. Numeric coverage above 75% — consistently presented as a positive in every quarterly review. The leadership team had approved a growth plan. The field team was executing it. The dashboard looked reasonable.
Then three quarters passed without meaningful growth. The business was not in trouble in any visible sense — but growth had flatlined at a point where the network size, the field investment, and the category opportunity all suggested it should have been accelerating.
The previous six months had seen eight new reps added to the network. More coverage, more visits, more growth — the logic was sound. The additional reps arrived, were deployed into existing beat structures, and the growth curve stayed flat. The diagnosis shifted from training to market conditions to distributor quality. Each produced its own action plan. None changed the number.
"Every metric on the leadership dashboard looked reasonable. Reps were hitting visit targets. Distributors were processing orders. Nobody had a clean explanation that survived two MBRs in a row."
When I pulled the beat-level SFA data against outlet revenue — not the summary dashboard, the raw transaction log — the picture was immediately different from what any of the review decks had shown. Not because the dashboard was dishonest, but because it was measuring the wrong things.
When I mapped each rep's beat against outlet revenue contribution, the misalignment was significant. High-volume outlets were receiving visits at the same frequency as low-volume outlets. Some were being visited less. The reps were not underperforming. They were being sent to the wrong places in the wrong order. The 5x output gap between best and worst performers on the same beat disappeared almost entirely once the deployment logic was corrected.
Primary billing was clean — that's the number in the monthly review. But when I cross-referenced billing velocity against secondary sell-through data, three distributors had ratios pointing to serious stock accumulation. One was sitting on inventory equivalent to 74 days of normal movement. Cashflow was locked. The field team was pushing; the market was not pulling. Expiry claims were quietly rising. Retailer reorder rate in that DP's area had thinned 18% over the quarter. All of it was in the data.
The coverage number looked excellent. 76% of 12,000 outlets stocking the brand is a genuinely good result. The problem: numeric distribution counts every outlet equally. Weighted distribution measures presence by actual volume contribution. The brand was present in 76% of outlets but only 42% of the volume — consistently present where it mattered least, underweighted in the high-throughput outlets where market share is decided daily. The coverage number was real and completely misleading at the same time.
The SFA system was generating beat-level data daily — GPS logs, visit timestamps, order values, SKU coverage per outlet. All of it existed. None of it was reaching the leadership table in a form that allowed action. By the time a field execution failure appeared in a review deck, it had been running for three weeks. The window to intervene before it compounded had already closed. The problem was never data collection. It was wiring and cadence.
On the data: All four findings came from data the field team was already generating — SFA check-ins, GPS timestamps, distributor billing records, secondary sell-through reports. No new data collection was required. The diagnostic is entirely about reading the right signals from what already exists.
The 90-day engagement involved four specific corrections — one per signal. No restructuring. No new hires. No territory changes. No pricing moves. No new product launches. The team, the territory, and the strategy remained identical throughout.
Beat structures were rebuilt around outlet revenue contribution, not historical routes. The three cashflow-locked DPs were identified, rebalanced, and stabilised, with forward monitoring wired to the review cadence. Weighted distribution gaps were mapped and rep priorities adjusted to address the underserved high-volume outlets. The review cadence was rebuilt on a weekly signal dashboard, bringing the lag from 21 days to 5.
None of these corrections required headcount. They required visibility. The data to make every one of these decisions had been sitting in the SFA system — generated daily by the same 48 reps — for the entire period the business was flat.
The numbers below are the actual before-and-after from the network — not projected, not modelled.
5x output gap. Corrected by rebuilding deployment around outlet revenue, not route history.
3 of 57 DPs in cashflow lock. Identified in week 1. Rebalanced by week 6. No commercial renegotiation required.
Numeric 76%, weighted 42%. A 34-point gap hiding behind a healthy headline number.
21-day lag → 5 days. Using data already being generated. No new tools required.
"We'd been looking at the same numbers for eight months trying to explain the gap. The explanations kept changing. In 90 days the picture completely changed — and the explanation stopped being necessary."
— National Sales Head · Regional Snacks Brand · Bihar & Jharkhand
The most important thing about the Bihar engagement is not the 2.1x result. It's the source. Every data point that led to every correction in this engagement was already being generated by the field team, every day, through normal SFA usage. No new surveys. No new data collection. No additional rep training. No new technology platform.
The four-signal framework is not a data collection exercise. It is a signal extraction and wiring exercise — reading what is already there, surfacing the four signals that determine field execution outcomes, and connecting them to the decisions that need them at the frequency those decisions require.
If your field team is using SFA, the signals exist. The question the diagnostic answers is whether they are currently readable by the people who need to act on them — and whether they are arriving in time to act before the leakage compounds. In most GT networks running at this scale, the answer to both is no.
The Bihar network was not unusual. Over-dumping DPs, beats built on historical routes, numeric distribution masking weighted gaps, review lag allowing compounding — this pattern appears in some combination in every GT-heavy network that has stopped growing despite a full field force. The variables are severity and combination. The signals are always the same four.
The diagnostic tool maps leakage across all four signals using your actual network inputs. Most leaders who run it are on the phone within the week — not because anyone asked, but because their own number made it obvious.
Three numbers from your last quarter. The tool maps your estimated leakage across S1 through S4. Under 5 minutes. Your result is yours — no follow-up unless you want one.
Run the DiagnosticYou describe your network. I tell you whether what you're seeing matches the four-signal pattern and whether a Decode engagement would change the picture. No pitch. No prep required.
Book Discovery CallNo obligation. No pitch. The diagnostic is free. The call is 45 minutes.