Keep the shortlist. Share the reasoning.
Organize company and people research into named workspace lists. Keep source references, shared notes, and current public context together so the next researcher can understand the decision.
A shared research list that preserves source identity and your team’s qualification notes.
One list, two kinds of knowledge
Role and employee band fit the brief. Verify territory responsibility before contact access.
Shared with workspace members- Company
- Forma Labs
- Country
- India
- Release
- fictional-preview
Build a list another researcher can use.
A saved name is not enough for a useful handoff. Keep the exact source reference, the reason for inclusion, and the questions to resolve next. Named lists make that work available to the workspace across the app, REST, and MCP.
Create a list around one research question
Use a company list for an account cohort or a people list for a prospect shortlist. Give it a specific name that describes the territory, account profile, or role. Workspace members share the list; its name is not a separate access boundary.
Save a source reference
The reference keeps the provider, record kind, source ID, and release. The saved workspace record has its own identifier. This distinction lets your team add research without editing source facts or confusing a notebook entry with an external identity.
Add the reasoning in a shared note
Record why the prospect fits, what still needs verification, and the next research action. Keep protected contact values and credentials out of notes. If another edit conflicts with yours, reload the current version before updating.
Refresh context before the handoff
Review role, company, and country for people, or domain, industry, location, and employee information for companies. Opening a list reads public source context without unlocking channels or spending credits. Unavailable source details do not erase workspace notes.
Know what belongs to the list.
Saved research belongs to the workspace. Source facts remain external records. Keep the distinction visible when a release changes or a source record becomes unavailable.
| Information | Owner | How to use it |
|---|---|---|
| List name and membership | Workspace | Organize the approved account or people cohort. |
| Qualification note | Workspace | Explain inclusion and preserve the next verification question. |
| Provider, source ID, and release | External source reference | Resolve the intended record without treating a workspace UUID as a source ID. |
| Current public context | Directory source | Refresh supported details; old releases can become unavailable. |
| Saved search criteria | Workspace | Keep the research definition. Saving criteria does not run a paid search. |
Give your AI client an explicit list to research.
MCP get_list_context and REST POST /api/v1/lists/{id}/context read public source context for 1–50 explicitly selected saved members. Both saved:read and directory:read are required, and each member must belong to that list and workspace.
Review these selected members of our prospect list. Read their public source context and existing notes. Draft the qualification gaps for my review. Do not change the list, run new searches, or unlock contacts.
List context follows your requested member order. Source failures or visibility changes fail the context read, so the client should preserve unavailable details as unresolved. Request saved:write only when you intentionally want it to edit workspace research.
Example instructions only. No client is connected here.Before the next step.
Does opening a list spend credits?
No. Lists, saved references, and public list-context reads are free. A new nonempty search page and an approved contact unlock have their own credit rules.
Can colleagues use the same list?
Lists and notes belong to the workspace and are shared with workspace members according to their permissions. Use the intended workspace before saving or reading research.
What happens when source context is unavailable?
Workspace notes remain readable independently. Old source releases are marked unavailable instead of being silently replaced with a different identity.
Is a prospect list a CRM or an outreach sequence?
Lists support shared research, notes, and source context. They do not run outreach sequences or provide a CRM pipeline. Plan the subsequent handoff in the tools your team uses.
Your next audience.
The right records behind it.
Define your market, keep shared prospect lists, and approve contact access with a clear credit budget.