How account development works before an opportunity exists

The route that begins with a client request

An existing client may ask for a reporting change, an integration or a new application capability. The request gives the account team a starting point. There is someone to speak to, a current problem to clarify and usually a reason the work has become relevant now.

The partner still needs discovery. A requested feature may be a good solution, a temporary workaround or a symptom of a larger operating problem. But the client has already initiated the conversation, so the immediate task is to establish the outcome, scope, decision owner and commercial conditions.

This is demand-led development in a practical sense: the account team responds to a need that has entered the relationship. It is efficient because the client has supplied the initial signal. It can produce valuable work without necessarily expanding the partner’s understanding of the client’s wider business.

The route that begins before the client asks

Another kind of account development starts with a change in the client’s business rather than a request for work. A distributor may enter a new market while its IT partner is still occupied with the existing ERP rollout. That move may change the economics of fulfilment, customer acquisition or service. Nothing in the implementation backlog necessarily records those questions.

The first task is to establish what has changed and whether it could alter a decision in the client’s business. Opening another depot, for example, does not by itself justify an IT conversation. If it changes how stock is allocated or who can commit delivery dates, there is an operating question worth testing. Public evidence still cannot show whether the move is a trial, a replacement for an existing facility or a priority for the client. Without a plausible decision behind it, the announcement remains background information.

Here the account team has to produce or obtain information before there is a specific commercial action to take. The work is research-led only in the sense that investigation supplies the initial reason for a conversation. Once the client confirms a need, the two routes can converge into the same discovery and qualification process.

One account can contain both routes

Consider an illustrative ERP partner working with a distributor. The Sales Director asks for a report showing customers who buy some product categories but not others. This is an explicit request. The partner can establish whether the underlying data are reliable, define the report and agree how the sales team will use it.

The report may reveal unpurchased categories, but it cannot establish that a customer should buy them. The customer may have no use for the products, buy through a central purchasing agreement or be uneconomic to serve. That is the distinction between product white space and a business opportunity.

Now suppose the same distributor begins advertising regional fulfilment roles and launches a new delivery promise. Those changes are not a request to the ERP partner. They may justify investigating whether the distributor’s service model is changing and what that could mean for cost, capacity and decision rights. The answer might involve pricing or operating policy rather than software.

The reporting request can be scoped with the existing commercial sponsor. A discussion about the delivery model may require Operations and Commercial leadership. The two lines of work concern the same client, but they differ in what is known, who can authorise a decision and what the supplier is entitled to infer.

Why the second route needs explicit ownership

A delivery request has a visible origin, an owner and usually a deadline. An uninvestigated change in the client’s market may have none of those things. If account managers are expected to find every reason for future work while also managing live projects and revenue targets, the research competes with activities that already have defined consequences.

That arrangement is not evidence of poor account management. The incentives and the available information favour issues arriving through existing contacts. A CRM can report opportunities the team has identified, but it cannot distinguish an account with no relevant changes from one whose changes have never been investigated. The boundary between account records and business evidence matters here.

Time for research is only part of the problem. Knowledge of the client is also distributed. The delivery lead may know why a workaround was accepted, while support sees recurring exceptions and the account manager knows what the sponsor is prepared to discuss. None of those observations automatically becomes an account-level question. Someone has to bring them together and decide whether they point to a business change. More CRM notes do not, by themselves, produce that interpretation.

To make this work repeatable, someone must own the production and interpretation of the initial evidence. That responsibility can sit within the account team, a strategy function or an external research service. The work needs time, an owner and a clear threshold for stopping. Otherwise the instruction to “find more opportunities” changes the target without changing how the information is produced.

The client still controls the strategic decision

Public evidence can make a question worth raising. It cannot confirm a board priority, internal economics or willingness to change. Before a partner proposes work, somebody on the client side must establish whether the issue matters and who has authority over the relevant decision.

An existing IT sponsor may be able to explain the installed system and the project backlog without owning pricing, service operations or market strategy. The order of the conversation therefore depends on stakeholder access and decision rights, not simply on who is easiest to contact.

A Quarterly Business Review (QBR) may provide a convenient meeting. It does not create evidence for a new business direction. A useful agenda is built from a question that is worth the client’s time, an explanation of why it has arisen and an account of what remains uncertain.

Keep a research question out of the sales forecast

An early account signal should be recorded as a question to investigate, with its evidence and alternative explanations. Before approaching the client, the account team must decide whether the evidence justifies taking time away from current work. The question is not only what might have changed, but what further investigation could establish and what result would justify stopping. An interesting observation does not, on its own, deserve a discovery meeting. At this stage there may be no client commitment, no agreed outcome and no role for the IT partner.

Once the client confirms that a change is worth pursuing, the team can establish ownership, timing, economic justification and whether its own services are relevant. Only then is there a basis for qualifying a sales opportunity. A plausible strategic alternative is not yet pipeline.

This distinction also changes what gets measured. The number of research ideas is not a reliable account-growth target: rewarding volume encourages weak hypotheses to be treated as progress. A better control is whether the team can explain why it investigated a question, what the client confirmed and why the direction was pursued or rejected.

Where a preliminary outside-in check is useful

When an account has no specific new request, a bounded review of public information can establish whether there is enough reason to invest further time in discovery. ProperBizFix’s £50 Account Screen does this for one existing client account. It can conclude that further research is justified, that the available evidence does not justify it, or that there is too little information to decide.

The Screen does not establish the client’s intentions or turn a signal into a project. The account team remains responsible for the relationship and for checking any relevant question with the right people. Where the client has already identified and authorised a clear requirement, an additional preliminary screen may add little.

Account development becomes more deliberate when a partner separates responding to demand from investigating whether a new reason to act exists. The first route can begin with a client request. The second requires someone to look for evidence before there is anything to put in the opportunity pipeline.

Research by Yulia Fomina · ProperBizFix