You sell industrial software in Europe. Meridian UK is your customer. The task is to establish whether another operating business in its group deserves a conversation.
Try this group in the explorer ↗Assume you sell industrial software in Europe and already serve Meridian UK. These commercial facts are supplied for the exercise; they are not inferred from the corporate tree.
| Entity | Offering | What we know | Decision | Next action |
|---|---|---|---|---|
| Meridian UK | Industrial software | Confirmed customer | Retain | Ask the account sponsor about group procurement. |
| Meridian Germany | Industrial software | Contract coverage unknown | Investigate | Confirm whether the UK agreement covers this entity. |
| Meridian France | Industrial software | Covered by group agreement in this example | Already covered | Check adoption with the owner; do not count it as a new logo. |
| Meridian Americas | Industrial software | Outside our European territory | Exclude | Record the territory reason, not a lack of need. |
| Meridian Holdings BV | Industrial software | Holding entity; operational fit unconfirmed | Exclude from operating shortlist | Keep the ownership link for context. |
The German entity is a research candidate, not a qualified opportunity. The French entity demonstrates a false gap caused by a parent-level agreement.
Start with the entity named on your existing customer agreement. Check its legal name, country and registration. In this fictional group, Meridian UK and Meridian Germany share a parent; Germany is a sister company, not a subsidiary of the UK business.
Germany operates in your territory and appears relevant to the offering. France is already covered in this exercise. The US company sits outside your territory. The holding company explains the structure but does not establish an operational software need. Record each reason so another reviewer can understand the shortlist.
For the German candidate, investigate operations leadership as a potential problem owner and procurement as a possible purchasing participant. These are role hypotheses. In a live group, open the company contacts, filter titles on the loaded page, and add an appropriate returned contact to the company plan. No real contact is supplied for this fictional group.
Ask the UK sponsor whether Germany already falls under the group agreement and whether purchasing is local or central. If it is covered, shift the next step toward adoption or an extension of scope. If it is not, establish need and responsibility before treating it as pipeline.
In the company plan, name the account owner, retain the evidence and contact to verify, and record the next question. Save the group. The action below is a draft for human review; EntityReach does not send it automatically.
Editable files, with no form to complete. Each template includes clearly labelled fictional examples and a blank starting row or section.
How to use these templates ↗Entities, contract coverage, fit, target role and next action.
Download CSV ↓Coverage evaluation checklistExpected versus returned records, source dates and unresolved gaps.
Download CSV ↓Customer introduction templateAsk your sponsor to confirm responsibility before requesting an introduction.
Download text file ↓Choose a representative sample that includes a familiar account, a complex group and a target country where coverage matters. Agree your acceptance thresholds before starting.