Local prospecting campaign For sales people, founders and agencies who build a pipeline in a defined market. Steps 16
Checklist items 82
Language English
What it is for
Build a pipeline in one market: pick a city and a service, qualify companies and people, get your approval before any contact, run it in waves and learn from the replies.
For sales people, founders and agencies who build a pipeline in a defined market.
Steps and what they prove 16
Brief: market, offer and goal Brief table (field, value, status confirmed or assumed) filled for city, service, offer, proof, sender, channels and register place, and confirmed by the user Two separate lists written: 2 to 3 checkable hard conditions and 4 to 6 priority signals, each checkable from a public source Goal table for wave 1 with a user-given number and a written denominator for every metric Context variables city, service, wave=1, maxWaves, touch=0 and maxTouches stored and read back to the user User answered which channels and tools exist, and whether the assistant has a search, social or mail tool, written down Rules and channels for this market Country table filled for every country in the market, each row dated and marked as checked by the user, with any unsettled e-mail position marked unsettled First channel chosen per country with a written reason, and the user's own check or legal contact noted where e-mail is unclear Opt-out line written for each channel in use, one sentence Record fields and the register place fixed, and the first SUPPRESSION run note created plus one note per entry the user pasted Mail checklist (SPF, DKIM, DMARC, unsubscribe route, real sender) confirmed by the user, or a note that e-mail will not be used User acknowledged the compliance reminders, with the date Find companies Long list table with columns Company, Website, Source link, Date seen and Status, and a source link and date on every row Hard conditions checked from a public page for every row, and rejected companies logged with the failed condition SUPPRESSION notes read with listNotes and the entry count recorded, with the number of rows removed as suppressed by name, domain or person Earlier-wave companies and duplicates removed, with a count per reason that adds up to the rows removed Count of companies added per source written down, and the user confirmed the list is complete enough to score Score and qualify companies Fit table with columns Company, Signal points, Total, Tier and Sources for every company on the long list, using one set of weights that adds up to 100 Hard conditions re-checked per company, and every removed company logged with the failed condition Every non-zero signal score has a source link and a date, or the label from the user; unconfirmed signals scored zero Tier counts written down (A, B, C), with the thresholds used marked as the workflow's recommendation and the A cap given by the user Exit chosen and recorded, companies qualify or no company qualifies, with a one-line reason and the user's confirmation Find the right people Contact table with columns Company, Role, Name as published, Title as published, Source link and date, Status; one row per person or per 'role not found' Every row marked confirmed has a source link and a check date; every inferred row is marked hypothesis Suppression list read with listNotes (keyword SUPPRESSION); the count of removed rows is written down, also if it is 0 At most three people per company; count of companies covered and people per role reported to the user No e-mail address was guessed: each contact channel has a source or was supplied by the user Qualify the people Decision table with columns Person, Hard conditions, Priority signals, Fact status, Grade and angle; one row per person including removed ones Each hard condition is written as pass, fail or unknown, with the date the user confirmed the condition list Counts per grade A, B, C, plus counts of failed, unknown and suppressed rows, shown to the user No row was removed or ranked because of a quiet profile, a like or a guessed intent Edge chosen: 'people qualify' or 'nobody qualifies', with a one-line reason Public signals Signal table with Person or company, Signal type, What was published, Source link, Source date and age in days, Use; one row per signal Every grade A and B person has one hook candidate with a dated link, or the entry 'no signal' with the sources tried The age limit chosen by the user is written down and no hook candidate is older than it Count of signals rejected (inferred, private, not linked to the offer) with the reason for each No signal is based on a like, a follow, tracked behaviour or a relationship the user did not confirm Contact plan Plan table with columns Person and grade, Channel, Hook (fact, link, date), Text version, Touch dates, Stop rule; one row per person Texts exist for each planned touch (LinkedIn note, first message, follow-ups) and every one carries the status 'not sent' maxTouches is written down with its value, and each person has dated touches that do not exceed it Every hook cites a public fact with a link and a date, or the row says 'segment-level' Suppression list read again with listNotes (keyword SUPPRESSION); date and count of removed rows recorded The user has seen the plan and their comments are recorded; no text is marked as sent Approval before any contact Pack shown to the user: a table with columns person and role, company, channel, class, hook with source and date, and the row count and counts per class A, B and C Suppression check done against the SUPPRESSION notes today, with the number of removed entries and their reasons written down Every distinct message shown in full with opt-out line and sender identification, and each row of the table linked to the text it receives Open questions and held-back rows listed, each with its reason, before the closed question is asked User's answer quoted with its date in the WAVE register note, naming the wave, the list and the texts it covers Useful public interaction Rows of class A and B each have a status in a table with columns person, platform, link to the public occasion, date seen, status prepared or done or skipped with a reason Each prepared interaction text has no offer and no link to the service, and cites the dated public source it reacts to Manual action list handed to the user with row, platform, text and suggested day, and no interaction marked done without the user's confirmation SUPPRESSION notes read before preparing; matches removed and the count written down Counts of prepared, done and skipped recorded in the WAVE register note First contact Suppression check run first against the SUPPRESSION notes, with the matched entries, the removed rows and the date written down Table with columns person, channel, final text id, status, confirmation date and source, where every status is not sent unless the user or the system confirmed Each text checked against the approved version, with sender identity, data source line and opt-out line present, and any changed text sent back to approval Rows without a confirmed address or with an unclear country rule marked held with the reason, never guessed WAVE register note refreshed with counts per status and the denominator, and the first follow-up date noted for each sent row Replies and follow-ups Pasted replies each classed in a table with columns person, channel, date, class, action taken and status, with the class taken from the reply classes table Every refusal added to the SUPPRESSION notes in the standard format with the date before any other action in this pass Follow-up due list built from confirmed-sent dates, the approved gap and the replies, showing who is due and who is excluded and why Value of touch and maxTouches stated before and after the round, and no follow-up sent or marked sent without the user's confirmation Counts per reply class recorded in the WAVE register note with the denominator of sent and confirmed rows Book the meetings Table of interested people with reply date and wording, question asked, suppression check and status (proposed / confirmed / pending / lost / no answer), each status with dated evidence Every proposed time is written with the time zone of both sides (for example 10:00 Warsaw time, 09:00 London), checked in the drafts Each confirmed meeting has evidence (acceptance wording with date, or calendar acceptance) and a confirmation text marked sent or not sent Pre-meeting brief per confirmed meeting: facts with source link and date, hypotheses marked as hypothesis, one opening question Reminder plan per confirmed meeting (default a day before and hours before) recorded, and the counts added to the WAVE register note Wave review Funnel table with named columns Stage, Count, Denominator, Rate for this wave, built from counts the user confirmed (messages not confirmed as sent counted as zero) The written definition of a positive reply, and the benchmark rows used with whose data they are, each flagged indicative Largest leak named with a hypothesis labelled as hypothesis and the evidence that would confirm it, or the note too small to judge Segment counts by channel, role or company size where the data allows, with the count in each segment Line review done with the date added to the WAVE register note, and the user's confirmation of the numbers quoted Learn from the replies Reply table with columns Person, Company, Reply date, Channel, Type, Segment, Hook used, Touch number covering every reply the user pasted, with the count of replies stated Every refusal or objection added as a SUPPRESSION note, and the second listNotes read with the keyword SUPPRESSION quoted with the number of new entries Four lists of proposed changes (ICP, people, message, cadence) each with the reply evidence behind it and labelled hypothesis or finding The user's approval of the changes quoted, and the plan stored in a note WAVE n+1 PLAN, or the statement that no next wave is planned Values of wave, touch and maxTouches read back after setContext before an edge is chosen, with wave not greater than maxWaves for a next wave Campaign summary Scope paragraph with city, service, the final ICP (hard conditions and priority signals separately), channels and dates of the first and last contact Per-wave table with named columns Wave, Companies qualified, People contacted, Replies, Meetings confirmed, plus totals and the written definition of a positive reply Up to five lessons each tied to evidence from the feedback steps and labelled hypothesis or finding, with benchmarks marked indicative and attributed Open items list (replies waiting, confirmed meetings with date and zone, promised follow-ups, not now dates, unsent drafts) and the SUPPRESSION entry count read at the end The user's confirmation that they have seen the summary quoted, before the run is closed with advance The assistant closes a checklist item only with evidence of what it did, so a finished run shows the work was done, not only claimed.
Use it
Create a free account, connect your assistant and run this workflow in a chat. You come back to this page after signing up.
Use this template
Not sure yet? Watch a demo run first, no account needed.
Already have an account? Sign in