Skip to main content

Prospect Outreach Execution SOP

Overview​

  • What: Work the weekly prospect batch. Research each prospect, assign it one bucket, correct its record, and send the first email.
  • When: Every working day, against the batch the prospecting agent produces each Friday.
  • Who: Prospecting Operator runs it. Principal provisions access, makes the calls, answers every reply, and answers escalations.
  • Time Required: About 15 minutes per prospect. 10 to 12 prospects a day, so roughly 3 hours.

Two roles are used throughout and mean exactly one thing each:

RoleWho it is
PrincipalThe person the emails are sent as, who takes the calls and owns the commercial relationship
Prospecting OperatorThe person working the batch: research, record hygiene, bucketing, and the email touches

The boundary between them is the whole point of this SOP. The Operator owns everything up to and including the first email. The Principal owns the conversation that email starts. A cold email that turns into a sales conversation, answered by the wrong person, is the main failure mode, and it is the reason the prohibitions in §4 exist.

The current holder of each role is in 10-people-operations. Do not assume it from a previous version of this document.

This is a delegation artifact. It exists so prospecting runs without founder time, which is the second of the two goals in SC Goals.

Prerequisites​

Principal, one-time. None of these are the Operator's to do, and the loop does not run until all four are done.

  1. Sub-account access provisioned for the Operator: Marketing > Prospecting, Contacts, and Conversations. Nothing else.
  2. The prospecting agent is active and producing a batch.
  3. Every bucket has a touch-1 template that resolves in the template registry.
  4. The Prospect Bucket field exists on the sub-account.

Operator, each day. The Slotting Checklist and the Send Checklist open in front of you. Everything else in this document is context for those two.

Procedure​

  1. Work the open queue. Rules in §1a. This comes first: an engaged prospect outranks a fresh one, and the signal decays.
  2. Select the day's prospects. Rules in §1.
  3. Slot each one. Run the Slotting Checklist end to end. About 10 minutes. It assigns exactly one bucket and produces the finding the email will carry.
  4. Send touch 1. Run the Send Checklist. About 5 minutes. The bucket decides the template, and that map lives in the checklist so it exists in one place only.
  5. Hand every reply to the Principal the same day. Rules in §2.
  6. Stop at the day's count and report. Rules in §3.

A prospect that cannot clear every box in either checklist does not get sent. Record why and move on. Parking a prospect is a good outcome; sending an email built on a guess is not.

The prospect does not move to Discovery. It enters the pipeline at New Lead and stays there for the whole cadence. What marks it as validated and ready are the tags the send checklist applies, not a stage. Discovery is reserved for a prospect that has replied and passed the ICP screen, because stages carry buyer progress: putting uncontacted cold prospects into a 25% stage stops the forecast meaning anything. The rule and its reasoning are in the cadence SOP.

§1 Selecting the day's prospects​

Work in score order, best first. Take them one at a time to completion rather than batching each step across ten prospects, because a half-processed record is indistinguishable from a finished one.

The fast no. Any one of these and you move on without opening the report:

SkipWhy
Score is in the low band, roughly under 60%The agent's own estimate that this will not convert. Better prospects exist in the same batch
No email address on the recordEmail is the only channel this role runs. Roughly half the batch is affected
Already marked lostSomeone has already decided. Do not re-open it
No real person can be identified as running the businessAn email addressed to nobody, or to the wrong person, is worse than no email
The audit report is more than 7 days oldRefresh it or take a fresher prospect. Stale findings get checked and get you caught out

On the score. Read the AI conversion score on the prospect card, not the Overall Score on the audit report. They are different numbers and they mean close to opposite things: the card score estimates whether they will convert, while a low report score means more to sell, not less. If the card shows more than one number and it is not obvious which is which, escalate per §5 rather than guessing.

§1a The open queue​

A prospect who picks up prospecting-audit-email-opened has engaged without replying. Workflow WF-3 applies the tag and sends an internal notification; nothing else happens automatically.

Work this queue before the day's new prospects. An engaged prospect is worth more than a fresh one and the signal decays within days.

StepAction
1Filter contacts on prospecting-audit-email-opened, sorted by most recent
2One business day after the tag, send Template 16. Pick 16a or 16b on whether First name is populated
3If the prospect has a verified phone, call as well — the touch-3 follow-up variant, open-tagged branch
4Counts against the three-email cap and the one-email-per-day rule like any other touch. The cadence SOP stop rules are unchanged

⚠️ The tag does not mean they read it, and you must never say they did. Apple Mail Privacy Protection prefetches images and fires an open event for mail nobody has looked at, so a share of this queue never saw the email. Both the template and the call script are written to survive that; do not improvise around them. The never-say is in call scripts §10.

Do not read the report link's view count as engagement. It is one shared counter across every contact and cannot tell you who viewed what. The tag is the only per-prospect signal available. Detail in the C-021 spec §3.4.

§2 When a prospect replies​

The Operator does not answer. Not to say thank you, not to acknowledge, not to answer a simple question.

  1. Hand it to the Principal the same day, on the channel in §5.
  2. Apply prospecting-responded.
  3. Stop the remaining touches for that prospect and cancel the follow-up tasks.

A reply is the moment the relationship starts, and it belongs to the Principal from that moment. This holds however small the reply looks. "Thanks, not right now" is a commercial signal and it is answered by the person who can act on it.

Two replies are handled differently. Anyone asking to be removed, unsubscribed, or not contacted again is actioned immediately rather than escalated: stop everything, and a do-not-call request additionally gets sc-suppressed, which overrides every other rule in this document, permanently.

⚠️ Neither prospecting-responded nor sc-suppressed exists in the sub-account. Verified live 2026-09-23: five prospecting tags exist and these are not among them. Until they are created:

  • Create the tag on first use, spelled exactly as written here. A tag typed from memory as suppressed or do-not-contact is a tag nothing will ever find.
  • Do not rely on the tag alone for a do-not-call. Set DND on the contact as well, which the platform enforces, and tell the Implementation Lead the same day. A tag is a label; DND is a block.

Creating the missing tags is tracked in the prospecting follow-up sprint. This is the gap worth closing first — a published workflow sends cold email today with no suppression check, and there is no tag for such a check to read even if one were built.

§3 Volume and the end of the day​

10 to 12 prospects a day. Stop at the count rather than pushing through a batch. The number exists so quality holds; a day of 20 rushed records costs more to repair than it gains.

At the end of the day, report four things to the Principal:

  • How many prospects were slotted
  • The bucket spread across them
  • How many were sent, and how many were parked or skipped
  • Anything that did not fit, per §5

The bucket spread is the number worth watching. It says which problems the supply is actually producing, and it is the input to whether the agent's targeting needs changing.

§4 What the Operator never does​

NeverBecause
Answer a reply§2. The relationship is the Principal's from the first reply
Discuss price, terms, discounts, or refundsCommercial conversations are the Principal's, in the room
Mention any guaranteeThe only one that exists is still in draft and has terms an email cannot carry
Put a number in an email that was not counted by handEvery claim in a cold email gets checked by the person receiving it
Quote a percentage from the audit reportReport scores are triage inputs. They never appear in anything a prospect sees
Describe review screening or filteringEvery customer is asked and every customer goes to Google. There is no version of the offer that filters, and describing one misrepresents the service
Make a callNot from this seat. The Operator owns the written touch. The spoken one belongs to the Principal or to a dedicated Inside Sales Caller, who dials under their own name and the compliance standard
Change any account settingContacts, Conversations and the Prospecting tool only. No workflows, no fields, no templates
Act on the "Payment method is missing" bannerIt is a reselling prompt asking for a client's card on an account that has no client. It blocks nothing. Never enter a card to clear it
Send while the record still holds a business name where a person's name belongsThe agent writes the business name into that field by default. It is the most visible possible error

On the calling row. Until 2026-10-26 this read "calls are the Principal's; the scripts are written in their voice and cannot carry another name." The second half stopped being true when the scripts were re-voiced for whoever is holding the phone, so the row is now a seat boundary rather than a blanket prohibition: the Operator still never dials, and a caller who does is a different role with its own reading path, gate and rule sheet. The Operator/Principal split this SOP exists to protect is unchanged.


§5 When something does not fit​

Escalate rather than improvise. A checklist step that seems to need judgement is a defect in the checklist, not a decision to make. Both checklists are written so that two people reach the same answer; where that fails, the wording needs fixing and the Principal needs to know.

An escalation says four things, in this order:

  1. What you were doing, and which prospect.
  2. What you checked.
  3. What you think is happening.
  4. What you would do.
SituationChannelExpect
A step is ambiguous, a record looks wrong, a prospect does not fit any bucketSlackAn answer the same working day
A prospect repliedSlack, flaggedSame day. Do not wait for it to be picked up
Something is genuinely time-sensitiveWhatsAppUsing it for routine questions costs it its meaning

Two things are never resolved without the Principal: anything commercial, and anything where the honest finding and the available template disagree.

Verification​

Per prospect, before moving on:

  • Prospect Bucket is set. Never blank — parked and disqualified both have values
  • The record carries a person's name, a city, the finding, and a report link that opens without a login
  • Tags applied in order, with prospecting-outreach-active last
  • The email went out through the platform from the contact's Conversations tab, plain text, one link, no attachment
  • Follow-up tasks exist for days 3, 7, 10 and 12

At the end of the day:

  • Every prospect opened today has a bucket value, including the ones not sent
  • No prospect received more than one email
  • Every reply that arrived was handed over, and none was answered

Weekly, by the Principal: re-slot three prospects independently and compare. A mismatch is a checklist defect first and a training issue second.

Document History​

VersionDateChanges
1.32026-11-10The never-say link follows the call scripts' new §10 (v1.18)
1.22026-10-26§4's "make a call" row changes from a blanket prohibition to a seat boundary. Its stated reason was that the scripts were written in the Principal's voice and could not carry another name; the scripts were re-voiced on the same day, so the reason no longer held while the prohibition it justified still blocked a role the business was about to onboard. The Operator still never dials. What changed is that someone other than the Principal now can, as a distinct seat with its own compliance gate — amended deliberately, as the readiness plan §2.1 required, rather than operated around
1.12026-09-23New §1a, the open queue: workflow WF-3 now tags prospecting-audit-email-opened, and that queue is worked before the day's new prospects because an engaged prospect outranks a fresh one. Template 16 one business day after the tag, plus a call where a verified phone exists. Records that the tag over-counts — Apple Mail prefetch fires opens nobody made — so the operator must never tell a prospect they read the report, and that the report link's view count is one shared counter rather than per-prospect engagement. §2 gains a warning that prospecting-responded and sc-suppressed do not exist in the sub-account, so a do-not-call sets DND rather than relying on a tag the platform has never heard of
1.02026-09-10Initial version, written from the 2026-09-10 daily check-in. Defines the Principal and Prospecting Operator roles and the boundary between them, the daily loop over the two existing checklists, batch selection, reply handoff, volume, prohibitions, and escalation. Records one deliberate override of the meeting: prospects stay at New Lead through the cadence rather than moving to Discovery at validation, because stages carry buyer progress and attempt state belongs on tags