ACCOUNT INTELLIGENCE · DECISION-MAKING

Incomplete signals are not the same as no evidence.

Why account development does not require perfect information — and why uncertainty must not be mistaken for an opportunity.

Marketing teams routinely make decisions using incomplete evidence. A website visit, job advert or change in buying behaviour rarely reveals a company's full intentions. The practical response is not always to wait for a complete picture. It is to form a testable hypothesis and decide what evidence would make it worth acting on.

The same reasoning may help a supplier understand existing clients. An IT implementation partner already has project records, stakeholder relationships and a view of system adoption. It may also be able to observe developments outside the original project: a new service, a changed delivery model or an acquisition. These are signals, not requirements.

The question is not whether the data is complete

The useful question is narrower: does the available evidence support a specific and consequential question for the client? That requires distinguishing an observation from an explanation. A new location, for example, might represent expansion, relocation or a reorganisation. Each implies different operational consequences. Public evidence alone may not distinguish them.

Nor does a changed business model establish that the implemented software has become inadequate. The relevant response could be a change in process, responsibility, data ownership, capacity or system design — or no intervention.

Account development is not simply marketing with better data

There is a significant organisational difference. Marketers can change campaigns within their own organisation and evaluate outcomes across large groups. An account manager is examining decisions inside another business. The supplier cannot authorise a change in the client's operations, and a poorly framed approach can affect a valuable relationship.

The available information is also fragmented by responsibility. Delivery staff know the system; account managers know the contacts; operations and finance leaders inside the client know the economic constraints. More integration may improve visibility, but it does not automatically assign responsibility for deciding which business questions to pursue.

From observation to a decision

  1. Establish the original scope. What activity, decision or operating assumption was the IT work intended to support?
  2. Record the signal. What exactly changed, according to which source and when?
  3. Consider alternatives. What explanations fit the same observation? What would make the difference commercially important?
  4. Identify the necessary evidence. Which client function could confirm the facts, priorities and constraints?
  5. Apply a stopping rule. Is the next conversation or investigation justified by the evidence and expected value of learning more?

Three conclusions are possible: ask a specific question, do not pursue it on present evidence, or acknowledge that the evidence is insufficient even for a preliminary judgement. None should be recorded as a qualified sales opportunity without client-side validation.

Who owns the next step?

An independent researcher can assess the public evidence and recommend what to check. The implementation partner owns the client relationship and decides whether the question merits contact. The client owns its priorities, internal evidence and decision rights. Keeping those boundaries explicit prevents research from becoming an invented sales forecast.

This is the purpose of a bounded Account Screen for one selected existing client. It does not rank an entire portfolio, monitor every signal continuously or guarantee additional work. If the account team already has enough information to make the decision, a separate review is unnecessary.

Have one selected client and an unresolved question? Check whether the £50 Screen fits before requesting research.

Account Screen · scope and enquiry ↗

All articles ←