Include entities, source permissions, identity resolution, historical roles, evidence, confidence and correction workflows. Decide whether you need public research, authorised interaction data, introduction execution or all three.
Sources change, identities merge, people move and records need deletion or access updates. Scoring requires validation against real connector feedback. Operational ownership matters as much as the first graph demonstration.
Test coverage, source transparency, permissions, availability, export rights and current API scope. A vendor may supply data without running the business workflow, or a service may run the workflow without offering a reusable graph export.
Use a limited, appropriately sourced dataset to test the core question. Public-data research still needs licensing, terms and privacy review; absence of inbox integration does not eliminate governance requirements.
Orbb is relevant where relationship-led research and execution fit the need. For Network Graph or API delivery, verify current scope directly. Choose build, buy or a combination from your requirements and total maintenance burden, not a fixed estimate copied from another team.