A score compresses a pursuit. A read explains it.
The difference matters because a score can rank work without helping a team decide what to do. A pursuit can receive a low score for several unrelated reasons: no urgent consequence, weak authority, stale evidence, an untested proof plan, or a paper path nobody owns. Those conditions should not produce the same response.
The Pursuit Read is a compact operating narrative. It tells the team what is happening, why that interpretation is credible, where it may be wrong, and which move could improve the outcome.
Begin With the Customer Change
The first sentence should name the change the customer is trying to make.
Not the product being evaluated. Not the seller's opportunity name. Not a generic pain statement. The read should describe the customer-side transition in language that a person inside the account could recognize.
The customer may be trying to reduce a risk, recover a missed target, coordinate a fragmented process, protect a strategic initiative, or make a decision that has become politically difficult. The exact language matters because it sets the standard for every claim that follows.
If the team cannot state the change, it may have an interested account without a coherent pursuit.
Name the People and the Work
The read should then explain the buyer room.
Who experiences the consequence? Who can allocate resources? Who can block the decision? Who translates the problem across functions? Who is doing work when the seller is absent? Which necessary role is still missing?
Titles help, but behavior matters more. A senior person who attends one call may contribute less authority than a director who can assemble finance, operations, and security around a shared decision. A friendly contact may provide access without carrying the pursuit. A skeptical reviewer may become essential because their objection defines the proof the room must trust.
The read should preserve those distinctions instead of flattening everyone into stakeholder labels.
Separate Evidence From Interpretation
Every read contains inference. The discipline is to mark it.
Evidence is what happened: a person shared a document, corrected a number, invited a colleague, named a deadline, rejected a scope, or committed to a proof step.
Interpretation is what the team thinks that event means: urgency is increasing, authority is forming, the champion is mobilizing, the paper path is real, or the pursuit is losing priority.
The interpretation may be sound. It becomes more useful when the team can see the evidence beneath it and the uncertainty beside it.
A good read can contain the sentence, “We may be wrong because…” That is not weakness. It is a decision aid.
Identify the Constraint
A pursuit can contain many imperfections while only a few constrain the next meaningful movement.
The constraint may be an absent economic consequence, a buyer room that cannot coordinate, proof that the skeptical function does not trust, a champion hypothesis that has not produced behavior, or a commercial process without an owner.
Naming every gap creates a checklist. Naming the current constraint creates focus.
The read should explain why this gap matters now and what would become possible if it changed.
Recommend a Move, Not More Activity
The final part is the next move.
A move is not “follow up,” “multithread,” or “get executive alignment.” Those phrases describe categories of effort. A move identifies a person, an action, a reason, and the evidence the team expects to learn or create.
For example: ask the operations owner to bring finance into a working session to correct the cost of delay, because the current case uses seller assumptions and cannot yet survive executive review.
The point is not that this move must work. The point is that the result should update the pursuit. Acceptance creates one kind of evidence. Refusal, delay, correction, or redirection creates another.
A Read Is a Living Argument
The Pursuit Read should change when the customer changes. It should preserve the prior interpretation, the new evidence, and the decision that followed.
That makes it useful to a seller preparing for a meeting, a manager coaching the pursuit, an executive inspecting the forecast, or a new team member entering the work. Each person can see the current argument without inheriting an unexplained score.
The standard is simple: after reading it, can the team explain what is happening and choose a better move?
If not, the pursuit may have more data than judgment.
Source note: This Essay is an authored operating argument derived from The Pursuit. It does not report customer results, external research, or product performance.