Turn customer changes into well-prepared account conversations.

Start by describing what changed. A customer announced another site, asked about an additional service or introduced a project with different requirements. Keep the dated source beside that statement. Avoid adding an inferred purchase decision to the event: a site announcement does not mean a supplier selection is open.

A whitespace analysis starts with an absence in order history or coverage. An expansion review starts with a relevant change. The two can meet: a new project may make a previously irrelevant category worth discussing. Keep the event and the gap separate so the owner can explain why the question is timely.

An enquiry from an existing customer can be more direct evidence of a need, but its scope still needs checking. Use the inbound qualification guide to clarify the task, buying unit and next step without treating every enquiry as an agreed opportunity.

Confirm the organisation, legal entity, site and trading names involved. A group announcement may concern a subsidiary outside the agreement you hold. An acquired business may keep its own suppliers. Record these relationships rather than merging every shared brand name into the account you already serve.

Where CRM and order data use different identifiers, check the mapping before drawing conclusions. HubSpot’s data-sync guidance distinguishes record matching from field mapping and describes how a chosen match field can create unexpected matches or duplicates. The practical question is whether the event and the order history really belong to the same buying unit.

Keep uncertain matches in a review queue. A colleague should be able to see the evidence for linking the new site to the account, or why the link remains provisional. An unresolved identity is a reason to research, not a reason to create an expansion task for an unrelated account owner.

Review current services, agreements, delivery conditions, open support issues and any active opportunity. A new site may need the same work, a different service model or nothing you can provide. Check relevant limits such as territory, certification, capacity and the coverage of the existing contract.

Identify the person who owns the relationship and the next conversation already agreed. If a service problem is unresolved, route that work to its owner. The commercial owner can still prepare the expansion question, but should not use the event to bypass the problem the customer is already asking you to solve.

Add the review to the account plan as an open question. Keep possible opportunity, confirmed requirement and agreed next action separate. This keeps an announcement out of the forecast until someone has established the customer requirement and next buying decision.

An expansion review can lead to several different kinds of work. Missing identity or dates go to research. An unresolved delivery issue stays with service. A potentially relevant need goes to the relationship owner for a conversation. An event outside your scope can be recorded with no further action.

Name the next review condition for anything left open. “Monitor” is incomplete unless it says what information would change the decision and who will notice it. The buying-signal guide offers a broader method for connecting observations to these different responses.

Give automation a specific job: collect the source, connect the account, prepare the context and route a review. Human confirmation is still needed for uncertain matches and decisions about relevance, qualification or customer contact. Repeated copies of an announcement should enrich one record rather than create multiple approaches.

Choose three recent changes: one that led to a real requirement, one ruled out after checking, and one still unresolved. Reconstruct what was known at the time. Could the owner find the account history and the source? Did the task state the missing question? Was any service issue visible?

Use the results to improve the review rules. Keep the rejected case: it can reveal an entity mismatch or an assumption that a new site always needs the same products. Judge the workflow first on whether it produces usable, correctly routed work. Assess resulting opportunities and revenue separately, with their dates and evidence.

Commission a focused account review through Plan and use the findings with your own team. Or agree a Build campaign to research and approach relevant customer accounts alongside the relationship owner. ClarityRev can operate the agreed outreach, share the work or hand over prepared accounts and context. A separate expansion-review workflow has its own scope. Start with the customer question and the handover it needs.