Understanding Pre-Call Research Challenges

Imagine an account executive whose first meeting of the day is with a prospect she has researched carefully. The remaining meetings arrive one after another, and by mid-morning she is no longer reading anything before she dials in. She knows this is a loss. Research before a call helps her understand who she is speaking with and what might matter to them, yet the schedule leaves her no room to do it well.

This pattern is the subject of this article. Before reading on, pause and ask yourself a question: if an AE wants to prepare for every call, what would have to be true about her day for that to be possible? Keep your answer in mind as you work through the constraint that shaped the problem.

In a real project, six discovery interviews were conducted during early scoping work, three of them with AEs at different levels of tenure. The AEs reported that they prepared for the first call of the day, skipped preparation for the rest, and felt uneasy about the gap. The useful question is not why the AEs were careless. The useful question is what constraint made skipping rational, and what a tool would need to do to remove that constraint.

The skipping was not caused by a lack of motivation. It was bounded by volume. Each AE was expected to take between eight and twelve calls a day. That range matters because it sets how many separate research sessions a day would be needed if every call received its own preparation.

The second number made the problem concrete. The existing research process took fifteen minutes for each call, and the AEs had only fifteen minutes between calls. Put side by side, the two figures leave almost no slack: the research step alone consumes the entire gap the AE has available. Any preparation beyond that point has to be taken out of time the AE does not really own.

Read the timeline as a question about time ownership. The research step and the gap have the same length, so any extra preparation has to be taken from time the AE does not control. The diagram illustrates the constraint; it does not show the AE being careless. The source describes the intended change as a shift in who carries the preparation load, not as a change in how much the AE cares about preparing.

The scope agreed with the project sponsor was deliberately narrow. It was called the first slice, and it asked for one specific output: a pre-call briefing agent that produces a one-page brief twenty minutes before each scheduled call. The brief is delivered to the AE's email and to Slack. Three parts of this definition each answer a separate design question: what the agent produces (a one-page brief), when it runs (twenty minutes before a scheduled call), and where the output is delivered (email and Slack).

The source does not describe how the brief is assembled internally, and this article will not guess at it. What the scope does establish is the pipeline's outer shape: a scheduled call triggers a brief, and the brief reaches the AE through two channels before the call begins. Notice that the delivery timing is part of the requirement. A brief that arrives after the call has started would fail the purpose of the first slice.

A briefing agent can be judged in more than one way, and the project chose two measures that answer different questions. The first is a self-reported usefulness score on a scale from 1 to 10, which the AE gives after using the brief. It captures the AE's own judgment of whether the brief helped. The second is briefing open rate, which tracks whether the brief was actually opened. The source calls the open rate a leading indicator.

The two measures are complementary. The usefulness score depends on the AE's reflection after reading or using the brief. The open rate depends on whether the brief reaches the AE and gets clicked. Neither measure replaces the other, because each is blind to the thing the other reveals.

The two measures work best together. A brief that is opened often but rated poorly suggests that AEs are checking it and finding little use. A brief that is rated highly but rarely opened suggests that the content may be good while the delivery is failing to reach the AE at the right moment. Reading only one of the two numbers hides one of these possibilities.

The validation threshold combines the two measures. The pilot was planned as a two-week run with eight AEs. To pass, the average usefulness score had to reach $\geq 7$, and the briefing open rate had to be $> 80\%$. Both conditions must hold. Meeting one of them is not enough.