account-org-mapping

Use this when a list of employees is not enough and the user needs a usable map of the account. It produces a scoped org chart plus the decision logic behind every inferred relationship and contact recommendation.

Frame the map

Confirm the company by domain. Then lock two choices before researching people:

1. Scope: whole company, leadership only, or one function. Default to the whole company below 50 employees. Above 50, recommend one function or the top four layers unless the user has a reason to map more.
2. Objective: sell, partner, recruit, or research. The same structure creates different contact priorities. Do not recommend a person until the objective is explicit.

Capture the company's employee band, business model, headquarters, and stage. Titles only make sense against that baseline: a CTO at a 12-person company is not equivalent to a CTO at a 12,000-person company.

Build the evidence set

Search for current employees in deliberate passes rather than one broad query:

• Executives and founders establish the top layer.
• VPs, Heads, and Directors establish functional ownership.
• Managers and team leads add operating depth only when the requested scope needs it.
• Individual contributors appear only for recruiting, technical influence, or a specifically requested full map.