Prospect-to-Meeting
A run starts when somebody decides to reach people who have not asked to hear from us: a list built from a territory, the accounts named in a plan, or a trigger somebody noticed. The processes here build the list and check it, decide what is worth saying to each part of it, run the sequence across mail, phone and social, keep every message inside the consent and suppression rules, and hand over a meeting that actually happened along with what was said and what the person wanted. A run ends at the meeting rather than at the reply, because a booked meeting nobody attended is a run that failed. Reaching people who did ask to hear from us is marketing, and the rules that decide who owns an answer belong to operations.
vs/sls/prospect-to-meeting v1The processes
The processes in this stream
Book the Meeting
Starts witha reply asks for a conversation
Ends whenthe meeting happened and what was said is handed on
Activities inside
- Take in the Reply
- Read What They Asked For
- Decide Who Should Attend
16 activities · 53 blanks to fill · 1 human gate
Build a Prospect List
Starts witha territory is assigned or an account plan is approved
Ends whena signed list is loaded and ready to be worked
Activities inside
- Take in the Territory or Plan
- Set the Fit Rules
- Pull the Candidate Accounts
14 activities · 52 blanks to fill · 1 human gate
Run an Outbound Sequence
Starts witha signed prospect list is handed over
Ends whenthe touches have run and the replies are handed on
Activities inside
- Take in the List
- Split the List into Groups
- Write the Touches
17 activities · 54 blanks to fill · 1 human gate
Work a Referral
Starts withsomebody offers to introduce somebody else
Ends whenthe introduction was worked and the introducer knows how it went
Activities inside
- Take in the Referral
- Thank the Introducer
- Check the Account
14 activities · 50 blanks to fill · 1 human gate