At a glance
Reconstruct one buying decision by separating recorded events, what participants report and your interpretation. Look for the evidence that helped or blocked a decision, then identify a practical improvement. An incomplete journey can support useful learning without supplying exact channel revenue.
A prospect arrives through a direct enquiry, mentions a colleague’s recommendation and later refers to a guide discussed internally. Those observations can help explain how the account evaluated you. They do not establish a complete sequence or the share of revenue caused by each interaction.
The useful investigation starts with the decision: what was the account trying to resolve, which evidence mattered and what remained unanswered? It should produce a better next action, not a reconstructed journey more precise than the available records.
Check whether the missing information is recoverable
First inspect the journeys you control: campaign links, redirects, recorded conversions and CRM associations. Google Analytics describes direct traffic as traffic without a clear referral source. Do not label the whole category as word of mouth or private content sharing.
Record tracking changes and their dates. A new integration may reveal events that were previously missing without any change in buyer behaviour. Keep that measurement change separate from a campaign effect.
Assemble three kinds of evidence
Recorded events include dated responses, requested assets, meetings and CRM milestones. Preserve the original dates and the units involved: person, account or opportunity.
Participant accounts describe what a buyer or colleague remembers. Retain their wording and the date of the conversation. One person’s explanation may not include work done privately by other stakeholders.
Interpretation connects those observations to a proposed explanation. Write it separately so another reviewer can disagree without disputing the underlying records. A guide mentioned in a meeting may have helped the discussion; that does not mean the guide caused the purchase.
Follow a worked reconstruction
In a fictional account, the CRM records an enquiry on 4 June and an evaluation meeting on 18 June. The respondent says a colleague shared a planning guide. Meeting notes show repeated questions about who would own implementation. The account subsequently requests a responsibilities outline before agreeing the next workshop.
The evidence supports three narrow findings: the guide was reportedly shared; implementation ownership was a recorded concern; and the responsibilities outline was requested as part of the next decision. It does not establish when everyone first encountered the business or what would have happened without the guide.
The editorial response is to examine whether the guide adequately explains implementation responsibilities. Add a clear treatment if it is missing, then ask sales to record whether the revised material answers that recurring question. The intended improvement is a better-supported evaluation, not a promised percentage uplift.
Also record an alternative explanation: perhaps the original guide already covered responsibilities but the participants had not read that section. The remedy could be navigation or a more relevant follow-up message rather than new content.
Use published case evidence at the right level
Our focused ABM case study describes account-specific sales materials and preparation informed by successive conversations. It reports progression into tailored pilots. That delivery account illustrates how customer feedback can shape the next piece of evidence, while the reported outcomes remain programme-level observations.
It does not tell us which individual asset caused a pilot, and it should not be used to fill missing events in another account’s journey. Use the mechanism as a question to investigate: what did the team learn in a conversation, and what changed in the next interaction?
Include accounts that stalled or chose another supplier
A review drawn only from enthusiastic customers will miss evidence about objections and failed explanations. Where access permits, include progressed, stalled and lost accounts selected under a stated rule. Record unavailable feedback rather than silently excluding it.
Ask neutral questions about the decision: what needed resolving, which information was useful, what was unclear and whose input mattered? A simple source question answers a different task. The Dreamdata self-reporting experiment is a useful vendor example of the limitations of remembered discovery, not proof that buyer conversations have no value.
End with one change and an observation plan
For each review, retain the decision, evidence, unresolved question, proposed change, owner and review date. A content improvement, a new stakeholder introduction or a clearer implementation discussion can be justified without assigning invented channel credit.
Compare subsequent cases carefully and retain negative evidence. If the same concern persists, inspect whether the response addressed it and whether it reached the right responsibility. Do not respond automatically by distributing more content.
Use our account-progression guide for the accompanying measures and account-based experience methodology for how research informs the approach. Discuss an account challenge with ABM Logic when the missing piece is the evidence needed for the next decision.
