The Monday pipeline review opens the way it always does. Calls are up. Quotes issued are ahead of last year. The lunch-and-learn count is on plan, samples are moving, and the CRM shows more activity logged this quarter than any quarter in company history. Every number on the dashboard is green. The quarter misses anyway. And the room does what rooms do in that situation: it concludes that the market softened, or a few big projects slipped, and it schedules the same review for next Monday with the same dashboard.
That conclusion is almost never examined, because the dashboard appears to rule it in. The team is working. The activity proves it. Therefore, the shortfall must have come from somewhere outside the building.
Here is the harder reading. The dashboard is not lying about the activity. It is answering a fair question that is rarely the most relevant one. “Are we busy?” deserves an answer, and the dashboard gives a good one. But the question the quarter turns on is whether the commercial engine is converting effort into orders, and most dashboards in this channel cannot answer it, because they were built to measure what is easy to count rather than what predicts revenue.
“Are we busy?” is a fair question. It is just not the question the quarter turns on.
Three Ways a Green Dashboard Hides a Failing Process
The failure is not one failure. It shows up in three recognizable patterns, and most commercial organizations are running at least one of them right now.
| Pattern | What happens | Why the dashboard misses it |
|---|---|---|
| The activity ceiling | A rep hits every activity target on the sheet, but the order still doesn’t come. | Activity targets assume a fixed conversion rate. When conversion degrades, nothing on the dashboard registers it. |
| Conversion blindness | Managers can name two or three lost deals from memory, but can’t say where in the funnel deals are dying as a pattern. | The reporting was never structured around stage conversion, only around activity volume. |
| The false comfort | Leadership reports a healthy pipeline-coverage ratio to the board and treats it as a margin of safety. | Coverage is only as honest as the definitions underneath it, and stale or written-off projects rarely get removed. |
Activity targets were set on the theory that effort converts at some assumed rate, and the assumed rate is doing all of the work in that theory. When conversion degrades — whether because the spec is eroding at buyout, because the wrong projects are being quoted, or because a competitor has quietly restructured the multiplier — the rep works harder, logs more, and converts less. A manufacturer tracking spec activity without tracking spec hold rate, the distinction at the center of the Specification Erosion framework, is the textbook case: the design-phase pipeline looks healthy while the order phase quietly underperforms, and nothing on the dashboard connects the two.
The data on seller optimism is not flattering here. XANT Labs, in a 2019 study of 270,912 closed-won opportunities representing over $18 billion in revenue across 18 companies, found that 47 percent of 90-day forecasts missed by more than half, and that when forecasts were wrong, sellers overestimated by an average of $91,000 and underestimated by an average of $47,000. The misses lean, consistently and predictably, toward comfort.
A pipeline that includes projects nobody has touched in six months is not coverage. It is an archive with a dollar value.
This Is Normal, and That Is the Opportunity
None of this makes the channel unusual. It makes the channel typical. Gartner’s State of Sales Operations research found that only 45 percent of sales leaders and sellers have high confidence in their own organization’s forecasting accuracy, and Gartner has separately reported median forecast accuracy among surveyed organizations at between 70 and 79 percent. Read those two findings together. Most commercial leaders, in most industries, are running reviews on numbers they only partly believe. That is not a personal failing in any one company, and it is not a channel failing either. It is a standing opportunity, because the organization that closes the gap between what gets measured and what gets believed ends up with a clearer view of its own future than most of its competitors have of theirs.
Before going further, it is worth granting what is true in the defense of activity measurement, because there is a defense, and in this channel it is a serious one.
Activity metrics exist because effort visibility is a legitimate need, and nowhere is that more structurally true than in rep-driven sales. A manufacturer working through independent agencies cannot see the field. The factory does not attend the specifier visits, does not sit in the distributor meetings, and experiences the territory mostly as a commission statement and a POS report. Activity reporting arose as the honest answer to a fair question from the principal: what are we getting for the commission? The NEMRA Manufacturer of the Future research, built on interviews with more than 30 manufacturer leaders, documents where those expectations now sit: more end-user calling, more specification activity, more demand generation, deeper product expertise. Manufacturers are entitled to visibility into that work, and agencies that provide it strengthen the relationship.
The channel’s reporting conversation, meanwhile, remains anchored even further downstream. The POS reporting standards NEMRA has developed, endorsed by more than 50 distributor entities and 50 manufacturer entities and featured at the 2026 NEMRA Annual Conference, are important and overdue work. But note what layer they operate on. Point-of-sale data is transaction data. It records what already sold, where, and through whom. It is the past, precisely documented. That work should continue. It should not be mistaken for forward measurement.
So the defense holds as far as it goes: activity data answers “is the work being done,” and that question deserves an answer. The trap is not in collecting activity data. The trap is in letting it stand in for the two questions it cannot answer: “is the work converting” and “what is going to happen next.” Those are different questions, they require different metrics, and no volume of activity data, however granular, ever becomes an answer to them.
The trap is not in collecting activity data. The trap is in letting it answer questions it cannot answer.
The Channel Has Been Arguing About This for Decades
This channel does not need the KPI trap explained in the abstract, because it has been living inside the argument for as long as anyone can remember. The channel’s version is the call report, and it may be the longest-running measurement dispute in the rep model. A longtime member writing on MANA’s own platform called it one of the most frequently discussed subjects in the association, and his account contains the whole problem in a single scene: visiting a new principal who had just demanded call reports, the rep noticed a pile of them sitting unread on the sales manager’s desk, asked about it, and got the sheepish admission that the manager had not gotten to them and that the information would be obsolete by the time he did.
Look at what each side is defending, because both are right. The manufacturer demands the reports because it cannot see the field and has a fair claim on knowing how its line is being worked. The rep resists because the reports consume selling time, go unread, and cut against the structural premise of the model itself: an independent agency sells outcomes in a territory, and a principal that starts directing how the agency spends its day has begun managing a sales force it does not employ. MANA’s own guidance to members adds the sharpest detail of all: a sudden principal demand for weekly reports is often a red flag that the agency is on the bubble. In this channel, an escalating appetite for activity data is not just low-value measurement. It is a distress signal in the relationship itself.
Now notice what both sides are actually fighting over: the lowest layer of the measurement stack. The argument is entirely about activity data, who must produce it, and who owns the rep’s time. Neither side wins that fight because the prize is worthless. The information the manufacturer actually wants- the spec hold rate, whether demand is being created, whether the line is going to grow- is not in a call report and never was. The resolution is not a better call report format. It is moving the reporting conversation up two layers, to metrics both parties genuinely want: spec hold rate by project cohort, alternate acceptance by territory, conversion at the stages where the line lives or dies. Those numbers predict the commission check and the purchase order alike. And because they measure what the buyer did rather than how the rep spent the day, they answer the manufacturer’s fair question without putting the principal in the business of managing an agency’s workday.
Neither side wins the call report fight because the prize is worthless. The information the manufacturer actually wants is not in a call report and never was.
The Three-Layer Test
The replacement discipline, for the internal dashboard and for the principal-and-agency reporting conversation alike, is not a longer dashboard. It is a shorter one, sorted honestly into three layers, with each metric forced to declare which layer it belongs to.
| Layer | Measures | Where it belongs | Its limit |
|---|---|---|---|
| Activity | Effort: calls, visits, quotes issued, samples placed, trainings delivered. | The sales manager’s weekly coaching conversation. | Diagnoses only whether work is being done — never whether it’s working. |
| Outcome | Results: orders, revenue, commission income, share in territory. | The scoreboard. | Always history — a problem it shows is already a quarter old. |
| Leading indicator | Observable buyer behavior that reliably precedes revenue. | The layer most dashboards are missing entirely. | Only valid if built on written, stable definitions. |
Four Leading Indicators for This Channel
Leading indicators have a strict definition that most candidate metrics fail: an observable buyer behavior that reliably precedes revenue. Not rep effort. Not rep opinion. Buyer behavior. The distinction matters because effort is controlled by the seller and can therefore be manufactured to hit a target, while buyer behavior can only be earned. Four indicators meet that definition and can be built from data most organizations already have.
| Indicator | What it measures | Why it leads |
|---|---|---|
| Spec hold rate | The fraction of specified projects in a cohort that survive to purchase order. | Announces a revenue miss two to four quarters in advance. |
| Alternate acceptance rate | How often alternates or substitutions are accepted on basis-of-design projects. | Moves before hold rate does — it registers the moment the spec is tested. |
| Second-meeting conversion | The fraction of first meetings that produce a second meeting with a defined next step. | The earliest honest signal that demand creation is actually creating demand. |
| Days from qualified to proposal | Velocity through the front of the funnel, once ‘qualified’ has a written definition. | Lengthening intervals surface funnel inflation while there’s still time to act. |
One condition sits underneath all four, and it is not optional. A leading indicator built on drifted definitions is theater with better vocabulary. If “qualified” means something different in each regional’s spreadsheet, then days from qualified to proposal is measuring the drift, not the funnel. The six-term discipline from Defining “Good” in a Market That Refuses to Stay Still, written definitions for qualified, active, at-risk, won, lost, and dormant, anchored to observable buyer behavior, is the prerequisite for this entire layer. Definitions first, indicators second. In that order, the dashboard starts telling the truth. In the reverse order, it tells the same lies with more precision.
A leading indicator built on drifted definitions is theater with better vocabulary.
The Audit
The full dashboard audit is a one-page exercise, and it is worth running formally with the leadership team. But its essence fits in a single question, and the question can be asked this week, in the next pipeline review, of any metric on the screen:
If this number improved by 20 percent and nothing else changed, would we confidently expect more revenue in the next two quarters?
Ask it of the call count. Ask it of quotes issued. Ask it of the coverage ratio, honestly, knowing what is actually in the pipeline it summarizes. Most metrics on most commercial dashboards fail the question immediately, and the ones that survive it are, almost without exception, either outcomes or genuine leading indicators tied to buyer behavior.
A dashboard is not a report. It is a theory of how the business makes money, expressed in numbers. When the numbers are green and the revenue is flat, the theory is wrong, and no amount of additional activity will fix a wrong theory. The organizations that get this right do not measure more. They measure less, define what they measure in writing, and reserve the word “indicator” for things a buyer did.
That is the work. It starts with sorting the current dashboard into its three layers, and it usually ends with a shorter, quieter, far more honest Monday meeting.
