The problem this solves
Speed to lead is the most replicated finding in sales research: response within minutes multiplies connection rates, and every hour of delay bleeds them. Yet the standard LinkedIn lead flow is built for delay - submissions sync to a CSV or a CRM on some cadence, a notification fires into a folder nobody watches, and the first human touch happens the next morning if the rotation holds. The form fill was a moment of live interest; the follow-up arrives addressed to its memory.
The teams that do respond fast usually respond empty-handed - a rep sees a name and an email and calls with nothing, because researching the lead would spend the very minutes speed was supposed to save. Fast or informed has been the standing trade.
This mission deletes the trade. On a tight schedule it checks for new submissions, and each one triggers the full prep in parallel: company researched, lead scored against your ICP, form answers formatted, an opening line suggested - and the finished dossier lands in your sales channel minutes after the form was submitted. The rep responds fast AND prepared.
How the mission runs
- Watch for new submissions. An hourly schedule pulls the delta since the last run - only genuinely new leads trigger work, so quiet hours cost nothing and busy hours miss nothing.
- Research at machine speed. For each new lead: the company enriched, the person's role read, recent signals gathered - the twenty minutes of prep a diligent rep would want, compressed into the gap before the Slack message.
- Score and frame. The lead is scored against your ICP so the channel sees priority at a glance - a 91 reads differently from a 45 - with the reasoning one line below the number.
- Compose the dossier. One tight Slack message per lead: who they are, what the company does, their exact form answers, the source campaign, the score, and a suggested opening line that engages what they submitted.
- Post where sales lives. The dossier lands in your named channel - #sales, or a dedicated leads room - where claiming it is a reply. The follow-up conversation continues on the same thread the platform already watches.
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 standing speed-to-lead pipeline: every new LinkedIn lead posted to Slack within minutes as a complete dossier - research, score, form answers, suggested opener - so the first human touch is both immediate and informed. The trade between fast and prepared stops existing.
Make it yours
- Post only leads above a score threshold to the main channel and batch the rest into a daily digest, keeping the room high-signal.
- Add a same-thread nudge if a hot lead sits unclaimed for two hours - gentle pressure the whole channel can see.
- Extend the dossier with the buying-committee expansion for top scores, so the biggest accounts arrive multi-threaded from minute one.
Frequently asked questions
How fast is "minutes" really?
The schedule checks hourly by default, so worst case is the schedule gap plus a minute or two of research; a lead submitted just before a check lands almost instantly. Teams in heavy flights tighten the cadence during campaign hours.
Why Slack instead of the CRM?
Both, in truth - this pairs with the CRM upsert playbook rather than replacing it. Slack is where the speed lives: a channel ping gets human eyes in minutes, while a CRM row waits to be found. The record persists in the CRM; the moment happens in chat.
What does the suggested opening line do?
It engages the lead's actual submission - the question they asked, the interest they picked - so the rep's first message proves someone read the form. It is a draft to edit in the rep's own voice; its job is deleting the blank-page seconds that turn into hours.