A static people list is a fixed collection of specific individuals. Unlike a company list — which groups entries by organization — a people list tracks individual contacts directly. You build it by uploading email addresses or LinkedIn profile URLs, and the list stays as you've defined it until you make manual changes.

This is the right choice when you have a defined set of people to track — conference attendees, event speakers, job candidates, LP prospects — and you want CTD's warm path intelligence mapped to each individual.

What you can upload

  • Email addresses — CTD resolves each to a person profile if it exists in the network.
  • LinkedIn profile URLs — e.g., linkedin.com/in/janedoe

Walkthrough

📹 Walkthrough coming soon.

People lists vs. company lists

The distinction matters for how you use the Paths view:

  • A company list shows warm paths to people at each company. You can apply persona filters to narrow which people you want to reach.
  • A people list shows warm paths to the specific individuals on the list — no filtering needed, because you've already decided who the targets are.

If you know the company but not the specific person, start with a company list. If you know exactly who you want to reach, use a people list.

Available views

Static people lists support three views:

  • List view — a table of all contacts with role, company, relationship signals, and notes.
  • Board view — a Kanban board with custom columns. Ideal for managing outreach stages or event attendance status per person.
  • Paths view — warm intro paths from your team to each individual on the list.

See List views: List, Board, and Paths for detail on each.

Use cases

Event team tracking conference speakers and VIPs

A partnerships team is hosting a 200-person industry summit. They upload the confirmed speaker and VIP attendee list as a static people list, then switch to Board view with columns: "Invited," "Confirmed," "Arriving," "Met," and "Follow up." Each teammate sees warm paths to the people they're most connected to, making it easy to coordinate who should do the meet-and-greet at the event.

VC firm managing LP prospect outreach

A partner at a growth fund uploads a list of 60 family office principals and institutional LP contacts they're targeting for their next fund raise. The Paths view surfaces which partners and operating partners in the firm have warm connections to each LP — making warm introductions the default, not the exception.

Recruiting team tracking senior engineering candidates

A talent team compiles a list of 40 senior engineers identified through outbound sourcing on LinkedIn. They upload the profiles as a static people list, share it with the hiring manager, and use Paths view to see who on the company's team has existing connections to each candidate. Rather than cold outreach, they send warm intro requests where relationships exist.

Sales team following up after a conference

After attending a large industry conference, an AE uploads the business card contacts they scanned into a static people list. They use Board view to track post-event follow-ups: "Email sent," "Call scheduled," "Demo booked," and "Closed/lost." The list stays organized as the post-event pipeline works its way through the funnel.

Tip: If you want CTD to discover people automatically based on criteria — rather than uploading a specific set — use a dynamic people list instead.