Prospecting overview

Prospecting in Pointerly is the early partnership research layer: look up a company domain, run an organization discovery job, and qualify email / org signals before you invite creators or open a brand conversation. The product talks to the pointerly-prospect-intelligence service (ProspectIntelligenceClient) with team/user caller headers. Surfaces may appear under internal/enterprise tooling as the capability rolls out—treat this guide as the canonical behavior of that service, not a promise of every nav label.

For day-to-day creator discovery inside the product, also see Creator Connections and brand Pipeline.

What you'll do

• Understand discovery jobs and email status values
• Know what must be configured for the intelligence service
• Use discovery results to decide outreach vs wait
• Hand off qualified prospects into partnerships / pipeline workflows

Before you start

• Brand (or internal) workspace with permission to run prospecting tools
• Prospect intelligence configured for the environment (PROSPECT_INTELLIGENCE_URL + token on the server)
• A company domain you are allowed to research
• Clear outreach policy (no spam; respect local email laws)

Concepts

Run organization discovery

1. Open the prospecting / discovery surface available to your workspace (enterprise or internal tooling when exposed).
2. Enter the organization domain (e.g. example.com).
3. Start discovery. The client POSTs /v1/organizations/discover and returns a job { id, domain, status, createdAt }.
4. Poll or refresh job status via /v1/jobs/{id} until completed or failed.
5. Review returned organization and contact signals, including email verification status.
6. Decide next step: warm outreach, save to Pipeline, or skip.

Qualify before outreach

1. Prefer contacts with verified email status for first touch.
2. Treat catch_all / risky as lower confidence—verify manually when stakes are high.
3. Skip unavailable addresses; find another channel (LinkedIn, form, partner manager).
4. Record the domain + job id in your CRM or Pointerly Pipeline card notes.
5. When a brand relationship is ready, move into Brand contracts / invites—not more cold discovery.

Tips

• Discover the corporate domain, not a marketing microsite, for cleaner org matches.
• One job per domain; wait for completion before re-queueing.
• Pair prospecting with Creator Connections performance data when you are picking creators, not brands.
• If the service is not configured, operators must set URL + token—end users will see configuration errors.

Troubleshooting

Related

• Brand workspace overview
• Brand partners overview
• Creator Connections overview
• Pipeline overview