RESEARCH / BEFORE DISCOVERY

Account records, outside-in research or client discovery?

The right first step depends on what is unknown. Internal account history, public business evidence and client-side discovery answer different questions; using one in place of another can create unjustified confidence.

Start with the decision, not the research tool

Suppose an implementation partner wants to develop an existing account. A request has not arrived, but the partner needs to decide whether to spend consultant time investigating the client's changing business. Three different sources are available: the history of the relationship, external evidence about the business, and direct access to the people who own decisions inside the client.

The sources are complementary. They are not equally good at answering every question. A partner that begins with a new solution design may spend time testing how to build something before establishing why the client should change. A partner that treats a news item as a qualified opportunity has made the opposite mistake: it has inferred internal intent from public evidence.

1. Account records: what is already known within the relationship?

CRM records, project artefacts, support tickets and the delivery team's knowledge can establish the original scope, current contacts, known issues and requests. They often provide enough evidence to respond to a clearly defined need. If the client has already described an authorised requirement, continuing with the normal discovery and qualification process may be the most economical choice.

Account history does not tell you whether no relevant business change exists. It tells you which changes have entered the relationship and been recorded. The distinction matters because ongoing support and expansion work can be concentrated around the people and processes involved in the first project.

2. Outside-in research: is there an observable change worth examining?

Public company information may show that a client has added a service, expanded its footprint, acquired a business or changed its customer proposition. Sector knowledge can help explain what those developments might mean for the operating model. But different explanations may fit the same event.

For example, a new service location may add capacity, replace an existing site or support a different delivery promise. The consequences for cost, process and systems depend on which explanation is correct. Preliminary research should state the alternatives and identify a question that internal evidence could resolve. It should not declare that an application is inadequate merely because the business changed.

This is the role of the ProperBizFix £50 Account Screen: a bounded comparison of one existing client's observable business changes with the partner's description of the delivered implementation. The output may be an investigation question, no sufficient grounds for further work or insufficient evidence to decide. It is not a guarantee that the account contains an expansion opportunity.

3. Client discovery: what can be established only with the decision owner?

Whether an initiative is a priority, whether the economics justify it, and which constraints really bind the business normally require internal evidence. The appropriate owner may be in Operations, Finance or Commercial leadership rather than the team that sponsored the IT implementation.

Discovery should test the observed change and possible consequences against the client's actual objectives. At this point the answer may be new software, a change to an existing application, a different operating policy or no intervention. The client controls that decision.

A practical decision rule

SituationBest first stepReason
Defined requirement with an authorised ownerDirect discoveryThe client has already supplied the initial business signal.
Unclear next step, no observable changeReview account records firstA desk study cannot create meaningful evidence where none is available.
Visible change outside the original project scopeConsider outside-in researchA small review can determine whether a specific client question is justified.
Suspected technical fault in the delivered systemTechnical assessmentCode, configuration and performance evidence are not available in external account research.

Separate the research question from a pipeline opportunity

A public signal does not establish a sponsor, budget, timing or willingness to change. It should not enter the sales forecast as though the client has expressed demand. A useful early-stage record identifies the observation, source, alternative explanations, what is missing and the decision that further evidence would support.

There is also a stopping rule. If the likely cost of further investigation exceeds the value of learning more, or if the available signal is too weak to frame a consequential question, the appropriate decision is not to continue. That is a legitimate result of research.

Apply the rule to different IT partners

For a HubSpot Solutions Partner, the immediate decision may be whether to introduce an external business question at an account review. For a custom software developer, it may be whether the assumptions in a completed brief deserve another look before estimating enhancements. Both need the same discipline: establish what is known, distinguish inference from evidence, and identify who can validate the issue.

Where a small preliminary investigation would help, the £50 Account Screen covers one existing client and produces a written decision. More detailed account research is scoped and quoted separately, typically £350–£1,500, and can be commissioned directly if the question is already defined. Neither service is required before client discovery.

Choose the smallest useful next step. If your team has an established client and an unresolved question about change beyond the implementation, review the £50 Account Screen scope.

Account Screen · £50 ↗