The problem this solves
The distance between "someone filled our LinkedIn form" and "sales has a workable record" is longer than any dashboard admits. The raw submission is a name, an email, and a few answers. Before anyone can act on it, somebody has to find the company behind the address, judge whether the lead resembles a customer, and create the CRM row with enough context that the next person does not start from zero. Multiply by every lead, every week, forever.
Most teams solve this with a straight pipe: form fills flow into the CRM untouched, and the judgment work is deferred to whoever opens the record. Which means it is done inconsistently, late, or never - and the CRM slowly fills with rows nobody trusts. The alternative, manual triage, works for exactly as long as the person doing it stays motivated, which is measured in sprints.
This mission is the pipe with the judgment built in. Weekly, it pulls the new submissions, enriches every lead's company, scores each against your ICP with the reasoning attached, and upserts the finished records - source, score, and rationale included - so the CRM receives leads that are already understood.
How the mission runs
- Pull the week's submissions. The Lead Sync connection returns every form fill in the window with its answers under human labels and its source campaign - your own first-party data, complete rather than whatever an export remembered.
- Enrich the company behind each lead. Each lead's domain resolves to firmographics: industry, headcount, the profile facts that turn a name into a company. Leads whose companies cannot be resolved are flagged rather than padded with guesses.
- Score against the ICP. Every lead gets a fit score with named factors - industry match, size band, seniority, what their answers signal - so downstream prioritization is an argument someone can read, never a mystery number.
- Upsert with provenance. Scored leads land in the CRM as creates or updates, never duplicates: existing records are matched and enriched instead of cloned. Source campaign, form, score, and reasoning ride along on every row.
- Report the week honestly. The run closes with counts and exceptions: leads processed, records created versus updated, unresolvable companies, anything skipped - so the pipe's health is visible instead of assumed.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A weekly lead pipeline that delivers understood records: every LinkedIn submission enriched, ICP-scored with reasoning, and upserted into the CRM with full provenance - plus an exception report that keeps the pipe honest. Sales opens records that already know what they are.
Make it yours
- Route leads above a score threshold to the speed-to-lead Slack alert as well, so the best ones get minutes-fast attention on top of the weekly batch.
- Tighten to daily during heavy campaign flights, when a week of untriaged leads is a week of cooling interest.
- Chain with the optimize-to-quality playbook: the same scores that route leads internally become the conversion signal LinkedIn learns from.
Frequently asked questions
What keeps duplicates out of the CRM?
Upsert semantics: each lead is matched against existing records by email before anything is written, and matches are enriched in place. The mission's report separates creates from updates, so you can watch the dedupe working.
Where does the ICP scoring come from?
From your workspace's stored ICP - industry, size, seniority, disqualifiers - applied per lead with the contributing factors written out. Change the ICP once in workspace memory and every subsequent run scores against the new definition.
What happens to leads that score badly?
They still land, scored and labeled, because a low-fit record with clear reasoning is information - it powers the campaign teardown and stops sales from rediscovering the same judgment. What to do with them (nurture, ignore, exclude) stays a routing decision you own.