What to decide before you source LinkedIn or Indeed leads

The job is a working list. A sales desk needs people in named roles, at companies they can sell to, in a schema the CRM already understands.

Teams arrive asking for “a LinkedIn scraper.” That is not a job. The job has a grain, a freshness rule, and a person who will open the row.

The questions that decide the build

Which title is in scope this month, and which geography. What must exist on every row before anyone will call: name, role, company, a way to reach them. How stale is allowed. Where the file lands — CRM, sheet, a morning Slack — and who owns a failed run.

If you cannot say what happens after the row appears, a cleaner export will still die in the inbox.

If Sales Navigator, Indeed, or a licensed provider already exports those fields, we will say so. Unofficial collection from authenticated networks is a last resort, not a starting personality. Lead sourcing on the automation service is that slice when the brief is real: pull the roles you name, clean them, drop them where the desk already works.

This is not GCC property coverage and not US car listing coverage. Those jobs are marketplace stock on a schedule. A lead list is a person and a next step. We will not paste a listing schema onto a sales motion.

What we will not sell as the first slice

We will not open with an outreach agent that writes and sends on your behalf. That is a different job, and a policy risk. We will not promise a volume from someone else’s dashboard.

If the stall is “we already have the seats and nobody works the pile,” the first hour is a routing rule, not a new crawl. If the titles are fixed and the stall is hours spent copying, we can scope source → clean → CRM. That is AI consultancy first, then a narrow scraping or automation build if a licensed path is not enough.

Bring the columns you already use in the CRM and three example accounts. Book a consult or email hello@jamilglobal.com.