Build an account expansion workflow

01 · Resolve the existing customer

Search KYB using its country and a reliable identifier. Ask the user to confirm ambiguous matches. Store the confirmed company ID, legal name and registration number alongside your CRM account ID.

02 · Map the group against your territory

Retrieve the full corporate tree with provenance. Traverse all returned roots, preserve relationship edges and mark the companies your team already serves. Compare countries and business context against the territory your team covers.

const roots = Array.isArray(payload) ? payload : payload.data;
if (!Array.isArray(roots)) throw new Error("Unexpected tree response");
const nodes = new Map();
const edges = new Set();
function visit(node, parentId = null) {
  if (node.id == null) return; // Resolve missing IDs separately.
  const id = String(node.id);
  const { children, ...company } = node;
  nodes.set(id, company);
  if (parentId) edges.add(JSON.stringify([parentId, id]));
  for (const child of children ?? []) visit(child, id);
}
for (const root of roots) visit(root);
// Store source metadata from the original payload alongside this map.

Illustrative traversal for the returned JSON tree. Add application-specific depth and size limits for very large responses; flag unresolved nodes for review.

03 · Ask a focused expansion question

Give Regis your offer, geography and confirmed customer identity. Ask it to distinguish supported company facts from commercial hypotheses. Your CRM and contract records remain the source for existing coverage.

{
  "query": "Our customer is GLOBAL DATA INTELLIGENCE LIMITED, GB, registration 09410808. We sell workforce software in Europe. Research the available corporate group and suggest which related companies deserve a fit assessment. Separate source facts from hypotheses. Do not assume any company needs our product or is covered by our contract.",
  "mode": "ai"
}

04 · Monitor the shortlist

Enroll relevant company IDs individually. A parent or group-structure change should trigger a fresh hierarchy lookup; newly returned members need their own eligibility review and subscription. Reconcile removed members against other workspaces before stopping an upstream watch.

05 · Save an actionable account review

Keep the original customer, candidate company, relationship evidence, territory fit, coverage status, owner and next action together. Use states such as “Needs review”, “Qualified” and “Outside territory” so a data signal does not become an unverified sales claim.

These are suggested fields for your own application, not additional provider API response fields.