Opportunities

Opportunity is deliberately broad in Clay. The platform does not narrow itself to one category of opportunity — it can route toward any of the following.
Looking for the vocabulary? The Glossary defines opportunity, fit brief, and related terms in one place.

On this page

Taxonomy

People

Individual collaborators, mentors, advisors, or co-founders.

Teams

Existing teams with an open seat for someone like you.

Projects

Side projects, open-source efforts, or research collaborations worth joining.

Jobs

Roles where the intention and personality fit the team’s needs.

Events

Meetups, conferences, residencies, or gatherings worth attending.

Communities

Long-running groups whose culture fits the personality.

Collaborators

One-to-one working relationships that fit both sides’ rhythms.

Partner experiences

Programs, residencies, accelerators, or partner-led opportunities.

Opportunity explanation

When Clay presents an opportunity, the user-facing explanation should name:
  1. Why the opportunity relates to the intention.
  2. Which personality or context signals matter for review.
  3. What the user should know before engaging.
Clay prefers action over chat. When the user approves the context and consent is granted, Clay can route, introduce, draft, or coordinate on the user’s behalf. Selection mechanics are out of scope for this page.

Mobile lane

The first mobile flow starts with four lanes: Collaborator, Project, Community, and Role. Those lanes are intentionally narrower than the full taxonomy so the capture screen stays fast while the broader opportunity model remains available to backend and recommendation flows.

Intentions

The direction signal used when explaining opportunity relevance.

Personalities

The fit signal that helps the user judge whether an opportunity feels right in practice.

Consent

Why Clay prefers action over chat only when the user permits translated sharing.

User experience flows

Flow 3 — Evaluate an opportunity — defines the review card and next-step decision.